zed-industries/zed · error
No response received
Error message
No response received
What it means
generate_streaming finished consuming the Anthropic SSE stream without ever receiving a MessageStart event, so no message object was captured; the guard at the end reports that no response message arrived despite the stream completing.
Source
Thrown at crates/edit_prediction_cli/src/anthropic_client.rs:135
while let Some(event_result) = stream.next().await {
let event = event_result.map_err(|e| anyhow::anyhow!("{:?}", e))?;
match event {
Event::MessageStart { message } => {
response = Some(message);
}
Event::ContentBlockDelta { delta, .. } => {
if let anthropic::ContentDelta::TextDelta { text } = delta {
text_content.push_str(&text);
on_progress(text_content.len(), &text_content);
}
}
_ => {}
}
}
let mut response = response.ok_or_else(|| anyhow::anyhow!("No response received"))?;
if response.content.is_empty() && !text_content.is_empty() {
response
.content
.push(ResponseContent::Text { text: text_content });
}
Ok(response)
}
}
pub struct BatchingLlmClient {
connection: Mutex<sqlez::connection::Connection>,
http_client: Arc<dyn HttpClient>,
api_key: String,
}
struct CacheRow {View on GitHub (pinned to f4178619ac)
Solutions
- Retry the request; a stream that closes without MessageStart is abnormal but often transient
- Check for API outages or malformed request payloads if persistent
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at crates/edit_prediction_cli/src/anthropic_client.rs:135 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of zed-industries/zed@f4178619ac (2026-08-20).
Data as JSON: /api/errors/66d1a63a8e1951f1.
Report an issue: GitHub.