New submission from Sebastien Bourdeauducq:
https://github.com/python/asyncio/issues/319
On Windows, asyncio servers sometimes print such log messages when clients
disconnect:
```
ERROR:master:asyncio:Fatal write error on pipe transport
protocol: <asyncio.streams.StreamReaderProtocol object at 0x0000000003F63FD0>
transport: <_ProactorSocketTransport fd=756>
Traceback (most recent call last):
File "C:\Users\User\Miniconda3\lib\asyncio\proactor_events.py", line 283, in
_loop_writing
self._write_fut = self._loop._proactor.send(self._sock, data)
File "C:\Users\User\Miniconda3\lib\asyncio\windows_events.py", line 450, in
send
ov.WSASend(conn.fileno(), buf, flags)
ConnectionAbortedError: [WinError 10053] An established connection was aborted
by the software on your host machine.
```
I guess that this line:
https://github.com/python/asyncio/blob/39c135baf73762830148236da622787052efba19/asyncio/proactor_events.py#L291
should be changed to also catch ``ConnectionAbortedError``, as this exception
also happens when connections are closed on Windows, in addition to
``ConnectionResetError``.
----------
components: asyncio
messages: 261321
nosy: gvanrossum, haypo, sebastien.bourdeauducq, yselivanov
priority: normal
severity: normal
status: open
title: spurious ConnectionAbortedError logged on Windows
versions: Python 3.5
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue26509>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
