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

未关闭
#39,188 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
desktop

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
TypeScript
星标
24.8k
派生
6.4k
平均合并
4 小时 29 分钟
30 天内合并 PR
488

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。