zed-industries/zed · error

{channel} recv: {err}

Error message

{channel} recv: {err}

What it means

Wrapper error formatting a runtimelib receive failure on a Jupyter kernel channel (parse or serde error): a message read from the kernel socket could not be decoded. The sentinel "{channel} recv: {err}" carries the channel name and underlying cause.

Source

Thrown at crates/repl/src/kernels/mod.rs:146

                            })
                            .ok();
                    }
                    Err(
                        ref err @ (runtimelib::RuntimeError::ParseError { .. }
                        | runtimelib::RuntimeError::SerdeError(_)),
                    ) => {
                        let error_detail = format!("Kernel issue on {channel} channel\n\n{err}");
                        log::warn!("kernel: {error_detail}");
                        session
                            .update_in(cx, |session, _window, cx| {
                                session.kernel_errored(error_detail, cx);
                                cx.notify();
                            })
                            .ok();
                    }
                    Err(err) => {
                        log::warn!("kernel: error reading from {channel}: {err:?}");
                        anyhow::bail!("{channel} recv: {err}");
                    }
                }
            }
        }
    });

    let routing_task = cx.background_spawn(async move {
        while let Some(message) = request_rx.next().await {
            match message.content {
                JupyterMessageContent::DebugRequest(_)
                | JupyterMessageContent::InterruptRequest(_)
                | JupyterMessageContent::ShutdownRequest(_) => {
                    control_send.send(message).await?;
                }
                _ => {
                    shell_send.send(message).await?;
                }
            }

View on GitHub (pinned to f4178619ac)

Solutions

1. Restart the kernel from the REPL panel
2. Check kernel logs (logged as a warning) for the decode failure detail
3. Update ipykernel/jupyter on the remote environment if protocol mismatches persist

When it happens

Trigger: Thrown at crates/repl/src/kernels/mod.rs:146 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/ad53ebaee0203cea. Report an issue: GitHub.