jschoubben 37613ec6a9 pacman reads the node-engine's packages as mesh-host.packages, the bucket each engine writes (ADR 0565 clause 6, issue 1953) ...

The read node-engine.packages named a bucket node-engine_packages that nothing writes:
the engine's manifest is mesh-host's, so its state is mesh-host_packages, read as
disk-load reads mesh-host.data. The view still names which source answered, the
engine's key or the controller's mirror.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

2026-11-01 16:09:50 +01:00

..

testdata

issue 1841/S2: leave the login manager's configuration path out of pacman's captured log, which the paths check refuses in another module's fixture

2026-10-22 17:45:29 +02:00

acts.go

Carry out an upgrade as an ask its node's keeper takes, through the root helper, and follow a run to its end after a restart, so a hand upgrade is a recorded, checked run like any other (issue 1841/S5)

2026-10-22 14:35:19 +02:00

aftercheck_test.go

issue 1841/S7: name the processes still mapping a replaced file and fail the check on a DKMS module not built for an installed kernel, so a machine is never left unable to load its drivers unnoticed

2026-10-22 14:39:29 +02:00

aftercheck.go

issue 1841/S7: name the processes still mapping a replaced file and fail the check on a DKMS module not built for an installed kernel, so a machine is never left unable to load its drivers unnoticed

2026-10-22 14:39:29 +02:00

bus_fake_test.go

Keep every upgrade as a run on the bus and read the log's past upgrades once, so pacman_upgrades answers every node's history without asking a machine (issue 1841/S2)

2026-10-22 14:29:23 +02:00

busshapes_test.go

issue 1841/S7: name the processes still mapping a replaced file and fail the check on a DKMS module not built for an installed kernel, so a machine is never left unable to load its drivers unnoticed

2026-10-22 14:39:29 +02:00

dkms_test.go

Hold a kernel an installed DKMS module's own bound excludes, with its headers, so an upgrade never leaves a machine whose storage driver cannot load (issue 1841/S4)

2026-10-22 14:31:53 +02:00

dkms.go

issue 1841/S4: format the gate's patterns as gofmt does, which the merge check requires

2026-10-22 14:32:01 +02:00

history.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

installed_health_test.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00

installed_health.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00

keeper_bus_test.go

issue 1840/S9: prove pacman's output puts no command line or environment on the bus

2026-10-22 14:37:00 +02:00

keeper_hooks_test.go

issue 1841/S8: join the round to the keeper's loop, so a node starts the moment the node before it passed and a pass is answered from the operator's channel

2026-10-22 17:35:36 +02:00

keeper_integration_test.go

pacman reads the node-engine's packages as mesh-host.packages, the bucket each engine writes (ADR 0565 clause 6, issue 1953)

2026-11-01 16:09:50 +01:00

keeper_manifest_test.go

pacman reads the node-engine's packages as mesh-host.packages, the bucket each engine writes (ADR 0565 clause 6, issue 1953)

2026-11-01 16:09:50 +01:00

keeper_test.go

issue 1840/S6: emit through the same EventSink as the upgrade parts, so one connection serves both

2026-10-22 14:32:10 +02:00

keeper.go

issue 1841/S12: prove the round on a real bus with two made-up nodes, so the second node is seen to start only after the first passed and never after a failed check

2026-10-22 17:39:15 +02:00

machine_test.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

machine.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00

main.go

pacman: a plain-words search finds pacman_round and pacman_upgrades first (answer on the first line, phrases they replace)

2026-10-26 13:27:09 +01:00

manifest_test.go

pacman, ssh-client: tests read nothing of the machine, so the unit level passes shut off and on a desk (issue 1891)

2026-10-23 09:38:40 +02:00

mapped_test.go

issue 1841/S7: name the processes still mapping a replaced file and fail the check on a DKMS module not built for an installed kernel, so a machine is never left unable to load its drivers unnoticed

2026-10-22 14:39:29 +02:00

mapped.go

issue 1841/S7: name the processes still mapping a replaced file and fail the check on a DKMS module not built for an installed kernel, so a machine is never left unable to load its drivers unnoticed

2026-10-22 14:39:29 +02:00

mirrors.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

news.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

packages.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00

pacman_test.go

issue 1841/S11: judge the upgrades' health from the runs, rounds and held kernels on the bus, so a node that slept through a run is judged by what happened, not by a unit's age (folds issue 1579)

2026-10-22 17:38:08 +02:00

query.go

issue 1840/S8: answer the package view from the bus, so every node is read at once and none is asked

2026-10-22 14:36:11 +02:00

reads-outside

mesh-build-go: a reads-outside marker lists what its tests read, so its package is kept until one of those files changes (issue 1936)

2026-10-26 22:02:58 +01:00

record_test.go

Take the node's package record before a run and read it back, refusing a run whose packages are not current, so a rollback always has a true record to return to (issue 1841/S3)

2026-10-22 14:30:34 +02:00

record.go

Take the node's package record before a run and read it back, refusing a run whose packages are not current, so a rollback always has a true record to return to (issue 1841/S3)

2026-10-22 14:30:34 +02:00

rollback_test.go

issue 1841/S10: return a node to a run's record, saying first what each package goes back to and from where

2026-10-22 14:44:24 +02:00

rollback.go

Let no run read from pacman's log, nor a run whose transaction ended, hold an asked upgrade back; read one run of the addressed machine whole (issue 1841)

2026-10-22 22:04:23 +02:00

root_test.go

issue 1841/S9: carry out the upgrade's root acts through a root helper on a socket only the keeper opens, so no sudo rule lets the keeper's account run anything as root (ADR 0510)

2026-10-22 17:34:20 +02:00

root.go

issue 1841/S9: carry out the upgrade's root acts through a root helper on a socket only the keeper opens, so no sudo rule lets the keeper's account run anything as root (ADR 0510)

2026-10-22 17:34:20 +02:00

round_integration_test.go

issue 1841/S12: prove the round on a real bus with two made-up nodes, so the second node is seen to start only after the first passed and never after a failed check

2026-10-22 17:39:15 +02:00

rounds_test.go

issue 1841/S8: upgrade the nodes one at a time in a weekly round in upgrade-order, stopping at a failure and passing a node only on the operator's Approve, so one bad upgrade never reaches every machine

2026-10-22 14:44:17 +02:00

rounds.go

issue 1841/S8: upgrade the nodes one at a time in a weekly round in upgrade-order, stopping at a failure and passing a node only on the operator's Approve, so one bad upgrade never reaches every machine

2026-10-22 14:44:17 +02:00

runs_test.go

Keep every upgrade as a run on the bus and read the log's past upgrades once, so pacman_upgrades answers every node's history without asking a machine (issue 1841/S2)

2026-10-22 14:29:23 +02:00

shape_test.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

shapes.go

issue 1841/S7: name the processes still mapping a replaced file and fail the check on a DKMS module not built for an installed kernel, so a machine is never left unable to load its drivers unnoticed

2026-10-22 14:39:29 +02:00

stale_run_test.go

Name the captured log's machine by its role, not its name (issue 1841)

2026-10-22 22:05:27 +02:00

templates_test.go

Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main

2026-10-16 09:42:45 +00:00

transaction_test.go

Merge branch 'feat/upgrade-safety' into p2

2026-10-22 14:44:41 +02:00

transaction.go

Let no run read from pacman's log, nor a run whose transaction ended, hold an asked upgrade back; read one run of the addressed machine whole (issue 1841)

2026-10-22 22:04:23 +02:00

updates_test.go

issue 1840/S7: prove updates is read at start, after a transaction, after the mirrors and daily, and written only on change

2026-10-22 14:33:20 +02:00

upgrade_health_test.go

issue 1841/S11: judge the upgrades' health from the runs, rounds and held kernels on the bus, so a node that slept through a run is judged by what happened, not by a unit's age (folds issue 1579)

2026-10-22 17:38:08 +02:00

upgrade_health.go

issue 1841/S11: judge the upgrades' health from the runs, rounds and held kernels on the bus, so a node that slept through a run is judged by what happened, not by a unit's age (folds issue 1579)

2026-10-22 17:38:08 +02:00

upgrades.go

Merge branch 'feat/upgrade-safety' into p2

2026-10-22 14:44:41 +02:00

view_test.go

pacman falls back to the controller's mirror for every node when the engine's state cannot be read, and says the engine's error (ADR 0565 clause 6, review round 2)

2026-11-01 09:54:07 +01:00

view.go

pacman reads the node-engine's packages as mesh-host.packages, the bucket each engine writes (ADR 0565 clause 6, issue 1953)

2026-11-01 16:09:50 +01:00

watch.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00