STINNER Victor added the comment:
> 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
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
Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list