Own server stayed on 0.2.12 while 0.2.13, 0.2.14 and 0.2.15 shipped; the link updater never offered a build and logs nothing

未关闭
#8 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with apps/link-service/src/app.mjs and apps/link-service/agent.mjs to trace how the server build is offered and why a failed check is silent; then inspect .github/workflows/release.yml and scripts/build-vps-package.mjs for release publishing. Confirm what the release workflow publishes and how checks are logged; done means the VPS package is published with releases and the updater reports each check result. The issue proposes several changes spanning release infrastructure, the link agent, and desktop app behavior.

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

描述

Version

Server 0.2.12 (installed 16 Nov 22:32 WIB / 15:32 UTC by the desktop's Add your VPS flow), link agent 2.4.4. Desktop apps meanwhile on 0.2.14 (Mac) and 0.2.15 released.

Platform

Own server (VPS)

Environment

Windows 11 + WSL2 Ubuntu 24.04, systemd units duskbot, duskbot-link, duskbot-server-update.timer (active), state signed=1.

What happened

Expected: createServerUpdater() in the link agent stages the newest signed server build, and install.sh --update-server installs it when idle.

Actual: the fresh install itself got 0.2.12, even though 0.2.13 had been on the releases page since 16 Nov 13:55 UTC, about 1.5 hours earlier. Over the next 12.7 hours, 0.2.14 (16 Nov 18:46 UTC) and 0.2.15 (17 Nov 03:15 UTC) shipped, and nothing was ever staged. ~omb-link/.config/duskbot-link/server-release/ does not exist, server-update.log is empty, and the link journal has no server build ... is staged or no server update (...) line. The Mac app 0.2.14 then called /api/feedback, which only exists from 0.2.13 (see #9). I had to update by hand from the release .deb.

Steps to reproduce
  1. Install a server with the VPS installer at version N.
  2. Publish N+1 for the desktop apps.
  3. Wait more than 2 hours. Check ls /var/lib/omb-link/.config/duskbot-link/server-release and journalctl -u duskbot-link | grep -i 'server build\|server update'.
Root cause (from source)
  • apps/link-service/src/app.mjs GET /v1/tunnels/:id/server hands out packages.current(), the build new installs get. If that is still 0.2.12, or the endpoint answers 404 no_build, stage() in apps/link-service/agent.mjs returns null without logging anything.
  • .github/workflows/release.yml does not build or publish the VPS package (scripts/build-vps-package.mjs --publish), so the VPS build looks like it is published separately and lagged behind the desktop releases.
Suggested fix
  • Publish the signed VPS package in the same release job as the desktop apps, so current.json moves with each release.
  • Log the result of each check, for example link: server is up to date (0.2.12, offered 0.2.12) or link: no server build published (404).
  • Have the desktop app warn when the connected server is older than the app, with an Update server button that triggers the check.
Workaround

Install the server from the release .deb by hand: copy opt/dusk-bot/resources/{server,ui,skills} over dist-server, dist and skills of the npm layout. For 0.2.12 every shared file matched byte for byte.

主要语言
TypeScript
星标
277
派生
27
平均合并
2 小时 47 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

DuskBotAI/duskbot 的其他 Issue

查看 DuskBotAI/duskbot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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