-
Notifications
You must be signed in to change notification settings - Fork 1
Write the scan report and SBOM before the blocking-rule gates exit #156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Quality - The code uses multiple "unwrap()" calls on fallible operations like "to_string_pretty", which can panic and crash the CLI instead of handling errors gracefully. This breaks the consistent error handling style in the file. View in Corgea ↗
More Details
🎟️Issue Explanation: The code uses multiple "unwrap()" calls on fallible operations like "to_string_pretty", which can panic and crash the CLI instead of handling errors gracefully. This breaks the consistent error handling style in the file.
- Crashes caused by "unwrap()" lose error context, making debugging harder than using structured error logs as seen elsewhere.
- Unexpected panics reduce CLI predictability, harming user experience and automation workflows relying on exit codes.
- Inconsistent error handling increases maintenance complexity, confusing developers about standard error patterns in the codebase.
🪄Fix Explanation: The report writer now handles serialization and file-write failures explicitly instead of panicking or silently ignoring detected errors. It logs actionable messages, stops the spinner, and exits with a failure status for consistent CLI behavior.
-Replaces "unwrap()" with "match" blocks for issues, SCA issues, and classifications, making serialization failures explicit and maintainable.
-Logs the original error through "log::error!", giving users actionable context about which report component could not be serialized.
-Replaces panic-based writes with "if let Err(e) = fs::write(...)", avoiding uncontrolled panic output and handling filesystem failures consistently.
-Calls "stop_spinner()" before serialization failure exits, ensuring terminal UI state is cleaned up before the process terminates.
-Uses "std::process::exit(1)" for all handled failures, providing a reliable nonzero status to scripts and CI pipelines.
To apply the fix, Download .patch.