Repository navigation
fix: reject --silent with --report-format json - #28
Merged
Merged
Conversation
Silent runs do not start the peak-RSS monitor, so a JSON summary reported metrics.max_memory_usage_kib as 0, which machine consumers cannot tell apart from a measurement. JSON mode already suppresses routine logging, so --silent adds nothing there. Reject the combination during CLI validation, whether silent mode comes from --silent or DPP_SILENT; such invocations now fail before any output is created. Text reports still accept --silent, and stdout output keeps its existing JSON rejection. Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Silent runs do not start the peak-RSS monitor, so a JSON summary reported metrics.max_memory_usage_kib as 0, which machine consumers cannot tell apart from a measurement. JSON mode already suppresses routine logging, so --silent adds nothing there.
Reject the combination during CLI validation, whether silent mode comes from --silent or DPP_SILENT; such invocations now fail before any output is created. Text reports still accept --silent, and stdout output keeps its existing JSON rejection.