Desktop SSH probe failure diagnosis and signal handling
Cluster 80836 · apps/desktop. Data as of
2 open items. Fix merged in #122295 on 25 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #122295. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read #122295, then check whether your report is the one still open.
Read #122295Pick up a Lab taskThese items address a bug where the desktop app incorrectly reports a host as unreachable when the SSH probe process is killed by a signal, and add logging to better diagnose what SSH did when a connection attempt fails.
Open issues1
- Issue#80836[Bug]: Desktop SSH on macOS: probe connects then dies ~1s in; app reports "Could not reach that host over SSH" while the identical ssh command succeeds from the terminal
Open PRs1
- PR#80890fix(desktop): distinguish a signal-killed SSH probe child from a genuine unreachable failure
Fixes on record
-
#121436 fix(desktop): do not classify a signal-killed ssh child as unreachable
files:
apps/desktop/electron/ssh-connection.test.ts,apps/desktop/electron/ssh-connection.ts -
#122295 fix(desktop): log what ssh did when an SSH connect fails
files:
apps/desktop/electron/ssh-connection.test.ts,apps/desktop/electron/ssh-connection.ts
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab