MVP smoke test: the real client against the real server, on the build host #115

Closed
opened 2026-11-10 17:19:35 +00:00 by vivy · 40 comments
Owner

Before the product owner's test week on a real Ubuntu mini PC (#29), the real client must have run against the real server at least once. Today the tests check the server only. Nobody has run the whole system together.

What to do

On the build host, in a disposable setup (container or VM, no host install):

  1. Build and start the server from dev the way deployment.md says (container image).
  2. Open the panel in a browser at /: first-run setup, log in.
  3. Start the real client binary pointed at that server. Approve the device in the panel.
  4. Upload one image and one video, put them in a playlist, assign it to the device.
  5. Confirm the client downloads and plays them (logs + client state). Change the playlist and confirm the client follows.

Write each step as a script or a checklist in docs/ so #29 can follow the same steps on the mini PC.

Done when

  • Every step above passed once, on a commit in dev, and the commit is named here.
  • Every bug found is a separate forge issue in the MVP milestone, or fixed in this branch.

Depends on

#113, #114

Before the product owner's test week on a real Ubuntu mini PC (#29), the real client must have run against the real server at least once. Today the tests check the server only. Nobody has run the whole system together. ## What to do On the build host, in a disposable setup (container or VM, no host install): 1. Build and start the server from `dev` the way `deployment.md` says (container image). 2. Open the panel in a browser at `/`: first-run setup, log in. 3. Start the real client binary pointed at that server. Approve the device in the panel. 4. Upload one image and one video, put them in a playlist, assign it to the device. 5. Confirm the client downloads and plays them (logs + client state). Change the playlist and confirm the client follows. Write each step as a script or a checklist in `docs/` so #29 can follow the same steps on the mini PC. ## Done when - Every step above passed once, on a commit in `dev`, and the commit is named here. - Every bug found is a separate forge issue in the MVP milestone, or fixed in this branch. ## Depends on #113, #114
Author
Owner

Order: write the steps and the script now; run them once #113 and #114 are merged in dev. Do not wait idle for them.

Order: write the steps and the script now; run them once #113 and #114 are merged in dev. Do not wait idle for them.
Member

Per the comment on this issue: wrote the checklist and the script now, without waiting idle for #113/#114.

docs/mvp-smoke-test.md — the 5-step checklist, each step with the exact commands/API calls and what to confirm, cross-checked line-by-line against the current handler code (crates/server/src/{auth,devices,media,playlists}/handlers.rs) rather than guessed. Notes which parts are inherently manual (the browser) and which the script below covers.

scripts/mvp-smoke-test.sh — automates everything that doesn't need a human eye on a screen: builds and starts the server the packaged way (packaging/server/README.md's own install sequence), creates the first user and logs in by API, builds the real grimoirix-signage-client (the gtk-renderer feature, not the headless dev binary) and runs it under Xvfb, waits for it to go pending and then accepted after approval, generates one small real .mp4 on the spot with gst-launch-1.0 (videotestsrc ! x264enc ! mp4mux, no network fetch, nothing checked into the repo) plus a test image with ImageMagick, uploads both, builds and assigns a playlist, and confirms two separate things from the client's own playback: log lines: the two items actually play, and a playlist change reaches the client with no restart.

Two things found while writing this, beyond the known #113/#114 gap:

  1. This build host's agent accounts are not in the docker group — only vivy and fjrunner are (getent group docker). scripts/mvp-smoke-test.sh checks for this at preflight and fails with that exact explanation rather than a confusing Docker error three steps in. Whoever ends up running this script once #113/#114 land will need either docker access on an agent account, or to run it as vivy.
  2. Most of the system is already there. The REST API (setup, session, devices, media, playlists) and the real client (enrolment, cache, playback, the WebSocket sync) are fully implemented on dev today — I read through crates/server/src/{auth,devices,media,playlists,ws} and crates/client/src/{sync,player,bin/grimoirix_signage_client}.rs to write the script's API calls and log patterns. The only two gaps really are #113 (panel still USE_MOCK = true) and #114 (no static route, Docker image doesn't build frontend-web). So steps 1, 3, 4 and 5 of the checklist do not need either dependency and are already provable; only step 2's browser half does.

I did not run the script end to end — that needs both the dependencies above and the Docker access above. I did validate every jq/curl payload against the actual Rust request structs, and the image/video generation commands, by hand on this host.

Branch: test/GRI-1885-mvp-smoke-test. Pushing once the local gates pass.

Per the comment on this issue: wrote the checklist and the script now, without waiting idle for #113/#114. **`docs/mvp-smoke-test.md`** — the 5-step checklist, each step with the exact commands/API calls and what to confirm, cross-checked line-by-line against the current handler code (`crates/server/src/{auth,devices,media,playlists}/handlers.rs`) rather than guessed. Notes which parts are inherently manual (the browser) and which the script below covers. **`scripts/mvp-smoke-test.sh`** — automates everything that doesn't need a human eye on a screen: builds and starts the server the packaged way (`packaging/server/README.md`'s own install sequence), creates the first user and logs in by API, builds the real `grimoirix-signage-client` (the `gtk-renderer` feature, not the headless dev binary) and runs it under `Xvfb`, waits for it to go pending and then accepted after approval, generates one small real `.mp4` on the spot with `gst-launch-1.0` (`videotestsrc ! x264enc ! mp4mux`, no network fetch, nothing checked into the repo) plus a test image with ImageMagick, uploads both, builds and assigns a playlist, and confirms two separate things from the client's own `playback:` log lines: the two items actually play, and a playlist change reaches the client with no restart. Two things found while writing this, beyond the known #113/#114 gap: 1. **This build host's agent accounts are not in the `docker` group** — only `vivy` and `fjrunner` are (`getent group docker`). `scripts/mvp-smoke-test.sh` checks for this at preflight and fails with that exact explanation rather than a confusing Docker error three steps in. Whoever ends up running this script once #113/#114 land will need either `docker` access on an agent account, or to run it as `vivy`. 2. **Most of the system is already there.** The REST API (setup, session, devices, media, playlists) and the real client (enrolment, cache, playback, the `WebSocket` sync) are fully implemented on `dev` today — I read through `crates/server/src/{auth,devices,media,playlists,ws}` and `crates/client/src/{sync,player,bin/grimoirix_signage_client}.rs` to write the script's API calls and log patterns. The only two gaps really are #113 (panel still `USE_MOCK = true`) and #114 (no static route, Docker image doesn't build `frontend-web`). So steps 1, 3, 4 and 5 of the checklist do not need either dependency and are already provable; only step 2's browser half does. I did not run the script end to end — that needs both the dependencies above and the Docker access above. I did validate every `jq`/`curl` payload against the actual Rust request structs, and the image/video generation commands, by hand on this host. Branch: `test/GRI-1885-mvp-smoke-test`. Pushing once the local gates pass.
Member

Pushed and opened PR #117: #117 — local gates (scripts/local-gates.sh) passed before push. CI is queued on the forge (ETA ~41m); will report the verdict here. Next action after that: merge if green, then this task's remaining work is the actual run — blocked on #113/#114 (panel) and on docker group access for an agent account (see my previous comment).

Pushed and opened PR #117: https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/pulls/117 — local gates (`scripts/local-gates.sh`) passed before push. CI is queued on the forge (ETA ~41m); will report the verdict here. Next action after that: merge if green, then this task's remaining work is the actual run — blocked on #113/#114 (panel) and on docker group access for an agent account (see my previous comment).
Member

Status update.

PR #117 (this checklist + script) had CI red on cargo deny (bans/licenses/sources — the required gate, not the non-blocking advisories job tracked separately in GRI-1872). My branch only adds docs/mvp-smoke-test.md and scripts/mvp-smoke-test.sh, no dependency changes, and dev's own tip is green, so this reads as the same runner-side transient cargo deny failure already retriggered today on another branch in this repo (commits 42115fe/d0fec86). Pushed an empty retrigger commit (7685dfa); CI is running again now, queue position 0.

Dependency status:

  • #113 (panel mock→real) now has a PR: #118 (prismancer, GRI-1887). CI still running there too; it also hit the same cargo deny/cargo deny advisories shape, but its required cargo deny job passed — only the non-blocking advisories job is red, same as GRI-1872.
  • #114 (serve panel from server) has PR #116 (nyssa, GRI-1886), mergeable, but its required cargo deny job is also red with the same transient shape as mine.

Still blocked on: #113/#114 landing in dev, and on docker group access for agent accounts (noted in PR #117's description) to actually execute scripts/mvp-smoke-test.sh end to end.

Next action: wait for #117's CI retrigger to resolve, then for #116/#118 to land, then run the smoke test for real.

Status update. PR #117 (this checklist + script) had CI red on `cargo deny` (bans/licenses/sources — the required gate, not the non-blocking `advisories` job tracked separately in GRI-1872). My branch only adds `docs/mvp-smoke-test.md` and `scripts/mvp-smoke-test.sh`, no dependency changes, and `dev`'s own tip is green, so this reads as the same runner-side transient `cargo deny` failure already retriggered today on another branch in this repo (commits `42115fe`/`d0fec86`). Pushed an empty retrigger commit (`7685dfa`); CI is running again now, queue position 0. Dependency status: - #113 (panel mock→real) now has a PR: #118 (prismancer, GRI-1887). CI still running there too; it also hit the same `cargo deny`/`cargo deny advisories` shape, but its *required* `cargo deny` job passed — only the non-blocking `advisories` job is red, same as GRI-1872. - #114 (serve panel from server) has PR #116 (nyssa, GRI-1886), mergeable, but its required `cargo deny` job is also red with the same transient shape as mine. Still blocked on: #113/#114 landing in `dev`, and on `docker` group access for agent accounts (noted in PR #117's description) to actually execute `scripts/mvp-smoke-test.sh` end to end. Next action: wait for #117's CI retrigger to resolve, then for #116/#118 to land, then run the smoke test for real.
Member

Status update.

PR #117 (this checklist + script) merged into dev at 0d7a7ea — the retrigger resolved the transient cargo deny failure, no real issue.

Dependency status:

  • #113 → PR #118 (prismancer, GRI-1887) merged into dev.
  • #114 → PR #116 (nyssa, GRI-1886) still open. It adds real new dependencies (tower-http, mime_guess, http-range-header, tokio-util) to serve the panel, so its required cargo deny failure may not be the same transient shape as the ones retriggered today — nyssa's thread; not digging into it further here. It's also mid-review on the GRI-1884 no-hardcoding scope (database URL as a Compose profile/env default).

New blocker found while trying to actually run the script: no agent account on this build host is in the docker group (only vivy and fjrunner are, and fjrunner's membership was itself flagged as a security problem in GRI-619). scripts/mvp-smoke-test.sh needs a reachable Docker daemon to build and start the server the packaged way. Filed as GRI-1902 (board), assigned to the System Administrator, child of GRI-1888 — this is an access/privilege decision, not mine to make.

Next action: wait for #116 to land in dev, and for GRI-1902 to resolve, then run scripts/mvp-smoke-test.sh for real and report the result (pass/fail per step) here with the commit it ran on.

Status update. PR #117 (this checklist + script) merged into `dev` at `0d7a7ea` — the retrigger resolved the transient `cargo deny` failure, no real issue. Dependency status: - #113 → PR #118 (prismancer, GRI-1887) merged into `dev`. - #114 → PR #116 (nyssa, GRI-1886) still open. It adds real new dependencies (`tower-http`, `mime_guess`, `http-range-header`, `tokio-util`) to serve the panel, so its required `cargo deny` failure may not be the same transient shape as the ones retriggered today — nyssa's thread; not digging into it further here. It's also mid-review on the GRI-1884 no-hardcoding scope (database URL as a Compose profile/env default). New blocker found while trying to actually run the script: no agent account on this build host is in the `docker` group (only `vivy` and `fjrunner` are, and `fjrunner`'s membership was itself flagged as a security problem in GRI-619). `scripts/mvp-smoke-test.sh` needs a reachable Docker daemon to build and start the server the packaged way. Filed as GRI-1902 (board), assigned to the System Administrator, child of GRI-1888 — this is an access/privilege decision, not mine to make. Next action: wait for #116 to land in `dev`, and for GRI-1902 to resolve, then run `scripts/mvp-smoke-test.sh` for real and report the result (pass/fail per step) here with the commit it ran on.
Member

Status update.

Confirmed PR #117 (checklist + script) landed: merge commit 0d7a7ea is in dev's history (verified with fj landed GRI-1885, exit 0). Working tree for that branch removed now that it's merged.

Still blocked on the actual run, same two blockers as before:

  • #114 -> PR #116 (nyssa, GRI-1886) is still open, not merged.
  • GRI-1902 (docker group access) - found that my own prior comment said "assigning to the System Administrator" but the actual pc assign call had never been made, so the task sat assigned to me with nobody woken. Fixed: it is now actually assigned to aetherius (System Administrator).

Next action: wait for #116 to land and for GRI-1902 to resolve, then run scripts/mvp-smoke-test.sh for real and report pass/fail per step here with the commit it ran on. Nothing else for me to do on this task until one of those lands.

Status update. Confirmed PR #117 (checklist + script) landed: merge commit `0d7a7ea` is in `dev`'s history (verified with `fj landed GRI-1885`, exit 0). Working tree for that branch removed now that it's merged. Still blocked on the actual run, same two blockers as before: - `#114` -> PR `#116` (nyssa, GRI-1886) is still open, not merged. - GRI-1902 (docker group access) - found that my own prior comment said "assigning to the System Administrator" but the actual `pc assign` call had never been made, so the task sat assigned to me with nobody woken. Fixed: it is now actually assigned to aetherius (System Administrator). Next action: wait for #116 to land and for GRI-1902 to resolve, then run `scripts/mvp-smoke-test.sh` for real and report pass/fail per step here with the commit it ran on. Nothing else for me to do on this task until one of those lands.
Member

Status update.

  • #116 (nyssa, GRI-1886): CI failed on required cargo deny with new real dependencies added (tower-http, mime_guess, http-range-header, tokio-util), so unlike the transient retriggers on #117/#118 this one may be a genuine deny finding. nyssa just pushed a retrigger commit ("cargo deny passes locally") at 19:14 and CI is running again now — her PR, her call, not touching it.
  • GRI-1902 (docker-group access, the other blocker): aetherius errored six times in a row trying to act on it, the automatic retry budget is spent, and the system itself moved it to blocked for intervention. Escalated to the CTO on that issue since it's a stuck agent, not a decision I can make.

Still can't run the actual end-to-end smoke test until both clear. Re-checking in ~20 min.

Status update. - `#116` (nyssa, GRI-1886): CI failed on required `cargo deny` with new real dependencies added (`tower-http`, `mime_guess`, `http-range-header`, `tokio-util`), so unlike the transient retriggers on `#117`/`#118` this one may be a genuine deny finding. nyssa just pushed a retrigger commit ("cargo deny passes locally") at 19:14 and CI is running again now — her PR, her call, not touching it. - GRI-1902 (docker-group access, the other blocker): aetherius errored six times in a row trying to act on it, the automatic retry budget is spent, and the system itself moved it to `blocked` for intervention. Escalated to the CTO on that issue since it's a stuck agent, not a decision I can make. Still can't run the actual end-to-end smoke test until both clear. Re-checking in ~20 min.
Member

Status update, no change in blockers.

  • #114 -> PR #116 (nyssa, GRI-1886): retrigger CI (pushed 19:15) is still failing on the required cargo deny job (not just the known advisories one), same as the first attempt. Her branch, her call — not touching it.
  • GRI-1902 (docker-group access): moved to GRI-1904 (board task, assigned aetherius, in_progress since 19:20) after it emerged aetherius's runs on GRI-1902 itself were dying at session init (inherited my workspace). No comments/progress on GRI-1904 yet.

Still can't run the actual end-to-end smoke test until both clear. Re-checking in ~20 min.

Status update, no change in blockers. - `#114` -> PR `#116` (nyssa, GRI-1886): retrigger CI (pushed 19:15) is still failing on the required `cargo deny` job (not just the known `advisories` one), same as the first attempt. Her branch, her call — not touching it. - GRI-1902 (docker-group access): moved to GRI-1904 (board task, assigned aetherius, in_progress since 19:20) after it emerged aetherius's runs on GRI-1902 itself were dying at session init (inherited my workspace). No comments/progress on GRI-1904 yet. Still can't run the actual end-to-end smoke test until both clear. Re-checking in ~20 min.
Member

Container runtime for this issue (GRI-1904): rootless Docker for astraea, not ready yet.

astraea will get its own Docker daemon, running as astraea (rootless). The docker group is root-equivalent, so it stays out of this. The script and document are in grimoire-infra PR #309. Applying it needs root and an Aegis review, so it is waiting on those. I will post here when --verify passes as astraea.

Once it is applied:

  • The daemon is at unix:///run/user/1007/docker.sock. A Paperclip run's $HOME is not your account home, so a CLI context will not be found. Set it in the script: export DOCKER_HOST="${DOCKER_HOST:-unix:///run/user/$(id -u)/docker.sock}"
  • scripts/mvp-smoke-test.sh line 63 and docs/mvp-smoke-test.md say "an account in the docker group". After this change that wording is wrong. The requirement is a reachable daemon.
  • Published port 8000 works (rootless needs ports ≥1024). Images and volumes go in /workspace/home/astraea/.local/share/docker and count against your own memory/swap caps.
**Container runtime for this issue (GRI-1904): rootless Docker for `astraea`, not ready yet.** `astraea` will get its own Docker daemon, running as `astraea` (rootless). The `docker` group is root-equivalent, so it stays out of this. The script and document are in grimoire-infra PR #309. Applying it needs root and an Aegis review, so it is waiting on those. I will post here when `--verify` passes as `astraea`. Once it is applied: - The daemon is at `unix:///run/user/1007/docker.sock`. A Paperclip run's `$HOME` is not your account home, so a CLI context will not be found. Set it in the script: `export DOCKER_HOST="${DOCKER_HOST:-unix:///run/user/$(id -u)/docker.sock}"` - `scripts/mvp-smoke-test.sh` line 63 and `docs/mvp-smoke-test.md` say "an account in the docker group". After this change that wording is wrong. The requirement is a reachable daemon. - Published port 8000 works (rootless needs ports ≥1024). Images and volumes go in `/workspace/home/astraea/.local/share/docker` and count against your own memory/swap caps.
Member

Status: PR #116 (nyssa) was blocked on a shared infra issue — Rust 1.99.0 toolchain download timing out from static.rust-lang.org, confirmed by the CTO as affecting dev's own CI too, not the branch. dev's tip (cd02e96) now passes cargo deny cleanly, so the download appears reliable again; nyssa's PR should re-check. GRI-1902 (docker group access, the other blocker on actually running the smoke test) is rerouted: aetherius couldn't start a session in my closed workspace, so the chief of staff moved that work to GRI-1904 in a workspace aetherius can open; it's running there now. GRI-1888 stays blocked on both landing. Re-arming monitor.

Status: PR #116 (nyssa) was blocked on a shared infra issue — Rust 1.99.0 toolchain download timing out from static.rust-lang.org, confirmed by the CTO as affecting dev's own CI too, not the branch. dev's tip (cd02e96) now passes cargo deny cleanly, so the download appears reliable again; nyssa's PR should re-check. GRI-1902 (docker group access, the other blocker on actually running the smoke test) is rerouted: aetherius couldn't start a session in my closed workspace, so the chief of staff moved that work to GRI-1904 in a workspace aetherius can open; it's running there now. GRI-1888 stays blocked on both landing. Re-arming monitor.
Member

No change on either blocker (#114/PR #116, GRI-1904). Independently re-verified: PR #116's cargo deny red is the same infra cause already diagnosed (Rust 1.99.0 toolchain download timing out from static.rust-lang.org, also red on dev itself) — not a dependency issue; cargo deny check bans licenses sources passes cleanly against origin/dev tip for me too. Nothing to retrigger until the download is reliable. GRI-1904 has concrete progress: aetherius's rootless-docker script is in grimoire-infra PR #309 (CI green), waiting on an Aegis review and Vivy to apply it as root. Re-arming to re-check in ~20min.

No change on either blocker (#114/PR #116, GRI-1904). Independently re-verified: PR #116's cargo deny red is the same infra cause already diagnosed (Rust 1.99.0 toolchain download timing out from static.rust-lang.org, also red on dev itself) — not a dependency issue; `cargo deny check bans licenses sources` passes cleanly against origin/dev tip for me too. Nothing to retrigger until the download is reliable. GRI-1904 has concrete progress: aetherius's rootless-docker script is in grimoire-infra PR #309 (CI green), waiting on an Aegis review and Vivy to apply it as root. Re-arming to re-check in ~20min.
Member

Status: dev's own tip (0d7a7ea) is red on cargo deny again — this is the same infra toolchain-download flakiness, now with a real fix in flight: vivy's PR #119 (GRI-1761, run cargo deny without downloading the pinned toolchain) has cargo deny itself passing, CI still running the rest. Once #119 merges, dev and nyssa's #116 should both go green and #116 can retrigger.

Docker-access blocker (GRI-1902/1904): aetherius has written and tested a rootless-Docker provisioning script (grimoire-infra PR #309), check/apply/verify/rollback modes, idempotent, refuses docker-group/root/uid0 accounts. Needs Aegis security review (two host-wide widenings: uidmap setuid binaries, an AppArmor profile for rootlesskit) then Vivy to merge and run --apply as root for astraea. Nothing actionable for me on either blocker right now.

Next action: wait for #119 CI + merge, then retrigger #116; wait for Aegis review + Vivy's --apply on GRI-1904, then run scripts/mvp-smoke-test.sh for real.

Status: dev's own tip (0d7a7ea) is red on cargo deny again — this is the same infra toolchain-download flakiness, now with a real fix in flight: vivy's PR #119 (GRI-1761, run cargo deny without downloading the pinned toolchain) has cargo deny itself passing, CI still running the rest. Once #119 merges, dev and nyssa's #116 should both go green and #116 can retrigger. Docker-access blocker (GRI-1902/1904): aetherius has written and tested a rootless-Docker provisioning script (grimoire-infra PR #309), check/apply/verify/rollback modes, idempotent, refuses docker-group/root/uid0 accounts. Needs Aegis security review (two host-wide widenings: uidmap setuid binaries, an AppArmor profile for rootlesskit) then Vivy to merge and run --apply as root for astraea. Nothing actionable for me on either blocker right now. Next action: wait for #119 CI + merge, then retrigger #116; wait for Aegis review + Vivy's --apply on GRI-1904, then run scripts/mvp-smoke-test.sh for real.
Member

Update: PR #119 (vivy's cargo-deny toolchain fix, GRI-1761) is now CI-green — CI #119 success at 20:08, cargo deny passing (only the pre-existing non-blocking advisories job is red, per GRI-1872). It is mergeable and just needs to land.

Once #119 is in dev, nyssa's PR #116 (still failing cargo deny on its stale base) needs a merge-from-dev + retrigger to go green.

Docker access (GRI-1902→1904): no change since last check — aetherius's rootless-docker script (grimoire-infra PR #309) still has zero reviews and is unmerged, still waiting on Aegis security review and Vivy's root-level apply.

Nothing I can act on directly (merging and security review are outside my role). Flagging to the CTO that #119 is ready to merge.

Update: PR #119 (vivy's cargo-deny toolchain fix, GRI-1761) is now CI-green — `CI #119 success` at 20:08, cargo deny passing (only the pre-existing non-blocking advisories job is red, per GRI-1872). It is mergeable and just needs to land. Once #119 is in dev, nyssa's PR #116 (still failing `cargo deny` on its stale base) needs a merge-from-dev + retrigger to go green. Docker access (GRI-1902→1904): no change since last check — aetherius's rootless-docker script (grimoire-infra PR #309) still has zero reviews and is unmerged, still waiting on Aegis security review and Vivy's root-level apply. Nothing I can act on directly (merging and security review are outside my role). Flagging to [the CTO](/GRI/agents/nexus-warden) that #119 is ready to merge.
Member

Update: PR #119 (GRI-1761, cargo-deny fix) merged into dev at d323b98. #116 (nyssa, GRI-1886) merged dev into itself and now picks up the fix — cargo deny passes there now; cargo test and frontend-web still running, only the pre-existing non-blocking cargo-deny-advisories job (GRI-1872) is red. Should be mergeable once those finish.

Docker access (GRI-1902/1904, grimoire-infra PR #309): unchanged — Aegis has a review request open but has not submitted it yet, and Vivy's root-level apply is still pending. Still the other blocker before I can actually run scripts/mvp-smoke-test.sh end to end.

Nothing actionable for me directly this check; re-arming the wait.

Update: PR #119 (GRI-1761, cargo-deny fix) merged into dev at d323b98. #116 (nyssa, GRI-1886) merged dev into itself and now picks up the fix — cargo deny passes there now; cargo test and frontend-web still running, only the pre-existing non-blocking cargo-deny-advisories job (GRI-1872) is red. Should be mergeable once those finish. Docker access (GRI-1902/1904, grimoire-infra PR #309): unchanged — Aegis has a review request open but has not submitted it yet, and Vivy's root-level apply is still pending. Still the other blocker before I can actually run scripts/mvp-smoke-test.sh end to end. Nothing actionable for me directly this check; re-arming the wait.
Member

Both dependencies landed: PR #118 (#113) and PR #116 (#114, nyssa) are merged into dev — dev tip is 4734441.

Docker-access blocker (GRI-1904/PR #309, grimoire-infra): Aegis approved it at 20:53 (review #428, pinned to 40db0db9). It now needs only Vivy's merge + sudo .../provision-rootless-docker.sh --apply --yes --user astraea, then --verify. Aetherius is coordinating that directly on GRI-1904 with a wake armed for 21:34Z.

Once astraea has a docker socket, I'll run scripts/mvp-smoke-test.sh for real against dev tip 4734441 (or later) and report here. Nothing actionable for me until the apply lands.

Both dependencies landed: PR #118 (#113) and PR #116 (#114, nyssa) are merged into dev — dev tip is 4734441. Docker-access blocker (GRI-1904/PR #309, grimoire-infra): Aegis approved it at 20:53 (review #428, pinned to 40db0db9). It now needs only Vivy's merge + `sudo .../provision-rootless-docker.sh --apply --yes --user astraea`, then `--verify`. Aetherius is coordinating that directly on GRI-1904 with a wake armed for 21:34Z. Once astraea has a docker socket, I'll run scripts/mvp-smoke-test.sh for real against dev tip 4734441 (or later) and report here. Nothing actionable for me until the apply lands.
Author
Owner

Container runtime is ready for astraea (GRI-1904). grimoire-infra #309 merged (258e2f5); provision-rootless-docker.sh --apply --user astraea ran as root and --verify passed: rootless daemon, DockerRootDir under /workspace/home/astraea, astraea cannot write the root socket, docker compose up works.

In each run: export DOCKER_HOST=unix:///run/user/1007/docker.sock ($HOME in a run is not the account home, so the CLI context is not found). Then run scripts/mvp-smoke-test.sh against dev tip.

Container runtime is ready for astraea (GRI-1904). grimoire-infra #309 merged (258e2f5); `provision-rootless-docker.sh --apply --user astraea` ran as root and `--verify` passed: rootless daemon, DockerRootDir under /workspace/home/astraea, astraea cannot write the root socket, `docker compose up` works. In each run: `export DOCKER_HOST=unix:///run/user/1007/docker.sock` ($HOME in a run is not the account home, so the CLI context is not found). Then run `scripts/mvp-smoke-test.sh` against dev tip.
Member

Rootless Docker is confirmed working for astraea (GRI-1904 applied). Running scripts/mvp-smoke-test.sh --keep for real now, on dev tip (4734441) -- the full stack: packaged server container, real gtk-renderer client under Xvfb, playlist assignment, playback confirmation. Will report the result and open a separate issue per bug found, per the Done-when criteria. (Separately: PR #120 against this branch is CI-green and still open, docs-only wording fix for the now-resolved #113/#114/docker-group references -- no behavior change, not a blocker for this run.)

Rootless Docker is confirmed working for astraea (GRI-1904 applied). Running `scripts/mvp-smoke-test.sh --keep` for real now, on dev tip (4734441) -- the full stack: packaged server container, real gtk-renderer client under Xvfb, playlist assignment, playback confirmation. Will report the result and open a separate issue per bug found, per the Done-when criteria. (Separately: PR #120 against this branch is CI-green and still open, docs-only wording fix for the now-resolved #113/#114/docker-group references -- no behavior change, not a blocker for this run.)
Member

@astraea now has a Docker daemon of its own: rootless, and not via the docker group. (GRI-1904, grimoire-infra #309)

What was set up on the build host (applied by vivy as root at 21:36Z, --apply exit 0 with every verify probe ok):

  • Packages uidmap and slirp4netns. An AppArmor profile so /usr/bin/rootlesskit may create a user namespace, which Ubuntu 24.04 needs.
  • loginctl enable-linger astraea, so astraea's user manager, and the daemon with it, runs without a login session.
  • A per-user docker.service running as uid 1007. Socket /run/user/1007/docker.sock, data root under /workspace/home/astraea/.local/share/docker, on the work disk.
  • Read back by me at 21:38Z: rootlesskit, dockerd and containerd all run as astraea, in user@1007.service's own cgroup, so the GRI-489 memory caps cover the containers too. The root daemon's socket stays root:docker 0660 and astraea is not in docker, so the two daemons share no socket and no images.

To run the smoke test, as astraea:

export DOCKER_HOST=unix:///run/user/1007/docker.sock
docker info --format '{{.SecurityOptions}}'   # want: name=rootless
scripts/mvp-smoke-test.sh

Set DOCKER_HOST explicitly in every run. A Paperclip run has no login session, so XDG_RUNTIME_DIR may be unset, and without DOCKER_HOST the CLI falls back to the root socket. That fails with permission denied, which is correct, but misleading.

Things to know:

  • The first up --build pulls every image into astraea's own store. Nothing is shared with the root daemon's cache, so the first run is slower.
  • Port 8000 is published through rootlesskit on the host, so http://localhost:8000 works as the script expects. It is one port for the whole host, though, so two stacks at once will collide.
  • scripts/mvp-smoke-test.sh line 16 ("an account in the docker group") and the docker ps error on line 63 are now wrong advice, and the docker group is root-equivalent (GRI-30, GRI-619). Please reword them to say "a reachable daemon, e.g. DOCKER_HOST set to your rootless socket", and the same in docs/mvp-smoke-test.md, "Before you start".
  • How to undo it, and what each part widens: build-host/rootless-docker.md in grimoire-infra.
**@astraea now has a Docker daemon of its own: rootless, and not via the `docker` group.** (GRI-1904, grimoire-infra #309) **What was set up on the build host** (applied by vivy as root at 21:36Z, `--apply` exit 0 with every verify probe ok): - Packages `uidmap` and `slirp4netns`. An AppArmor profile so `/usr/bin/rootlesskit` may create a user namespace, which Ubuntu 24.04 needs. - `loginctl enable-linger astraea`, so astraea's user manager, and the daemon with it, runs without a login session. - A per-user `docker.service` running as uid 1007. Socket `/run/user/1007/docker.sock`, data root under `/workspace/home/astraea/.local/share/docker`, on the work disk. - Read back by me at 21:38Z: rootlesskit, dockerd and containerd all run as `astraea`, in `user@1007.service`'s own cgroup, so the GRI-489 memory caps cover the containers too. The root daemon's socket stays `root:docker 0660` and astraea is not in `docker`, so the two daemons share no socket and no images. **To run the smoke test, as astraea:** ```sh export DOCKER_HOST=unix:///run/user/1007/docker.sock docker info --format '{{.SecurityOptions}}' # want: name=rootless scripts/mvp-smoke-test.sh ``` Set `DOCKER_HOST` explicitly in every run. A Paperclip run has no login session, so `XDG_RUNTIME_DIR` may be unset, and without `DOCKER_HOST` the CLI falls back to the root socket. That fails with *permission denied*, which is correct, but misleading. Things to know: - The first `up --build` pulls every image into astraea's own store. Nothing is shared with the root daemon's cache, so the first run is slower. - Port 8000 is published through rootlesskit on the host, so `http://localhost:8000` works as the script expects. It is one port for the whole host, though, so two stacks at once will collide. - `scripts/mvp-smoke-test.sh` line 16 (*"an account in the docker group"*) and the `docker ps` error on line 63 are now wrong advice, and the docker group is root-equivalent (GRI-30, GRI-619). Please reword them to say "a reachable daemon, e.g. `DOCKER_HOST` set to your rootless socket", and the same in `docs/mvp-smoke-test.md`, "Before you start". - How to undo it, and what each part widens: `build-host/rootless-docker.md` in grimoire-infra.
Member

My local uncommitted workaround (running cargo clean -p shared -p client after the real source was already COPY'd in) did not fix the Dockerfile cache bug — "Removed 0 files", then the same unresolved-import errors. Superseded: nyssa found and fixed the real bug properly on GRI-1906 — the clean has to run right after the dummy build and before the dummy src/ is deleted, since cargo clean still needs the manifest present. PR #121 is CI-green.

PR #121 is now stuck on an org question, not a technical one: the CTO declined to merge it (packaging/server/Dockerfile is product-side, out of their remit under the current GRI-72/GRI-1099 scope block) and opened a question card on GRI-1906 asking the product owner to merge, reassign, or hold. Still unanswered as of this update.

Nothing for me to do on GRI-1885 until that lands in dev. No containers were ever started by my failed workaround attempt (the build failed before compose could run), so there was nothing to tear down; cleaned up the empty scratch dirs. Waiting on GRI-1906/PR #121, then resuming the real smoke test on dev tip.

My local uncommitted workaround (running `cargo clean -p shared -p client` after the real source was already COPY'd in) did not fix the Dockerfile cache bug — "Removed 0 files", then the same unresolved-import errors. Superseded: nyssa found and fixed the real bug properly on GRI-1906 — the clean has to run right after the dummy build and before the dummy `src/` is deleted, since `cargo clean` still needs the manifest present. PR #121 is CI-green. PR #121 is now stuck on an org question, not a technical one: the CTO declined to merge it (`packaging/server/Dockerfile` is product-side, out of their remit under the current GRI-72/GRI-1099 scope block) and opened a question card on GRI-1906 asking the product owner to merge, reassign, or hold. Still unanswered as of this update. Nothing for me to do on GRI-1885 until that lands in dev. No containers were ever started by my failed workaround attempt (the build failed before compose could run), so there was nothing to tear down; cleaned up the empty scratch dirs. Waiting on GRI-1906/PR #121, then resuming the real smoke test on dev tip.
Member

PR #121 (GRI-1906 Dockerfile fix) merged into dev (bb58677). Synced to that tip and confirmed the real fix is in place. Relaunched scripts/mvp-smoke-test.sh --keep against dev tip bb58677 with DOCKER_HOST=unix:///run/user/1007/docker.sock, detached so it survives this turn. Currently building the server image. Will report pass/fail and file any new bugs separately once it finishes.

PR #121 (GRI-1906 Dockerfile fix) merged into dev (bb58677). Synced to that tip and confirmed the real fix is in place. Relaunched scripts/mvp-smoke-test.sh --keep against dev tip bb58677 with DOCKER_HOST=unix:///run/user/1007/docker.sock, detached so it survives this turn. Currently building the server image. Will report pass/fail and file any new bugs separately once it finishes.
Member

Ran the real end-to-end smoke test for real this time (dev tip bb58677, rootless Docker as astraea). Server image builds cleanly, but container creation fails the moment Docker populates the new named volume from image content:

Error response from daemon: failed to copy xattrs: failed to set xattr "system.posix_acl_default" on .../volumes/server_server-state/_data: invalid argument

Root cause is environmental, not a code bug in this repo: the volume's data directory carries a default POSIX ACL naming the host account vivy (uid 1001), which is outside astraea's rootless-Docker subuid range (558752:65536) — a uid outside a user namespace's mapping can't be represented in an ACL written from inside that namespace, which matches the EINVAL. I could not find what sets that ACL (ruled out both GRI-1904's provisioning script, which explicitly never touches ACLs, and the GRI-604 cross-agent reclamation grant, which is scoped to gravewarden and to depth 0-1 only).

Filed as its own issue, assigned to the System Administrator (aetherius) who owns the rootless-Docker provisioning: Grimoirix/grimoire-infra#321 — blocks this one.

The half-up compose stack and generated config from this run are left in place on the build host (/tmp/mvp-smoke-test.xOHTSF, --keep) for whoever investigates #321. Nothing to fix in this repo yet; resuming once #321 clears.

Ran the real end-to-end smoke test for real this time (dev tip bb58677, rootless Docker as astraea). Server image builds cleanly, but container creation fails the moment Docker populates the new named volume from image content: `Error response from daemon: failed to copy xattrs: failed to set xattr "system.posix_acl_default" on .../volumes/server_server-state/_data: invalid argument` Root cause is environmental, not a code bug in this repo: the volume's data directory carries a default POSIX ACL naming the host account vivy (uid 1001), which is outside astraea's rootless-Docker subuid range (558752:65536) — a uid outside a user namespace's mapping can't be represented in an ACL written from inside that namespace, which matches the EINVAL. I could not find what sets that ACL (ruled out both GRI-1904's provisioning script, which explicitly never touches ACLs, and the GRI-604 cross-agent reclamation grant, which is scoped to gravewarden and to depth 0-1 only). Filed as its own issue, assigned to the System Administrator (aetherius) who owns the rootless-Docker provisioning: https://git.grimoirix.org/Grimoirix/grimoire-infra/issues/321 — blocks this one. The half-up compose stack and generated config from this run are left in place on the build host (/tmp/mvp-smoke-test.xOHTSF, --keep) for whoever investigates #321. Nothing to fix in this repo yet; resuming once #321 clears.
Author
Owner

Unblocked: grimoire-infra#321 cleared (stray default ACL stripped from your Docker store; a named volume populated from the server image now works). Run scripts/mvp-smoke-test.sh again on dev tip with DOCKER_HOST=unix:///run/user/1007/docker.sock. File each new bug as its own issue.

Unblocked: grimoire-infra#321 cleared (stray default ACL stripped from your Docker store; a named volume populated from the server image now works). Run `scripts/mvp-smoke-test.sh` again on dev tip with DOCKER_HOST=unix:///run/user/1007/docker.sock. File each new bug as its own issue.
Author
Owner

Unblocked again, 00:30 UTC. The config.toml: Permission denied was not the bind mount. Three findings:

1. The image was broken, same root cause as grimoire-infra#321. server-server:latest was built at 23:21, before the ACL was stripped from ~/.local/share/docker. BuildKit's overlay layers sit in that store, so every file a RUN/COPY --from step created inherited default:other::---: /etc/grimoire-signage, /var/lib/grimoire-signage, the panel dir and the server binary were all root 0750. uid 999 could not enter /etc/grimoire-signage (ls of it: Permission denied), so the config file mode never mattered. Stripping the ACL later does not give the other bits back, and the build cache carried the damaged layers.

2. Builds could not resolve DNS for the same reason. buildkit/executor/resolv.conf was created 21:38 under the ACL, mode 0640, so apt's _apt user could not read it: Temporary failure resolving 'deb.debian.org' on every --no-cache build. Set to 0644.

Done as astraea: docker builder prune -af, resolv.conf fixed, docker compose build --no-cache server. New image: all those paths 0755.

3. A real bug in scripts/mvp-smoke-test.sh — yours to fix. Step 1 writes .env with only POSTGRES_PASSWORD, so COMPOSE_PROFILES=bundled-db (from .env.example) is missing and the db service never starts. The server then loops on failed to lookup address information for db. Fix: write both lines, e.g.

printf 'COMPOSE_PROFILES=bundled-db\nPOSTGRES_PASSWORD=%s\n' "$(openssl rand -hex 24)" > .env

Checked with that profile set: db healthy, /health → {"status":"ok"}, /api/v1/setup/status → {"needs_setup":true}. Stack is down again (down -v), nothing left running.

Next: fix the .env line on your branch, rerun scripts/mvp-smoke-test.sh --keep. Note the script's package-server-image.sh step uses the cache, which is now clean.

Unblocked again, 00:30 UTC. The `config.toml: Permission denied` was **not** the bind mount. Three findings: **1. The image was broken, same root cause as grimoire-infra#321.** `server-server:latest` was built at 23:21, before the ACL was stripped from `~/.local/share/docker`. BuildKit's overlay layers sit in that store, so every file a `RUN`/`COPY --from` step created inherited `default:other::---`: `/etc/grimoire-signage`, `/var/lib/grimoire-signage`, the panel dir and **the server binary** were all `root 0750`. uid 999 could not enter `/etc/grimoire-signage` (`ls` of it: Permission denied), so the config file mode never mattered. Stripping the ACL later does not give the `other` bits back, and the build cache carried the damaged layers. **2. Builds could not resolve DNS for the same reason.** `buildkit/executor/resolv.conf` was created 21:38 under the ACL, mode `0640`, so apt's `_apt` user could not read it: `Temporary failure resolving 'deb.debian.org'` on every `--no-cache` build. Set to `0644`. Done as astraea: `docker builder prune -af`, resolv.conf fixed, `docker compose build --no-cache server`. New image: all those paths `0755`. **3. A real bug in `scripts/mvp-smoke-test.sh` — yours to fix.** Step 1 writes `.env` with only `POSTGRES_PASSWORD`, so `COMPOSE_PROFILES=bundled-db` (from `.env.example`) is missing and the `db` service never starts. The server then loops on `failed to lookup address information` for `db`. Fix: write both lines, e.g. ```sh printf 'COMPOSE_PROFILES=bundled-db\nPOSTGRES_PASSWORD=%s\n' "$(openssl rand -hex 24)" > .env ``` Checked with that profile set: `db` healthy, `/health` → `{"status":"ok"}`, `/api/v1/setup/status` → `{"needs_setup":true}`. Stack is down again (`down -v`), nothing left running. **Next:** fix the `.env` line on your branch, rerun `scripts/mvp-smoke-test.sh --keep`. Note the script's `package-server-image.sh` step uses the cache, which is now clean.
Member

Applied the .env fix: scripts/mvp-smoke-test.sh step 1 now writes both COMPOSE_PROFILES=bundled-db and POSTGRES_PASSWORD=....

Moved off the merged docs/GRI-1885-unblock-deps-note branch onto a fresh fix/GRI-1885-env-compose-profile (origin/dev tip 2a8a3de), committed as 6637187.

Relaunched scripts/mvp-smoke-test.sh --keep detached (setsid, survives the turn) against the rebuilt clean image and this fix branch. Will report pass/fail here once it finishes, push and open a PR, and file any new bugs as separate issues in the MVP milestone.

Applied the `.env` fix: `scripts/mvp-smoke-test.sh` step 1 now writes both `COMPOSE_PROFILES=bundled-db` and `POSTGRES_PASSWORD=...`. Moved off the merged `docs/GRI-1885-unblock-deps-note` branch onto a fresh `fix/GRI-1885-env-compose-profile` (origin/dev tip `2a8a3de`), committed as `6637187`. Relaunched `scripts/mvp-smoke-test.sh --keep` detached (setsid, survives the turn) against the rebuilt clean image and this fix branch. Will report pass/fail here once it finishes, push and open a PR, and file any new bugs as separate issues in the MVP milestone.
Member

Run4 (dev tip 2a8a3de + fix/GRI-1885-env-compose-profile's one-line .env fix, detached PID 2039650, log /tmp/mvp-smoke-test-GRI-1885-run4.log) got further than any prior run: build, volume-populate and the db container all passed with Vivy's rebuilt image. The server container still restart-loops on the same config.toml: Permission denied as the 23:52 report -- a freshly-generated working-tree file created after the 00:31 image fix still carries the inherited home-dir default ACL, so the root cause (the default: ACL on /home/astraea itself) is confirmed still live, not just a stale-image artifact. Evidence posted on grimoire-infra#321: Grimoirix/grimoire-infra#321 (comment)

Nothing left for a Test Writer to do until that lands -- it needs a root-level ACL fix on the home directory, same ask as before. Blocking again on grimoire-infra#321 (aetherius).

Run4 (dev tip 2a8a3de + fix/GRI-1885-env-compose-profile's one-line `.env` fix, detached PID 2039650, log `/tmp/mvp-smoke-test-GRI-1885-run4.log`) got further than any prior run: build, volume-populate and the db container all passed with Vivy's rebuilt image. The server container still restart-loops on the same `config.toml: Permission denied` as the 23:52 report -- a freshly-generated working-tree file created *after* the 00:31 image fix still carries the inherited home-dir default ACL, so the root cause (the `default:` ACL on `/home/astraea` itself) is confirmed still live, not just a stale-image artifact. Evidence posted on grimoire-infra#321: https://git.grimoirix.org/Grimoirix/grimoire-infra/issues/321#issuecomment-10206 Nothing left for a Test Writer to do until that lands -- it needs a root-level ACL fix on the home directory, same ask as before. Blocking again on grimoire-infra#321 (aetherius).
Author
Owner

01:15 (Vivy): the run4 restart loop is fixed. The server is up, /health answers {"status":"ok"}, and the panel is served on :8000.

Cause: packaging/server/config.toml was created at 00:32 under the inherited home ACL (grimoire-infra#321), so it was 0660 with other::---. It is bind-mounted read-only, and the server in the container runs as a non-root uid. Under rootless Docker that uid counts as "other" on the host file, so it could not read it. The image was fine.

What I did: as astraea, chmod 0644 and setfacl -b on that one file, then docker restart server-server-1. Nothing else changed. The containers are still running (--keep).

For your branch fix/GRI-1885-env-compose-profile: add chmod 0644 config.toml in mvp-smoke-test.sh right after the script writes the file. In the compose path this file holds no secret (the DB url comes from SIGNAGE_DATABASE_URL), and the script then does not depend on the umask or ACL of whoever runs it. Then carry on from the step after server start and report pass/fail here.

01:15 (Vivy): the run4 restart loop is fixed. The server is up, `/health` answers `{"status":"ok"}`, and the panel is served on :8000. **Cause:** `packaging/server/config.toml` was created at 00:32 under the inherited home ACL (grimoire-infra#321), so it was `0660` with `other::---`. It is bind-mounted read-only, and the server in the container runs as a non-root uid. Under rootless Docker that uid counts as "other" on the host file, so it could not read it. The image was fine. **What I did:** as astraea, `chmod 0644` and `setfacl -b` on that one file, then `docker restart server-server-1`. Nothing else changed. The containers are still running (`--keep`). **For your branch `fix/GRI-1885-env-compose-profile`:** add `chmod 0644 config.toml` in `mvp-smoke-test.sh` right after the script writes the file. In the compose path this file holds no secret (the DB url comes from `SIGNAGE_DATABASE_URL`), and the script then does not depend on the umask or ACL of whoever runs it. Then carry on from the step after server start and report pass/fail here.
Member

Vivy's config.toml fix (0644 + ACL strip on the bind-mounted file) confirmed: server came up healthy on :8000.

Added the same fix to scripts/mvp-smoke-test.sh (commit 8af8ddc on fix/GRI-1885-env-compose-profile): chmod 0644 + setfacl -b on config.toml right after it's copied from the example, so future runs don't trip the home-directory default ACL from grimoire-infra#321.

Tore down the manually-patched stack and relaunched the full automated script clean (run5) to get a real end-to-end pass on the fix rather than relying on the hand-patched state. Currently building the server image; will report the result here.

Vivy's config.toml fix (0644 + ACL strip on the bind-mounted file) confirmed: server came up healthy on :8000. Added the same fix to scripts/mvp-smoke-test.sh (commit 8af8ddc on fix/GRI-1885-env-compose-profile): `chmod 0644` + `setfacl -b` on config.toml right after it's copied from the example, so future runs don't trip the home-directory default ACL from grimoire-infra#321. Tore down the manually-patched stack and relaunched the full automated script clean (run5) to get a real end-to-end pass on the fix rather than relying on the hand-patched state. Currently building the server image; will report the result here.
Member

Run 5 (dev tip 8af8ddc, with the config.toml ACL fix) got further than every prior run: build, volume populate, db, server all up, client built and connected, device pending, approved through the admin API — and then rejected: sync: server says Rejected: already enrolled on another connection, backing off for minutes. This is no longer an infra/ACL blocker; it looks like a real race/bug in the enrolment handshake (handle_temporary_reconnect / issue_token in crates/server/src/ws.rs + devices.rs, likely compounded by the socket being dropped without a WebSocket close frame after approve()/pend()). Full evidence, code pointers and a repro note are on #123, labelled Area/Backend + Kind/Bug + Lang/Rust + Priority/High so it routes to a backend engineer.\n\nStack left up for inspection: server-server-1 / server-db-1 (compose project server) in /home/astraea/repos/wt-GRI-1885, client log at /tmp/mvp-smoke-test.iTBIty/client.log. Not touching crates/server or crates/client myself — that is #123's owner's call, not a Test Writer's. Blocking #115 on #123.

Run 5 (dev tip 8af8ddc, with the config.toml ACL fix) got further than every prior run: build, volume populate, db, server all up, client built and connected, device pending, approved through the admin API — and then rejected: `sync: server says Rejected: already enrolled on another connection`, backing off for minutes. This is no longer an infra/ACL blocker; it looks like a real race/bug in the enrolment handshake (handle_temporary_reconnect / issue_token in crates/server/src/ws.rs + devices.rs, likely compounded by the socket being dropped without a WebSocket close frame after approve()/pend()). Full evidence, code pointers and a repro note are on #123, labelled Area/Backend + Kind/Bug + Lang/Rust + Priority/High so it routes to a backend engineer.\n\nStack left up for inspection: server-server-1 / server-db-1 (compose project server) in /home/astraea/repos/wt-GRI-1885, client log at /tmp/mvp-smoke-test.iTBIty/client.log. Not touching crates/server or crates/client myself — that is #123's owner's call, not a Test Writer's. Blocking #115 on #123.
Author
Owner

Vivy 02:00: good find on #123, Nyssa has it (GRI-1912, running). One open item for you while you wait: your script fix (8af8ddc on fix/GRI-1885-env-compose-profile: COMPOSE_PROFILES=bundled-db + config.toml chmod) is not on the forge. Push it and open the PR to dev; I review and merge it. When #123 lands, rerun the smoke test on dev tip.

Vivy 02:00: good find on #123, Nyssa has it (GRI-1912, running). One open item for you while you wait: your script fix (8af8ddc on fix/GRI-1885-env-compose-profile: COMPOSE_PROFILES=bundled-db + config.toml chmod) is not on the forge. Push it and open the PR to dev; I review and merge it. When #123 lands, rerun the smoke test on dev tip.
Member

Pushed the script fix Vivy flagged: PR #124 (fix/GRI-1885-env-compose-profile, head 8af8ddc) — COMPOSE_PROFILES=bundled-db + config.toml chmod/ACL fix, both already verified end-to-end on this host. Local gates pass; CI now running on #124.

Separately, #123 (the reconnect-rejected bug that stopped run5) is being worked as GRI-1912 by nyssa.

Next: once #124 is merged and #123/GRI-1912 lands, rerun the smoke test on dev tip for the real end-to-end pass.

Pushed the script fix Vivy flagged: PR #124 (fix/GRI-1885-env-compose-profile, head 8af8ddc) — COMPOSE_PROFILES=bundled-db + config.toml chmod/ACL fix, both already verified end-to-end on this host. Local gates pass; CI now running on #124. Separately, #123 (the reconnect-rejected bug that stopped run5) is being worked as GRI-1912 by nyssa. Next: once #124 is merged and #123/GRI-1912 lands, rerun the smoke test on dev tip for the real end-to-end pass.
Member

No change needing action. PR #124 (script fixes) is CI-green on the required gate, ready to merge but not yet merged. PR #125 (nyssa, GRI-1912 backend reconnect fix) is still mid-CI. Will rerun the full smoke test on dev tip once both land.

No change needing action. PR #124 (script fixes) is CI-green on the required gate, ready to merge but not yet merged. PR #125 (nyssa, GRI-1912 backend reconnect fix) is still mid-CI. Will rerun the full smoke test on dev tip once both land.
Member

Run6 against dev tip 54ea3ea (after both PR #124 and GRI-1912/PR #125 merged) got further than ever: build, volume-populate, server up, db healthy, client connects, pending, approved. But the reconnect-rejection bug reproduces again at the exact same point — client goes straight to 'Rejected: already enrolled on another connection' on its first post-approval reconnect, never 'Accepted'. GRI-1912's graceful-close fix did not resolve the client-observed symptom end-to-end with the real client; reopened #123 with the new evidence (same milestone, assignee nyssa unchanged). Stack left up for inspection in /home/astraea/repos/wt-GRI-1885. Blocking GRI-1885 on #123 again.

Run6 against dev tip 54ea3ea (after both PR #124 and GRI-1912/PR #125 merged) got further than ever: build, volume-populate, server up, db healthy, client connects, pending, approved. But the reconnect-rejection bug reproduces again at the exact same point — client goes straight to 'Rejected: already enrolled on another connection' on its first post-approval reconnect, never 'Accepted'. GRI-1912's graceful-close fix did not resolve the client-observed symptom end-to-end with the real client; reopened #123 with the new evidence (same milestone, assignee nyssa unchanged). Stack left up for inspection in /home/astraea/repos/wt-GRI-1885. Blocking GRI-1885 on #123 again.
Member

Run7 (dev tip c789d2b, with #126's approve-token fix) is the furthest the smoke test has ever gotten: build, server up, db healthy, client enrolls, gets approved, reconnects as Accepted with no rejection loop — #126 confirmed fixed. Playlist arrives at the client (sync: server says Accepted: welcome back), upload and assignment succeed server-side.

It then fails step 5 for a different, more fundamental reason: the client never receives any file bytes. Player::next reports FallbackReason::CannotLoad forever (playback: nothing in the playlist can be shown yet) — the playlist is known and an item is due, but the cache never has it.

Root cause, filed as #127 (MVP milestone, assigned nyssa): the server never sends a TransferOffer. grep -rn TransferOffer crates/server/src is empty. push_to_device (playlists/handlers.rs) pushes MediaManifest and PlaylistPush only; ws.rs:5 says outright "Transfers are later work." The client's half of the protocol (session.rs::on_offer/on_binary, chunked resume, hash verify) is fully implemented and unit-tested but has never been exercised against a real server, because the server has no code path that constructs a TransferOffer for any device, ever. This is specced in plan/shared/protocol.md ("Media transfer") but was never built server-side.

This is the core "device downloads and plays content" feature, and it's missing, not flaky — not something I should patch as Test Writer. Stack left up for inspection: server-server-1/server-db-1 in /home/astraea/repos/wt-GRI-1885, client log at /tmp/mvp-smoke-test.Yrmzrd/client.log.

Blocking GRI-1885 on #127. Will rerun the full smoke test once media transfer is implemented server-side.

Run7 (dev tip c789d2b, with #126's approve-token fix) is the furthest the smoke test has ever gotten: build, server up, db healthy, client enrolls, gets approved, **reconnects as Accepted with no rejection loop** — #126 confirmed fixed. Playlist arrives at the client (`sync: server says Accepted: welcome back`), upload and assignment succeed server-side. It then fails step 5 for a different, more fundamental reason: the client never receives any file bytes. `Player::next` reports `FallbackReason::CannotLoad` forever (`playback: nothing in the playlist can be shown yet`) — the playlist is known and an item is due, but the cache never has it. Root cause, filed as #127 (MVP milestone, assigned nyssa): **the server never sends a `TransferOffer`.** `grep -rn TransferOffer crates/server/src` is empty. `push_to_device` (`playlists/handlers.rs`) pushes `MediaManifest` and `PlaylistPush` only; `ws.rs:5` says outright "Transfers are later work." The client's half of the protocol (`session.rs::on_offer`/`on_binary`, chunked resume, hash verify) is fully implemented and unit-tested but has never been exercised against a real server, because the server has no code path that constructs a `TransferOffer` for any device, ever. This is specced in `plan/shared/protocol.md` ("Media transfer") but was never built server-side. This is the core "device downloads and plays content" feature, and it's missing, not flaky — not something I should patch as Test Writer. Stack left up for inspection: `server-server-1`/`server-db-1` in `/home/astraea/repos/wt-GRI-1885`, client log at `/tmp/mvp-smoke-test.Yrmzrd/client.log`. Blocking GRI-1885 on #127. Will rerun the full smoke test once media transfer is implemented server-side.
Member

PR #128 confirmed merged into dev (91e72c4): server-side media transfer (TransferOffer, chunk streaming, resend of assignment on Accepted reconnect) is implemented. Closing #127 as fixed. Relaunched the smoke test (run8) against dev tip 91e72c4 — will report pass/fail here once it finishes.

PR #128 confirmed merged into dev (91e72c4): server-side media transfer (TransferOffer, chunk streaming, resend of assignment on Accepted reconnect) is implemented. Closing #127 as fixed. Relaunched the smoke test (run8) against dev tip 91e72c4 — will report pass/fail here once it finishes.
Member

Run8 (dev tip 91e72c4, with #127/#128 server-side media transfer landed) is the furthest yet: enroll, approve, upload, assign, and initial playback (image + video both played) all pass for the first time — the core download-and-play feature works end to end.

It then fails on the last step: changing the already-assigned playlist's items. The client never receives the update and loops the original playlist forever (confirmed via 30s+ of client log with no new frame).

Root cause: replace_items (PUT /playlists/{id}/items, crates/server/src/playlists/handlers.rs:236) never pushes to the live connection — only assign_playlist and the Accepted-reconnect resend do. plan/shared/protocol.md:104 requires PlaylistPush "once on assignment and again on every change to the device's assigned playlist." Filed as #129, assigned nyssa.

Stack left up for inspection in /home/astraea/repos/wt-GRI-1885 (compose project server); client log at /tmp/mvp-smoke-test.oCVzze/client.log; full run log /tmp/mvp-smoke-test-GRI-1885-run8.log.

Blocking on #129; will rerun the smoke test once the playlist-edit push lands.

(Side note, not blocking: fj issue-open --label/fj label --add both 403 for me with "token does not have at least one of required scope(s): [read:organization]" — #129 was opened with no labels and milestone unset as a result. Not spending more time on it; flagging in case it's a wider token-scope gap.)

Run8 (dev tip `91e72c4`, with #127/#128 server-side media transfer landed) is the furthest yet: enroll, approve, upload, assign, and initial playback (image + video both played) all pass for the first time — the core download-and-play feature works end to end. It then fails on the last step: changing the already-assigned playlist's items. The client never receives the update and loops the original playlist forever (confirmed via 30s+ of client log with no new frame). Root cause: `replace_items` (`PUT /playlists/{id}/items`, `crates/server/src/playlists/handlers.rs:236`) never pushes to the live connection — only `assign_playlist` and the `Accepted`-reconnect resend do. `plan/shared/protocol.md:104` requires `PlaylistPush` "once on assignment and again on every change to the device's assigned playlist." Filed as #129, assigned nyssa. Stack left up for inspection in `/home/astraea/repos/wt-GRI-1885` (compose project `server`); client log at `/tmp/mvp-smoke-test.oCVzze/client.log`; full run log `/tmp/mvp-smoke-test-GRI-1885-run8.log`. Blocking on #129; will rerun the smoke test once the playlist-edit push lands. (Side note, not blocking: `fj issue-open --label`/`fj label --add` both 403 for me with "token does not have at least one of required scope(s): [read:organization]" — #129 was opened with no labels and milestone unset as a result. Not spending more time on it; flagging in case it's a wider token-scope gap.)
Author
Owner

Run 9 pass on eb0de5b is good news, thank you. But please do not close #115 yet.

The smoke test covers image + video only (step 4 of scripts/mvp-smoke-test.sh). The product owner's must-haves for 11-20 are PDF and web page URL (2 campuses each); image and video are the first things we cut. So the end-to-end path that matters has not run yet.

Please extend the script, in the same PR as the docs result or a follow-up before closing:

  1. Generate a 2-page PDF (e.g. convert xc:white xc:white lobby.pdf, or gs), upload via POST /api/v1/media, and check the server returns page images.
  2. Add a web page item (URL kind; use the server's own /health or a local static page so no internet is needed).
  3. Playlist = PDF + web page (keep image/video after them if cheap), assign, and wait_for_log for PDF page playback (each page as an Image item) and for the web page item.
  4. Edit-follow-through step stays as is.

Any failure: file a forge issue as before; I triage and route it.

Run 9 pass on eb0de5b is good news, thank you. But please do not close #115 yet. The smoke test covers **image + video** only (step 4 of `scripts/mvp-smoke-test.sh`). The product owner's must-haves for 11-20 are **PDF and web page URL** (2 campuses each); image and video are the first things we cut. So the end-to-end path that matters has not run yet. Please extend the script, in the same PR as the docs result or a follow-up before closing: 1. Generate a 2-page PDF (e.g. `convert xc:white xc:white lobby.pdf`, or `gs`), upload via `POST /api/v1/media`, and check the server returns page images. 2. Add a web page item (URL kind; use the server's own `/health` or a local static page so no internet is needed). 3. Playlist = PDF + web page (keep image/video after them if cheap), assign, and `wait_for_log` for PDF page playback (each page as an Image item) and for the web page item. 4. Edit-follow-through step stays as is. Any failure: file a forge issue as before; I triage and route it.
Member

PR #132 (PDF render-dir fix) merged into dev at b71fd85. Synced wt-GRI-1885 (merge commit 0698f94), no leaked processes/stacks from run10. Relaunched scripts/mvp-smoke-test.sh --keep detached under setsid (run11, PID 323803, own session, survives this turn) with DOCKER_HOST=unix:///run/user/1007/docker.sock. Log: /tmp/mvp-smoke-test-GRI-1885-run11.log. This exercises PDF (2-page) + web-page items for the first time, with every previously found bug fixed on dev. Will report pass/fail once it finishes.

PR #132 (PDF render-dir fix) merged into dev at b71fd85. Synced wt-GRI-1885 (merge commit 0698f94), no leaked processes/stacks from run10. Relaunched scripts/mvp-smoke-test.sh --keep detached under setsid (run11, PID 323803, own session, survives this turn) with DOCKER_HOST=unix:///run/user/1007/docker.sock. Log: /tmp/mvp-smoke-test-GRI-1885-run11.log. This exercises PDF (2-page) + web-page items for the first time, with every previously found bug fixed on dev. Will report pass/fail once it finishes.
Member

Run11 is a full PASS on dev tip b71fd85 (scripts/mvp-smoke-test.sh --keep): enroll, approve, upload of an image, a video, a 2-page PDF, and a web page URL, playlist assignment, and playback of all four item kinds — including the two must-haves for the test week (#29), the PDF pages and the web page — plus a live playlist-edit follow-through, all end to end in one run.

This also confirms #131/#132 (PDF render-dir deleted before pages were read) has no recurrence.

Writing up docs/mvp-smoke-test.md's Result section now (describing run11 instead of run9, which only covered image+video), running local gates, then opening the PR to dev. Full log held locally at /tmp/mvp-smoke-test-GRI-1885-run11.log; posting the tail here for the record:

== step 4: upload an image, a video, a PDF, and a web page URL; build a playlist; assign it ==
uploaded: image=61c54e99-a628-4d2d-ac62-642d6372e634 video=ce1a2f58-86d7-4bd1-82f3-fc9994fb0187
uploaded: pdf -> page1=8e1d0795-1a89-4f00-890a-86add0814e55 page2=9fa667ad-fda1-4cbd-babb-7eebbbd28730 (AC-3-03)
playlist 4d90ad28-420c-4823-8eec-3544eb3e04c6 (PDF page 1+2, web page, image, video) assigned to device ad9c56e4-b93c-4f11-82d5-5eccda7678cd (AC-4-01)

== step 5: confirm playback, then change the playlist ==
PDF page 1 played (AC-3-03, AC-5-01)
PDF page 2 played (AC-3-03)
web page played (AC-3-04, AC-5-01)
image played (AC-5-01, AC-5-02)
video played
the client followed the changed playlist with no restart

== done ==
PASS: AC-1-01 (backend half, via API), AC-2-01, AC-2-02, AC-3-01, AC-3-02 (upload only, deferred conversion job out of MVP scope), AC-3-03, AC-3-04, AC-4-01, AC-5-01, AC-5-02.

MANUAL, still to confirm by eye in a browser: the panel itself (Step 2) -- no browser-automation tooling on this host.
Run11 is a full PASS on dev tip b71fd85 (scripts/mvp-smoke-test.sh --keep): enroll, approve, upload of an image, a video, a 2-page PDF, and a web page URL, playlist assignment, and playback of **all four item kinds** — including the two must-haves for the test week (#29), the PDF pages and the web page — plus a live playlist-edit follow-through, all end to end in one run. This also confirms #131/#132 (PDF render-dir deleted before pages were read) has no recurrence. Writing up docs/mvp-smoke-test.md's Result section now (describing run11 instead of run9, which only covered image+video), running local gates, then opening the PR to dev. Full log held locally at /tmp/mvp-smoke-test-GRI-1885-run11.log; posting the tail here for the record: ``` == step 4: upload an image, a video, a PDF, and a web page URL; build a playlist; assign it == uploaded: image=61c54e99-a628-4d2d-ac62-642d6372e634 video=ce1a2f58-86d7-4bd1-82f3-fc9994fb0187 uploaded: pdf -> page1=8e1d0795-1a89-4f00-890a-86add0814e55 page2=9fa667ad-fda1-4cbd-babb-7eebbbd28730 (AC-3-03) playlist 4d90ad28-420c-4823-8eec-3544eb3e04c6 (PDF page 1+2, web page, image, video) assigned to device ad9c56e4-b93c-4f11-82d5-5eccda7678cd (AC-4-01) == step 5: confirm playback, then change the playlist == PDF page 1 played (AC-3-03, AC-5-01) PDF page 2 played (AC-3-03) web page played (AC-3-04, AC-5-01) image played (AC-5-01, AC-5-02) video played the client followed the changed playlist with no restart == done == PASS: AC-1-01 (backend half, via API), AC-2-01, AC-2-02, AC-3-01, AC-3-02 (upload only, deferred conversion job out of MVP scope), AC-3-03, AC-3-04, AC-4-01, AC-5-01, AC-5-02. MANUAL, still to confirm by eye in a browser: the panel itself (Step 2) -- no browser-automation tooling on this host. ```
Member

Pushed and opened PR #133 (dev <- docs/GRI-1885-smoke-test-pass, commit db2c029), carrying the run11 Result write-up and the script's PDF+web-page extension. Local gates passed before push; forge CI is running now (queue position 0).

Pushed and opened PR #133 (dev <- docs/GRI-1885-smoke-test-pass, commit db2c029), carrying the run11 Result write-up and the script's PDF+web-page extension. Local gates passed before push; forge CI is running now (queue position 0).
vivy closed this issue 2026-11-11 10:56:29 +00:00
Author
Owner

Done. Smoke run 11 on dev b71fd85 passed in full: enrol, approve, upload, assign, playback of PDF pages, web page, image and video, live edit. Script and doc merged in #133 (dev 3ef69ad).

Done. Smoke run 11 on dev b71fd85 passed in full: enrol, approve, upload, assign, playback of PDF pages, web page, image and video, live edit. Script and doc merged in #133 (dev 3ef69ad).
Sign in to join this conversation.
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage#115
No description provided.