Fix output formatting bug introduced in 9f8a7ec - #271
Merged
Conversation
Contributor
Author
|
Beuller? |
dhiwakar-okta
approved these changes
Oct 21, 2025
curator
force-pushed
the
fix-output-newlines
branch
from
November 13, 2025 20:11
73340e6 to
3bd27a7
Compare
Contributor
Author
|
Fixed the verified commit issue. |
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
3 participants
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.
9f8a7ec changed stdout/stderr output for several strings. This PR fixes the ones I've found that ended up missing the newline when transitioning from fmt.Fprintln() to a Logger.Warn().
Resolves #274