Desktop gives up on a slow-exiting old server after 10 s and never retries, so it sits with no backend after the home frees

Aperta
#39,188 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
desktop

Direzione di ricerca

Start by tracing DesktopHomeOwner.isHomeOwnershipLocked and the bootstrap path that waits for server-owner.sqlite; the issue also points to DesktopBackendPool's onStateDirOwned handling for exit code 78. Check how server-runtime.json identifies the owner and how backend startup responds when the lock is released. Done means bootstrap retries after the old server exits and starts the backend without requiring a dialog dismissal or app restart.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

[!NOTE]
Written by Claude Opus 5.5 on behalf of @WhiteWarrior625

Desktop gives up on a slow-exiting old server after 10 s and never retries, so it sits with no backend after the home frees

Linux AppImage, 0.1.11-nightly.20261119.4941, which includes #34932.

#34932 made bootstrap wait BACKEND_QUIT_STOP_TIMEOUT + 3 s for a draining owner to release server-owner.sqlite. When the old server takes longer than that, bootstrap shows the modal "This T3 home is unavailable" and starts no backend. It does not check the lock again, so the window stays up with no backend after the old server is gone, until someone dismisses the dialog or restarts the app.

What happened here (2026-11-19, times EST):

  • 10:54:46: the previous desktop was ended during an update restart. Its server did not go with it: on Linux it runs in its own systemd scope (app-com.t3tools.T3Code-<pid>.scope), and it ran from the old AppImage mount.
  • 10:54:52: the new desktop started. DesktopHomeOwner.isHomeOwnershipLocked ran 40 times, 250 ms apart, from 10:54:53 to 10:55:03. Then bootstrap stopped: no backend start was requested.
  • 10:55:40: the old server exited (SIGBUS, when its AppImage mount went away) and released the lock, 37 s after the desktop stopped waiting.
  • The window stayed up with no backend until a manual restart at 11:01.

Possible fixes:

  1. After the grace, keep polling (or watch the lock) while server-runtime.json names an owner whose desktop is gone, and start the backend when the lock frees.
  2. Or show a non-modal state that retries when the lock frees, instead of a blocking dialog with nothing behind it.

The other path to the same dialog, DesktopBackendPool onStateDirOwned on exit code 78, may want the same retry. We worked around it locally by making our update restart wait for the old server to release the home before starting the desktop.

Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
4h 29m
PR unite (30g)
488

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pingdotgg/t3code

Tutte le issue di pingdotgg/t3code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.