-
Notifications
You must be signed in to change notification settings - Fork 25
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
Websocket disconnect errors instead of handling gracefully #201
Comments
Hi @bryaan, What kind of behavior would expect to get when a client forcefully disconnects? It should be simple enough to explicitly catch and hide this error since it's so common |
Yes, that sounds like a good default. |
Any progress on this? really ugly to see these common messages in my error log. |
I've tried to fix this like so, but the error still bubbles up.
|
HTTP canceled request also has a big error. It would be nice to hide or simplify these in the log as well:
Note: working on a map app, so these are frequent when you pan/zoom and the map component decides to cancel a tile request. |
When my websocket client disconnects, the server throws an error:
The text was updated successfully, but these errors were encountered: