Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[bug] text chat --api responses --tool web_search: non-streaming requests systematically fail with headers timeout; --stream works

Aperta
#239 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
57/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
node.js, typescript

Direzione di ricerca

Start by reading the bl text chat command and its --stream option handling, then trace how non-streaming Responses API requests with tools are sent and how headers timeouts are handled. Reproduce the reported non-TTY request with --api responses --tool and compare it with --stream. Done means the non-streaming tool request can return successfully, or the CLI handles the timeout as intended; add a regression test for the behavior.

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

Descrizione

Environment

  • CLI: bl 2.1.0
  • Skill: 2.1.0
  • Node: v25.9.0
  • OS: macOS 26.5.2 (arm64)
  • Region: cn-beijing (domestic; config profile token-plan, base_url https://token-plan.cn-beijing.maas.aliyuncs.com)

Reproduce

# Non-TTY (agent) invocation — systematically times out:
bl text chat --api responses --tool '{"type":"web_search"}' --timeout 300 \
  --system "Reply in 简体中文。" \
  --message "<a search question>"

# Same request with forced streaming — succeeds:
bl text chat --api responses --stream --tool '{"type":"web_search"}' --timeout 550 \
  --system "Reply in 简体中文。" \
  --message "<the same search question>"

Expected

Both invocations return the model's answer with web search results.

Actual

Without --stream: request systematically fails with headers timeout — Error: Network request failed: UND_ERR_HEADERS_TIMEOUT: Headers Timeout Error (exit 6) or Error: Request timed out ... This operation was aborted (exit 5). ~13 of 14 attempts failed over a period of hours; the single success took several minutes.

With --stream: 3/3 attempts succeeded, responses returned normally.

Analysis

bl text chat --help says --stream Stream response tokens (default: on in TTY). In non-TTY (agent/pipe) context the default is non-streaming, so the CLI waits for the full Responses-API + web_search run (multi-round searches, server-side) before receiving response headers — which reliably exceeds the gateway's headers timeout. Streaming receives headers early and works. Suggestion: for --api responses with tools (or in non-TTY generally), default to streaming, or automatically retry with streaming on UND_ERR_HEADERS_TIMEOUT.

Already tried

  • bl update / skill version aligned (2.1.0 across CLI, npm, skills)
  • Network ruled out: direct curl --noproxy '*' to the endpoint returns 404 in ~0.1s; same with system proxy — no local connectivity issue
  • --timeout raised to 550s — non-streaming still fails; streaming succeeds with the same timeout
  • Multiple retries over several hours: non-stream failure rate ~13/14, stream success 3/3

Notes

  • Frequency: always (non-streaming); none so far (streaming)
  • Invoked via: agent (non-TTY automation)
  • No request ID available: headers timeout means no response headers/ID were ever received
Lingua principale
TypeScript
Stelle
540
Fork
35
Merge medio
6h 43m
PR unite (30g)
23

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 modelstudioai/cli

Tutte le issue di modelstudioai/cli

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.