Register R233: a declaration that restores the package manager applies while it does not answer (hq issue 233) #82

Closed
mesh-admin wants to merge 1 commits from fix/233-replay into main
Contributor

What

Registers replay R233 in replays/register.go: the node-engine test TestReplay233 (./cmd/mesh-host, file cmd/mesh-host/replay233_test.go) in mesh-host, fix = the merge of mesh-host #90 (a1f9856b).

Why

Issue 233 is a core issue; it resolves with its replay registered. On 2026-10-04 a removed pacman configuration made pacman stop answering, and the node-engine refused every declaration whole, including the one that would have written the file back. The replay holds that such a declaration applies: only what needs pacman fails, with the probe's words, and the file is written and recorded.

The controller's half of the fix (mesh-controller #263, db7e4869: a machine refused or only partly applied past one apply interval raises a condition) is held by its own tests in the controller; the comment on the entry says so.

How it was tested

  • go run ./cmd/prove R233:
    R233 (issue 233): PROVED — before its fix fails, on its fix passes
    before: replay233_test.go:50: the declaration that restores the package manager's configuration was refused whole: this is the arch host and pacman does not answer here. ...
  • go test ./... in replays/ passes; sh merge-check.sh passes (the asks proof says NOT RUN for lack of the mesh-tools clone here, as on any machine without it).

Note: mesh-lab #81 (R237) inserts at the same place in the register; whichever merges second needs a one-line rebase.

Fixes issue 233 (its replay).

## What Registers replay R233 in `replays/register.go`: the node-engine test `TestReplay233` (`./cmd/mesh-host`, file `cmd/mesh-host/replay233_test.go`) in mesh-host, fix = the merge of mesh-host #90 (`a1f9856b`). ## Why Issue 233 is a core issue; it resolves with its replay registered. On 2026-10-04 a removed pacman configuration made pacman stop answering, and the node-engine refused every declaration whole, including the one that would have written the file back. The replay holds that such a declaration applies: only what needs pacman fails, with the probe's words, and the file is written and recorded. The controller's half of the fix (mesh-controller #263, `db7e4869`: a machine refused or only partly applied past one apply interval raises a condition) is held by its own tests in the controller; the comment on the entry says so. ## How it was tested - `go run ./cmd/prove R233`: `R233 (issue 233): PROVED — before its fix fails, on its fix passes` `before: replay233_test.go:50: the declaration that restores the package manager's configuration was refused whole: this is the arch host and pacman does not answer here. ...` - `go test ./...` in `replays/` passes; `sh merge-check.sh` passes (the asks proof says NOT RUN for lack of the mesh-tools clone here, as on any machine without it). Note: mesh-lab #81 (R237) inserts at the same place in the register; whichever merges second needs a one-line rebase. Fixes issue 233 (its replay).
mesh-admin added 1 commit 2026-10-12 14:19:25 +00:00
Register R233: a declaration that restores the package manager applies while it does not answer (hq issue 233)
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go), asks/merge-check.sh …
mesh/delivery stopped: the pull request closed unmerged
a8a7889c82
Proved with go run ./cmd/prove R233: fails on mesh-host#90's commit before
(36704b5), passes on the fix (a1f9856, mesh-host#90).
Author
Contributor

Delivery novox/mesh-lab@a8a7889c825b — stopped since 2026-10-12T14:42:24Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-12 14:19 (new) → proposed (announced): novox/mesh-lab#82's head announced
  • 2026-10-12 14:23 proposed → checked (checked): the verdict names this commit
  • 2026-10-12 14:23 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-12 14:42 ready → stopped (closed): the pull request closed unmerged

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-lab@a8a7889c825b` — **stopped** since 2026-10-12T14:42:24Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-12 14:19 (new) → proposed (announced): novox/mesh-lab#82's head announced - 2026-10-12 14:23 proposed → checked (checked): the verdict names this commit - 2026-10-12 14:23 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-12 14:42 ready → stopped (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Replaced by #84: the same R233 entry on a fresh branch off main after #83 (R237) merged at the same insertion point, placed after R237 and proved again there (go run ./cmd/prove R233: PROVED). Closing this one.

Replaced by #84: the same R233 entry on a fresh branch off main after #83 (R237) merged at the same insertion point, placed after R237 and proved again there (`go run ./cmd/prove R233`: PROVED). Closing this one.
mesh-admin closed this pull request 2026-10-12 14:42:03 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-lab#82