Keep jq stderr in jq_lacks (converge with Docker repos)#221
Merged
Conversation
Discard only stdout (drop 2>&1); jq's exit 0/1/4 cases produce no stderr so normal runs stay silent, but a real jq error (2/3/5) now prints its message. Converges with the Docker repos. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts the repo-config/configure.sh audit helper jq_lacks so jq error diagnostics are no longer suppressed, improving observability during repository configuration validation (while keeping normal “match/lacks” runs quiet).
Changes:
- Update
jq_lacksto discard only stdout (remove2>&1) so jq stderr is preserved for real jq errors. - Update the surrounding comment to document the intended stdout/stderr behavior.
This was referenced Jul 9, 2026
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.
Discard only stdout in
jq_lacks(drop2>&1). jq's exit 0/1/4 cases produce no stderr so normal audit runs stay silent, but a real jq error (exit 2/3/5) now prints its diagnostic instead of failing silently.Converges
repo-config/configure.shwith the Docker repos (PlexCleaner/VSCode-Server), where Copilot surfaced this. Verified:bash -n, shellcheck, and the lacks/match cases still behave with no spurious stderr.