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
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
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Install a server with the VPS installer at version N.
- Publish N+1 for the desktop apps.
- Wait more than 2 hours. Check
ls /var/lib/omb-link/.config/duskbot-link/server-releaseandjournalctl -u duskbot-link | grep -i 'server build\|server update'.
Root cause (from source)
apps/link-service/src/app.mjsGET /v1/tunnels/:id/serverhands outpackages.current(), the build new installs get. If that is still 0.2.12, or the endpoint answers 404no_build,stage()inapps/link-service/agent.mjsreturnsnullwithout logging anything..github/workflows/release.ymldoes 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.jsonmoves with each release. - Log the result of each check, for example
link: server is up to date (0.2.12, offered 0.2.12)orlink: 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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 277
- Forks
- 27
- Merge medio
- 2 h 47 min
- PR fusionados (30 d)
- 1
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DuskBotAI/duskbot
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
Los mantenedores suelen responder en 1 día
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 pageAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443Posiblemente ocupada @viniciusbregoli la tomó hoy. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
Todos los issues de DuskBotAI/duskbot
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vercel-labs/ui#865 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
outline/outline#14638 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
wayfinder:grilling
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
midnightntwrk/platform-js#69 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 1 día