Arthur Jean
45ca651f43
## Summary Fixes #48289 Closes https://github.com/zed-industries/zed/issues/52021 Diagnostic error markers (red/yellow dots) in the project panel file tree persisted after errors were resolved. Three root causes: - **WorktreeUpdatedEntries ignored** — when files changed on disk (e.g. `yarn install`), stale diagnostic summaries were never cleared. Added `invalidate_diagnostic_summaries_for_updated_entries()` to clear summaries for `Removed`/`Updated`/`AddedOrUpdated` paths. - **Missing DiagnosticsUpdated emission on server stop** — `stop_local_language_server()` cleared summaries and sent proto messages but never emitted `LspStoreEvent::DiagnosticsUpdated`, so the project panel never refreshed. - **Buffer reload not handled** — reloading a buffer from disk did not clear stale summaries. Added `BufferEvent::Reloaded` handler. All three paths also send zeroed `UpdateDiagnosticSummary` proto messages to downstream collab clients. ## Test plan - [x] `./script/clippy` passes - [x] `cargo test -p project -p project_panel -p worktree` passes (319 tests, 0 failures) - [x] 4 new tests added: - `test_diagnostic_summaries_cleared_on_worktree_entry_removal` - `test_diagnostic_summaries_cleared_on_worktree_entry_update` - `test_diagnostic_summaries_cleared_on_server_restart` - `test_diagnostic_summaries_cleared_on_buffer_reload` - [x] Manual testing: error markers clear when files change on disk - [x] Manual testing: error markers clear on LSP restart Release Notes: - Fixed stale diagnostic data persisting after file reloads, server restarts and FS entry removals
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.