mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Scheduled alternative rate limits remain in effect when unscheduled #4201
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#4201
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mjb2010 on GitHub (Apr 20, 2016).
Go to Options > Speed and set the global and alternative rate limits as desired. Check 'Schedule the use of alternative rate limits', From: [some block of time which includes the present], When: Every day. Click Apply. Observe that the alternative rate limits are in effect (speedometer icon at bottom of screen has the needle pointing to the right, and limits are shown in square brackets.)
Now go back to the options, uncheck 'Schedule the use of alternative rate limits', and click Apply. Observe that the alternative rate limits are still in effect. This is unexpected; it should go back to full speed.
(This is on Windows 7, and has been an issue since I started using qBittorrent in mid-2015. It is still happening in 3.3.4.)
@thalieht commented on GitHub (Apr 20, 2016):
I confirm.
@ngosang commented on GitHub (Apr 20, 2016):
I think this is not a bug because qBittorrent doesn't know if you want the global or the alternative rate limit.
We should add a confirmation dialog when the scheduler is enabled and the user change the rate limit from the status bar (the scheduler is disabled without notice). I can do it in the WebUI. @qbittorrent/qbittorrent-frequent-contributors
@mjb2010 commented on GitHub (Apr 22, 2016):
Yeah, I understand re: qBittorrent not knowing which rate limit you want to be in effect when the scheduler is disabled. It is just counterintuitive to turn it on, then turn it off and have it not go back to the way it was.
I agree that the user should know that the scheduler is being disabled when they change the rate limit from the status bar, although that's a separate issue from what I was asking about. There may be a better way to deal with it as well.
For example, I don't think the scheduler should ever be fully disabled; rather, the switch on the status bar should just temporarily override the scheduler, and should indicate when it's doing so. So, if you toggle the switch to alternative mode when the scheduler normally would put qBittorrent in global mode, the status bar should indicate that the scheduler is being overridden. When the scheduled start time arrives, the override indicator will disappear and it will be like nothing unusual happened, i.e. the scheduler will be in effect and when the end time arrives, the toggle will go back to global. Similarly, if you set the switch to global mode during the time when the scheduler would normally be in alternative mode, the override light would be on until the scheduler's end time arrives, and it would just stay in global mode until the next scheduled start time for the alternative rate limits. And if you put the switch in whatever mode the scheduler would normally have set, everything should just be normal.
Anyway, it sounds like neither of these issues can be resolved within the current UI. Maybe this should be considered a feature request, then.
@ngosang commented on GitHub (Sep 16, 2018):
We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.