[issue39700] asyncio.selector_events._SelectorTransport: Add logging when sock.getpeername() fails

David added the comment: Hi asvetlov, Thank you for your reply. I'm currently trying to debug a network issue, but I cannot determine the root cause of it because of lack of logs. It would be extremely helpful for my debugging if we could log the error that was raised by getpeername. I

[issue39700] asyncio.selector_events._SelectorTransport: Add logging when sock.getpeername() fails

Andrew Svetlov added the comment: I'm not sure. Logging can pollute the logger and make it almost useless. Most of mentioned errno codes are programming errors, a few may happen due network issues. Would you share what reasons did you observe? --

[issue39700] asyncio.selector_events._SelectorTransport: Add logging when sock.getpeername() fails

Change by David : -- keywords: +patch Added file: https://bugs.python.org/file48900/log-peername-and-sockname-errors.patch ___ Python tracker ___

[issue39700] asyncio.selector_events._SelectorTransport: Add logging when sock.getpeername() fails

New submission from David : `sock.getpeername` can fail for multiple reasons (see https://pubs.opengroup.org/onlinepubs/7908799/xns/getpeername.html) but in `asyncio.selector_events._SelectorTransport` it's try/excepted without any logging of the error: ``` if 'peername' not in