Journey event  ·  14 Sep 2026

Deploy hot-synced SPA static (bundle index-B2R-r53j.js) is not in the dsc-hub-brain:8.3.0 image – the next container recreate reverts the span-picker popover fi

NO LONGER APPLICABLE 2026-09-14 20:40 (verified live): the PR #267 (19:55) and PR #268 (20:22) deploys were both image-builds from master, so the image now carries the current SPA

  state copied from the tracker, never improved

  event date 2026-09-14

Event date 2026-09-14
Version found
Version fixed
Expected kit firmware
Release file
SHA-256
Served count
Source https://app.notion.com/3db2b4cda370815493c4d456235979d6

NO LONGER APPLICABLE 2026-09-14 20:40 (verified live): the PR #267 (19:55) and PR #268 (20:22) deploys were both image-builds from master, so the image now carries the current SPA static. Live /health reports 8.3.0 and the served bundle is index-CLihF9Oj.js — the #268 image-build bundle — so a container recreate no longer reverts the span-picker fix. Rule kept in memory: after a docker-cp hot-sync, the next deploy must be an image-build. — ORIGINAL: To avoid a third container recreate (each one costs a Sonoff failsafe burst while the hub session re-attaches), the PR #263 CSS fix was shipped by copying spa-dist into the running container and into /opt/dsc-hub-repo/brain/static only. The image the compose file recreates from was built from master b641744 and predates it. Fix: run deploy-brain.ps1 (with -SkipSpaBuild after a fresh npm run build) at a quiet moment, or make the remote script rebuild the image from the synced static on hot-sync.

All events  ·  DSC  ·  CannaLib  ·  Site  ·  Firmware releases

Empty rows are honest

A blank cell means the tracker has no value for it. Nothing on this page is filled in to look complete.