Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deluge: create a category for lidarr to consider a download failed. c… #2805

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

doguitar
Copy link

@doguitar doguitar commented May 5, 2022

…ategory can be applied by an external tool to handle stalled downloads.

Database Migration

NO

Description

Allow users to apply a category that lidarr to consider a download a failure. This should allow users to detect and handle stalled downloads either manually or with an external automation tool to detect stalled or slow torrents.

Screenshot (if UI related)

Todos

  • [?] Tests
  • [?] Translation Keys (./src/NzbDrone.Core/Localization/Core/en.json)
  • Wiki Updates

Issues Fixed or Closed by this PR

…ategory can be applied by an external tool to handle stalled downloads.
@bakerboy448
Copy link
Contributor

See the discussion on Radarr's GH for related pain points for this time of topic
Radarr/Radarr#5407

@doguitar
Copy link
Author

doguitar commented May 5, 2022

I have looked through that issue and is why I chose to implement this manual category as a way to mark failures. There's a lot of back and forth disagreements on what should count as a stall/failure for torrents and a variety of opinions and concerns. By having a category applied externally, a user can use whatever method they want to mark those downloads as failed through some rules in their download client or an external automation tool.

My hope is to at least get the ball rolling on a feature of this type as the discussion in that thread seems to have come to an impasse.

Should this be approved, I imagine a similar implementation for qbittorrent/rtorrent/utorrent but I use deluge so the implementation was easier for me to start with.

@bakerboy448 bakerboy448 added the Status: Unlikely This issue is unlikely to be fixed, since it would only be useful to one person or is out of scope. label Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Unlikely This issue is unlikely to be fixed, since it would only be useful to one person or is out of scope.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Blacklist idle/stalled/0kb files after 'x' time sitting at the downloader
2 participants