Opened 10 years ago

Closed 10 years ago

Last modified 7 years ago

#2400 closed bug (Fixed)

Torrent isn't auto managed yet stops when reaching ratio 1, refuses to resume (need force start behaviour)

Reported by: OmegaPhil Owned by: OmegaPhil
Priority: minor Milestone: 2.x
Component: Core Version: 1.3.6
Keywords: Cc:

Description

I have an organised system of labels with Queue settings applied to stop seeding at ratio 1. Occasionally a torrent that belongs to a particular category/label comes along but needs permanent seeding - in the uTorrent days I would have Force Started the torrent, but deluge doesn't have this.

Please can I have an equivalent ability to force start a torrent - override the 'Stop seed at ratio' setting or similar - since label is controlling this, I have put this feature request against this plugin.

Thanks

Change History (15)

comment:2 Changed 10 years ago by OmegaPhil

I have done this, but it makes no difference - I assumed the label functionality was overriding normal management.

comment:3 Changed 10 years ago by Cas

Did you check or uncheck auto managed for queue settings in the label options?

Last edited 10 years ago by Cas (previous) (diff)

comment:4 Changed 10 years ago by OmegaPhil

Auto Managed is off as standard with the queue settings I use.

I have had a review of how I configure Deluge in general - I think originally some years ago, I found setting Auto Managed to Off made no difference (torrents were still getting paused etc, even when I wanted them permaseeding) - back then I had 10 active torrents allowed, but obviously wanted unlimited permaseeding torrents as I saw fit.

So to work around this, I used labels to remove management (Auto Managed off) and enforce permaseeding.

Nowadays I'm on a VDSL2 connection, so I don't really need an active torrents limit... because of this, instead of hacking around with label settings, I am going to use 100 active torrents (essentially unlimited) and set Auto Managed to off for those that need to permaseed.

I'll see how it goes - historically this was probably an issue with Auto Managed in general.

comment:5 Changed 10 years ago by OmegaPhil

  • Resolution set to Invalid
  • Status changed from new to closed

OK, I have done this for a week with no issues - so obviously whatever it was before that pushed me to doing this is no longer relevant now - resolving invalid.

comment:6 Changed 10 years ago by OmegaPhil

  • Component changed from Plugin to Core
  • Resolution Invalid deleted
  • Status changed from closed to reopened
  • Summary changed from [label] Ability to override label options on a per-torrent basis - Force Start? to Torrent isn't auto managed yet stops when reaching ratio 1, refuses to resume (need force start behaviour)
  • Type changed from feature-request to bug
  • Version changed from other (please specify) to 1.3.6

Right, the real problem I was running from is back - once a torrent that isn't automanaged reaches ratio 1 (which is my global seeding limit), its stopped, and refuses to resume. This is why I then moved to labels to enforce permaseeding.

comment:7 Changed 10 years ago by OmegaPhil

Finally understand why... torrents have a per-torrent 'Stop seed at ratio' option that isn't exposed by the right-click menu, but is available in the Options tab. As soon as I killed that off, I could resume the torrent. At this stage, I don't even know if Auto Managed matters.

In terms of the 'bug', perhaps this is a usability issue... not something I'm going to complain about anyway. Pays to study software.

Would it be worth me adding this option to the right-click menu?

comment:8 Changed 10 years ago by Cas

I guess for completeness it would be worth doing. I think a sub-menu with Disable|Enable... and the Enable is a popup for ratio value input.

While you are looking at that code you could see if you can fix #2401

comment:9 Changed 10 years ago by OmegaPhil

OK - depending on exactly what happens, this work might need to wait as I shift it to a dedicated slot.

comment:10 Changed 10 years ago by OmegaPhil

  • Owner set to OmegaPhil
  • Status changed from reopened to assigned

comment:12 Changed 10 years ago by OmegaPhil

Feedback from Cas:

Lambdas to proper functions Remove errbacks - unnecessary (no need to do something specialised, error will be emitted from twisted regardless)

Last edited 10 years ago by OmegaPhil (previous) (diff)

comment:13 Changed 10 years ago by Cas

  • Milestone changed from Future to 1.4.0

comment:14 Changed 10 years ago by Cas

  • Resolution set to Fixed
  • Status changed from assigned to closed

Fixed in develop: [ea7ef950a3]

comment:15 Changed 7 years ago by Cas

  • Milestone changed from 2.0.x to 2.x

Milestone renamed

Note: See TracTickets for help on using tickets.