recent_projects: Fix remote reconnect when server is not running#49834
Merged
Veykril merged 1 commit intozed-industries:mainfrom Feb 23, 2026
Merged
Conversation
When an existing remote workspace's connection is dead (e.g. server died and reconnect failed, leaving the client in ServerNotRunning state), `remote_connection()` returns `None`. Previously this caused an error, blocking reconnection. Now the code falls through to establish a fresh connection instead.
|
We require contributors to sign our Contributor License Agreement, and we don't have @mangas on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'. |
Contributor
Author
|
@cla-bot check |
|
We require contributors to sign our Contributor License Agreement, and we don't have @mangas on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'. |
|
The cla-bot has been summoned, and re-checked this pull request! |
Contributor
Author
|
Tested manually and it works for me. Let me know if there's anything else to get it merged. |
Contributor
Author
|
@cla-bot check |
|
The cla-bot has been summoned, and re-checked this pull request! |
Contributor
Author
|
Member
|
/cherry-pick preview |
github-actions bot
pushed a commit
that referenced
this pull request
Feb 23, 2026
) Closes #49363 When an existing remote workspace's connection is dead (e.g. the server died and reconnect failed, leaving the client in `ServerNotRunning` state), `remote_connection()` returns `None`. Previously this caused an error dialog, blocking reconnection — the user had to manually switch to another project and back to recover. Now the code falls through to establish a fresh connection instead, matching the previous behavior where clicking "Reconnect" would just work. Release Notes: - Fixed remote reconnect failing with an error when the server is not running, now establishes a fresh connection instead.
Contributor
|
🍒💥 Cherry-pick did not succeed |
Veykril
pushed a commit
that referenced
this pull request
Feb 25, 2026
) Closes #49363 When an existing remote workspace's connection is dead (e.g. the server died and reconnect failed, leaving the client in `ServerNotRunning` state), `remote_connection()` returns `None`. Previously this caused an error dialog, blocking reconnection — the user had to manually switch to another project and back to recover. Now the code falls through to establish a fresh connection instead, matching the previous behavior where clicking "Reconnect" would just work. Release Notes: - Fixed remote reconnect failing with an error when the server is not running, now establishes a fresh connection instead.
Veykril
pushed a commit
that referenced
this pull request
Feb 25, 2026
) (cherry-pick to preview) (#49871) Cherry-pick of #49834 to preview ---- Closes #49363 When an existing remote workspace's connection is dead (e.g. the server died and reconnect failed, leaving the client in `ServerNotRunning` state), `remote_connection()` returns `None`. Previously this caused an error dialog, blocking reconnection — the user had to manually switch to another project and back to recover. Now the code falls through to establish a fresh connection instead, matching the previous behavior where clicking "Reconnect" would just work. Release Notes: - Fixed remote reconnect failing with an error when the server is not running, now establishes a fresh connection instead. Co-authored-by: Filipe Azevedo <filipe@azevedo.io>
Anthony-Eid
pushed a commit
to bobbymannino/zed
that referenced
this pull request
Feb 25, 2026
…-industries#49834) Closes zed-industries#49363 When an existing remote workspace's connection is dead (e.g. the server died and reconnect failed, leaving the client in `ServerNotRunning` state), `remote_connection()` returns `None`. Previously this caused an error dialog, blocking reconnection — the user had to manually switch to another project and back to recover. Now the code falls through to establish a fresh connection instead, matching the previous behavior where clicking "Reconnect" would just work. Release Notes: - Fixed remote reconnect failing with an error when the server is not running, now establishes a fresh connection instead.
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
2 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 #49363
When an existing remote workspace's connection is dead (e.g. the server died and reconnect failed, leaving the client in
ServerNotRunningstate),remote_connection()returnsNone. Previously this caused an error dialog, blocking reconnection — the user had to manually switch to another project and back to recover.Now the code falls through to establish a fresh connection instead, matching the previous behavior where clicking "Reconnect" would just work.
Release Notes: