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 thehesiod
Recipients gvanrossum, thehesiod, vstinner, yselivanov
Date 2015-11-10.07:16:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
asyncio.selector_events.BaseSelectorEventLoop._sock_connect_cb is a callback based on the selector for a socket. There are certain situations when the selector triggers twice calling this callback twice, resulting in an InvalidStateError when it sets the Future to None.  The way I triggered this was by having several parallel connections to the same host in a multiprocessing script. I suggest analyzing why this callback can be called twice and figuring out what the correct fix is.  I monkey patched it by adding a fut.done() check at the top.  If this information is not enough I can try to provide a sample script. Its currently reproducing in a fairly involved multiprocessing script.
Date User Action Args
2015-11-10 07:16:34thehesiodsetrecipients: + thehesiod, gvanrossum, vstinner, yselivanov
2015-11-10 07:16:34thehesiodsetmessageid: <>
2015-11-10 07:16:33thehesiodlinkissue25593 messages
2015-11-10 07:16:33thehesiodcreate