whitecat1331
1ff9082ced
SQLite fails fast with `SQLITE_BUSY` when another process holds the database lock. This database, and others like it, are shared between Zed instances. SQLite allows multiple readers at once, but only one writer at a time. Writes are short-lived, but if multiple Zed instances try to write to the file at the same time, the default fail-fast behavior throws `SQLITE_BUSY` and the write is dropped instead of retried. The fix is to keep trying the write for up to five seconds, so transient lock contention resolves and the write succeeds instead of erroring. A concrete case is the agent threads database (`threads.db`), which lives in the shared per-user data directory and is not namespaced by release channel. Running two Zed instances side by side means both can attempt to write to the same file at the same time, resulting in the error mentioned previously. Release Notes: - Fixed intermittent "database is locked" errors when sharing a database across Zed instances
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.