Cause (Documented platform behavior): The helpers build a message snapshot starting at message_start; ending the request with no snapshot throws 'request ended without sending any chunks' (TS), finalMessage without an assistant message throws 'stream ended without producing a Message with role=assistant', a second message_start before message_stop (TS) or any event before message_start (Python) raises 'Unexpected event order ...'.
Fix status: documented_behavior
Limitations:
- Mapping of specific gateways to these symptoms not established from reports; derived from SDK source.
Other error fragments:
- stream ended without producing a Message with role=assistant
- Unexpected event order, got ${event.type} before receiving "message_stop"
- Unexpected event order, got {event.type} before "message_start"
Evidence (public sources, summarized; not reproduced by this contributor):
- https://registry.npmjs.org/@anthropic-ai/sdk/-/sdk-0.128.0.tgz#package/lib/MessageStream.js (github_source, unknown, documented_behavior): _endRequest throws 'request ended without sending any chunks' without snapshot; accumulate throws 'Unexpected event order, got ... before receiving "message_stop"'; finalMessage throws 'stream ended without producing a Message with role=assistant'.
- https://files.pythonhosted.org/packages/5b/18/5d25a703b66ba34e9277f875f692a3bea3b0ff4d47ee5d188521a01cdd2a/anthropic-1.8.0-py3-none-any.whl#anthropic/lib/streaming/_messages.py (github_source, unknown, documented_behavior): accumulate_event raises RuntimeError('Unexpected event order, got {event.type} before "message_start"').
Search phrasings: anthropic request ended without sending any chunks; Unexpected event order got content_block_delta before message_start; anthropic stream ended without producing a Message with role=assistant proxy
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- The streaming helper throws accumulator errors instead of an HTTP/API error, even though the HTTP status was 200; raw (non-helper) streaming may silently yield nothing.
- Context
- Product: Anthropic TypeScript SDK / Anthropic Python SDK (messages.stream helpers) Component: MessageStream accumulator Operation: client.messages.stream(...) through LLM gateways, Anthropic-compatible proxies, or buffering proxies Affected versions: unknown Environment: unknown Exception: AnthropicError, RuntimeError Packages: @anthropic-ai/sdk checked 0.128.0, anthropic checked 1.8.0 Trigger: Gateway returns a 200 JSON (non-stream) body, an empty stream, events without message_start first, or concatenates two messages without message_stop.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- request ended without sending any chunks
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Anthropic SDKs via gateways/proxies] Streaming helpers fail with 'request ended without sending any chunks' (TS), 'stream ended without producing a Message with role=assistant', or 'Une
Recommended action: Verify the intermediary supports Anthropic SSE streaming unchanged (content-type text/event-stream, event order message_start ... message_stop); test with the raw stream (stream=True) to see what arrives; fall back to non-streaming through gateways that do not stream.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- d15b5a4c-fd51-405c-af8a-bd43ad7d66b3
- Proposed action
- Recommended action: Verify the intermediary supports Anthropic SSE streaming unchanged (content-type text/event-stream, event order message_start ... message_stop); test with the raw stream (stream=True) to see what arrives; fall back to non-streaming through gateways that do not stream.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.