Oliver Azevedo Barnes
9d40c471a0
Closes #47489 The search worker pool was sized as `num_cpus - 1`, which spawned zero workers when a devcontainer exposed only 1 CPU. All search channels closed immediately and the search yielded zero results, while file finder and LSP symbols worked fine. The fix ensures at least 1 worker is always spawned: `(num_cpus - 1).max(1)`. A `num_cpus` override on `TestDispatcher` and a new test reproduce the bug with `server_cx.executor().set_num_cpus(1)`. ## Manual testing Add a `.devcontainer/` directory to a new project with these files: ``` // docker-compose.yml services: dev: image: debian:bookworm-slim cpuset: "0" volumes: - ..:/workspace:cached command: sleep infinity ``` ``` // devcontainer.json { "name": "zed-sandbox (1 CPU)", "dockerComposeFile": "docker-compose.yml", "service": "dev", "workspaceFolder": "/workspace" } ``` Build zed and point it at the new project: ``` cargo run -p zed -- ~/Repos/zed-sandbox-project ``` Open the built-in terminal, confirm `nproc` prints `1`. Finally, run a project search (`Cmd+Shift+F`) and search for contents that exist in it. Results should appear 🎉 Release Notes: - Fixed project search returning no results in devcontainers with a single visible CPU.
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.