-
-
Notifications
You must be signed in to change notification settings - Fork 583
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
Fail to reconnect #561
Comments
My bad, the error (and quick fix) is actually in the python-engineio package. |
@aprilmay Yes, that is correct. Would you like to craft the fix yourself? |
Sure. A simple
I'm not familiar with github PRs, but i can learn if you want one. |
Thanks!
Only if you want to. I can apply the change myself if you are not interested or don't have time. |
Sorry for late reply. It would be nice and more simple if you could apply the patch, then. |
Done |
Thanks! |
Some exceptions are not caught on reconnect, and the client enters a "dead" state (note that i use asyncio and websocket transport, i'm not sure about other setup).
In my case, it's usually an error with DNS resolution, which raises a aiohttp.client_exceptions.ClientConnectionError.
A quick workaround is to add the relevant exception type in the try/except block of the _connect_websocket method in the asyncio_client.py file (around line 308).
The text was updated successfully, but these errors were encountered: