-
-
Notifications
You must be signed in to change notification settings - Fork 686
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
Handle ConnectionClosed exceptions #16
Comments
Hi Bryant, Have you managed to fix the ConncetionClosed exception at all? |
yes, but it depends on a fix in the websockets library. They just fixed it this week and the maintainer said a new release would be on pypi soon. Once thats done, I have changes in a branch I can merge in to fix it. |
i merged in a partial solution - when the exceptions are received, it will attempt to reconnect. The other issue the rest of my changes address (unmerged) are when the connection goes dead but there is no disconnect. They will kill the connection and reconnect. |
…trade-spec-change Hotfix/gateio trade spec change
Websocket connections can be closed for a variety of reasons. These should be handled and the connection re-established if possible. Some tracebacks from my server:
The text was updated successfully, but these errors were encountered: