websocket: Add warning if client connection isn't closed cleanly #3264
+64
−29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bdarnell
force-pushed
the
websocket-client-warning
branch
3 times, most recently
from
413281e
to
ad4ad5e
Compare
This gives a warning that is not dependent on GC for the issue in tornadoweb#3257. This new warning covers all websocket client connections, while the previous GC-dependent warning only affected those with ping_interval set. This unfortunately introduces an effective requirement to close all websocket clients explicitly for those who are strict about warnings.
bdarnell
force-pushed
the
websocket-client-warning
branch
from
ad4ad5e
to
321a9cd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This gives a warning that is not dependent on GC for the issue in #3257.