-
Notifications
You must be signed in to change notification settings - Fork 45
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
Feature Request: Only Log Changes Made #124
Comments
Smh misread, thought it was changes not made |
Can't you achieve this result better by looking at your updates on the anilist page? |
I didn't fully read the thread before my comment, I thought they requested "Only log changes not made", i.e; errors |
I agree, when I do a test run for example I'd prefer only seeing logs of
Entries that are |
I changed some logs to debug level in the Also I noticed that way that the logic for multiple anilist entries for 1 Plex season was broken. For example, PlexAniSync wanted to set completed entries with 13 episodes to a watched count of 50. Anilist didn't do anything in that case, but now that situation should only happen if your mappings or Plex metadata are incorrect (for example having too many episodes in a Plex season compared to the TMDB season). You can currently detect it if you see I'll probably add another check so it logs something different when the watched count is greater than the total episodes of the Anilist entry. |
Oh nice. I can confirm I no longer see the "Updating series: " message. |
It prints to stderr because coloredlogs does so by default, but how are you planning on viewing stdout and stderr separately? |
If you only open the |
It would be nice to have an option in the settins to only log changes made, instead of showing all shows scanned.
With this option it would only log to the console when a missmatch in episode counts is found and updated.
This will make it easier to look at a docker's logs and just see the changes its made, instead of needing to sort through tons of unneeded logs.
The text was updated successfully, but these errors were encountered: