-
Notifications
You must be signed in to change notification settings - Fork 278
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
WARNING badge repeatedly lit up on SHOWQUEUE-UPDATE spurious IMDbPie "error" #10571
Comments
Apologies, I haven't done a pull request ("patch"?) here before, so a single word change seems like [for me at least] it is overkill to learn how to do a pull request ("patch"?) and then probly screw it up on my part. (Then have an extra branch sitting around in my environment just for the one word change... A branch I have to later nuke, which has always seemed quite tedious in github.) Again, apologies. |
Nah this is some kind of bug From which indexer has this show been added? |
The indexer for that show (at the time of adding it to Medusa's DB) was thetvdb |
So at the time - i suspect - that show didn't have an imdb added in tvdb. But it has now. So I can't reproduce it for that show now. |
I don't have an example of another show that lacks an imdb page. I concur with your assessment. That is a bit of an obscure show, and new at the time, so probly the exception was imdb saying "I dunno?" Good that it would be handled now -- thanks! |
Seems like this could be log.info() instead of log.warning(). On every nightly show update, the following appears in the log; because it is a WARNING the tools pulldown badge is always lit with warnings every morning. This makes the badge less useful. Since the badge is always lit up, you don't know when there are actual warnings that might require your attention.
Note the surrounding context describing the show "Kiss Sixth Sense" that is involved.
I did a quick hack in .../medusa//tv/series.py (on line 1692 of master branch) to simply change it from log.warning() to log.info().
The text was updated successfully, but these errors were encountered: