stackexchange-notifications
stackexchange-notifications copied to clipboard
Rob--W
Websockets eventually stop working
I'm experiencing a recurring issue where, after a missed heartbeat restart, the endpoint simply won't report any events despite the subscription in the first packet.
Heartbeats for the connection continue as normal, but no topbar events ever arrive. As such, the extension does not suspect anything.
This may not be a problem on the extension's side, but requires research.
I see a similar issue in Firefox. Sometimes, when I regain my network connection after loosing it (e.g. due to sleeping or just a bad connection), the WebSocket seems live, but I don't receive any events.
Perhaps it might be useful to periodically ping the WebSocket to see if the other end responds. Patches are welcome :)
Like I said, heartbeat messages continue to be exchanged.. Did you mean re-sending the subscription message?
By the way, why is -topbar used instead of -inbox?
Like I said, heartbeat messages continue to be exchanged.. Did you mean re-sending the subscription message?
I mean in case the server is gone, and the browser somehow fails to detect that the socket is gone.
By the way, why is -topbar used instead of -inbox?
The protocol changed at some point, and then I wrote 926542f1ca5a80d43cbb8d1532dcb00cf4140c7e, which resolved the issue, and is still working to this date.