-
Notifications
You must be signed in to change notification settings - Fork 180
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
Flood of error messages when connection closes #157
Comments
Indeed, it's on the checklist for releasing Currently, when an error is received it's just logged and not propagated to the user because in most cases it's not possible to determine which request failed because it's mapped per Thus, I think the proper way is just to terminate the connection when an error is received on the connection (with the error to user) Thoughts? |
In the case of an unrecoverable error like a closed connection I think it should definitely be propagated to the user. I am not sure what should happen when an error occurs that is only effecting one request, but just ignoring it probably isn't a good idea, as I imagine it could lead to unexpected program freezes |
+1 |
Fixed by #180, the error message could be improved though. I will open another issue for that. |
When the connection is closed (because e.g. the server shuts down), there is an unending flood of these messages:
It would be nice if this error was handled a bit more graciously.
The text was updated successfully, but these errors were encountered: