-
-
Notifications
You must be signed in to change notification settings - Fork 694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix ConnectionClosedError raised from websockets library #856
Closed
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
Hi @euri10 sorry! I just saw this (I didn't get the notification). I installed your branch but unfortunately I am getting the same traceback as before:
Thank you and let me know if I can provide any more info! |
ok I'm going to close this if this doesnt fix it, I'm afraid I'm out of ideas as to what's happening |
OK no problem, thank you for your help :) |
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.
Fixes #757
This looks right to me but I'm not a ws expert by any means, previous behaviour was calling the parent connection_lost even if the transport is not in a closing state, which I added, seems like it's ok
This said, given #760 , if some affected users could gently test this PR if it has any unwanted side-effects that would be cool, /poke https://github.com/stefanw and https://github.com/oTree-org