-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Ready is not being re-dispatched after disconnects #207
Comments
I might have a fix for this, will need testing |
I'm not sure it's the same bug, but when I login from my VPS, I am quickly disconnected: Probably irrelevant logs: May 15 05:09:53 vps-9bd6f395 steam[2673158]: INFO:slidge.core.gateway.base:Login success for <User [email protected]> Relevant logs May 15 05:12:22 vps-9bd6f395 steam[2673158]: INFO:steam.state:Websocket closed, cannot reconnect. Trying to send a steam chat message May 15 05:12:41 vps-9bd6f395 steam[2673158]: Traceback (most recent call last): Further relevant logs: May 15 05:12:53 vps-9bd6f395 steam[2673158]: INFO:steam.gateway:Attempting to create a websocket connection to ext1-par1.steamserver.net:27034 (load: 9.016203) Let me know if I should open another issue for this @Gobot1234 |
Some more logs, maybe useful? The bad thing about this is that no event is raised, so I have no way (or didn't find out how?) to know that the client died until I actually try to send something. When the connection died: May 17 23:10:49 vps-9bd6f395 steam[2735737]: DEBUG:steam.gateway:Socket has received CMsgClientFriendsGroupsList(bremoval=False, bincremental=False) from the websocket. When I noticed it by trying to send a message: May 18 06:40:35 vps-9bd6f395 steam[2735737]: Traceback (most recent call last): |
Summary
After (forcefully) disconnecting from the WS we fail to dispatch the ready event
Reproduction Steps
Disconnect and reconnect to a CM, wait 60s and then the bot will crash after timing out fetching the friends list causing ready to not be redispatched
Expected Results
No crashing to occur
Actual Results
It crashes in SteamWebsocket.fetch_users after timing out waiting for a refresh.
System Information
v1.0.0 on 82e7482
Checklist
The text was updated successfully, but these errors were encountered: