Anthropic provider: cache breakpoint lands on a thinking block (400: thinking.cache_control: Extra inputs are not permitted)

Aperta
#455 0 commenti 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
78/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Start in src/provider/anthropic.rs at Breakpoint 3 around lines 632–660, then inspect bridge_breakpoint around line 935 and the existing is_empty_text helper. Build the request described in the issue and check that thinking blocks never receive cache_control, while an earlier cacheable block still gets a breakpoint. Done means both breakpoint paths follow that rule.

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

Descrizione

Ask (narrow): in src/provider/anthropic.rs (0.27.9), never put cache_control on a thinking or redacted_thinking block. Anthropic accepts cache_control only on text / tool_use / tool_result / image / document blocks.

Where: Breakpoint 3 (~L632-660) scans back from the second-to-last message and sets cache_control on content.last_mut() whenever it is not an empty text block (is_empty_text, L921). bridge_breakpoint (L935) uses the same last-block rule. Neither excludes thinking blocks.

Trigger: any assistant message whose last block is thinking: a refusal (stop_reason: refusal) that kept only its thinking, an interrupted turn, or a thinking-only turn. Seen in yoyo Day 261 (yologdev/yoyo-evolve#1206):

error: API error: HTTP 400 Bad Request: messages.19.content.0.thinking.cache_control: Extra inputs are not permitted

Because the picker is deterministic, every following request rebuilds the same body, so the session may stay poisoned (not measured on yoagent; opencode reported exactly that for the same defect).

Fix shape used elsewhere (litellm aa3d59d0, antra-tess/membrane 2d405944 lastCacheableBlockIndex, opencode #51141): pick the last cacheable block in the message; if the message has none, keep scanning to the previous message. Same rule in bridge_breakpoint.

Test: a request built from [user, assistant(thinking only), user] has no cache_control on any thinking block and still has one breakpoint on an earlier cacheable block.

yoyo-side: #1206 tracks the yoyo test that pins this once a release ships.

Lingua principale
Rust
Stelle
327
Fork
46
Merge medio
2h 36m
PR unite (30g)
107

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 yologdev/yoagent

Tutte le issue di yologdev/yoagent

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.