[Bug]: One 5s readiness-probe miss tears down a working SSH tunnel, so a briefly slow remote shows "reconnecting" loops

Offen
#39,798 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@juliusmarminge arbeitet bereits daran.

Seit 20.11.2026.

  • #39802 von @juliusmarminge — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
node.js, typescript
Bereich
backend, networking

Rechercherichtung

Read packages/ssh/src/tunnel.ts, especially ensureTunnelEntry and the readiness timeout handling. Check how waitForHttpReady distinguishes timeouts from a refused local port and an exited ssh -L process; the linked pull request #39802 is already addressing this issue. Done means a slow, live server keeps its tunnel while a dead tunnel is recreated.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Version: desktop 0.1.11-nightly.20261118.4890. Remote is a Linux VM over SSH whose disk sometimes stalls fsync for tens of seconds.

What happened

The remote environment showed "<host> is reconnecting" every few minutes. Every time, ssh/tunnel.ensureTunnelEntry probed the existing tunnel, got SshReadinessError: Timed out waiting 5000ms for backend readiness, closed the tunnel, and ran the full SSH launch again. The server was alive and unchanged throughout (same pid for the whole period). It was briefly slow, with event-loop stalls of 2–150 s recorded in event-loop-stalls.ndjson.

Cause

In packages/ssh/src/tunnel.ts, ensureTunnelEntry runs one waitForHttpReady with SSH_TUNNEL_READY_PROBE_TIMEOUT_MS = 5_000 against the existing forward. On any failure it deletes the entry and calls closeTunnelEntry, then createTunnelEntry. The new launch hits the same slow server, so it adds SSH round-trips and a second readiness wait instead of helping. It can also fail outright, for example with "still running but did not become ready" or a banner-exchange timeout while the host is stalled.

Expected

A slow but alive server keeps its tunnel. One way to get there:

  • Treat a probe timeout as "server slow": keep the forward and retry with backoff.
  • Recreate the forward only when the local port is refused or the ssh -L process has exited, meaning the tunnel itself is dead.

Created with Claude Opus 5.5 in Claude Code.

Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
4 Std. 29 Min.
Gemergte PRs (30 T.)
488

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.