Fix: Info logs incorrectly displayed as ERROR in stderr#3880
Closed
Chessing234 wants to merge 1 commit into
Closed
Fix: Info logs incorrectly displayed as ERROR in stderr#3880Chessing234 wants to merge 1 commit into
Chessing234 wants to merge 1 commit into
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
1 participant
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.
Bug: Uvicorn and other libraries write INFO-level startup messages to
sys.stderr. Becausesys.stderrwas globally redirected to a logger withlogging.ERRORlevel, these normal INFO messages were prefixed withERROR | stderr. Root cause: Global redirection ofsys.stderrtoStreamToLoggerwithlogging.ERROR. Why fix is correct: Removing this forced redirection allows standard streams to function naturally, letting native loggers output at their correct severity without being artificially escalated to ERROR.