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 twisteroid ambassador
Recipients asvetlov, twisteroid ambassador, yselivanov
Date 2018-06-11.13:47:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528724850.44.0.592728768989.issue33833@psf.upfronthosting.co.za>
In-reply-to
Content
Sometimes when a socket transport under ProactorEventLoop is writing while the peer closes the connection, asyncio logs an AssertionError. 

Attached is a script that fairly reliably reproduces the behavior on my computer.

This is caused by _ProactorBasePipeTransport._force_close() being called between two invocations of _ProactorBaseWritePipeTransport._loop_writing(), where the latter call asserts self._write_fut has not changed after being set by the former call.
History
Date User Action Args
2018-06-11 13:47:30twisteroid ambassadorsetrecipients: + twisteroid ambassador, asvetlov, yselivanov
2018-06-11 13:47:30twisteroid ambassadorsetmessageid: <1528724850.44.0.592728768989.issue33833@psf.upfronthosting.co.za>
2018-06-11 13:47:30twisteroid ambassadorlinkissue33833 messages
2018-06-11 13:47:30twisteroid ambassadorcreate