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

Aberta
  • Algo errado?
#564 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
backend, release

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
6
Forks
2
Merge médio
1d 3h
PRs com merge (30d)
42

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de elastos/elastos-runtime

Todas as issues de elastos/elastos-runtime

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.