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

未关闭
#564 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
backend, release

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Rust
星标
6
派生
2
平均合并
1 天 3 小时
30 天内合并 PR
42

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

elastos/elastos-runtime 的其他 Issue

查看 elastos/elastos-runtime 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。