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
but after waiting for not that long, the thread will panic at the unwrap on let message = message.unwrap()
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Protocol("Connection reset without closing handshake")'
i'd expect tokio-tungstenite to handle this and attempt a reconnect. maybe that's a flawed expectation - if so, do y'all have recommendations on how to handle that protocol message?
The text was updated successfully, but these errors were encountered:
We currently do not attempt to reconnect because we don't know what the disconnect means in the application. Sometimes disconnects are expected.
If there is no activity on TCP, the operating system will disconnect you sooner or later. If you don't have any better activity, send WebSocket ping messages periodically. This prevents disconnecting. If you do ping and still experience disconnects, this means network malfunction and is to be handled accordingly.
i would expect the following code snippet to work fine:
but after waiting for not that long, the thread will panic at the unwrap on
let message = message.unwrap()
i'd expect tokio-tungstenite to handle this and attempt a reconnect. maybe that's a flawed expectation - if so, do y'all have recommendations on how to handle that protocol message?
The text was updated successfully, but these errors were encountered: