-
Notifications
You must be signed in to change notification settings - Fork 4
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
Websocket Life #27
Comments
Probably discord requesting reconnect (opcode 7)? Documented as happening randomly, whenever discord feels like it. For reconnecting, the session ID and last received sequence ID need to be sent when reconnecting |
No, that has been handled. |
Just occurred again and here's the traceback.
|
You just gotta handle it like a new session. |
That is handled as well. Currently, dankcord yeets the old connection and opens a new one. |
Well apparently it doesn't? Why is the error saying the connection is closed then? |
It should raise the exception before, in the receive part (_events_listener). The fact that it waits for heartbeat is more troublesome |
Hmm, then idk. I don't have that much knowledge of the code. |
Websocket disconnects after a duration, could be 5 minutes, could be 4 hours- NOT caused by machine/host network.
no useful tracebacks, more information on this issue is required.
The text was updated successfully, but these errors were encountered: