Debug messages appeaering with 0.5.2 -> 0.6.0 update
See original GitHub issueSeems requests-cache is using root logger and prints debug info with logging.info, should use logging.debug at least:
$ ./plex_trakt_sync.sh cache
INFO: Patching requests.Session with class: type
INFO: Initializing backend: sqlite
INFO: Initializing DbPickleDict with serializer: <class 'module'>
INFO: Using a secret key to sign cached items is recommended for this backend
INFO: Initializing DbDict with serializer: <class 'module'>
INFO: Using a secret key to sign cached items is recommended for this backend
redirects: 0
responses: 1539
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Debug mode not working · Issue #17314 · spyder-ide ... - GitHub
i have to close spyder and open it again. What steps reproduce the problem? debug any code and try to step inside. What...
Read more >OpenZWave not working after update - Z-Wave
Hey guys, I've just updated to the openZWave integration to version 0.5.0 and have lost all my devices. I notice the Serial Port...
Read more >Disable HttpClient logging - java - Stack Overflow
I am using log4j. Adding the first two lines in the log solver my problem completely. All my other log messages appear according...
Read more >[Closed] Prusa Connect & PrusaLink updates and releases
This thread contains the latest releases of the PrusaLink system and Prusa Connect updates along with changelogs.
Read more >Piklab Homepage - Changelog - SourceForge
... correct firmware loaded) * fixed toolchain output when executable cannot ... is off [fix by David Taylor] * fixed debugger stepping not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

seems current workaround is to limit this module logging:
@JWCook in that application trakt and plex debug entries are also logged (on purpose) to application file log (not terminal).
the only breaking change was that 0.5.x used no logging and 0.6.0 used info log level, so these end up in the console (terminal).
but I think you changed info -> debug. I have not verified were all log calls changed or just a few.