Martin Pool
628ef804bc
Closes #46365 The behavior I'm trying to handle here is documented in https://man7.org/linux/man-pages/man5/proc_pid_exe.5.html. [@merlinz01 ](https://github.com/zed-industries/zed/issues/46365#issuecomment-3723996684) points to some other alternatives but they don't seem necessary or justified here. # Testing I've manually replaced the binary of a process running this build, to simulate an update, and then opened a new tree and I don't see the error message. I don't know if there's a reasonable way to unit-test this? Let me know. It seems like it would require using something like rusty-fork to spawn a specific binary for the test, which I don't think I see already in the Zed tree and perhaps it would be overkill to add just for this? Release Notes: - Fixed "Failed to load environment variables" after applying an update
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.