Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Retry does not seem active on read timeout #15083
Comments
|
I'm facing the same issue. It's insanely annoying. |
Make sure you are using the latest version: run
youtube-dl --versionand ensure your version is 2017.12.23. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.Before submitting an issue make sure you have:
What is the purpose of your issue?
Report
I am currently on holiday in a place with debatable and variable internet quality: nominally 1024k (~120kB/s effective) with ~50ms ping best case
However the ping can randomly shoot up to the second range, and packet loss can reach 10% in these situations (when the connection doesn't go down entirely) with effective bandwidth being similarly affected.
A more typical scenario is ~80kB/s effective with lag spikes into the 300ms range (connection is currently as perfect as I usually see it and running ping for 150 packets yields min 45.604, avg 55.589, max 330.341, stdev 37.513)
As a result watching videos online is an impossibility and I rely on youtube-dl to get the videos offline and watch uninterrupted.
However the "retry" option does not seem to affect Read Timeout errors, which happen any time the ping shoots up a bit too high or the connection falls down entirely (even if it reconnects by the time the timeout actually triggers, the original read will never complete).
Verbose Log
These are two runs (back to back):
Mitigation
I currently have a small script just running ydl in a loop until it succeeds, but a working Retry option would definitely be superior.