test(providers): verify interleaved thinking and tool calls via Responses

Aperta
  • Qualcosa non va?
#1,344 2 commenti 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
46/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
api, testing-qa

Direzione di ricerca

Start by reviewing #1085 and PR #1343, then trace the Messages request → canonical chat → Responses input → upstream response → Messages response/SSE path. Add composed-path tests with interleaved thinking blocks and tool calls/results, covering streaming and non-streaming where supported. Done means tests establish ordering at both boundaries and make unsupported ordering explicit; wait for #1343 to merge before rebasing a follow-up branch.

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

Descrizione

Context

Follow-up to #1085 and PR #1343. #1085 tracks Messages ingress onto Responses-only upstreams. PR #1343 addresses reasoning summary request/rendering, but does not prove preservation of ordering when Anthropic thinking blocks and tool calls are interleaved.

Scope

Verify the complete translation path for interleaved assistant thinking and tool use: Messages request → canonical chat → Responses input → upstream response → chat → Messages response/SSE.

  • Add realistic fixtures/tests for multiple thinking blocks interspersed with tool calls/results.
  • Assert ordering and content at the Responses upstream boundary and the Messages client boundary.
  • Cover both streaming and non-streaming paths where supported.
  • If ordering cannot be preserved by the current canonical representation, document the limitation and propose the smallest compatible fix.
  • Avoid duplicate end-to-end scaffolding if existing contract/probe helpers suffice.

Acceptance criteria

  • Behavior is demonstrated by tests across the actual composed translation path, not inferred from individual converter tests.
  • Tests establish which ordering is supported; unsupported cases are explicit rather than silently reordered or dropped.
  • Any production fix has regression coverage.

Part of the remaining verification work tracked by #1085. Depends on #1343 merging; rebase the follow-up branch onto updated upstream main before opening the follow-up PR.

Lingua principale
Go
Stelle
1.2k
Fork
111
Merge medio
20h 53m
PR unite (30g)
142

Preparare l'ambiente

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 ENTERPILOT/GoModel

Tutte le issue di ENTERPILOT/GoModel

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.