Skip to content

Fix bug when using client without timeouts under 3.6 - #383

Merged
sethmlarson merged 1 commit into
masterfrom
fix/sync-client-no-timeout
Sep 25, 2019
Merged

sethmlarson merged 1 commit into
masterfrom
fix/sync-client-no-timeout

Conversation

@florimondmanca

Copy link
Copy Markdown
Contributor

Fixes #382 cc @StephenBrown2

@florimondmanca
florimondmanca force-pushed the fix/sync-client-no-timeout branch from 0443e85 to c6c7058 Compare September 25, 2019 07:37

@sethmlarson sethmlarson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@sethmlarson
sethmlarson merged commit cadb9a4 into master Sep 25, 2019
@sethmlarson
sethmlarson deleted the fix/sync-client-no-timeout branch September 25, 2019 11:31
dmoerner added a commit to dmoerner/pytorrent that referenced this pull request Mar 1, 2025
Legacy asyncio timeout code was causing read races. The exact cause
of these races is still under investigation, but they have been
significantly reduced with the removal of this code. They are suspected
to be connected to a race between a reader and the timeout cancellation
of that reader. See encode/httpx#383, for example.

Also handle other named exceptions.

This code is now able to successfully download a complete torrent file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Python 3.6 RuntimeError: read() called while another coroutine is already waiting for incoming data

2 participants