CubeCraft-Creations/remote-rig
11
0
Fork 0
generated from CubeCraft-Creations/Tracehound
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

docs: CONTEXT.md — mark camera pipeline end-to-end verified
Build (Dev) / build (push) Successful in 11s
Details
CI / quality (push) Successful in 11s
Details
CI / quality (pull_request) Successful in 11s
Details

Browse Source 
Camera rig-86d978 registers + lists in the API/dashboard with status
ingested. Add decisions for modernc/sqlite datetime scanning and legacy
camera-id migration.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Joshua King
2026-06-05 14:37:57 -04:00
parent 8e6cd11d9c
commit f03dbb056d
1 changed files with 10 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CONTEXT.md
+10 -5
View File
@@ -176,6 +176,13 @@ reach; the Pi pulls instead.
now defaults the service user to `$SUDO_USER`. now defaults the service user to `$SUDO_USER`.
12. **Hub embeds the frontend** via `//go:embed all:src/dist`; Vite builds into 12. **Hub embeds the frontend** via `//go:embed all:src/dist`; Vite builds into
`cmd/server/src/dist` (a committed `index.html` placeholder keeps the embed valid). `cmd/server/src/dist` (a committed `index.html` placeholder keeps the embed valid).
13. **SQLite/modernc datetime:** `modernc.org/sqlite` returns a `COALESCE()`/expression
as a raw string (no type affinity) → can't scan into `time.Time`. Scan plain
`DATETIME` columns (returned as `time.Time`) via `sql.NullTime`; `ListCameras`
`COALESCE`s NULL int/bool status columns. Nodes send no usable timestamp on
status/heartbeat (numeric `millis()`) — the hub ignores it / stamps server-side.
14. **Legacy id migration:** `handleAnnounce` migrates a MAC registered under a
different `camera_id` (e.g. a pre-self-id `cam-NNN`) to the node's self-id.
## 10. Conventions ## 10. Conventions
@@ -192,13 +199,11 @@ reach; the Pi pulls instead.
- Full CI/CD loop proven: commit → CI build → `dev-latest` → Pi self-update - Full CI/CD loop proven: commit → CI build → `dev-latest` → Pi self-update
(checksum, atomic replace, health-check) → service active. (checksum, atomic replace, health-check) → service active.
- C6 (fw `0.4.0`) joins RemoteRig, connects to the broker, announces as `rig-86d978`, - C6 (fw `0.4.0`) joins RemoteRig, connects to the broker, announces as `rig-86d978`,
publishes status. ESP-01S UART link alive. and is **registered + listed** in `GET /api/v1/cameras` and the dashboard, with
status/heartbeat ingested cleanly. Shows `online:false` / zeros until a GoPro is
attached (expected on the bench). ESP-01S UART link alive. **End-to-end verified.**
**In progress / unresolved:** **In progress / unresolved:**
- **Verifying the hub registered `rig-86d978`** — needs confirmation that the hub is on
build `18db26c2` (Option B) and that the camera is in the DB / dashboard
(`GET /api/v1/cameras`, header `X-API-Key: changeme`). Status currently shows
`online:false` because no GoPro is attached on the bench (expected).
- **GoPro Hero 3 protocol fix** (ESP-01S `fetchStatus` shutter bug) — required before - **GoPro Hero 3 protocol fix** (ESP-01S `fetchStatus` shutter bug) — required before
real battery/recording data; needs a real Hero 3. real battery/recording data; needs a real Hero 3.
- **Rotate the Gitea runner registration token** (was exposed in a setup paste). - **Rotate the Gitea runner registration token** (was exposed in a setup paste).