Feature request: Retry request after socket-timeout #7732

Closed
opened 2026-02-21 04:06:10 -05:00 by deekerman · 3 comments
Owner

Originally created by @spookyahell on GitHub (May 13, 2016).

  • I've verified and I assure that I'm running youtube-dl 2016.05.10

Before submitting an issue make sure you have:

  • At least skimmed through README and most notably FAQ and BUGS sections
  • Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

  • Bug report (encountered problems with youtube-dl)
  • Site support request (request for adding support for a new site)
  • Feature request (request for a new functionality)
  • Question
  • Other

Description of your issue, suggested solution and other information

Issue is: I use a local proxy for requests that sometimes freezes and won't respond. Usually I have to execute a whole command again, even if it's already almost done. The option "--socket-timeout" only automatically quits the command, it doesn't retry the current request.

An option like "--socket-timeout-retry SECONDS" would be nice to have. It would need to do what socket-timout does and then continue where it left of.

Originally created by @spookyahell on GitHub (May 13, 2016). - [x] I've **verified** and **I assure** that I'm running youtube-dl **2016.05.10** ### Before submitting an _issue_ make sure you have: - [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections - [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones ### What is the purpose of your _issue_? - [ ] Bug report (encountered problems with youtube-dl) - [ ] Site support request (request for adding support for a new site) - [x] Feature request (request for a new functionality) - [ ] Question - [ ] Other --- ### Description of your _issue_, suggested solution and other information Issue is: I use a local proxy for requests that sometimes freezes and won't respond. Usually I have to execute a whole command again, even if it's already almost done. The option "--socket-timeout" only automatically quits the command, it doesn't retry the current request. An option like "--socket-timeout-retry SECONDS" would be nice to have. It would need to do what socket-timout does and then continue where it left of.
Author
Owner

@dstftw commented on GitHub (May 13, 2016):

Isn't --retries enough? There is no such thing as "command almost done". In general extraction process is extractor specific and particular extractor may want to have own retry strategy or do not have such.

@dstftw commented on GitHub (May 13, 2016): Isn't `--retries` enough? There is no such thing as "command almost done". In general extraction process is extractor specific and particular extractor may want to have own retry strategy or do not have such.
Author
Owner

@spookyahell commented on GitHub (May 13, 2016):

When does a retry trigger? Does ít trigger when nothing happens for a certain amount of time? I kind of have the feeling that the extractor won't retry what it needs to finish. I meant sometimes it's only few requests to end but a lot if you restart the whole extraction process. Almost done: Nearly ready to create and execute ffmpeg command.

@spookyahell commented on GitHub (May 13, 2016): When does a retry trigger? Does ít trigger when nothing happens for a certain amount of time? I kind of have the feeling that the extractor won't retry what it needs to finish. I meant sometimes it's only few requests to end but a lot if you restart the whole extraction process. Almost done: Nearly ready to create and execute ffmpeg command.
Author
Owner

@ssokolow commented on GitHub (May 22, 2017):

Is it possible that this is another manifestation of one of the "socket timeouts don't trigger retry" bugs described in issues #8625 and #4240?

@ssokolow commented on GitHub (May 22, 2017): Is it possible that this is another manifestation of one of the "socket timeouts don't trigger retry" bugs described in issues #8625 and #4240?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/youtube-dl-ytdl-org#7732
No description provided.