-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Rename forced downloads #232
Comments
This is intended behaviour. The fact that the content was downloaded with force suggests it probably won't match well to the volume and it's issues; there's a high chance of files not matching or matching wrong. So renaming has a high chance of only half of the files actually being renamed and those files being named wrong. |
Everything i've forcefully downloaded and then renamed was correctly identified and renamed. And it was a lot of issues/volumes. When you manually download something with any other arr-stack app, it gets renamed according to your renaming settings. So calling this intended behavior seems lazy to me... |
It's not lazy at all. I actually had to do extra work to avoid them being renamed. I made a poll on Discord to check with other people whether the files match correctly for them often enough that we can confidently rename them by default. If so, I'll open the issue and implement the changes (mostly just removing the code that avoids it). |
It doesn't unzip files with multiple issues either, right? |
To be honest i haven't tested that yet. |
It should |
Description of the bug
since the latest release we are able to force a download when the regular download doesn't work or the volume name is slightly off. When forcing a download, the downloaded file(s) are not renamed like they are with a regular download.
To Reproduce
force a download
Expected behaviour
The the forced downloaded file(s) are renamed.
Version info
The text was updated successfully, but these errors were encountered: