You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After some amount of time, both the dev and release client, if left idle long enough (and maybe related to the laptop going to sleep and waking up) can no longer communicate correctly with the server, and spams the server with these errors:
Jul 26 22:38:49 server npm[4966]: [WebSocket] closed 4009
somewhere between 2-5 per second.
To Reproduce
Steps to reproduce the behavior:
use either dev.app.spacebar.com or app.spacebar.com and connect a server
wait long enough for the session to expire
the client will no longer be able to send messages nor refresh the session
you will see the error messages spam the server
Expected behavior
session either re-initializes, or if that is impossible, the client stops trying to connect to the server and informs the user to refresh the page or whatever is appropraite.
Console Logs
Jul 26 22:38:49 server npm[4966]: [WebSocket] closed 4009
System Information (please complete the following information):
OS: [e.g. Debian Linux, Arch Linux etc.]
Version (If not applicable skip): [e.g Ubuntu 22.04 LTS/Windows Server 2022]
Describe the bug
After some amount of time, both the dev and release client, if left idle long enough (and maybe related to the laptop going to sleep and waking up) can no longer communicate correctly with the server, and spams the server with these errors:
somewhere between 2-5 per second.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
session either re-initializes, or if that is impossible, the client stops trying to connect to the server and informs the user to refresh the page or whatever is appropraite.
Console Logs
System Information (please complete the following information):
Env and Software info
The text was updated successfully, but these errors were encountered: