Ensure stdout is flushed before exit#37
Merged
yiftach-armis merged 1 commit intomainfrom Jan 13, 2026
Merged
Conversation
Test Coverage Reporttotal: (statements) 76.8% Coverage by function |
Add os.Stdout.Sync() before os.Exit() to prevent output truncation when scan findings trigger a non-zero exit code. This is especially important in CI/CD environments where stdout is piped or captured.
yiftach-armis
force-pushed
the
fix/stdout-sync-on-exit
branch
from
5aa6382 to
88b3428
Compare
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.
Description
Adds
os.Stdout.Sync()beforeos.Exit()in theExitIfNeeded()function to ensure all scan output is flushed before the process terminates.Type of Change
Related Issues
None
Testing
Checklist
Additional Notes
This fix prevents output truncation when the CLI exits with a non-zero code due to security findings. This is particularly important in CI/CD environments where stdout may be piped or captured. The change is defensive programming that ensures output reliability without altering existing behavior.