Stable Homes cannot check for updates while a Test version is published

Abierto
  • ¿Algo no está bien?
#564 1 comentario 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
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
backend, release

Línea de trabajo

Start with the release head selection described in the issue and elastos/crates/elastos-server/src/update.rs, then trace how update check results reach gateway_home_update.rs and System, About. The issue says the publisher keeps a head per channel; check how Stable Homes obtain that head while preserving the existing refusal to downgrade or change channels. Done when Stable Homes report the Stable status during a Test release instead of a connection problem.

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

Descripción

While a Test version is published (now: 2.0.1-rc.1 since 9 Nov ~04:15 UTC), every Home on Stable cannot check for updates, and System, About tells it the wrong reason.

Facts:

  • The seed serves one head at the root for every channel: https://elastos.elacitylabs.com/release-head.json is 2.0.1-rc.1 with channel canary; no per-channel path (/channels/stable/release-head.json is not served).
  • A Stable Home's check refuses that head: Error: Signed release channel 'canary' differs from trusted source 'default' subscription 'stable'. To follow 'canary' releases on this Home, run: elastos source switch-channel 'default' 'canary', then try again. (update --check exit 1 on fresh Linux x86_64, Linux arm64 and macOS Homes on 9 Nov; report ~/omp-inbox/2.0.1-rc1-installed-checks.md). Same refusal in 2.0.0 (elastos/crates/elastos-server/src/update.rs:180 at v2.0.0).
  • System, About in 2.0.0 then shows "Could not check for updates. Check again when Carrier is connected." (gateway_home_update.rs at v2.0.0, None arm), which blames the connection. The refusal itself is right: no downgrade or channel change is offered.
  • 2.0.0 is the first stable with Homes in use, so this is the first rc window where it shows to people. It ends when the stable release is published.
  • The same root cause stops a stable-pinned launcher from installing during an rc window (Elacity/elastos-launcher#62, comment 6732364060), and fresh installs with the install command get the Test version.

Expected: a Stable Home keeps getting the newest Stable head while a Test version is out (the publisher keeps a head per channel), and a channel mismatch is reported as "You are up to date on Stable" rather than a connection problem.

Lenguaje dominante
Rust
Estrellas
6
Forks
2
Merge medio
1 d 3 h
PR fusionados (30 d)
42

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

  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 elastos/elastos-runtime

Todos los issues de elastos/elastos-runtime

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.