Released 1.10.0 reports stale installed/running 1.9.370 in bridge_list

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Closed bug report

John Lauer · 2mo ago ·closed by John Lauer

After bridge_install using the insiders fusion-bridge/version.json succeeded with version 1.10.0 (5147 ms), bridge_list on arav-rog repeatedly reports contradictory version fields:

version: 1.10.0 installedVersion: 1.9.370 runningVersion: 1.9.370 versionDrift: false manifestSource: insidersManifestUrl latest: 1.9.370

The cache BRIDGE_VERSION file reads 1.10.0, and the spawned bridge's fusion_readiness reply reports bridgeVersion 1.10.0. Thus this appears to be stale bridge-list version telemetry, not established evidence of a downgrade. The cache is unpinned. Please reconcile installed/running version readback and drift reporting so installed-release acceptance can rely on the public lifecycle view. This may require an Adom Bridge fix rather than a Fusion runtime change.

1 Reply

John Lauer · 2mo ago

Confirmed, and it is not this bridge's readback: the rows come from ab's bridge registry (the bridge_list verb of Adom Bridge), which keeps a snapshot from the last time it looked and does not re-read the cache manifest or the live process after bridge_install / bridge_dev_mode. Today all four boxes had the same drift: the cache BRIDGE_VERSION and the running exe (fusion_readiness.bridgeVersion) both said 1.10.0 while bridge_list still said 1.9.365 (CRR, pinned), 1.9.370 (arav-rog) and 1.10.0-dev.routing.5 (AdomLapper, pinned). refresh_bridges did not reconcile it either.

Filed on the owner with the three-box table: adom/adom-bridge#160. Until that lands, the acceptance read for an installed release is fusion_readiness (bridgeVersion comes from the running exe) plus the cache's BRIDGE_VERSION file, not bridge_list. Closing here since nothing in fusion-bridge can change those rows.

John Lauer closed this · 2mo ago