Piotr Osiewicz
14bf07c916
It was possible to unload a root of worktree when it was a .git directory; due to that, test_fs_events_in_dot_git_worktree was sometimes stuck in an infinite loop on CI. The gist of an issue is that when .git dir is a root dir, then modifying a file within this directory could sometimes unload the .git dir; the test went into an infinite loop when the first event in an filesystem stream was not the event for the file creation, but for a dir modification. In that case we'd unload the root directory and a subsequent event for file creation would never be registered, leading to the test being stuck waiting for it to happen. This commit alleviates it by special-casing worktrees rooted in .git directories. Release Notes: - Fixed a possible hang when opening a worktree in .git directory.
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
You can download Zed today for macOS (v10.15+).
Support for additional platforms is on our roadmap:
- Linux (tracking issue)
- Windows (tracking issue)
- Web (tracking issue)
For macOS users, you can also install Zed using Homebrew:
brew install --cask zed
Alternatively, to install the Preview release:
brew install --cask zed@preview
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
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.