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
I'll probably handle this with a keepalive boolean upon initiating the connection, and it will send the keepalive every 60s.
I would still like some sort of coherent message if this happens, regardless. As it stands now, there is no message and if you print messages sent, it will appear that it is indeed attempting to send the messages, but never times out or tells you that the socket connection is not open.
The text was updated successfully, but these errors were encountered:
I'll probably handle this with a keepalive boolean upon initiating the connection, and it will send the keepalive every 60s.
I would still like some sort of coherent message if this happens, regardless. As it stands now, there is no message and if you print messages sent, it will appear that it is indeed attempting to send the messages, but never times out or tells you that the socket connection is not open.
The text was updated successfully, but these errors were encountered: