Fix Failed to load environment variables error message after self-update on Linux#46367
Merged
Veykril merged 1 commit intozed-industries:mainfrom Jan 13, 2026
Merged
Conversation
cla-bot
Bot
added
the
cla-signed
github-actions
Bot
added
the
community champion
sourcefrog
changed the title
sourcefrog
force-pushed
the
46365-deleted-exe
branch
from
62299f2 to
03a29a2
Compare
Contributor
sourcefrog
changed the title
Failed to load environment variables error message after self-update on Linux
Contributor
Author
|
@SomeoneToIgnore if it's no trouble, could you take a look or assign someone? Thanks! |
Veykril
approved these changes
Jan 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
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: