-
-
Notifications
You must be signed in to change notification settings - Fork 304
fix(rendering): honor suppressWarnings in settled build output #470
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
Open
JoshKappler
wants to merge
1
commit into
getsentry:main
Choose a base branch
from
JoshKappler:fix/suppress-warnings-in-domain-result-text
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
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
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.
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.
Bug: The
suppressWarningsflag is not passed tocreateSpecialCaseItems, causing warnings to be displayed forinstall-result,launch-result, andstop-resultfailures even when suppression is requested.Severity: MEDIUM
Suggested Fix
Extract the
suppressWarningsoption from theoptionsobject at the beginning of therenderDomainResultTextItemsfunction, beforecreateSpecialCaseItemsis called. Then, pass thesuppressWarningsflag through the call chain tocreateSpecialCaseItemsand subsequently tocreateFailureStatusWithDiagnosticsto ensure it is respected.Prompt for AI Agent
Did we get this right? 👍 / 👎 to inform future reviews.
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.
I checked this against the result constructors and I don't think the path is reachable.
Every
install-result,launch-result, andstop-resultis built with an empty warnings array.buildInstallSuccess,buildLaunchSuccess, andbuildStopSuccesshardcodewarnings: [], and the failure builders (buildInstallFailure,buildLaunchFailure,buildStopFailure) callcreateBasicDiagnostics({ errors: [...] }), which normalizes the absent warnings to[].swift_package_stopbuilds itsstop-resultthe same way.createStandardDiagnosticSectionsonly emits the Warnings section whendiagnostics.warnings.length > 0, so those three kinds never render one whether or not the flag is set. ThreadingsuppressWarningsintocreateSpecialCaseItemswould be dead code today.The kinds that actually populate warnings are build, build-run, and test, and those are the ones this PR threads the flag into. If you would rather have the flag wired through the special-case path anyway so it cannot drift if those results ever start carrying warnings, say so and I will extend it.