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

Abierto
#39,188 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

[!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.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
4 h 29 min
PR fusionados (30 d)
488

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.