[Bug]: min_seeding_time and max_seeding_time are calculating incorrectly about qbit_manage HOT 3 CLOSED

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.

from qbit_manage.

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.

from qbit_manage.

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

from qbit_manage.