zed-industries/zed · error · anyhow::Error

Failed to shutdown kernel: {}

Error message

Failed to shutdown kernel: {}

What it means

Raised in RemoteRunningKernel::force_shutdown(): the DELETE /kernels/{kernel_id} request to the remote Jupyter server returned a non-success status, so the remote kernel could not be terminated. The status is embedded in the error returned by the shutdown task.

Source

Thrown at crates/repl/src/kernels/remote_kernels.rs:294

    }

    fn force_shutdown(&mut self, window: &mut Window, cx: &mut App) -> Task<anyhow::Result<()>> {
        let url = self
            .remote_server
            .api_url(&format!("/kernels/{}", self.kernel_id));
        let token = self.remote_server.token.clone();
        let http_client = self.http_client.clone();

        window.spawn(cx, async move |_| {
            let request = Request::builder()
                .method("DELETE")
                .uri(&url)
                .header("Authorization", format!("token {}", token))
                .body(AsyncBody::default())?;

            let response = http_client.send(request).await?;

            anyhow::ensure!(
                response.status().is_success(),
                "Failed to shutdown kernel: {}",
                response.status()
            );
            Ok(())
        })
    }

    fn kill(&mut self) {
        self.request_tx.close_channel();
        self.stdin_tx.close_channel();
    }
}

View on GitHub (pinned to f4178619ac)

Solutions

1. Check that the kernel id still exists on the remote server
2. Verify remote server connectivity and token

When it happens

Trigger: Thrown at crates/repl/src/kernels/remote_kernels.rs:294 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/6740832a86325ee5. Report an issue: GitHub.