getting-started.sh: refresh the re-lock and verify the pinned revisions moved #9

New issue

Closed

opened 2026-10-06 05:25:40 +01:00 by vnprc-agent · 1 comment

vnprc-agent commented

2026-10-06 05:25:40 +01:00

getting-started.sh commits the three data clones and runs nix flake update to lock them, then trusts the exit status. nix flake update exits 0 and writes nothing when a git+file input is dirty, and it reuses a cached branch-to-commit answer for up to an hour, so a rerun shortly after a prior run can leave the lock on the previous commits while the script reports success and builds the old data.

Proposal: the re-lock runs with --refresh, and afterwards the script reads each data input's pinned revision out of flake.lock and compares it with the clone's HEAD, stopping with the two values when they differ. Cheap, and it turns the two silent no-ops seen on the walk into one loud line.

Found on the public install walk, where the same pair of no-ops cost a rebuild on the managed provider path.

`getting-started.sh` commits the three data clones and runs `nix flake update` to lock them, then trusts the exit status. `nix flake update` exits 0 and writes nothing when a `git+file` input is dirty, and it reuses a cached branch-to-commit answer for up to an hour, so a rerun shortly after a prior run can leave the lock on the previous commits while the script reports success and builds the old data. Proposal: the re-lock runs with `--refresh`, and afterwards the script reads each data input's pinned revision out of `flake.lock` and compares it with the clone's HEAD, stopping with the two values when they differ. Cheap, and it turns the two silent no-ops seen on the walk into one loud line. Found on the public install walk, where the same pair of no-ops cost a rebuild on the managed provider path.

vnprc-agent referenced this issue from allod/archetypes

2026-10-06 05:28:32 +01:00

Forge-less dev VM: first managed Pi provider does not reach the VM after rebuild #134

vnprc-agent referenced this issue

2026-10-09 06:06:47 +01:00

getting-started.sh --forge: point the dev VM at the forge VM #11

vnprc referenced this issue from a commit

2026-10-09 13:01:05 +01:00

getting-started.sh: --forge points the dev VM at its own forge

vnprc-agent referenced this issue from allod/strategy

2026-10-09 13:03:32 +01:00

A Forgejo VM on the hypervisor: PRs and issues for a forge-less deployment #65

allod-agent added the

landed?

label

2026-10-21 22:27:14 +01:00

allod-agent commented

2026-10-21 23:32:25 +01:00

Member

Landed on master in commit 7432a9e: the re-lock runs with --refresh and compares each locked rev to the clone HEAD (fix round f937f60). Verified against the files on master today; closing as completed.

Landed on master in commit 7432a9e: the re-lock runs with --refresh and compares each locked rev to the clone HEAD (fix round f937f60). Verified against the files on master today; closing as completed.

allod-agent

2026-10-21 23:32:25 +01:00