Mac source Home: Browser shows 'needs preparation' (unstamped image row, missing TURN program, config-only exit) #477

Activity

1. andersalm

   added this to the After 0.8.0 milestone on Oct 22, 2026
2. andersalm commented on Oct 22, 2026

   

   andersalm

   on Oct 22, 2026

   Last edited by andersalm

   ContributorAuthor

   More actions

   Two more source-Home gaps from the same check (22 Oct):

   • TURN program missing: build-and-setup-source-home.sh forces SETUP_SOURCE_HOME_RUNTIME_TURN=0, so the Browser config on a Mac never gets ELASTOS_BROWSER_VM_TURN_PROGRAM. The Engine readiness probe (browser-vm-artifact-preflight.sh --host-readiness) then reports preparation_required, and Browser shows "needs preparation" even after the image row is fixed. Writing the config with ELASTOS_BROWSER_VM_TURN_PROGRAM set gives ready.
   • Config-only setup exits at once: SETUP_SOURCE_HOME_CONFIG_ONLY=1 exits 1 because require_source_engine_bundle uses [[ … ]] || return under set -e.

   From the source, the packaged setup path writes a stamped image row and configures TURN: elastos setup takes the release's turnserver helper (elastos/crates/elastos-server/src/setup/browser_config.rs:452 at 26f7c7589) and writes it into the Browser config as ELASTOS_BROWSER_VM_TURN_PROGRAM (line 487). This is source-path reasoning. The exact packaged Mac installation and the alpha.24 update to the new image still need acceptance. One fix for all three, with a source-Home Browser readiness test.
3. andersalm

   changed the title [-]Mac source Home: Browser can't prepare a locally staged image while components.json keeps the template's unstamped browser-vm-image row[/-] [+]Mac source Home: Browser shows 'needs preparation' (unstamped image row, missing TURN program, config-only exit)[/+] on Oct 22, 2026
4. andersalm commented on Oct 23, 2026

   

   andersalm

   on Oct 23, 2026

   ContributorAuthor

   More actions

   Another source-Home gap, same kind: Apps → Models is empty. setup-source-home copies the model_catalog pin from components.json (head bafkreid5…in7z4) but never installs model-catalog.json beside it. So model_catalog_entries fails (elastos/crates/elastos-server/src/api/capsule_inventory.rs:102-116; read model gateway_capsule_catalog/read_model.rs:64). At startup the gateway logs "Local AI model catalogue unavailable: model catalog pin is present but model-catalog.json is missing".

   Release path: not affected. The catalog is a release artifact, admitted by scripts/release-platform-input.py admit_model_catalog_artifact and written by setup through SignedSetupMetadata::install (setup.rs:698). An installed Home on this Mac has the same 3,550 B file, head CID equal to the pin.

   Fix: have setup-source-home fetch model-catalog.json from the publisher and check its head CID against the pin before writing it (or take it from a local path). A source-Home test should assert that the catalog state is verified.

   Workaround used on the 0.8.0 test Home: fetched https://elastos.elacitylabs.com/artifacts/model-catalog.json, checked that its raw CIDv1 equals the pinned head_cid, and installed it as <data dir>/model-catalog.json (mode 600). No restart is needed, because the catalog is read on each request.