-
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
nzbToCouchpotato reports failure when status was already success. #1192
Comments
this api call asks for the status of the movie (status = snatched, downloaded, available, wanted, done etc) The general expectation is that the initial status should be either snatched or wantedm but after renaming the status should be done. this is how we know the renaming has been completed. The "success":true is the result of the api call to get the status. The reason this is done this way is to prevent accidental deleting of files that have nor been renamed (or not yet finished renaming). Basically, to be in the situation where status doesn't change, I suspect the following: So, can you post full renamer logs and confirm if this movie was snatched from CouchPotato, and if the movie was already "done" in couchpotato? Other than reporting "failure" are there any other issues? |
I think I can add to this:
meanwhile CP is happy:
then the filter for CP has nothing and the status change never happens
perhaps.. nzbToMedia could just be happy with the reported success and not try extra stuff? this test case was of a file I sent to sabnzbd via the nntp indexer, so it was not pushed by couchpotato |
The main issue I see is that Potentially there is a risk of reporting a movie as Successful when in fact it was not renamed... |
yes.. the risk is only potential and sabnzbd should not care anyway if CP does its job or not. I'd really appreciate if that check could be turned off via a config switch. (or a working solution for hardlinks as I do want to keep them) edit: it also happens if movie downloads are triggered from CP. so for me it reports every movie as failed. |
Try latest nightly branch
|
thank you! some thoughts: I noticed that the response to the few CP api calls I tried: |
Yeah, I'll take a look at it. having a quick look, media.get not returning a title shouldn't be an issue. We only really rely on, and use, the id for the release anyway. The flow of CP api checks is: We check for a release id using movie.get and using the imdb id In the case of a manual download, this isn't going to match any snatched releases in CP so we don't have the initial release id. After calling the renamer, it then: tries the movie.get using the release id to then see if the release status has changed. When no release id exists is tries to see if it can determine any recent changes, but obviously this doesn't appear to have much luck. Basically, Media status and files are not much help to us if we can't confirm the media... the renamed files can't be matched to the download name since this is dependent on your CP renaming. Status and recent changes are dangerous since this would assume no other changes can happen due to other automation or front-end access in CP. The safest way is to determine the imdb id. but currently I can only do this using ombdapi. There are other tools (i.e. using similar identifying algorithms as CP itself.... but that is a lot trickier to implement) |
I moved this no-status check so that it now by-passes all status checks when set. |
works great! slightly OT, but CP no longer seems to be maintained. sooner or later debian will drop python2.7, so time to look for an alternative? |
yeah.... I've been happily using CP for years and it continues to do what I want. Given my history with CP, I'd love to see it updated to py3 support. I just don't know that RuudBurger is going to find the time for that... Now, my scripts have supported Radarr for some time... and Looking at recent commits to SickChill indicate pending (I don't know how far away) support for movies. I'll reach out to Ruud to see what his intentions are for CP. |
I'd love to see CP staying alive (=runable without too much headache on a debian stable) for a while longer because it looks nice and I can't think of any feature I miss. |
Same here... I do recall SickChill indicated they would have a "Select your CP Database" option to import existing CP data (and config??) when setting up movie support... so that may make things a bit easier... From RuddBurger, I get the impression that a Py3 update to CP is unlikely. It will either be maintained as Py2 for so long as it can be, and then eventually un-supported, or it would be replaced by a different/new code base completely. Again that is all subject to his time... |
For some reason, the processing had succeeded in couchpotato but was reported as a failure to nzbget. My default behavior is to re-trigger the post-processing from nzbget.
nzbToMedia logs tell me:
The url mentioned returns
"success": true
, but if you look atcore/autoProcess/autoProcessMovie.py
(line 333) the script expects a status change.Why does not it expect the status to be success (rather than a change)?
The text was updated successfully, but these errors were encountered: