so dont set it as completed until the files have been moved?
On rtorrent that’s the completed event that trigger the movment toward its final directory (the sync directory) :
method.set_key = event.download.finished,move_complete,"d.move_to_complete=$d.get_data_full_path=,$d.get_finished_dir="
any possibility of telling sonarr where the files actually are and have it move them instead?
I currently map the sync folder on rtorrent side to the final local path of this synced folder in sonarr, once file is moved by rtorrent, path is update so sonarr is able to pin point the local sync folder, but there’s a delay before local sync folder is properly synced with distant folder (transfer time)
well the issue there is that the drone factory didnt have a download associated with it, it was just an import run at intervals on a specific folder - to be fair im not sure why it was deprecated as it does cover the “weird” download requirements like this
I agree, I clearly understand the benefit of Download Handler, but as you mentioned the dumb drone factory did a good job in this unconventionnal situation.
if the download is completed then the files are meant to be in the download location already, there shouldnt be any requirement to wait, if there was then the job would not actually be completed.
your issue is that you have an extra step in between job completion and the files being in the correct location for import.
Exaclty, but at least sonar should wait for every files individualy (I know you told me it expect files to be there), I mean it search for a season, it knows how many file it has to gather, but if it moves only 1 file of the season, it considers the job as done, something is missing in its logic, at least an icon or a warning.
except the import code dosnt. it appears to be generic in that all it knows is that the job is completed and to run an import on a specific folder (to pick up every file in there) or to import a single specific file. the simplicity makes the code easier and more robust but it wont handle edge cases like this.
it still comes back to the job being marked as completed when the files are not in the correct location. i would expect that rewriting the code to handle an exact number of files would end up causing issues. this is after all an edge case, not something standard. everything else works normally except the way you have it setup - and this only fails because you’ve gotten in between the job completion and the files being in the location you want to import them from
I agree, but to some extend, a finish download is an event at rtorrent side, not sonarr. Sonarr should handle a life cycle for each of it’s request (it may actually), I mean if it search for a season, it may handle sub cycle for each episode. I don’t really know how people using seedbox with a local sonarr do there stuff, I should search for that, maybe through the sonarr API.
if you dont move the files does it fail and give you the orange icon or does it clear out the job? just wondering if it might be better to sync them to a different folder and have a script that uses the API to import the files from that folder as they sync? (sort of mimicking the drone factory import functionality)
if sync is off for exemple, and files are not in the local folder, it stays with the orange icon for each episode. but once 1 or 2 episodes are moved, it clear out the job with the whole list of episode. As mentioned above, using the API may be a lead. I’m also searching a way to lock files during transfer like append a dot before the name of the transfert folder, so once the transfert is done Sonarr should see all the files spawning instantly.
the main concern that I have, is the fact that only season pack is faulty, for individual episodes, I don’t have any issue at all.