-
-
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
Stderr spammed with ssl-related error messages #3675
Comments
GitMate.io thinks the contributor most likely able to help you is @asvetlov. Possibly related issues are #3242 (Error), #2822 (Unexpected SSL error (CERTIFICATE_VERIFY_FAILED)), #3393 (Fatal error on SSL transport), #3292 (Can't suppress all SSL verification errors), and #950 (WebSocket bad logic/error message). |
Are you sure that it's aiohttp and not asyncio dumping such logs? |
Oh, I'm not. Judging by the tracebacks it's likely the case, sorry for the noise then. |
Well, just check that first and maybe try setting up the logging to better identify the log sources. I think @asvetlov fixed something like this a while back in CPython so maybe also try Python 3.8 dev/alpha release. |
This is an issue with asyncio rather than aiohttp. |
Not the same but tightly coupled with #3535 |
This should now be fixed with python/cpython#13548 in Python 3.8.0 (and with python/cpython#13594 in Python 3.7.4). See https://bugs.python.org/issue37035. |
I'll confirm it - still waiting for 3.8.0 to appear in FreeBSD ports. |
Confirmed - with python 3.8 the problem is gone. |
Long story short
On SSL errors in connection, aiohttp issues messages to stderr. This doesn't seem to be correct behavior as these messages clobber actual application output, there's nothing useful can be done with them, and we have exceptions to actually handle the errors.
Expected behaviour
No messages from aiohttp on stderr.
Actual behaviour
A lot of messages even from a single request (output from the example program listed below):
Steps to reproduce
Despite SSL exception is intercepted, stderr is still polluted by a lot of errors as listed above.
Your environment
aiohttp 3.5.4 (client), FreeBSD 12.0 amd64, python 3.7, no proxy server
The text was updated successfully, but these errors were encountered: