Repository navigation
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 23 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
|
…verage gaps Every distinct failure tonight collapsed to "after 3 attempts: claude exited 1". This records what a stage failure and a coverage gap actually were, at the runner, through the orchestrator, and at the public boundary: - runner annotates each terminal result with model, attempts, and retryable - cli extracts a structural terminalReason tier (closed enum) without touching the restricted event.result envelope unless it is a confirmed api_error - orchestrator passes apiErrorStatus/apiErrorMessage/terminalReason/model/ attempts/retryable through stageFailure and coverageGap, and collapses distinct statuses and models into the finder failure census - review-entry shape-checks all six fields at the public boundary and drops malformed values instead of publishing them; coverage gaps now carry the stage diagnostic so a gapped lens is nameable - final-review.schema.json extends failures and coverageGaps items so the artifact contract validates the additive fields Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: ENGINE-DIAGNOSTIC-CONTRACT
The contract's whole point is that an exhausted record names its own cause - 503 vs 402 vs 400 all collapsed to "after N attempts: claude exited 1". Assert the fields surface on the surviving record for each infra class: status, model, attempts, retryable. The 402 balance class was the only named cause with no explicit test; it now has one. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: w13-diagnostic-contract
c136e96 to
24cb49e
Compare
|
@coderabbitai review |
|
Summary
Every distinct failure tonight collapsed to the same string —
after 3 attempts: claude exited 1. This PR records what a stage failure and a coverage gap actually were, end to end:model,attempts,retryable(schema-error exhaustion isretryable: false— the runner misreading the model, not the model failing)terminalReasontier (closed enum) that surfaces even for CLI-level errors, without opening the restrictedevent.resultenvelope unless it is a confirmedapi_errorwith integer status 100–599apiErrorStatus/apiErrorMessage/terminalReason/model/attempts/retryablethroughstageFailureandcoverageGap, and the finder failure census now collapses distinct statuses (apiErrorStatuses) and models (models) across the dead batchesdiagnosticso a gapped lens is nameablefailures.itemsandcoverageGaps.itemsso the artifact contract validates the additive fields (additionalProperties: falsewould otherwise reject them)Test plan
apiErrorStatuses: [402, 503]), public-boundary junk-dropping test, coverage-gap structured-field passthrough tests, schema shape assertions🤖 Generated with Claude Code