-
Notifications
You must be signed in to change notification settings - Fork 206
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
Special Episodes not in episode list in SickBeard fail to process #17
Comments
Could you post the log? |
Will do, btw I am just posting these as place holders for down the road...Also I intend to help where I can :) |
Here is the part of the log that matters: [######### ] 99% Processing /Users/craigsmith/Downloads/complete/The.Office.S09.Special.720p.HDTV.x264-EVOLVE/The.Office.S09.Special.720p.HDTV.x264-EVOLVE.mp4 (The.Office.S09.Special.720p.HDTV.x264-EVOLVE.nzb) Processing failed for /Users/craigsmith/Downloads/complete/The.Office.S09.Special.720p.HDTV.x264-EVOLVE/The.Office.S09.Special.720p.HDTV.x264-EVOLVE.mp4: |
This appears to be a Sickbeard bug not a problem with my script. What do you think? |
Well, sickbeard is missing the episode altogether, in this case this was a last minute change to the episodes. TVDB didn't have it.... What I am proposing is if Sickbeard doesn't have it, allow the process to move forward and still move the file to the correct location. I do not have a problem tackling this in the coming days. |
I think that would be better handled in other ways, it seems like adding a lot of functionality to the script that would be better placed elsewhere (either by submitting an issue with Sickbeard or by correcting thetvdb entry). Trying to replicate Sickbeard's functionality when Sickbeard fails seems rather overly complicated, even if the code turns out to be reasonable. |
If an episode is not found in sickbeard, still try to tag, even if that fails lets maybe use guessit to figure out what show it is at least and give it some info. Then still move the file to the final location. Currently it just fails and stops.
The text was updated successfully, but these errors were encountered: