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

Aperta
#8 1 commento 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
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, typescript
Ambito
devops, release

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
TypeScript
Stelle
277
Fork
27
Merge medio
2h 47m
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 DuskBotAI/duskbot

Tutte le issue di DuskBotAI/duskbot

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.