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

Ouverte
  • Quelque chose ne va pas ?
#564 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
backend, release

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
6
Forks
2
Merge moyen
1 j 3 h
PR mergées (30 j)
42

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de elastos/elastos-runtime

Toutes les issues de elastos/elastos-runtime

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.