eluminocity: fix delta-bridge.conf.default path so first-boot seed works#28
Open
RAR wants to merge 1 commit into
Open
eluminocity: fix delta-bridge.conf.default path so first-boot seed works#28RAR wants to merge 1 commit into
RAR wants to merge 1 commit into
Conversation
The default config was written to /etc/delta-bridge.conf.default but first-boot.sh seeds from $DBDIR/delta-bridge.conf.default (/etc/delta-bridge/delta-bridge.conf.default). The cp failed silently and first-boot.sh still printed "seeded ...", so the unit booted on compiled-in defaults (web_enable=0, rfid_enable=0) — no web UI, no RFID. Bench-caught 2026-05-21 on the first real M12 flash: the eraseblock fix booted clean, but the web UI never came up. Root-caused to this one path mismatch; delta-bridge's own log history confirms web + RFID work when a config file is present. - build-dcofimage.sh: write the default to etc/delta-bridge/ - first-boot.sh: guard the "seeded" message on cp success - verify_dcofimage.py: assert the default at the correct subdir path (the verifier had encoded the same wrong path, so it passed the bug) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
First real M12 bench flash (2026-05-21): the eraseblock fix booted clean — no brick — but the web UI never came up.
Root cause:
build-dcofimage.shwrote the default config to/etc/delta-bridge.conf.default, butfirst-boot.shseeds from/etc/delta-bridge/delta-bridge.conf.default. Thecpfailed,first-boot.shprintedseeded ...anyway, and delta-bridge fell back to compiled-in defaults (web_enable=0,rfid_enable=0).delta-bridge's own log history confirms web + RFID work fine once a config file is present — this is purely the seed path.
Changes
build-dcofimage.sh: write the default toetc/delta-bridge/first-boot.sh: guard the "seeded" message oncpsuccess (was unconditional)verify_dcofimage.py: assert the default at the correct subdir path — the verifier had encoded the same wrong path, so it passed the broken buildTest Plan
make test— 657/657 passmake dcofimage— builds;verify_dcofimage.pynow checks the correct path