You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(selfhost): only escalate the final AI-provider retry attempt to Sentry (#5046) (#5048)
logSelfHostAiProviderFailed fired console.error on every subscription-
CLI attempt, not just the final one -- contradicting ai-review.ts's
own documented "per-attempt=warn, exhausted=error" policy (#26).
GITTENSORY-K (claude_stalled_no_output) hit 2077+ events: pulled raw
events sharing the same jobId/trace_id at attempt 0, 1, 2, confirming
one review's 3x-retry-per-model loop was independently escalating
each attempt to Sentry instead of just the exhausted outcome.
Thread finalAttempt through AiRunOptions (mirroring the existing
attempt/jobId correlation fields) so the provider's own log can tell
a retried attempt (quiet) from a genuinely exhausted one (loud).
runWorkersOpinion, the dual-AI tie-break judge, the issue planner, and
the AI slop advisory all compute it as "last attempt of the last
model" and pass it through. Two of those callers (planner.ts,
ai-slop.ts) have no logging of their own -- their retry loops rely
entirely on this log for visibility, so a blanket downgrade would have
silenced them; unset stays loud by default for exactly that reason.
0 commit comments