-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 all concurrent.futures._base.TimeoutError and throw a aiohttp.errors.TimeoutError instead. #1207
Comments
Nothing to fix: |
So how to solve the issue? |
You should catch |
I can confirm on python 3.6 and aiohttp latest, the error doesn't get caught with |
@EFF I don't follow, what error is not caught? |
@asvetlov You're totally right I wasn't on latest. Thanks for the quick answer, sorry for the inconvenience. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs. |
Long story short
This is better to explain with the full Traceback:
Expected behaviour
To Throw a
aiohttp.errors.TimeoutError
instead of aconcurrent.futures._base.TimeoutError
onFile "aiohttp\client.py", line 198, in _request conn = yield from self._connector.connect(req)
Actual behaviour
Line 198 thows a
concurrent.futures._base.TimeoutError
making it hard to handle if you do not want to importconcurrent
just to handle the exceptions from it.Steps to reproduce
Something that used to exist but does not anymore so when it tries to connect for x time it throws this.
Your environment
Windows 7 Ultimate x64
Python 3.5.2 (embedded) (I Insalled aiohttp (latest 1.0.2) with a installed version but use the embedded one because I can 😛)
The text was updated successfully, but these errors were encountered: