Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
For the last two days I have been having issues with all downloads, this is the same setup I have been running for years, so not sure whats' gone wrong.
This piece of code has been in there for quite some time, so I'm surprised that you suddenly get this.
Even so, I will look into this.
The os.renames() documentation isn't clear about support of cross-volume issues.
Thanks for the response shypike, I rolled back to commit e90ff0eeb76aa9d7d7b6aeb1c78ff3a47c30f265 and the issue doesn't occur. I can try updating one commit at a time to see when the issue does if it will help?
I am auto updating on SAB restart, I guess if its been a couple weeks since it restarted I could have been behind a couple commits.
Scanning through the changes since the 30f265 commit shows nothing related.
Very strange, if it's indeed a bug, it must be some far removed side-effect.
I would appreciate if you spend the effort on finding the bad commit.
Looking at the rename_and_collapse() function, it doesn't take into account cross-volume moves,
because there shouldn't be one.
This is also what your logging shows. I don't see a cross-volume move:
/media/1000gb1/Downloads/complete/tv/_UNPACK_XXXXXX _S06E16.720p_HDTV_x264-XXXXXX
/media/1000gb1/Downloads/complete/tv/XXXXXX _S06E16.720p_HDTV_x264-XXXXXX
Of course I can change the code to what you suggest, but I would need to check
the behaviour on multiple platforms.
I will work on it , it has happened to several pals now and they discovered that if you turn off config -> switches, 'folder rename', then it works again.
Which there is a note under that option to turn off if it doesn't work on your system....lol
I haven't messed with the config, so not sure what the deal was.
Odd, the option was only ever there for Windows systems,
which can be completely paranoid about folder renames.
Odd that more sensible systems suffer from the same problem.
Maybe it's a problem in Python's run-time library after all.
I will look into your alternative code.