Open appiekap653 opened 4 weeks ago
Hey! Could you try this again with the latest main/develop image? Logging was improved a few weeks ago, but isn’t released yet.
I tried with the main image, logs are better but with the particular error it only added the path of the URI not the full URI.
[maintainerr] | 19/08/2024 00:00:59 [DEBUG] [ExternalAPI] GET request to /tv/57243/season/14 failed: AxiosError: Request failed with status code 500
I tried with the main image, logs are better but with the particular error it only added the path of the URI not the full URI.
[maintainerr] | 19/08/2024 00:00:59 [DEBUG] [ExternalAPI] GET request to /tv/57243/season/14 failed: AxiosError: Request failed with status code 500
That's a TMDB api call. It's trying to fetch season 14 of Doctor Who, but TMDB doesn't know of season 14.
Doctor who is a special one with it's latest season. It appears to have been rebooted, but Plex still added it as season 14, thus the search for season 14.
https://www.themoviedb.org/tv/57243/season/14
For instance, this works: https://www.themoviedb.org/tv/57243/season/13
For season '14' it should actually use this. There's's no way for Maintainerr to know cases like this. https://www.themoviedb.org/tv/239770/season/1
Is it an idea to have the full URI in the logs so we can see that it is trying to access TMDB, so we can debug it?
Describe the bug I see a lot of the following
AxiosError
messages when havingDEBUG
environment variable set totrue
:Is it possible to have some more details in the logs explaining the who, where, why about the error? At the moment it just says it has a 500 or 404 status code error, but not which URL it requested. Debugging those errors will be very difficult as it is now.