Bind the gitea bundle's event consumers again until they hold, so verdicts reach the forge (issue 1793) #428

Merged

mesh-tools merged 1 commits from fix/1793-verdict-reaches-the-forge into main 2026-10-21 22:44:16 +00:00

Conversation 2 Commits 1 Files Changed 3

+68 -3

mesh-tools commented 2026-10-21 22:38:50 +00:00

Member

Copy Link

Copy Source

What

The gitea bundle binds its consumers of mesh-controller.checked and node-build-agent.started in a loop (new bind.ts): a refused bind is said and asked again after 2 s, 5 s, 10 s, then every 30 s, until it holds.

Why

Issue 1793, case 2 (mesh-catalog#427, 2026-10-22 00:28-00:32): the bundle started with node-tools at 00:28:35, its bind of the consumer novox_gitea was answered 'nats: no responders available for request' (the runtime's bus part was not up yet), and the unhandled rejection ended the bundle. Nothing logged from it after 00:29:21, so the verdict of 00:32:18 was never heard and the statuses stayed at the 00:27:56 out-of-date ones. The out-of-date logic was not at fault. (The bridge treating the same refusal as final is issue 1801, not changed here. Case 1, #430, is a different cause: the bundle stayed up; fixed by mesh-catalog#424.)

How it is checked

• test/bind.test.ts: a bind refused three times with no responders is asked again with waits 2/5/10 s and then holds; a bind that holds first time says nothing; the wait caps at 30 s.
• mesh-controller.try on 0d2686b5 against trunk 839be0eb: pass (go and typescript parts, 54s), build-1792622257520937676.

Reviewed-by: pending

## What The gitea bundle binds its consumers of mesh-controller.checked and node-build-agent.started in a loop (new bind.ts): a refused bind is said and asked again after 2 s, 5 s, 10 s, then every 30 s, until it holds. ## Why Issue 1793, case 2 (mesh-catalog#427, 2026-10-22 00:28-00:32): the bundle started with node-tools at 00:28:35, its bind of the consumer novox_gitea was answered 'nats: no responders available for request' (the runtime's bus part was not up yet), and the unhandled rejection ended the bundle. Nothing logged from it after 00:29:21, so the verdict of 00:32:18 was never heard and the statuses stayed at the 00:27:56 out-of-date ones. The out-of-date logic was not at fault. (The bridge treating the same refusal as final is issue 1801, not changed here. Case 1, #430, is a different cause: the bundle stayed up; fixed by mesh-catalog#424.) ## How it is checked - test/bind.test.ts: a bind refused three times with no responders is asked again with waits 2/5/10 s and then holds; a bind that holds first time says nothing; the wait caps at 30 s. - mesh-controller.try on 0d2686b5 against trunk 839be0eb: pass (go and typescript parts, 54s), build-1792622257520937676. Reviewed-by: pending

mesh-tools added 1 commit 2026-10-21 22:38:50 +00:00

Bind the gitea bundle's event consumers again until they hold, so a refusal at its start no longer ends it and loses verdicts (issue 1793) 0d2686b5eb

mesh-tools commented 2026-10-21 22:39:07 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@0d2686b5ebee — delivered since 2026-10-21T22:46:41Z

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-21 22:38 (new) → proposed (announced): novox/mesh-catalog#428's head announced
• 2026-10-21 22:43 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-21 22:43 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-21 22:44 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-21 22:44 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-21 22:46 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@0d2686b5ebee` — **delivered** since 2026-10-21T22:46:41Z **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-21 22:38 (new) → proposed (announced): novox/mesh-catalog#428's head announced - 2026-10-21 22:43 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 22:43 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 22:44 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-21 22:44 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-21 22:46 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-21 22:43:31 +00:00

Author

Member

Copy Link

Copy Source

Merge check at 0d2686b5
Judged: head 0d2686b5ebee merged into trunk 4b8e7f11cf53; read beside it: mesh-controller a929df9b0ec3, mesh-controller-main a929df9b0ec3, mesh-host 4065b45ae84f, mesh-tools e0fadc43d9dd

• 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-1792622343612796080 (builds --log build-1792622343612796080).

✔ a start heard after the verdict writes nothing (1.017605ms)
✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.960988ms)
✔ an old run's verdict redelivered after a recheck's pending is not written over it (1.018817ms)
[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 (2.432807ms)
✔ a rechecked head says where its new run is: building on which machine (0.847304ms)
✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (1.030438ms)
✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.715576ms)
✔ a recheck the forge does not take fails its caller, and the head is as it was (0.646446ms)
✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (32.619953ms)
✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (2.111643ms)
✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (0.404131ms)
✔ a repository as the mesh clones it is told from another (0.277612ms)
✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.669837ms)
✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (73.18848ms)
✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (38.046713ms)
✔ gitea_api still writes what an author writes (7.870748ms)
✔ gitea_branch_protection_set only strengthens (19.988798ms)
✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (45.970181ms)
✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (148.459399ms)
✔ gitea_merge_pull_request asks no check of a member that waits for its group's composed check (33.858473ms)
✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (17.815709ms)
✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (13.643099ms)
✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (27.685238ms)
✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (102.880633ms)
✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (21.812099ms)
✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.336288ms)
✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (7.209605ms)
✔ a rule named for a branch is not made weaker than the glob rule that guards it now (14.213542ms)
✔ a repository owner or name is never another path (0.266351ms)
✔ the judges, without a forge (0.375056ms)
✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.258917ms)
✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (4.683803ms)
✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.216109ms)
✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.922982ms)
✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each head approved (229.854731ms)
✔ gitea_merge_pull_request refuses a head the Approve did not name (19.36273ms)
✔ 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) (63.297722ms)
✔ gitea_create_repo has no owner argument and posts only to the tools' own user's repositories (1124/AC8) (39.615444ms)
✔ the tools' team cannot create in the organisation and its token holds no write:organization (1124/AC8) (0.357813ms)
✔ no ready mark, trusted ready-authors setting or approval-by-mark rule is left in the module (18.733076ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (29.858538ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.709675ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (18.800602ms)
✔ a lookup the forge refuses is thrown, not read as no module (6.46342ms)
✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (7.396967ms)
✔ a new head beyond the newest 20 open pull requests is announced, exactly once (139.12718ms)
✔ a pass pages until it reaches back past its floor, and no further (22.815195ms)
✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (26.228598ms)
✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (7.624155ms)
✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (5.150099ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (3.946836ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.290487ms)
✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.657658ms)
✔ another branch's body carries no merge whitelist (0.249229ms)
✔ 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.316595ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (15.307119ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.163138ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.798112ms)
✔ no verdict sets warning on a required check; only a person's decision fails (1.117653ms)
✔ a commit status is set on the commit, under the merge check's context (39.287277ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.514207ms)
✔ a head announced is pending in the build queue, since the local time it was announced (0.317056ms)
✔ a composed verdict sets every member's gate at its own head, naming its trunk and the group (0.40911ms)
✔ a member's own verdict with a composed gate layer leaves the gate to the composed verdict, in either order (0.45192ms)
✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.103478ms)
[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.48699ms)
✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (2.140758ms)
✔ a verdict without siblings is said exactly as before (an older controller) (0.784877ms)
✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (1.033023ms)
✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (5.301304ms)
✔ a sibling closed unmerged puts the member's verdict out of date (0.574961ms)
✔ a move of the sibling's base puts it out of date, naming both commits (0.772543ms)
✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.623563ms)
✔ a merge of another head, or onto another base, is a move (1.072929ms)
✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.692753ms)
✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.662546ms)
✔ the group rule names every missing thing: the group status at each head read, and each head the Approve does not cover (6.180769ms)
✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.376057ms)
✔ without the composed verdict's siblings, a sibling's own merge of its new head is a move (the pin of issue 1049) (0.360939ms)
✔ 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.80786ms)
✔ a composed verdict keeps nothing for a member it cannot name, and a group of one is none (issue 1049) (0.23934ms)
✔ a consumer that asks nothing, or write, publishes: the package team (1.540067ms)
✔ a consumer that asks to read joins the readers, who write no package (0.439307ms)
✔ a reader is made, put on the readers team, and taken off the package team (0.521952ms)
✔ a publisher is made and put on the package team, as before (0.365878ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (42.319232ms)
✔ second start: reuses the kept token, mints nothing (22.042171ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (28.20707ms)
✔ 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 (154.467623ms)
✔ 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 (38.73064ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (22.943236ms)
✔ concurrent first calls share one mint (13.833607ms)
✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (15.029107ms)
✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (57.170341ms)
✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (5.641274ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (15.61586ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.753849ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (260.338374ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.366984ms)
✔ nothing to mint with and no token: the client says what is missing (0.207721ms)
[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-3roebY/state/token
✔ the tools register once there is a way to a token, and the first call mints it (28.63184ms)
[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-kPojYA/state/token
✔ a pull request can be closed, read and cleaned up through the tools (41.294183ms)
[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-zYq1MZ/state/token
✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (81.304781ms)
[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-gzglkE/state/token
✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (49.38757ms)
[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-wiwrw2/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 (48.434658ms)
[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-6vRHzp/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 (152.811156ms)
[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-yvmPH8/state/token
✔ a tools' account someone made an administrator is made a plain account again at the next mint (34.684858ms)
✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.716889ms)
✔ the manifest hands the tools their account, and the Go forge bundle holds no administrator password (1.002887ms)
[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-s4XgmZ/state/token
✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (40.531508ms)
[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 (30.206902ms)
[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-oaq5kM/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 (44.222332ms)
[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-kqD0Zt/state/token
✔ a team another process made between the look and the create is found, not a failure (37.181205ms)
[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-0clzth/state/token
✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (33.51628ms)
[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-Fqz7uz/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.176312ms)
✔ 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) (11.7517ms)
[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.769059ms)
✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (1.226567ms)
✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (5.514084ms)
✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.46771ms)
✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.613093ms)
✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.363744ms)
✔ a verdict that landed out of date keeps its account on the pull request (0.315484ms)
✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (1.24924ms)
✔ a signed event is published on the bus and acted on once (62.561757ms)
✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (30.12581ms)
✔ an event and the poll seeing the same head announce it once (0.381087ms)
✔ each forge event is named in the module's stream and trimmed (0.490062ms)
✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.261704ms)
✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.343067ms)
✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.049287ms)
✔ a forge that makes no system webhook is said, never taken as heard (0.599889ms)
✔ the receiver tells what it verified and what it refused (9.314835ms)
✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (1.210688ms)
✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.486926ms)
✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.303421ms)
✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.18606ms)
✔ a pull request's edit event carries its description, and no other pull request event does (issue 1079) (0.213391ms)
ℹ tests 167
ℹ suites 0
ℹ pass 167
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 1119.661585

**Merge check** at `0d2686b5` Judged: head `0d2686b5ebee` merged into trunk `4b8e7f11cf53`; read beside it: mesh-controller `a929df9b0ec3`, mesh-controller-main `a929df9b0ec3`, mesh-host `4065b45ae84f`, mesh-tools `e0fadc43d9dd` - `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-1792622343612796080` (`builds --log build-1792622343612796080`). ``` ✔ a start heard after the verdict writes nothing (1.017605ms) ✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.960988ms) ✔ an old run's verdict redelivered after a recheck's pending is not written over it (1.018817ms) [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 (2.432807ms) ✔ a rechecked head says where its new run is: building on which machine (0.847304ms) ✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (1.030438ms) ✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.715576ms) ✔ a recheck the forge does not take fails its caller, and the head is as it was (0.646446ms) ✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (32.619953ms) ✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (2.111643ms) ✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (0.404131ms) ✔ a repository as the mesh clones it is told from another (0.277612ms) ✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.669837ms) ✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (73.18848ms) ✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (38.046713ms) ✔ gitea_api still writes what an author writes (7.870748ms) ✔ gitea_branch_protection_set only strengthens (19.988798ms) ✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (45.970181ms) ✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (148.459399ms) ✔ gitea_merge_pull_request asks no check of a member that waits for its group's composed check (33.858473ms) ✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (17.815709ms) ✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (13.643099ms) ✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (27.685238ms) ✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (102.880633ms) ✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (21.812099ms) ✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.336288ms) ✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (7.209605ms) ✔ a rule named for a branch is not made weaker than the glob rule that guards it now (14.213542ms) ✔ a repository owner or name is never another path (0.266351ms) ✔ the judges, without a forge (0.375056ms) ✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.258917ms) ✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (4.683803ms) ✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.216109ms) ✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.922982ms) ✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each head approved (229.854731ms) ✔ gitea_merge_pull_request refuses a head the Approve did not name (19.36273ms) ✔ 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) (63.297722ms) ✔ gitea_create_repo has no owner argument and posts only to the tools' own user's repositories (1124/AC8) (39.615444ms) ✔ the tools' team cannot create in the organisation and its token holds no write:organization (1124/AC8) (0.357813ms) ✔ no ready mark, trusted ready-authors setting or approval-by-mark rule is left in the module (18.733076ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (29.858538ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.709675ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (18.800602ms) ✔ a lookup the forge refuses is thrown, not read as no module (6.46342ms) ✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (7.396967ms) ✔ a new head beyond the newest 20 open pull requests is announced, exactly once (139.12718ms) ✔ a pass pages until it reaches back past its floor, and no further (22.815195ms) ✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (26.228598ms) ✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (7.624155ms) ✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (5.150099ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (3.946836ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.290487ms) ✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.657658ms) ✔ another branch's body carries no merge whitelist (0.249229ms) ✔ 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.316595ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (15.307119ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.163138ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.798112ms) ✔ no verdict sets warning on a required check; only a person's decision fails (1.117653ms) ✔ a commit status is set on the commit, under the merge check's context (39.287277ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.514207ms) ✔ a head announced is pending in the build queue, since the local time it was announced (0.317056ms) ✔ a composed verdict sets every member's gate at its own head, naming its trunk and the group (0.40911ms) ✔ a member's own verdict with a composed gate layer leaves the gate to the composed verdict, in either order (0.45192ms) ✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.103478ms) [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.48699ms) ✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (2.140758ms) ✔ a verdict without siblings is said exactly as before (an older controller) (0.784877ms) ✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (1.033023ms) ✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (5.301304ms) ✔ a sibling closed unmerged puts the member's verdict out of date (0.574961ms) ✔ a move of the sibling's base puts it out of date, naming both commits (0.772543ms) ✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.623563ms) ✔ a merge of another head, or onto another base, is a move (1.072929ms) ✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.692753ms) ✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.662546ms) ✔ the group rule names every missing thing: the group status at each head read, and each head the Approve does not cover (6.180769ms) ✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.376057ms) ✔ without the composed verdict's siblings, a sibling's own merge of its new head is a move (the pin of issue 1049) (0.360939ms) ✔ 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.80786ms) ✔ a composed verdict keeps nothing for a member it cannot name, and a group of one is none (issue 1049) (0.23934ms) ✔ a consumer that asks nothing, or write, publishes: the package team (1.540067ms) ✔ a consumer that asks to read joins the readers, who write no package (0.439307ms) ✔ a reader is made, put on the readers team, and taken off the package team (0.521952ms) ✔ a publisher is made and put on the package team, as before (0.365878ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (42.319232ms) ✔ second start: reuses the kept token, mints nothing (22.042171ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (28.20707ms) ✔ 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 (154.467623ms) ✔ 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 (38.73064ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (22.943236ms) ✔ concurrent first calls share one mint (13.833607ms) ✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (15.029107ms) ✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (57.170341ms) ✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (5.641274ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (15.61586ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.753849ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (260.338374ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.366984ms) ✔ nothing to mint with and no token: the client says what is missing (0.207721ms) [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-3roebY/state/token ✔ the tools register once there is a way to a token, and the first call mints it (28.63184ms) [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-kPojYA/state/token ✔ a pull request can be closed, read and cleaned up through the tools (41.294183ms) [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-zYq1MZ/state/token ✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (81.304781ms) [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-gzglkE/state/token ✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (49.38757ms) [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-wiwrw2/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 (48.434658ms) [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-6vRHzp/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 (152.811156ms) [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-yvmPH8/state/token ✔ a tools' account someone made an administrator is made a plain account again at the next mint (34.684858ms) ✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.716889ms) ✔ the manifest hands the tools their account, and the Go forge bundle holds no administrator password (1.002887ms) [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-s4XgmZ/state/token ✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (40.531508ms) [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 (30.206902ms) [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-oaq5kM/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 (44.222332ms) [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-kqD0Zt/state/token ✔ a team another process made between the look and the create is found, not a failure (37.181205ms) [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-0clzth/state/token ✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (33.51628ms) [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-Fqz7uz/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.176312ms) ✔ 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) (11.7517ms) [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.769059ms) ✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (1.226567ms) ✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (5.514084ms) ✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.46771ms) ✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.613093ms) ✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.363744ms) ✔ a verdict that landed out of date keeps its account on the pull request (0.315484ms) ✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (1.24924ms) ✔ a signed event is published on the bus and acted on once (62.561757ms) ✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (30.12581ms) ✔ an event and the poll seeing the same head announce it once (0.381087ms) ✔ each forge event is named in the module's stream and trimmed (0.490062ms) ✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.261704ms) ✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.343067ms) ✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.049287ms) ✔ a forge that makes no system webhook is said, never taken as heard (0.599889ms) ✔ the receiver tells what it verified and what it refused (9.314835ms) ✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (1.210688ms) ✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.486926ms) ✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.303421ms) ✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.18606ms) ✔ a pull request's edit event carries its description, and no other pull request event does (issue 1079) (0.213391ms) ℹ tests 167 ℹ suites 0 ℹ pass 167 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 1119.661585 ```

mesh-tools merged commit c770f7947d into main 2026-10-21 22:44:16 +00:00

mesh-tools deleted branch fix/1793-verdict-reaches-the-forge 2026-10-21 22:44:16 +00:00

mesh-tools referenced this pull request 2026-10-21 22:47:09 +00:00

Start the gitea bundle's binds without awaiting them, so its handshake is answered (issue 1793) #429

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#428