Add standalone JSON logging (cre_logging) - #1101
Conversation
Keep cre_logging off the Flask application package so importing a logger never loads create_app. Emit one JSON object per line with module, file, and calling method.
|
Important Review skippedToo many files! This PR contains 305 files, which is 205 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (305)
You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Merging with admin bypass: Test, Lint, Frontend Lint, Librarian, Analyze (python), and both e2e jobs are green. CodeQL failed on pre-existing |
Summary
cre_loggingso every module canfrom cre_logging import get_loggerwithout importing Flask/application.__init__.module,file,method, andlevel.logging.basicConfig()/ unusedpprint, and send relevantprintprogress/errors through the logger. CLI machine output (print(summary.to_json())) stays on stdout.Supersedes #856 (optional JSON +
application.utils.logging_config, which still sits under the heavy application package).Test plan
python -m unittest application.tests.cre_logging_test(includes subprocess check thatimport cre_loggingdoes not loadapplicationorflask)make lint/make mypy/make testMade with Cursor