-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Handle ConnectionResetError #3648
Comments
GitMate.io thinks the contributor most likely able to help you is @asvetlov. Possibly related issues are #720 (My server cant handle Exception.), #255 (Handling WebSocket disconnects), #850 (How to handle ClientResponseError/ServerDisconnectedError properly), #962 (Handling very long connection timeouts), and #2489 (drop handle.cancel). |
have same problem with python-socketio library
|
Same here (python 3.7.3, aiohttp 3.5.4). I am unable to catch this exception in my code, as the traceback is 100% in aiohttp side. This happens very rarely, and I'm sure is no real problem, but it causes Sentry issues, so is kind of annoying:
|
@gjcarneiro hi, i fixed that with patching streamwriter
and patch code
|
That may not be the 100% correct fix for this: I am worried that |
@gjcarneiro in my case, ConnectionResetError happens very often when client moves through the city and loses connection then just reconnect |
(cherry picked from commit 7846174) Co-authored-by: Gustavo J. A. M. Carneiro <[email protected]>
Would be nice to get a new aiohttp release to fix this bug. |
Long story short
There was introduced
ConnectionResetError
within #2989. What is the preferable way to handle this exception on the server side?Expected behaviour
No exceptions or all exceptions are catched and handled.
Actual behaviour
Steps to reproduce
Close client connection while there is running coroutine on the server side.
Your environment
Server: aiohttp==3.5.4
The text was updated successfully, but these errors were encountered: