[FEATURE] Allow http timeout values greater than 100 #31

Closed
opened 2025-10-09 16:56:57 -05:00 by giteasync · 2 comments
Owner

Originally created by @TrisMcC on GitHub.

What would you like to see implemented next?

The 100 seconds is not enough for an especially tempermental Transmission instance. Is there any technical reason why we can't put 300 seconds (or higher)? I am running into this trying to evaluate DownloadCleaner, no matter how many retries I do.

Originally created by @TrisMcC on GitHub. ### What would you like to see implemented next? The 100 seconds is not enough for an especially tempermental Transmission instance. Is there any technical reason why we can't put 300 seconds (or higher)? I am running into this trying to evaluate DownloadCleaner, no matter how many retries I do.
giteasync added the enhancement label 2025-10-09 16:56:57 -05:00
Author
Owner

@Flaminel commented on GitHub:

No specific technical reason other than it slows everything down. A lot of calls are made during a job run and 100s for each of those would mean a very long time to run a job. Is there a good reason why Transmission can't be reached within 100s or less?

@Flaminel commented on GitHub: No specific technical reason other than it slows everything down. A lot of calls are made during a job run and 100s for each of those would mean a very long time to run a job. Is there a good reason why Transmission can't be reached within 100s or less?
Author
Owner

@Flaminel commented on GitHub:

@TrisMcC ?

@Flaminel commented on GitHub: @TrisMcC ?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Cleanuparr#31