Fix delayed log output and missing crash logs - #82
MarcusStill wants to merge 1 commit into
Conversation
- Added `buffering=1` to `logger.add()` to force line-buffered logs so log messages are flushed to disk in real-time instead of blocked. - Fixed lost error/crash logs by placing `logger.complete()` in global exit hooks, uncaught exception hooks, and connection failures. - Added support for reading and parsing the dynamic `log_level` parameter from the `config.ini` [OTHER] section to replace hardcoded log levels. - Replaced the split standard logging setup in `modules/config.py` with the central application logger.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Fix delayed logging and missing logs in production by enabling correct loguru line-buffering and enforcing queue flushing via
logger.complete()before application exit. Also adds dynamic log level parsing.PR created automatically by Jules for task 14881234621651060158 started by @MarcusStill