fix: send async logger output to stderr#1971
Open
nightcityblade wants to merge 1 commit into
Open
Conversation
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
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.
Summary
Fixes #1968
Routes
AsyncLoggerconsole output to stderr by default so stdout remains clean for stdio protocols such as MCP, while still allowing callers to pass a custom Rich console.List of files changed and why
crawl4ai/async_logger.py- Default logger console output to stderr and add an optional custom console parameter.tests/loggers/test_async_logger_stderr.py- Cover stderr default behavior and custom console override.How Has This Been Tested?
. .venv/bin/activate && python -m pytest tests/loggers/test_async_logger_stderr.pyChecklist: