analyze_issue_with_seer can't replace a completed Seer run

Aperta
  • Qualcosa non va?
#2,273 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
tooling

Direzione di ricerca

Read packages/mcp-core/src/tools/catalog/analyze-issue-with-seer.ts around L149 (the startAutofix gate), L209-225 (the path that returns an existing terminal run), and the input schema at L83-92 with its Results are cached description at L80. Check the related getsentry/toolkit#1270 runId guard before changing the branch, since the new parameter has to coexist with it and with the fact that starting a run spends Seer credits. Done means a caller can explicitly request a fresh analysis, instruction is honoured or rejected rather than silently dropped, and the tool's existing tests are updated to cover both the reuse and refresh paths.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

MCP mcp-feedback-pattern

Pattern: once an issue has a completed Seer run, analyze_issue_with_seer always returns that run. Callers can't start a fresh analysis through MCP, even when the stored root cause is stale (for example, it points at code that has since been fixed and shipped), and the instruction argument is dropped without notice.

Reports: 1 (user feedback, MCP server 0.42.0, analyze_issue_with_seer, impact: blocked)

Current behavior (packages/mcp-core/src/tools/catalog/analyze-issue-with-seer.ts @ 516cad4)

  • L149: the tool calls startAutofix only when there's no previous run or the previous run's status is error.
  • L209-225: any other terminal run (completed, waiting for input) is returned as-is with Found existing analysis (Run ID: …). params.instruction is only passed to startAutofix (L155), so on this path it is silently ignored.
  • The input schema (L83-92) has no way to ask for a new run, and the description says Results are cached - subsequent calls return instantly (L80).

Sentry API (getsentry/sentry@fe43ef0)

  • POST /issues/{id}/autofix/ starts a new run whenever neither run_id nor sentry_run_id is passed (src/sentry/seer/endpoints/group_ai_autofix.py L286-299). An existing completed run doesn't block it.
  • GET /issues/{id}/autofix/ returns the group's latest run (get_autofix_agent_state → fetch_latest_run_state, src/sentry/seer/autofix/autofix_agent.py L558-575). So the gap is on the MCP side only.

Evidence from the report

  • The sampled analyze_issue_with_seer call made GET …/issues/{id}/ and GET …/issues/{id}/autofix/ and no POST. It returned Found existing analysis (Run ID: …) / ## Analysis Complete with the old root cause. That sampled call had no instruction argument; the reporter says an earlier call did pass one. We sample 30% of traces, so that call may not have been recorded.

Reporter's proposal: a force/refresh parameter on analyze_issue_with_seer.

Related: getsentry/toolkit#1270 adds a runId guard on the same code path that stops the tool from starting a new run. Any change here needs to fit with it. Starting a new run spends Seer credits, which is likely why the tool reuses the existing run today.

via automation evt_905b9c478746fd9deeb853f85ad7441b · Run ID dispatch_603ac936cce8aaa570e9b7eae0aa9519.

--

View Session [Sentry]

Lingua principale
TypeScript
Stelle
961
Fork
179
Merge medio
15h 33m
PR unite (30g)
476

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/toolkit

Tutte le issue di getsentry/toolkit

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.