[issue21447] Intermittent asyncio.open_connection / futures.InvalidStateError
STINNER Victor
report at bugs.python.org
Mon Jun 30 16:09:02 CEST 2014
STINNER Victor added the comment:
This issue contains two sub-issues:
- race condition in_write_to_self() => already fixed
- race condition with scheduled call to future.set_result(), InvalidStateError => I just opened the issue #21886 to discuss it
@Ryder: If you are able to reproduce the second issue (InvalidStateError), please use set the environment variable PYTHONASYNCIODEBUG=1 to see the traceback where the call to set_result() was scheduled. It requires the latest development version of Tulip, Python 3.4 or Python 3.5 to get the traceback.
I close this issue because I prefer to discuss the InvalidStateError in the issue #21886.
Thanks for the report Ryder. Thanks for the fix for the race condition in _write_to_self() Guido.
----------
resolution: -> fixed
status: open -> closed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21447>
_______________________________________
More information about the Python-bugs-list
mailing list