search_issues agent strips punctuation from quoted phrases

Aperta
  • Qualcosa non va?
#2,212 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
ai, search

Direzione di ricerca

Start with the search_issues path in search-issues.ts (around lines 195-244, where the query goes to Seer or the embedded agent) and the agent prompt in support/search-issues/config.ts (lines 11 and 25). Check whether a quoted phrase containing parentheses survives the agent's rewrite, and how rewriteSearchQuery treats it. Done means a quoted phrase like "organization step(s) failed" is passed through unchanged, or any rewrite is reported in the result notes.

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

Descrizione

Through the embedded repair agent, search_issues can rewrite a quoted literal phrase. In MCP-SERVER-GPC (opencode, server 0.42.0), "organization step(s) failed" was reported to run as organization step failed. It returned nothing, though a matching issue existed (a search for organization found it).

  • Not verified from telemetry: the failing call isn't in the sampled spans, and the feedback trace is unsampled. The call path below comes from code and from the same caller's other calls.
  • The deterministic rewrite keeps the phrase: rewriteSearchQuery('"organization step(s) failed"', { issueSearch: true }) returns it unchanged with no notes. A quoted phrase alone isn't structured syntax (looksLikeSentrySearchSyntax → false), so it goes to Seer or the agent (search-issues.ts:195-244).
  • This org uses the agent path: the same user and org's earlier quoted search_issues call (trace e90e6dd4…, 2026-11-10, "timeout of 20000ms exceeded") shows the org feature-flag GET and then callEmbeddedAgent, with no Seer translate call. That run kept the quotes, so the rewrite seems tied to the punctuation.
  • Likely trigger (inference): the agent prompt counts only field:value forms as explicit tokens (support/search-issues/config.ts:11), so a quoted free-text phrase is natural language that the agent may rewrite. It also says parentheses are "invalid in issue search even when written explicitly" (config.ts:25), which doesn't separate grouping parens from literal characters inside a quoted phrase.
  • The rewrite is silent: the result's notes only include rewrites from rewriteIssueQuery (search-issues.ts:282-289). An agent rewrite shows up only as the changed executedSearch.query, and the explanation only appears with includeExplanation.

Related: the same feedback's search_logs part (unknown attribute with no suggestions) is in #2211.

via Sentry.

--

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.