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 basnijholt
Recipients aeros, asvetlov, basnijholt, lukasz.langa, paul.moore, steve.dower, tim.golden, yselivanov, zach.ware
Date 2020-07-16.15:13:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1594912382.83.0.461179096687.issue38856@roundup.psfhosted.org>
In-reply-to
Content
I have noticed the following on Linux too:
```
Traceback (most recent call last):
  File "/config/custom_components/kef_custom/aiokef.py", line 327, in _disconnect
    await self._writer.wait_closed()
  File "/usr/local/lib/python3.7/asyncio/streams.py", line 323, in wait_closed
    await self._protocol._closed
  File "/config/custom_components/kef_custom/aiokef.py", line 299, in _send_message
    await self._writer.drain()
  File "/usr/local/lib/python3.7/asyncio/streams.py", line 339, in drain
    raise exc
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 814, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
ConnectionResetError: [Errno 104] Connection reset by peer
```
after which every invocation of `await asyncio.open_connection` fails with `ConnectionRefusedError` until I restart the entire Python process.

IIUC, just ignoring the exception will not be enough.

This issue is about the `ProactorEventLoop` for Windows specifically, however, my process uses the default event loop on Linux.
History
Date User Action Args
2020-07-16 15:13:02basnijholtsetrecipients: + basnijholt, paul.moore, tim.golden, asvetlov, lukasz.langa, zach.ware, yselivanov, steve.dower, aeros
2020-07-16 15:13:02basnijholtsetmessageid: <1594912382.83.0.461179096687.issue38856@roundup.psfhosted.org>
2020-07-16 15:13:02basnijholtlinkissue38856 messages
2020-07-16 15:13:02basnijholtcreate