[issue34506] Traceback logged when SSL handshake fails

2019-06-17 Thread Andrew Svetlov


Change by Andrew Svetlov :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Don't log OSError exceptions in asyncio transports

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue34506] Traceback logged when SSL handshake fails

2019-06-17 Thread Aymeric Augustin


Aymeric Augustin  added the comment:

Yes, that seems reasonable.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue34506] Traceback logged when SSL handshake fails

2019-06-17 Thread Andrew Svetlov


Andrew Svetlov  added the comment:

I believe the issue is a duplicate for #37035 at least regarding traceback 
logging.

It can be closed, OSError exceptions are not logged anymore.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue34506] Traceback logged when SSL handshake fails

2019-06-16 Thread Ned Deily


Change by Ned Deily :


--
components: +asyncio
nosy: +asvetlov, yselivanov

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue34506] Traceback logged when SSL handshake fails

2019-06-16 Thread Aymeric Augustin


Aymeric Augustin  added the comment:

The same issue was reported in the bug tracker for websockets: 
https://github.com/aaugustin/websockets/issues/614

--
nosy: +aymeric.augustin

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue34506] Traceback logged when SSL handshake fails

2019-03-22 Thread lilydjwg


Change by lilydjwg :


--
nosy: +lilydjwg

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue34506] Traceback logged when SSL handshake fails

2019-03-11 Thread Harmon


Change by Harmon :


--
nosy: +Harmon758

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue34506] Traceback logged when SSL handshake fails

2019-02-14 Thread cdods


cdods  added the comment:

Any update on this one? Still happening on 3.7.1

--
assignee:  -> christian.heimes
components: +SSL
nosy: +cdods, christian.heimes
type:  -> behavior
versions: +Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue34506] Traceback logged when SSL handshake fails

2018-08-26 Thread Hrvoje Nikšić

New submission from Hrvoje Nikšić :

When an SSL handshake fails in asyncio, an exception traceback is logged to 
standard error even if the application code catches the exception. This logging 
cannot be suppressed, except by providing a custom exception handler for the 
whole event loop. The question was raised on StackOverflow in 
https://stackoverflow.com/q/52012488/1600898

To reproduce the issue, run the attached minimal example (taken from the SO 
question). Expected behavior is for "Error handled" to be printed. Actual 
behavior is that, in addition to that line, two tracebacks are printed.

It looks like a bug that _fatal_error both logs the exception and calls 
connection_lost on the protocol (through transport._force_close()). If the idea 
is for the exception not to get swallowed by protocols that don't implement a 
sensible connection_lost (e.g. because they've just inherited from 
BaseProtocol, like the echo server examples), then maybe a protocol that 
propagates the exception in connection_lost should be able to opt out of the 
additional logging. That way the stream protocols would avoid spurious output 
for the suppressed exception by default, and the same opt-out mechanism would 
be available to user-written protocols.

--
files: sslerr.py
messages: 324113
nosy: hniksic
priority: normal
severity: normal
status: open
title: Traceback logged when SSL handshake fails
Added file: https://bugs.python.org/file47763/sslerr.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com