Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

send: resource vanished (Broken pipe) #70

Closed
Eilie opened this issue Jun 1, 2014 · 3 comments
Closed

send: resource vanished (Broken pipe) #70

Eilie opened this issue Jun 1, 2014 · 3 comments

Comments

@Eilie
Copy link

Eilie commented Jun 1, 2014

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.

@jaspervdj
Copy link
Owner

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).

@Eilie
Copy link
Author

Eilie commented Jun 10, 2014

Okay, thank you for response!

@Eilie Eilie closed this as completed Jun 10, 2014
@jberryman
Copy link

Related to #120

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants