AntFleet

Disagreement · 52c1a3b9-anthropic-4

Webhook ignores enqueueReview's returned reviewId staleness — old commit shas not refreshed

solo Opus
repo e24ef98c·PR #11·reviewed 1 week ago

Opus finding

Webhook ignores enqueueReview's returned reviewId staleness — old commit shas not refreshed

lowbuglow
  • apps/web/app/api/github/webhook/route.ts:297-320
When isNew=false, the webhook returns and never schedules a worker — comments on retry hand-off. But if the prior row is terminally 'failed' (max attempts), a new identical delivery cannot re-trigger work. This is by design per the comment ('the original one (or the retry cron) will settle the row'), but a 'failed' row will never re-run. Borderline maintainability concern — the operator must reset status manually.

Recommendation

Document this on the duplicate path, or detect status==='failed' and reset to pending_retry if the operator wants a re-attempt via duplicate redelivery.

Other reviewer

The other reviewer flagged nothing in this file/line range.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →

From the same review

These findings passed the unanimous gate on the same PR review. The disagreement above was filtered out; the findings below were posted.