Description
** Commit: c9d90ad
** Operating System: windows 10 Home 64bit
** Python Version [python -V]: 3.5.1
Actually there are 2 issues (one being consequence of the other):
1/ when downloading a file not via Watcher in monitored directory then the file is processed at each scheduled postprocessing no matter that it was properly managed the first time: I have not set "Clean up download dir" nor "only process new files"
I investigated a bit a figured out that there could be inconsistency in the GUID computed from directory name as it is first used in upper case (scheduler.py line 119) but it is then turned to lower case (line 479 in postprocessing.py) when completed saves status in DB thus when second postprocessing starts again it does not find the GUID and do all the metadata seeking again and then the mover + renamer
I've tried shortly to patch the postprocessing start turning GUID to lower case at the earliest (I added in core/postprocessing.py line 480 "data['guid'] = data['guid'].lower()") then it find back the previous run results and retrieve metadata from local but still performs complete task doing again mover + renamer without check if status wasn't already set to "Finished".
2/ consequence of doing again mover then renamer is that at the end I have two files in target directory: one with original file name and second with renamed one.
I would have assumed that it was because renamer after mover failed as the target renamed file already exists but I have no ERROR log telling so as expected according to lines 698 of postprocessing.py