-
Notifications
You must be signed in to change notification settings - Fork 501
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
[Bug] One more websocket issue #426
Comments
Two bugs here.
Do you have any more logs for (1)? I'd be interested in the surrounding context - was this after a disconnect, or after a logoff, or did Steam terminate the connection....? |
Sadly I don't have anything more useful, this is entire log from what happened until I manually restarted my app:
It looks like it happened just by itself sometime during normal I'll try to reproduce this with debug log being turned on, although this is the first time I stumbled upon that, so I have no clue if I'll be able to reproduce it anytime soon. |
I double-checked and yeah there are no prior disconnects, connection failures or anything. This happened in the middle of all-fine scenario. Bot reconnecting was done by my refreshing session code after it couldn't use now-broken |
What might be interesting clue is that broken pipe error seems to happen each 30 seconds, I noticed that in the log just now. |
What happened before that in the log? Anything unusual? |
Nothing, everything was working smoothly. I have my heartbeat function that checks if Steam is operative by requesting profile info of its own account if there was no any sort of packet communication in last 60 seconds. Everything worked fine until array exception. Edit: I'm actively using my bot in debugging mode with only websocket CMs since yesterday but I'm not able to reproduce this issue. I'm not sure if it pops up anytime soon, I'd not count on that. |
Got another one but not from my own reproduction but from one of the ASF users. Maybe it can help.
In this one broken pipe seemed to happen on its own, without array exception. Once again bot is working perfectly fine after reconnect, but old websocket connection is throwing unobserved exceptions all the time. Attaching full ASF log from this incident, but trust me you don't want to go through it. Sadly still no debug log. I still believe this is just some networking hiccup that is not handled yet in the code. |
One more to the collection:
This time full log is a bit more readable - https://gist.githubusercontent.com/GUiHKX/baffe602ef531862b553a94c96be7a91/raw/12336f9bb7efafbe42ff618215d21758211ae8ef/log.txt |
UTC-3 or UTC-4 Summer Time? It is maintenance time, if it helps. |
Could be maintenance, but that is not the only factor that is causing those issues. It might be just more likely to happen when Steam servers are going down (makes sense, connections are closed forcibly). |
The only way I can see that we got the byte array that's not big enough for a message header is if:
I can see (2) happening if somehow we got a text websocket message. I've added handling for the |
I see, thank you for taking a look into this. I'll do my best to test websockets on bigger scale in my ASF, so we can verify if there is nothing else wrong happening. I'm positive that we nailed one of the last websocket issues 👍. |
After first issue I'm getting broken pipes all the time. I'm not 100% sure what is the reason for this particular exception, but it should probably be handled in SK2 internals, thanks!
The text was updated successfully, but these errors were encountered: