Repository navigation
Add Force Start option for Automation #1798
Replies: 1 comment
Agent BriefCategory: enhancement Current behavior: Desired behavior: Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Feature scope is a maintainer call. Also decide whether Force Start is its own action or an option on Resume, and how it interacts with Pause in the same rule. Related: #732 (a closed request for per-tracker automatic force start). |
Uh oh!
There was an error while loading. Please reload this page.
I tried to put a troubleshooting ticket in for this but it went nowhere, but have more info so seems to be a feature change now.
I am running qBittorrent 5.1.4 against the latest qui, both in docker.
I setup as automation to resume torrents that had stopped due to their ratios as well as label them. They get labeled but do not resume.
While the qui code shows the json defintion for Resume in the automation.go show as resume, onitempty:
the bulk actions that call the go-bittorrent methods.go ResumeCtx uses the torrents/start method, which should work.
However, there are cases where resuming a torrent past its defined ratio will automatically stop it if it is not set to be forced. This can be seen by manually trying to select Start on a torrent in the qBitTorrent interface that is stopped from hitting its ratio, it will start briefly then stop again. The only way past this is to Force Start it which will resume it and keep it running.
I see that the go-bittorent methods.go has a SetForceStartCtx function, and it is being called as well from qui in the sync_manager.go executeBulkActionforInstance and that is called from the torrents.go BulkAction, so most of the ground work seems to be there. It just doesn't have support in the automations.
I am requesting that the ForceStart be added as an Automation option.
All reactions