[Deluge] #3497: "stop seed at ratio" feature fails to trigger when not logged into Web UI
Deluge
-------------------------+-------------------------------------------------
Reporter: | Type: bug
glodomorrapl |
Status: new | Priority: major
Milestone: needs | Component: Web UI
verified | Keywords: seed limit,web ui,stop seed at
Version: 2.0.3 | ratio
-------------------------+-------------------------------------------------
i have a torrent, which i set "stop seed at ratio" to 2.
what i expected to happen: as soon as the torrent exceeds the ratio of 2,
it's automatically stopped regardless of whether or not I'm currently
logged into the Web UI
what happened: i log into the Web UI just to see the torrent exceed the
upload ratio by multiple amounts of the value I set - the torrent was
still active, and it paused after about a second or two after I logged
into the Web UI
i think priority of this bug would be "major" at least, as the failure of
that feature may potentially result in exceeding upload quotas
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3497>
Deluge <https://deluge-torrent.org/>
Deluge Project
Deluge
-------------------------+-------------------------------------------------
glodomorrapl |
Type: bug | Status: new
Priority: major | Milestone: needs verified
Component: Web UI | Version: 2.0.3
Resolution: | Keywords: seed limit,web ui,stop seed at
| ratio
-------------------------+-------------------------------------------------
Comment (by tcoza):
I have the exact same problem. This doesn't seem to have anything to do
with Web UI, tho. It would be the role of the Deluge Daemon to pause
seeding torrents after they have reached a certain ratio, but it doesn't.
The same thing happens when you use Deluge-GTK in Thin-Client mode,
connected to a daemon. The torrent keeps seeding until you open Deluge-
GTK, then it keeps going for about 1 second and pauses.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3497#comment:1>
Deluge
-------------------------+-------------------------------------------------
Reporter: | Owner:
glodomorrapl |
Type: bug | Status: new
Priority: major | Milestone: needs verified
Component: Core | Version: 2.0.3
Resolution: | Keywords: daemon,seed limit,stop seed at
| ratio,web ui,gtk
-------------------------+-------------------------------------------------
Changes (by tcoza):
* cc: traian.coza@… (added)
* keywords: seed limit,web ui,stop seed at ratio => daemon,seed limit,stop
seed at ratio,web ui,gtk
* component: Web UI => Core
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3497#comment:2>
Deluge
-------------------------+-------------------------------------------------
Reporter: | Owner:
glodomorrapl |
Type: bug | Status: new
Priority: major | Milestone: needs verified
Component: Core | Version: 2.0.3
Resolution: | Keywords: daemon,seed limit,stop seed at
| ratio,web ui,gtk
-------------------------+-------------------------------------------------
Comment (by gazpachoking):
Okay, started looking in to this. I haven't fully confirmed yet, but it
looks like with no clients connected, the cached status of the torrent
keeps getting used for the stop ratio check. Once a client connects, it
forces the cache to update, and the stop ratio check works properly.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3497#comment:3>
Deluge
-------------------------+-------------------------------------------------
Reporter: | Owner:
glodomorrapl |
Priority: major | Milestone: 2.1.0
Component: Core | Version: 2.0.3
Resolution: Fixed | Keywords: daemon,seed limit,stop seed at
| ratio,web ui,gtk
-------------------------+-------------------------------------------------
Changes (by Cas):
* status: new => closed
* resolution: => Fixed
* milestone: needs verified => 2.1.0
Comment:
Thanks gazpachoking for fixing this!
Fixed in [8ff468378]
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3497#comment:4>