EOF error logging with lower verbosity level #165
Merged
Conversation
This file contains 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
SandraRodgers
force-pushed
the
sr/fix-logging-error-for-EOF
branch
from
3c6e7e5 to
77433f8
Compare
davidvonthenen
approved these changes
Jan 19, 2024
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.
Proposed changes
This change handles an EOF condition more gracefully in the
live.Stream()function by logging it with a lower verbosity level (V(4)) rather than treating it as a regular error (V(1)).Instead of:
klog.V(1).Infof("r.Read failed. Err: %v\n", err)It logs:
klog.V(4).Infof("r.Read encountered EOF. Err: %v\n", err)