zed-industries/zed · error

language server for worktree and language not found

Error message

language server for worktree and language not found

What it means

In LspStore symbol/buffer resolution: no language server is registered for the given worktree and language, so the requested operation (e.g. opening a buffer for a symbol) cannot be routed to a server. Fires when a symbol lookup arrives before/without a running server for that language.

Source

Thrown at crates/project/src/lsp_store.rs:10138

                    version: None,
                    diagnostics: Vec::new(),
                },
                result_id: None,
                registration_id: None,
                server_id,
                disk_based_sources: Cow::Borrowed(&[]),
            })
            .collect::<Vec<_>>();
        self.merge_diagnostic_entries(diagnostic_updates, retain_diagnostic, cx)
            .context("clearing path diagnostics")
            .log_err();
    }

    pub fn merge_diagnostic_entries<'a>(
        &mut self,
        diagnostic_updates: Vec<DocumentDiagnosticsUpdate<'a, DocumentDiagnostics>>,
        merge: impl Fn(&lsp::Uri, &Diagnostic, &App) -> bool + Clone,
        cx: &mut Context<Self>,
    ) -> anyhow::Result<()> {
        let mut diagnostics_summary = None::<proto::UpdateDiagnosticSummary>;
        let mut updated_diagnostics_paths = HashMap::default();
        for mut update in diagnostic_updates {
            let abs_path = &update.diagnostics.document_abs_path;
            let server_id = update.server_id;
            let Some((worktree, relative_path)) =
                self.worktree_store.read(cx).find_worktree(abs_path, cx)
            else {
                log::warn!("skipping diagnostics update, no worktree found for path {abs_path:?}");
                continue;
            };

            let worktree_id = worktree.read(cx).id();
            let project_path = ProjectPath {
                worktree_id,
                path: relative_path,
            };

View on GitHub (pinned to 9d272b0363)

Solutions

  1. Ensure the relevant language extension/server is installed and running
  2. Wait for language servers to finish starting before triggering symbol navigation
Defensive patterns

Strategy: type-guard

When it happens

Trigger: Thrown at crates/project/src/lsp_store.rs:9419 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of zed-industries/zed@9d272b0363 (2026-08-20). Data as JSON: /api/errors/bf62dd0c280b1c97. Report an issue: GitHub.