This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients gvanrossum, kevinconway, vstinner, yselivanov
Date 2016-09-15.07:53:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> On the asyncio side, with debug turned on, we see nothing.

Hum, I'm concerned by this issue. I would expect that in debug log, a log would be emitted. Maybe something like "accept queue saturated! we may probably loose incoming connections".

Does someone see a way to log a message in such case? Maybe only in debug mode?

I spent time to make sure that asyncio logs events related to network to try to understand what is happening. It's hard to decide which events should be logged, because logging everything is likely to flood logs.

For example, _SelectorSocketTransport._read_ready() logs an event for

* "EOF" (when recv() returns an empty string).
* transport pauses reading
* transport resumes reading
Date User Action Args
2016-09-15 07:53:13vstinnersetrecipients: + vstinner, gvanrossum, yselivanov, kevinconway
2016-09-15 07:53:13vstinnersetmessageid: <>
2016-09-15 07:53:13vstinnerlinkissue27906 messages
2016-09-15 07:53:13vstinnercreate