Skip to content

Preserve torrents based on presence of trackers#1482

Merged
liiight merged 2 commits intoFlexget:developfrom
schunemunk:patch-1
Nov 8, 2016
Merged

Preserve torrents based on presence of trackers#1482
liiight merged 2 commits intoFlexget:developfrom
schunemunk:patch-1

Conversation

@schunemunk
Copy link
Copy Markdown

Motivation for changes:

Forum discussion about skipping cleanup for certain torrents based on the presence of a tracker in the torrent's tracker list

Detailed changes:

Creation of a new config setting "preserve_tracker" and adding corresponding logic

Addressed issues:

None

Config usage if relevant (new plugin or updated schema):

clean_transmission:
host: localhost
port: 9091
username: myusername
password: mypassword
tracker: nyaa|animebytes
preserve_tracker: alpharatio|what

@gazpachoking
Copy link
Copy Markdown
Member

My first reaction is that I don't really like the current design of clean_transmission, and think we should move to a system where it can live in its own task with from_transmission input, and use normal filter plugins on that task to control what it cleans. The current model only begets this sort of option adding for internal filtering. That being said, I'm not sure if that should hold up this PR or not.

(is_torrent_seed_only and is_torrent_idlelimit_since_added_reached) or
(not is_torrent_seed_only and is_torrent_idlelimit_since_finished_reached))
and is_tracker_matching and is_directories_matching):
and is_directories_matching (not is_preserve_tracker_matching and is_tracker_matching)):
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and is_directories_matching (not is_preserve_tracker_matching and is_tracker_matching)

is there meant to be an 'and' or an 'or' in between is_directories_matching and that parenthetical?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops yes. Fixing now...

(is_torrent_seed_only and is_torrent_idlelimit_since_added_reached) or
(not is_torrent_seed_only and is_torrent_idlelimit_since_finished_reached))
and is_tracker_matching and is_directories_matching):
and is_directories_matching and (not is_preserve_tracker_matching and is_tracker_matching)):
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no need for that parenthesis.

@cvium
Copy link
Copy Markdown
Contributor

cvium commented Nov 6, 2016

I don't think it makes sense to not allow these kinds of PRs. Small changes that improve QoL. Should Transmission plugins be refactored completely? Yes, but that's quite a daunting task for most, so who's to say when and if that will happen.

@liiight
Copy link
Copy Markdown
Member

liiight commented Nov 6, 2016

Like we discussed in gitter, I'm @gazpachoking on this one. I think that any feature that is added to the current state of this plugin will just deter any work on modifying it.

@liiight liiight merged commit b54394a into Flexget:develop Nov 8, 2016
@marine1988
Copy link
Copy Markdown

I think thes feature is awesome i do download form alot of place but I only and to keep torrents from 2 or 3 trackers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants