analyze_issue_with_seer can't replace a completed Seer run

Offen
  • Stimmt etwas nicht?
#2,273 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
68/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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]

Vorherrschende Sprache
TypeScript
Sterne
961
Forks
179
Ø Merge
15 Std. 33 Min.
Gemergte PRs (30 T.)
476

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus getsentry/toolkit

Alle Issues in getsentry/toolkit

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.