The call to `_untrack_reader` is performed too soon, causing the protocol to forget about the reader before `connection_lost` can run and feed the EOF to the reader. See bpo-35065.
|
Thank you for the fix, it looks correct. |
|
@asvetlov: Please replace |
The call to
_untrack_readeris performed too soon, causing the protocol to forget about the reader beforeconnection_lostcan run and feed the EOF to the reader.This PR currently fixes the issue by removing the
_untrack_readercall and definition altogether.https://bugs.python.org/issue35065