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
After closing browser which was connected to web-sockets I'm getting
"executable-name: send: resource vanished (Broken pipe)" message in console. It doesn't actually crashes application and I can continue to use web-sockets but I feel like I'm doing something wrong or there is a bug in library because of that message.
It means that the browser closed the connection without sending a proper "close" message. It can't do any harm. I'll do a run to clean up error messages soon...
Note that this is an IOException and not a WS.ConnectionException (although I should rethrow the IOException as WS.ConnectionException).
@jaspervdj I'm noticing resource vanished (Connection reset by peer) from receiveData; I wonder if this issue should be reopened to address re-raising resource vanished exceptions?
Or put another way, if I wrap receiveData in a handler that reraises those as ConnectionClosed, would that be correct, or might I be hiding some bugs that way?
Hello,
After closing browser which was connected to web-sockets I'm getting
"executable-name: send: resource vanished (Broken pipe)" message in console. It doesn't actually crashes application and I can continue to use web-sockets but I feel like I'm doing something wrong or there is a bug in library because of that message.
Tried to catch exception:
WS.runServer "0.0.0.0" 9160 $ (flip catch ((_ :: WS.ConnectionException) -> return ()) . websockets)
But that haven't changed a thing.
The text was updated successfully, but these errors were encountered: