Closed DetermineAbsurd closed 5 months ago
I'm getting the same issue. If I use -1 for max_ratio or max_seeding_time when min_seeding_time is set to any value, I get verification error that value cannot be lower than min_seeding_time.
If I try remove max_ratio and max_seeding_time so it reverts to default values I still get the verification error as script still expects values for those fields. In effect the new change is making max_ratio and max_seeding_time mandatory fields if min_seeding_time is set.
To work around the verification, I've had to set arbritury high values to max_ratio (999) and max_seeding_time (525600) for any groups where they weren't set or used -1.
Additional checks were added in place to avoid invalid configurations. The min_seeding_time was only being used whenever max_ratio is set.
In the case where max_ratio isn't set or set to infinite, setting min_seeding_time isn't doing anything. In order to fix this error you would want to change your min_seeding_time to max_seeding_time and therefore the share limits being applied will only delete the torrents once that particular group meets the max_seeding_time.
Ah ok. Yeah that makes sense now. I've removed min_seeding_time where I don't use max_ratio and script now works as expected. Thanks
Describe the Bug
qbit_manage reports that my max_seeding_time is lower than my min_seeding_time, but the max is set to infinite, so I don't know why it's reporting this.
config has replaced references to the trackers with numbered generic names, but the tags and tracker keywords in the actual config do not contain odd characters. Just alphanumeric, "." and "-" in the tracker domains only.
Config
Logs
https://gist.github.com/DetermineAbsurd/4a430a033a64b4d4c505208135ee52d8
Screenshots
No response
Installation
Unraid
Version Number
4.1.1
What branch are you on?
master