fix(gate): serialize archive command failures - #2934
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 6 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
Comment |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
There was a problem hiding this comment.
Pull request overview
This PR hardens the deliberate-break gate’s JSON result payloads by normalizing subprocess stdout/stderr to text when git archive failures surface byte output, and adds a regression test to ensure the result remains JSON-serializable. The change is applied in both the source script and the consumer template to preserve parity.
Changes:
- Added
_subprocess_output_text()to normalizestr | bytes | Noneinto JSON-safe text. - Applied normalization to the
archive-command-failedresult path inverify_spec. - Updated the regression test to simulate byte output and assert
json.dumps()succeeds.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tests/scripts/test_check_deliberate_break.py | Extends regression coverage to ensure byte outputs don’t break JSON serialization. |
| scripts/check_deliberate_break.py | Normalizes git archive failure stdout/stderr to text in the gate result payload. |
| templates/consumer-repo/scripts/check_deliberate_break.py | Mirrors the same normalization change in the consumer template copy to maintain parity. |
Automated Status SummaryHead SHA: 530766b
Coverage Overview
Coverage Trend
Top Coverage Hotspots (lowest coverage)
Low Coverage Files (<50.0%)
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeNo scope information available Tasks
Acceptance criteria
|
Summary
Validation
python3 -m pytest -q tests/scripts/test_check_deliberate_break.py(105 passed)Source follow-up from review on the generated consumer wave after #2932.