fix reason not being set after local close #159
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During a local-initiated close handshake, the following incorrect behavior was observed:
closed
attribute would beNone
send_message()
would be silently ignored (wsproto < 0.2.0) or leak aLocalProtocolException
(wsproto >= 0.2.0)Upon local-initiated close,
closed
will now have the reason, andsend_message()
will raiseConnectionClosed
.Fixes #158.