zed-industries/zed · error

Could not send write action to background thread

Error message

Could not send write action to background thread

What it means

A panic in the sqlez background write queue: the worker thread's sender failed while enqueueing a write, meaning the sqlezWorker thread has exited (e.g. panicked earlier) while the connection is still open. Further writes cannot be persisted, so the caller aborts.

Source

Thrown at crates/sqlez/src/thread_safe_connection.rs:301

    use std::sync::mpsc::channel;

    Box::new(|| {
        let (sender, receiver) = channel::<QueuedWrite>();

        thread::Builder::new()
            .name("sqlezWorker".to_string())
            .spawn(move || {
                while let Ok(write) = receiver.recv() {
                    write()
                }
            })
            .unwrap();

        let sender = UnboundedSyncSender::new(sender);
        Box::new(move |queued_write| {
            sender
                .send(queued_write)
                .expect("Could not send write action to background thread");
        })
    })
}

pub fn locking_queue() -> WriteQueueConstructor {
    Box::new(|| {
        let write_mutex = Mutex::new(());
        Box::new(move |queued_write| {
            let _lock = write_mutex.lock();
            queued_write();
        })
    })
}

#[cfg(test)]
mod test {
    use indoc::indoc;
    use std::ops::Deref;

View on GitHub (pinned to f4178619ac)

Solutions

1. Rebuild the worker thread and channel when send fails
2. Avoid panics inside worker write callbacks that kill the thread
3. Propagate an error to the write caller

When it happens

Trigger: Thrown at crates/sqlez/src/thread_safe_connection.rs:301 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/7db02b305b192d6c. Report an issue: GitHub.