fix: bump clio to fix logging when no tty present #2268
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
Previously if GRYPE_LOG_FILE was not set and no TTY was present, log.Warn messages would be discarded instead of sent to stderr. Now send them to stderr. Signed-off-by: Will Murphy <[email protected]>
kzantow
approved these changes
Nov 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.
Bump anchore/clio to pull in anchore/clio#68
Previously if GRYPE_LOG_FILE was not set and no TTY was present, log.Warn messages would be discarded instead of sent to stderr. Now send them to stderr.
Fixes #2180
Manually tested via python script described at #2180 (comment)