zed-industries/zed · error
Failed to send to output writer
Error message
Failed to send to output writer
What it means
Panics when sending an example's serialized line to the output-writer task via the mpsc channel fails — the writer task has shut down (e.g. after a prior write error), so remaining examples cannot be recorded.
Source
Thrown at crates/edit_prediction_cli/src/main.rs:1449
false
};
let should_write = !failed || args.failed == FailedHandling::Keep;
if should_write {
if args.markdown {
let markdown_dir =
output.as_ref().expect("--markdown requires -o");
let filename = format!("{}.md", example.spec.filename());
let path = markdown_dir.join(&filename);
let markdown = example.spec.to_markdown();
std::fs::write(&path, &markdown)
.expect("Failed to write markdown file");
} else if let Some(ref mut sender) = output_sender.clone() {
let line = serde_json::to_string(&example).unwrap();
sender
.send(line)
.await
.expect("Failed to send to output writer");
} else if args.output.is_none()
&& !matches!(command, Command::Eval(_))
{
let line = serde_json::to_string(&example).unwrap();
println!("{}", line);
}
}
}
let project = repo_examples
.iter()
.find_map(|e| e.state.as_ref().map(|s| s.project.clone()));
if let Some(project) = project {
let mut cx = cx.clone();
let shutdown_task: Task<()> =
project.update(&mut cx, |project, cx| {View on GitHub (pinned to f4178619ac)
Solutions
- Look earlier in the log for the writer task's underlying I/O error
- Re-run with resume to repopulate the output file
- Avoid killing the process mid-write
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at crates/edit_prediction_cli/src/main.rs:1449 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/eab7b0f22f1effbd.
Report an issue: GitHub.