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.
Some Errors Are Not Caught And Retried? #24188
Comments
|
OK, incomplete tag huh? In my defense, I didn't provide verbose log because I cannot reliably corrupt my network connection. It's a networking error, it doesn't happen all the time and when it does I can't foresee it to supply If you really need logs, here they are.
I ran the same download (URL) 3 times to get the error to occur. Didn't know if this changes anything, but like I said there's no way to reliably generate this error. |
Checklist
Verbose log
See #23782.
Description
This is a related issue brought by #23782. I meant to comment on the original but decided to open a new one.
Just saw this error today and it’s starting to stick. (Maybe I downloaded too much and YouTube now hates me?) Restarting
youtube-dlwith the same URL works but it’s tedious procedure and this breaks my workflow a bit.My issue isn’t exactly with this error code. Network condition shifts and weird error happens. I’m used to that.
The problem is I ran
youtube-dlwith-R infinite --fragment-retries infinitewhich should make YTDL swallow any errors and auto retry until the download is completed, given that I’m not offline. Even if I am offline, the command should hang (run indefinitely) because that’s what infinite retry means. Telling me there’s been an error after I supplied infinite retries as input isn’t what I expected.