-
Notifications
You must be signed in to change notification settings - Fork 176
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
TorrentToMedia is not moving files #1723
Comments
ok, can you try updating to latest nightly again and test? As a note, when using api, you would ideally want to set the fork as |
@clinton-hall thanks very much, this has fixed the issue. I was looking at updating the wiki but might wait till this is in Master. Probably not a big deal but thought it was worth mentioning for the wiki later.....the fork specified seems to be case sensitive. I have tested setting the fork in lower case fork = sickchill-api
fork = SickChill-api
|
Merged to master, and wiki updated |
Describe the bug
On Nightly, TorrentToMedia is not moving files on completion of the download, whether it be triggered by Synology download station or during a manual run, the logs appear all okay. This does not occur on the master branch.
Technical Specs
Expected behavior
Usually, the file is moved from /volume1/downloads/tv to a more permanent location at the end of the process.
If the script is set to clean-up, and if the torrent media was downloaded with a containing folder, then the media file and folder are deleted from /volume1/downloads/tv once moved to the permanent location.
If a media file alone is downloaded with no folder, the process creates a temp folder and only cleans up the temp folder and the original media file is sometimes left behind, sometimes not. I can't work it out when this is expected.
Lately, the media file downloaded alone has been left behind by the clean-up process, but in both scenarios above, nothing is being moved when passed to Sickchill post-processing. I think this has been occurring since I had to stash everything and pull down nightly again just yesterday.
I am not experiencing any issues using SickChill manual post-processing.
I have included the log from master below also.
The log for nighly was a fresh download from this morning....
NIGHLY Log
MASTER Log
The text was updated successfully, but these errors were encountered: