-
Notifications
You must be signed in to change notification settings - Fork 1
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
Make "Remove From Client" configurable #36
Comments
Hi @wbio 👋 Thank you for your feedback - I really appreciate it. This could indeed be very useful, I’ll make sure to look into it tomorrow. It's highly likely that I'll implement this into the next release of Swaparr, keep an eye out for any updates within this issue. ^ Thijmen |
Good news @wbio 😄 Your request has been introduced in the new release 🎉 I've done some thorough testing, but would like to hear if all is working out for you as well. Looking forward to hearing from you. ^ Thijmen |
Hi @wbio, I'm closing this feature request as completed, feel free to reopen it to add your feedback. ^ Thijmen |
I use private trackers and 99% of the time if a download is stalled or downloading slowly it's because there's an issue with the torrent (e.g. it's been nuked), so it's fine to remove that download from the client, but I typically like to do a quick check on it before removing it from the download client in order to avoid potential issues with hit and runs.
By default the *arrs set
removeFromClient
totrue
on the delete from queue API, and since swaparr doesn't pass a value for that parameter, that's the behavior we get, but it would be great if that behavior could be configured with an environment variable so that we can still clear the item from the *arr queue, but not auto-remove it from the download client if desired in order to avoid potential HnR issues.The text was updated successfully, but these errors were encountered: