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 Eamonn Nugent
Recipients Eamonn Nugent, ned.deily, racitup, ronaldoussoren
Date 2018-10-15.01:34:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1539567255.37.0.788709270274.issue33450@psf.upfronthosting.co.za>
In-reply-to
Content
Fwiw, this also happens in asyncio. Theoretically, I *think* you could wrap a try-except as a monkey patch.

My stack trace is:

Fatal write error on socket transport
protocol: <RequestHandler connected>
transport: <_SelectorSocketTransport fd=163 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/selector_events.py", line 761, in write
    n = self._sock.send(data)
OSError: [Errno 41] Protocol wrong type for socket

I can try to PR the fix mentioned by @ronaldoussoren, though it might take me a bit. I'm happy to do whatever to get this fixed, though, since it's flooding my terminal with several hundred errors every time it happens...
History
Date User Action Args
2018-10-15 01:34:15Eamonn Nugentsetrecipients: + Eamonn Nugent, ronaldoussoren, ned.deily, racitup
2018-10-15 01:34:15Eamonn Nugentsetmessageid: <1539567255.37.0.788709270274.issue33450@psf.upfronthosting.co.za>
2018-10-15 01:34:15Eamonn Nugentlinkissue33450 messages
2018-10-15 01:34:14Eamonn Nugentcreate