fix(agent-mention): respect repository dispatch payload limit - #826
fix(agent-mention): respect repository dispatch payload limit#826seonghobae wants to merge 5 commits into
Conversation
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Comment |
|
Exact-current-head automated review request for The predecessor head exposed one deterministic contract drift after review-control fields moved under @coderabbitai review Review only. Do not mutate the branch, merge, or infer approval from predecessor-head evidence. |
|
|
|
@cwl-noema-review review Exact-current-head review only for |
![opencode-agent[bot]](https://avatars.githubusercontent.com/in/1549082?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.
Findings
1. HIGH Current-head GitHub Checks - Fix failed required checks before approval
- Problem: Failed same-head checks remain for
c4e11196fcb85bff3c37905d81521ef7d64d5185. - Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
- Fix: Read and fix the failed check logs below, then rerun the current-head checks.
- Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.
Failed checks:
- Strix Changed Path Quality CI/exact-head-path-policy: CANCELLED (https://github.com/ContextualWisdomLab/.github/actions/runs/31185839235/job/92890004303)
- exact-head-path-policy check run: cancelled (https://github.com/ContextualWisdomLab/.github/actions/runs/31185839235/job/92890004303)
Changed-File Evidence Map
flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Workflow: agent-mention-opencode-dispatch.yml"]
S1 --> I1["GitHub Actions review job"]
I1 --> R1["Review risk: Workflow: agent-mention-opencode-dispatch.yml"]
R1 --> V1["actionlint plus required checks"]
Evidence --> S2["Changed file: CHANGELOG.md"]
S2 --> I2["repository behavior"]
I2 --> R2["Review risk: Changed file: CHANGELOG.md"]
R2 --> V2["required checks"]
Evidence --> S3["CI script: agent_mention_router.py"]
S3 --> I3["review and security gate shell path"]
I3 --> R3["Review risk: CI script: agent_mention_router.py"]
R3 --> V3["bash -n plus Strix self-test"]
Evidence --> S4["Test (2 files)"]
S4 --> I4["regression suite"]
I4 --> R4["Review risk: Test (2 files)"]
R4 --> V4["targeted test run"]
OpenCode Review Overview
Pull request overviewOpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed. Findings1. HIGH Current-head GitHub Checks - Fix failed required checks before approval
Failed checks:
Changed-File Evidence Mapflowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Workflow: agent-mention-opencode-dispatch.yml"]
S1 --> I1["GitHub Actions review job"]
I1 --> R1["Review risk: Workflow: agent-mention-opencode-dispatch.yml"]
R1 --> V1["actionlint plus required checks"]
Evidence --> S2["Changed file: CHANGELOG.md"]
S2 --> I2["repository behavior"]
I2 --> R2["Review risk: Changed file: CHANGELOG.md"]
R2 --> V2["required checks"]
Evidence --> S3["CI script: agent_mention_router.py"]
S3 --> I3["review and security gate shell path"]
I3 --> R3["Review risk: CI script: agent_mention_router.py"]
R3 --> V3["bash -n plus Strix self-test"]
Evidence --> S4["Test (2 files)"]
S4 --> I4["regression suite"]
I4 --> R4["Review risk: Test (2 files)"]
R4 --> V4["targeted test run"]
|
|
@opencode-agent address Reconcile this PR with the exact current protected Before writing, refetch and require the PR head, protected-main tip, and both changelog blobs to remain exactly those values. Merge the exact protected-main tip into the existing PR branch with a normal non-forced merge. Resolve After reconciliation, verify the effective product diff is still limited to the five intended files and the payload contract is unchanged. Rerun Agent Mention Router Quality CI, complete central/Strix quality, security/supply-chain checks, and request fresh exact-head review; the predecessor OpenCode |
|
@opencode-agent address Reconcile this operational HTTP-422 repair onto the current protected base without rewriting history. Exact PR head is Use a trusted checkout and perform a normal non-forced merge of exact protected
Do not use force-push, |
|
Superseded before execution: do not write this branch from this request. The central mention-dispatch path being repaired by this PR is itself the unreliable writer-routing dependency, so this run is switching to an auditable connector-backed replacement from the exact current protected |
|
Superseded by #840, which is rebuilt from the current exact |
1 participant
Root cause
The failing
route-local-agent-mentionjob attempted to POST anagent-mention-opencoderepository_dispatchwhoseclient_payloadcontained 14 top-level properties. GitHub rejects repository-dispatch client payloads with more than 10 top-level properties, producing HTTP 422 before the OpenCode wrapper can run.Fix
review_policyobject, reducing the first dispatch from 14 top-level properties to 10 without weakening the invocation-key binding;CHANGELOG.md.The production merge scheduler remains unchanged and continues to receive its existing top-level control fields. No token, permission, approval, merge, or review policy is weakened.
Fixes the HTTP 422 observed in Actions run
31183770526, job92883146832.