[FR]: Add an option to limit the speed of downloads to the "share_limits" variable about qbit_manage HOT 2 CLOSED

• QBm only operates on completed torrents so this is moot
• Share limits only apply to completed torrents

from qbit_manage.

I'm still using Qbittorrent 4.3.9 and I didn't realize qbit_manage had a lock to only work with "completed" torrent. I was thinking to try Qbittorrent 4.5.x as it has an option to run an external program when a torrent is added to limit public torrents. Is there any chance the share_limts behavior will ever be changed to works when a torrent is added?

It's all down to this line from what I could see:

changing it to
torrent_list = self.qbt.get_torrents({"status_filter": "completed"} and {"status_filter": "downloading"})
or
torrent_list = self.qbt.get_torrents({"status_filter": "completed"} and {"status_filter": "paused"} and {"status_filter": "downloading"})
or
torrent_list = self.qbt.get_torrents({"status_filter": "all"})
With the changes, Share_limits get set when a torrent is added (at least --run from bash command line, I don't have qbittorrent 4.5.x installed yet)

|============================= Updating Share Limits based on priority ==============================|
| Assigning torrents to share limit groups... |
|===================== Updating Share Limits for [Group default] [Priority 999] =====================|
| Torrent Name: Linux-Image-nogroup |
| Tracker: |
| Added Tag: ~share_limit_999.default |
| Share Limit: Max Ratio = 1.0, Max Seed Time = 60 min |
| Webhook attribute set to notifiarr but notifiarr attribute is not configured. |
|====================================================================================================|
| Finished Run |
| Total Torrents Tagged: 1 |
| Total Share Limits Updated: 1 |
| Run Time: 0:00:00

from qbit_manage.