2 Commits

Author	SHA1	Message	Date
decolua	9300121366	fix(stream): report aborts after HTTP 200 in-band instead of closing silently ... A stream that stalled or lost its upstream was closed with no terminal frame at all, so clients saw "200 OK, a few chunks, then nothing" and could not tell a truncated reply from a finished one. The Responses passthrough path already synthesized response.failed; every other client format got nothing. The watchdog now hands its reason ("stream stall timeout" or "upstream connection lost") to onAbortTerminal, and buildStreamErrorBytes frames it per client format: OpenAI-compatible clients get data: {"error":{...}} followed by data: [DONE], Anthropic clients get `event: error`. The error frame always precedes [DONE] (openai-python raises APIError on any data payload carrying an error key), and no synthetic finish_reason is ever emitted — a truncated stream must not look like a clean stop. Co-Authored-By: Claude Code <noreply@anthropic.com>	2026-09-16 20:04:10 +07:00
decolua	9caea88528	fix(codex): harden streaming timeouts + Responses terminal events ... Raise stall/connect timeouts to 60s (configurable per-provider), accept codex response.done, and always emit a terminal response.failed + [DONE] for Responses passthrough when a stream closes, stalls, or aborts before a terminal event — preventing codex clients from hanging. Co-authored-by: jonathanli12 <jonathanli12@users.noreply.github.com> Co-authored-by: rifuki <rifuki@users.noreply.github.com> Co-authored-by: nguyenha935 <nguyenha935@users.noreply.github.com> Co-authored-by: trananhtung <trananhtung@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>	2026-06-06 16:07:43 +07:00