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
Client hides exceptions that occur further in the pipeline #15
Comments
|
The reason is that |
|
Found this issue from a search on stackoverflow -- I'm trying to do something dead easy. Just connect to a websocket and print out whatever comes back. If the server goes down, it just hangs forever. This Mojo code says "closed" and exits immediately if the server goes down: |
|
Well, that's quite a serious design issue indeed, but it hasn't been decided yet how can we patch it without breaking backward compatibility. Perhaps @jnthn thought on some directions where we can move to? |
|
There are at least two different issues here: Started an investigation... |
|
I am splitting the issue... Client exception will be here, zombie server will be in another place. |
This deals with the issue reported in #15.
|
Original issue is tested with b0a142e#diff-682f00620c71b3e986ab48ab169399cbR125 now. |
See https://stackoverflow.com/questions/51405074/crowebsocketclient-doesnt-work/51408569#51408569
I am not sure immediately where we can fix that, but this has to be fixed.
The text was updated successfully, but these errors were encountered: