Richard Feldman
d986344da5
PR #51415 introduced the `PlatformHeadlessRenderer` trait and `PlatformWindow::render_to_image` method in `gpui`, both gated on `#[cfg(any(test, feature = "test-support"))]`, plus corresponding impls in `gpui_macos` (`window.rs` and `metal_renderer.rs`) gated on the same cfg. A dependent crate's `cfg(test)` flag does **not** propagate to its dependencies. So when `cargo test -p gpui_macos` is run in isolation, `gpui_macos`'s own `cfg(test)` is true (its impls get compiled) but `gpui` is just a regular dependency without `test-support` enabled (the trait and method don't exist), and the build fails: ``` error[E0405]: cannot find trait `PlatformHeadlessRenderer` in crate `gpui` error[E0407]: method `render_to_image` is not a member of trait `PlatformWindow` ``` The fix is to enable `gpui/test-support` as a dev-dependency, so the feature is on exactly when `gpui_macos`'s tests are being built. This bug is latent on `main` — workspace-level `cargo test` typically pulls in `gpui/test-support` transitively from other crates, masking it. Running `cargo test -p gpui_macos` alone is what surfaces it. Release Notes: - N/A
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.