## Summary Replace the broken rescan-warning rate limiter, which repeatedly emitted “not logging more” without advancing its counter. - Keep the last 10 queued path occurrences per watcher backend, preserving full paths. - Build and write rescan reports in the existing background dispatch task, keeping blocking log I/O off the native watcher reader. - Emit one error line per dispatched rescan after coalescing duplicate pathless rescans and before registration fan-out, containing the backend-provided reason, affected paths, and preceding paths. - Remove the redundant rescan warnings and rate-limit bookkeeping without changing rescan scheduling. - Add one focused test for the path history and report contents. ## Verification - `corgi test -p fs --lib` — 23 tests passed. - `corgi test -p fs --features test-support --test integration` — 24 tests passed. - `corgi fmt -p fs -- --check` - `git diff --check` Release Notes: - Improved filesystem watcher rescan diagnostics and removed repetitive “not logging more” warnings.
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 discussion)
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
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
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.