zed-industries/zed · error
Failed to flush output
Error message
Failed to flush output
What it means
A panic in the edit-prediction CLI when flushing the buffered output writer after writing results fails — typically disk full or I/O error on the output file. Buffered results would be lost, so the CLI aborts rather than silently truncate output.
Source
Thrown at crates/edit_prediction_cli/src/main.rs:1283
temp
} else {
output_path.clone()
};
let file = OpenOptions::new()
.create(true)
.write(true)
.truncate(args.in_place)
.append(!args.in_place)
.open(&write_path)
.expect("Failed to open output file");
let mut writer = BufWriter::new(file);
let (sender, mut receiver) = mpsc::unbounded::<String>();
cx.background_spawn(async move {
while let Some(line) = receiver.next().await {
writeln!(writer, "{}", line).expect("Failed to write example");
writer.flush().expect("Failed to flush output");
}
})
.detach();
output_sender = Some(sender);
}
let example_batches = if args.group_by_repo {
group_examples_by_repo(examples)
} else {
chunk_examples(examples, args.max_parallelism)
};
let example_batches = Mutex::new(example_batches);
let finished_examples = Mutex::new(Vec::new());
let mut tasks = Vec::new();
for _ in 0..args.max_parallelism {
tasks.push(async {
loop {View on GitHub (pinned to f4178619ac)
Solutions
- Free disk space and re-run with resume enabled
- Inspect the output file for missing trailing lines
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at crates/edit_prediction_cli/src/main.rs:1283 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/3c3a5af3ff21cd12.
Report an issue: GitHub.