Change logging level from warning to debug - #3
Merged
Conversation
There is no actual warning or issue going on in these logger messages. I think it is more appropriate to either remove them completely, or change the logging to debug. These kinds of things becomes important when tracker-scraper is used as a library
Contributor
Author
|
I see now this is kind of exactly related to #1 |
modbender
approved these changes
Aug 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is no actual warning or issue going on in these logger messages. I think it is more appropriate to either remove them completely, or change the logging to debug.
These kinds of things becomes important when tracker-scraper is used as a library.
To test, set the
LOG_LEVELenvironment variable toDEBUG