mirror of
https://github.com/Carve/qbittorrent-webui-cjratliff.com.git
synced 2025-12-05 17:32:36 -05:00
[GH-33] Availability shows seeding rate limit value #47
Labels
No labels
UX
bug
can not replicate
documentation
duplicate
enhancement
fixed
good first issue
help wanted
invalid
looking Into It
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cj/qbittorrent-webui-cjratliff.com#47
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?
Mirrored from GitHub issue #33
Original author: @Beimeith
Created at: 2023-09-12T06:23:43Z
Labels:
fixedDescription
As in the title, when using the theme, the Availability column always reports 1.01 regardless of the actual value.
Mirrored from GitHub comment by @Carve
Created at: 2023-09-12T12:47:12Z
Cannot replicate
Mirrored from GitHub comment by @Beimeith
Created at: 2023-09-12T13:02:49Z
Something is definitely off somewhere. Switching to default the value shows correctly.
And it isn't a cache issue this time, I've cleared it each time I've switched themes.
Mirrored from GitHub comment by @Beimeith
Created at: 2023-09-12T13:12:18Z
It looks to be related to the seeding limit value set in options. Whenever I change that value, the Availability value changes.
Mirrored from GitHub comment by @Beimeith
Created at: 2023-10-08T14:23:25Z
Some additional information:
The issue only appears to present itself if the Ratio Limit column is NOT selected/enabled. If it is not enabled, then the Availability column uses the ratio value. If the Ratio Limit column Is selected/enabled, then the Availability column works correctly. You may need to F5/reload the page for the changes to be reflected.
Mirrored from GitHub comment by @Carve
Created at: 2023-10-11T02:29:41Z
Are you on version 1.2.7.2?
Mirrored from GitHub comment by @Beimeith
Created at: 2023-10-12T00:28:56Z
I tested with 1.2.7.2 and by pulling down the current source and the result is the same.
Mirrored from GitHub comment by @Carve
Created at: 2023-10-12T16:59:34Z
Great examples, hopefully this will help me debug the JavaScript
Mirrored from GitHub comment by @Carve
Created at: 2023-10-30T20:01:24Z
Please test with today's release of 1.2.8 and re-open if needed.