smit
5c5caf1ffe
Closes #22666 This PR fixes the long wait time to open Zed (2 mins in my case) after reloading on Linux. This bug fix is funny: 1. We were using TCP for Zed instances to talk to each other. Reload was broken here too due to TCP connections not being killed on time. 2. [#11488](https://github.com/zed-industries/zed/pull/11488) PR fixed the TCP connection issue by adding a wait until it gets killed. I suppose at that time, this wait time was small. 3. Later, we changed how Zed talks to each other in [#11585](https://github.com/zed-industries/zed/pull/11585) by using Datagram and removing TCP. The new approach simply uses a `.sock` file and a file descriptor to check if some program is listening to it. 4. TCP check is now unnecessary, and it still wait for a long time (I suppose, TIME_WAIT time, don't quote me on this), even though we don’t use TCP anymore for this. This PR just removes that unnecessary TCP wait. Release Notes: - Fixed issue where reload hangs for several minutes on Linux.
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
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.