gitea fills repositories.json through the provisioner client, so an approved repositories value lands at once (issue 1128) #364

Merged

mesh-tools merged 1 commits from fix/1128-repositories-template into main 2026-10-18 16:03:59 +00:00

Conversation 2 Commits 1 Files Changed 3

+27 -11

mesh-tools commented 2026-10-18 15:59:38 +00:00

Member

Copy Link

Copy Source

Issue 1128: the operator's Approve of the repositories value (mesh-delivery) set it in mesh-config at 17:16, but the file was a mergeable file (merge, takes-config) that the controller fills only on a node's send, and a config change opens no send (ADR 0348 §10). So novox/mesh-delivery was never made.

• modules/gitea/module.json: repositories-file loses merge and takes-config, so the controller hands it to the provisioner client (handedFile).
• modules/gitea/files/repositories.json: {"repositories": ${config:repositories}}; the client writes an object value as its JSON (configText), the default as {"repositories": {}}, which the program reads as empty like today's {} on novox. The node-engine reruns the run-once program that names the file under restart-on.
• Test 1128/AC1 (manifest_test.go): fails on main, passes here.

Try: pass (build-1792339115784891656, 37 s). Same delay in two more gitea files: issue 1139.

Reviewed-by: reviewer-1128@shanks at e75e793a4b

Issue 1128: the operator's Approve of the repositories value (mesh-delivery) set it in mesh-config at 17:16, but the file was a mergeable file (merge, takes-config) that the controller fills only on a node's send, and a config change opens no send (ADR 0348 §10). So novox/mesh-delivery was never made. - `modules/gitea/module.json`: repositories-file loses merge and takes-config, so the controller hands it to the provisioner client (handedFile). - `modules/gitea/files/repositories.json`: `{"repositories": ${config:repositories}}`; the client writes an object value as its JSON (configText), the default as `{"repositories": {}}`, which the program reads as empty like today's `{}` on novox. The node-engine reruns the run-once program that names the file under restart-on. - Test 1128/AC1 (manifest_test.go): fails on main, passes here. Try: pass (build-1792339115784891656, 37 s). Same delay in two more gitea files: issue 1139. Reviewed-by: reviewer-1128@shanks at e75e793a4b3ba4ea7ce22ef5c60ba828cb89c77e

mesh-tools added 1 commit 2026-10-18 15:59:38 +00:00

gitea: fill repositories.json through the provisioner client, so an approved value lands at once (issue 1128) ... e75e793a4b

The file was merged by the controller (merge, takes-config), which writes a
config change only on the node's next send (ADR 0348 §10): the operator's
Approve of the mesh-delivery repository set the value and nothing made it.
A plain template saying ${config:repositories} is filled by the provisioner
client on config-changed, and the node-engine reruns the run-once program
that names the file under restart-on.

mesh-tools commented 2026-10-18 15:59:46 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@e75e793a4b3b — delivered since 2026-10-18T16:07:26Z

Delivery plan — builds gitea → novox; no bus step

• tier 0: gitea
• novox: receives gitea
• gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it
• gitea keeps data (ADR 0233): what it holds is backed up before it moves

Machines

• gitea on every machine running it: sent

Transitions

• 2026-10-18 15:59 (new) → proposed (announced): novox/mesh-catalog#364's head announced
• 2026-10-18 16:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-18 16:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-18 16:04 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-18 16:04 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
• 2026-10-18 16:07 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@e75e793a4b3b` — **delivered** since 2026-10-18T16:07:26Z **Delivery plan** — builds gitea → novox; no bus step - tier 0: gitea - novox: receives gitea - gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - gitea on every machine running it: sent **Transitions** - 2026-10-18 15:59 (new) → proposed (announced): novox/mesh-catalog#364's head announced - 2026-10-18 16:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 16:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 16:04 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-18 16:04 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-18 16:07 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools commented 2026-10-18 16:02:33 +00:00

Author

Member

Copy Link

Copy Source

Merge check at e75e793a
Judged: head e75e793a4b3b merged into trunk cfb90d7b2f96; read beside it: mesh-controller 48e9656c670b, mesh-controller-main 48e9656c670b, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5

• mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea)
• mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds gitea → novox; no bus step

• tier 0: gitea
• novox: receives gitea
• gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it
• gitea keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on ace as build-1792339181581837082 (builds --log build-1792339181581837082).

✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.596051ms)
✔ a start heard after the verdict writes nothing (0.540206ms)
✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.675391ms)
✔ an old run's verdict redelivered after a recheck's pending is not written over it (0.973641ms)
[gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check the forge holds pending; not written
[gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check now pending; not written
✔ an old run's verdict in flight when the recheck comes lands before the recheck's pending (3.937617ms)
✔ a rechecked head says where its new run is: building on which machine (0.897659ms)
✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.773155ms)
✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.612752ms)
✔ a recheck the forge does not take fails its caller, and the head is as it was (1.165603ms)
✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (9.581312ms)
✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (1.998187ms)
✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (0.4092ms)
✔ a repository as the mesh clones it is told from another (0.278223ms)
✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.79465ms)
✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (49.6234ms)
✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (16.62977ms)
✔ gitea_api still writes what an author writes (7.245017ms)
✔ gitea_branch_protection_set only strengthens (14.993472ms)
✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (42.951731ms)
✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (139.844377ms)
✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (14.644045ms)
✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (12.486287ms)
✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (26.394537ms)
✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (55.513621ms)
✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (20.423437ms)
✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.210059ms)
✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (5.852387ms)
✔ a rule named for a branch is not made weaker than the glob rule that guards it now (13.851675ms)
✔ a repository owner or name is never another path (0.238649ms)
✔ the judges, without a forge (0.351321ms)
✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.251212ms)
✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (2.067799ms)
✔ gitea_api never approves a pull request nor requests changes: those are the operator's (1.530899ms)
✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.576478ms)
✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each head approved (80.232186ms)
✔ gitea_merge_pull_request refuses a head the Approve did not name (20.009518ms)
✔ a group of two merges in one pass: the sibling's merge of the composed head does not stop the member's merge (issue 1049) (15.1303ms)
✔ gitea_create_repo has no owner argument and posts only to the tools' own user's repositories (1124/AC8) (30.548511ms)
✔ the tools' team cannot create in the organisation and its token holds no write:organization (1124/AC8) (0.344147ms)
✔ no ready mark, trusted ready-authors setting or approval-by-mark rule is left in the module (19.4948ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (27.526417ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.450227ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (11.974905ms)
✔ a lookup the forge refuses is thrown, not read as no module (3.872274ms)
✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (4.330986ms)
✔ a new head beyond the newest 20 open pull requests is announced, exactly once (77.544711ms)
✔ a pass pages until it reaches back past its floor, and no further (21.696452ms)
✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (25.429674ms)
✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (9.553579ms)
✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (3.802663ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (3.594461ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.311937ms)
✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.602624ms)
✔ another branch's body carries no merge whitelist (0.270269ms)
✔ the rule main is put right in the forge's own words: the body a setup sends carries no status checks of its own (0.380125ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (13.834994ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.121469ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.796668ms)
✔ no verdict sets warning on a required check; only a person's decision fails (1.115038ms)
✔ a commit status is set on the commit, under the merge check's context (41.582455ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.482337ms)
✔ a head announced is pending in the build queue, since the local time it was announced (0.383351ms)
✔ a composed verdict sets every member's gate at its own head, naming its trunk and the group (0.584529ms)
✔ a member's own verdict with a composed gate layer leaves the gate to the composed verdict, in either order (0.692943ms)
✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.645205ms)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 at bbbbbbbbbbbb, it is now at dddddddddddd: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was closed unmerged: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 merged onto cccccccccccc, its main is now eeeeeeeeeeee: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-host's main moved from 444444444444 to 333333333333: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382)
[gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head dddddddddddd onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382)
✔ both statuses name the siblings the verdict read, keeping the verdict word and the start of its reason within 140 characters (2.457662ms)
✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (1.293232ms)
✔ a verdict without siblings is said exactly as before (an older controller) (0.824931ms)
✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (0.932764ms)
✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (1.896547ms)
✔ a sibling closed unmerged puts the member's verdict out of date (0.357553ms)
✔ a move of the sibling's base puts it out of date, naming both commits (0.437993ms)
✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.720826ms)
✔ a merge of another head, or onto another base, is a move (0.859056ms)
✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.743599ms)
✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.626959ms)
✔ the group rule names every missing thing: the group status at each head read, and each head the Approve does not cover (1.264468ms)
✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.218812ms)
✔ without the composed verdict's siblings, a sibling's own merge of its new head is a move (the pin of issue 1049) (0.291148ms)
✔ a composed verdict names the siblings of each member at the heads and base commits it composed, so a sibling's own merge of its new head is no move (issue 1049) (0.822638ms)
✔ a composed verdict keeps nothing for a member it cannot name, and a group of one is none (issue 1049) (0.249058ms)
✔ a consumer that asks nothing, or write, publishes: the package team (2.209586ms)
✔ a consumer that asks to read joins the readers, who write no package (0.440619ms)
✔ a reader is made, put on the readers team, and taken off the package team (0.572046ms)
✔ a publisher is made and put on the package team, as before (0.235423ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (33.07823ms)
✔ second start: reuses the kept token, mints nothing (20.950458ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (22.864208ms)
✔ a token kept with write:admin by an earlier build is minted again without it at the next start, and the forge drops the old one (28.459021ms)
✔ a kept token lacking a scope the tools need: the forge refuses the call for the scope, the token is re-minted with the whole list, and the call goes through (24.624239ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (19.950337ms)
✔ concurrent first calls share one mint (12.147881ms)
✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (14.351464ms)
✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (65.251858ms)
✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (6.65578ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (15.878708ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.716207ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (20.066394ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.164311ms)
✔ nothing to mint with and no token: the client says what is missing (0.171723ms)
[gitea] no tools — no Gitea token, and nothing to mint one with — set MESH_GITEA_TOKEN, or MESH_GITEA_ADMIN_USER, MESH_GITEA_ADMIN_PASSWORD_FILE, MESH_GITEA_STATE_DIR
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-DloqJV/state/token
✔ the tools register once there is a way to a token, and the first call mints it (27.808588ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-gQJLp1/state/token
✔ a pull request can be closed, read and cleaned up through the tools (33.858999ms)
[gitea] no token kept — minting one
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-eakMwu/state/token
✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (60.329641ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-orW2Qo/state/token
✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (51.338817ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-iuLlBi/state/token
✔ what a base's protection asks is read from the branch, which the tools' account may read, not from the rules' list it may not (43.867014ms)
[gitea] the kept token was minted with other scopes than the tools take now — minting one with them
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-zqU1Ib/state/token
[gitea] deleted 1 token(s) named "mesh-tools" the admin account "mesh-admin" held: the tools act as "mesh-tools" now
✔ the administrator's token from before goes: a kept admin token is minted again for the tools' account, and the forge drops the old one (41.998458ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-erzWBs/state/token
✔ a tools' account someone made an administrator is made a plain account again at the next mint (32.691102ms)
✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.824181ms)
✔ the manifest hands the tools their account, and the Go forge bundle holds no administrator password (0.841824ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-buQCm9/state/token
✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (38.932743ms)
[gitea] no token kept — minting one
✔ a mint that fails leaves the administrator's old token in place: the tools are never left without one (26.409976ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-Z6wcem/state/token
[gitea] FAILED to delete the token(s) named "mesh-tools" the admin account "mesh-admin" holds — tried again at the next start: Gitea DELETE /users/mesh-admin/tokens/902 (named mesh-tools): 500 {"message":"the forge is not well"}
✔ an old token that cannot be deleted after the mint is said, the new token kept, and deleted at the next start (42.681674ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-TnEnKl/state/token
✔ a team another process made between the look and the create is found, not a failure (37.131505ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-ji65ww/state/token
✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (36.291012ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-TrMb7q/state/token
✔ a glob rule covering main keeps its statuses when main is given a rule of its own name (issue 948, review round 1) (35.739226ms)
✔ a start with the token kept still puts main's rules right: the module's start asks for it each time (issue 948, review round 1) (12.501105ms)
[gitea] novox/mesh-host's main moved from a2c2c35bbbbb to d28ca95ccccc: 25 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
[gitea] novox/mesh-host's main moved from d28ca95ccccc to ffffffffffff: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
[gitea] novox/mesh-host: whether a trunk moved could not be weighed, so it is weighed again on the next pass — the forge is away
[gitea] novox/mesh-host's main moved from a2c2c35bbbbb to d28ca95ccccc: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
[gitea] novox/mesh-controller's feat/57-config-and-provisioning moved from eeeeeeeeeeee to d28ca95ccccc: 1 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323)
✔ both statuses say the head and the trunk commit the verdict judged, first, whatever the summary's length (2.099028ms)
✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (0.838297ms)
✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (2.644023ms)
✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.436731ms)
✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.416022ms)
✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.243027ms)
✔ a verdict that landed out of date keeps its account on the pull request (0.21236ms)
✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.355308ms)
✔ a signed event is published on the bus and acted on once (50.810796ms)
✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (31.129695ms)
✔ an event and the poll seeing the same head announce it once (0.433605ms)
✔ each forge event is named in the module's stream and trimmed (0.4677ms)
✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.554474ms)
✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.006403ms)
✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.831235ms)
✔ a forge that makes no system webhook is said, never taken as heard (0.57961ms)
✔ the receiver tells what it verified and what it refused (7.558998ms)
✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (0.848947ms)
✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.54239ms)
✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.393951ms)
✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.164719ms)
✔ a pull request's edit event carries its description, and no other pull request event does (issue 1079) (0.182182ms)
ℹ tests 157
ℹ suites 0
ℹ pass 157
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 727.135079

**Merge check** at `e75e793a` Judged: head `e75e793a4b3b` merged into trunk `cfb90d7b2f96`; read beside it: mesh-controller `48e9656c670b`, mesh-controller-main `48e9656c670b`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds gitea → novox; no bus step - tier 0: gitea - novox: receives gitea - gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on ace as `build-1792339181581837082` (`builds --log build-1792339181581837082`). ``` ✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.596051ms) ✔ a start heard after the verdict writes nothing (0.540206ms) ✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.675391ms) ✔ an old run's verdict redelivered after a recheck's pending is not written over it (0.973641ms) [gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check the forge holds pending; not written [gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check now pending; not written ✔ an old run's verdict in flight when the recheck comes lands before the recheck's pending (3.937617ms) ✔ a rechecked head says where its new run is: building on which machine (0.897659ms) ✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.773155ms) ✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.612752ms) ✔ a recheck the forge does not take fails its caller, and the head is as it was (1.165603ms) ✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (9.581312ms) ✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (1.998187ms) ✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (0.4092ms) ✔ a repository as the mesh clones it is told from another (0.278223ms) ✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.79465ms) ✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (49.6234ms) ✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (16.62977ms) ✔ gitea_api still writes what an author writes (7.245017ms) ✔ gitea_branch_protection_set only strengthens (14.993472ms) ✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (42.951731ms) ✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (139.844377ms) ✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (14.644045ms) ✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (12.486287ms) ✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (26.394537ms) ✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (55.513621ms) ✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (20.423437ms) ✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.210059ms) ✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (5.852387ms) ✔ a rule named for a branch is not made weaker than the glob rule that guards it now (13.851675ms) ✔ a repository owner or name is never another path (0.238649ms) ✔ the judges, without a forge (0.351321ms) ✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.251212ms) ✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (2.067799ms) ✔ gitea_api never approves a pull request nor requests changes: those are the operator's (1.530899ms) ✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.576478ms) ✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each head approved (80.232186ms) ✔ gitea_merge_pull_request refuses a head the Approve did not name (20.009518ms) ✔ a group of two merges in one pass: the sibling's merge of the composed head does not stop the member's merge (issue 1049) (15.1303ms) ✔ gitea_create_repo has no owner argument and posts only to the tools' own user's repositories (1124/AC8) (30.548511ms) ✔ the tools' team cannot create in the organisation and its token holds no write:organization (1124/AC8) (0.344147ms) ✔ no ready mark, trusted ready-authors setting or approval-by-mark rule is left in the module (19.4948ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (27.526417ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.450227ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (11.974905ms) ✔ a lookup the forge refuses is thrown, not read as no module (3.872274ms) ✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (4.330986ms) ✔ a new head beyond the newest 20 open pull requests is announced, exactly once (77.544711ms) ✔ a pass pages until it reaches back past its floor, and no further (21.696452ms) ✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (25.429674ms) ✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (9.553579ms) ✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (3.802663ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (3.594461ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.311937ms) ✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.602624ms) ✔ another branch's body carries no merge whitelist (0.270269ms) ✔ the rule main is put right in the forge's own words: the body a setup sends carries no status checks of its own (0.380125ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (13.834994ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.121469ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.796668ms) ✔ no verdict sets warning on a required check; only a person's decision fails (1.115038ms) ✔ a commit status is set on the commit, under the merge check's context (41.582455ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.482337ms) ✔ a head announced is pending in the build queue, since the local time it was announced (0.383351ms) ✔ a composed verdict sets every member's gate at its own head, naming its trunk and the group (0.584529ms) ✔ a member's own verdict with a composed gate layer leaves the gate to the composed verdict, in either order (0.692943ms) ✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.645205ms) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 at bbbbbbbbbbbb, it is now at dddddddddddd: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was closed unmerged: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 merged onto cccccccccccc, its main is now eeeeeeeeeeee: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-host's main moved from 444444444444 to 333333333333: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head bbbbbbbbbbbb onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382) [gitea] novox/mesh-controller#346: its verdict was judged beside mesh-host#114 was merged otherwise than its head dddddddddddd onto cccccccccccc: out of date, nothing run (novox/hq ADR 0382) ✔ both statuses name the siblings the verdict read, keeping the verdict word and the start of its reason within 140 characters (2.457662ms) ✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (1.293232ms) ✔ a verdict without siblings is said exactly as before (an older controller) (0.824931ms) ✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (0.932764ms) ✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (1.896547ms) ✔ a sibling closed unmerged puts the member's verdict out of date (0.357553ms) ✔ a move of the sibling's base puts it out of date, naming both commits (0.437993ms) ✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.720826ms) ✔ a merge of another head, or onto another base, is a move (0.859056ms) ✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.743599ms) ✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.626959ms) ✔ the group rule names every missing thing: the group status at each head read, and each head the Approve does not cover (1.264468ms) ✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.218812ms) ✔ without the composed verdict's siblings, a sibling's own merge of its new head is a move (the pin of issue 1049) (0.291148ms) ✔ a composed verdict names the siblings of each member at the heads and base commits it composed, so a sibling's own merge of its new head is no move (issue 1049) (0.822638ms) ✔ a composed verdict keeps nothing for a member it cannot name, and a group of one is none (issue 1049) (0.249058ms) ✔ a consumer that asks nothing, or write, publishes: the package team (2.209586ms) ✔ a consumer that asks to read joins the readers, who write no package (0.440619ms) ✔ a reader is made, put on the readers team, and taken off the package team (0.572046ms) ✔ a publisher is made and put on the package team, as before (0.235423ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (33.07823ms) ✔ second start: reuses the kept token, mints nothing (20.950458ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (22.864208ms) ✔ a token kept with write:admin by an earlier build is minted again without it at the next start, and the forge drops the old one (28.459021ms) ✔ a kept token lacking a scope the tools need: the forge refuses the call for the scope, the token is re-minted with the whole list, and the call goes through (24.624239ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (19.950337ms) ✔ concurrent first calls share one mint (12.147881ms) ✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (14.351464ms) ✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (65.251858ms) ✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (6.65578ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (15.878708ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.716207ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (20.066394ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.164311ms) ✔ nothing to mint with and no token: the client says what is missing (0.171723ms) [gitea] no tools — no Gitea token, and nothing to mint one with — set MESH_GITEA_TOKEN, or MESH_GITEA_ADMIN_USER, MESH_GITEA_ADMIN_PASSWORD_FILE, MESH_GITEA_STATE_DIR [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-DloqJV/state/token ✔ the tools register once there is a way to a token, and the first call mints it (27.808588ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-gQJLp1/state/token ✔ a pull request can be closed, read and cleaned up through the tools (33.858999ms) [gitea] no token kept — minting one [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-eakMwu/state/token ✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (60.329641ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-orW2Qo/state/token ✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (51.338817ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-iuLlBi/state/token ✔ what a base's protection asks is read from the branch, which the tools' account may read, not from the rules' list it may not (43.867014ms) [gitea] the kept token was minted with other scopes than the tools take now — minting one with them [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-zqU1Ib/state/token [gitea] deleted 1 token(s) named "mesh-tools" the admin account "mesh-admin" held: the tools act as "mesh-tools" now ✔ the administrator's token from before goes: a kept admin token is minted again for the tools' account, and the forge drops the old one (41.998458ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-erzWBs/state/token ✔ a tools' account someone made an administrator is made a plain account again at the next mint (32.691102ms) ✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.824181ms) ✔ the manifest hands the tools their account, and the Go forge bundle holds no administrator password (0.841824ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-buQCm9/state/token ✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (38.932743ms) [gitea] no token kept — minting one ✔ a mint that fails leaves the administrator's old token in place: the tools are never left without one (26.409976ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-Z6wcem/state/token [gitea] FAILED to delete the token(s) named "mesh-tools" the admin account "mesh-admin" holds — tried again at the next start: Gitea DELETE /users/mesh-admin/tokens/902 (named mesh-tools): 500 {"message":"the forge is not well"} ✔ an old token that cannot be deleted after the mint is said, the new token kept, and deleted at the next start (42.681674ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-TnEnKl/state/token ✔ a team another process made between the look and the create is found, not a failure (37.131505ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-ji65ww/state/token ✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (36.291012ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-tools" (write:repository, write:issue, read:user), kept at /tmp/gitea-tools-account-TrMb7q/state/token ✔ a glob rule covering main keeps its statuses when main is given a rule of its own name (issue 948, review round 1) (35.739226ms) ✔ a start with the token kept still puts main's rules right: the module's start asks for it each time (issue 948, review round 1) (12.501105ms) [gitea] novox/mesh-host's main moved from a2c2c35bbbbb to d28ca95ccccc: 25 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) [gitea] novox/mesh-host's main moved from d28ca95ccccc to ffffffffffff: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) [gitea] novox/mesh-host: whether a trunk moved could not be weighed, so it is weighed again on the next pass — the forge is away [gitea] novox/mesh-host's main moved from a2c2c35bbbbb to d28ca95ccccc: 0 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) [gitea] novox/mesh-controller's feat/57-config-and-provisioning moved from eeeeeeeeeeee to d28ca95ccccc: 1 open pull request(s) into it put out of date, nothing run (novox/hq ADR 0323) ✔ both statuses say the head and the trunk commit the verdict judged, first, whatever the summary's length (2.099028ms) ✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (0.838297ms) ✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (2.644023ms) ✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.436731ms) ✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.416022ms) ✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.243027ms) ✔ a verdict that landed out of date keeps its account on the pull request (0.21236ms) ✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.355308ms) ✔ a signed event is published on the bus and acted on once (50.810796ms) ✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (31.129695ms) ✔ an event and the poll seeing the same head announce it once (0.433605ms) ✔ each forge event is named in the module's stream and trimmed (0.4677ms) ✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.554474ms) ✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.006403ms) ✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.831235ms) ✔ a forge that makes no system webhook is said, never taken as heard (0.57961ms) ✔ the receiver tells what it verified and what it refused (7.558998ms) ✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (0.848947ms) ✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.54239ms) ✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.393951ms) ✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.164719ms) ✔ a pull request's edit event carries its description, and no other pull request event does (issue 1079) (0.182182ms) ℹ tests 157 ℹ suites 0 ℹ pass 157 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 727.135079 ```

mesh-tools merged commit 4301da630d into main 2026-10-18 16:03:59 +00:00

mesh-tools deleted branch fix/1128-repositories-template 2026-10-18 16:03:59 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#364