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.
Split Retry to Retry to Access, Retry After Partial Download and Retury when Data received. #1858
Comments
|
I think I do understand your suggestion, but I don't see any rationale. Why should we split the option in three? I'm all for making sure that retry always works (there were some reports of an error there), but as a user, I'd certainly be confused by three different retry options. |
|
If some data was received I do not want it to give up when the retry number is reached. |
|
Also would be helpful to find a way to overcome time out errors if you had finer control on what cases to re try on: [youtube] PW1ylyeX364: Downloading video webpage [download] Downloading video #70 of 142 [download] Downloading video #71 of 142 .... [download] 2.9% of 25.02MiB at 4.92KiB/s ETA 01:24:13ERROR: unable to downloa |
|
#4240 is specific to the SSLError part of this. While I agree they shouldn't be split out, possible exceptions should be treated specifically enough to retry after all transient errors. Because SSLError subclasses socket.error, they are being treated as socket errors (i.e. only connection resets are treated as recoverable), while there are many recoverable SSLError. |
The retry option can be split to 3.