A repository the gitea module makes refuses an administrator's merge past its checks (issue 1141) #365

Merged

mesh-tools merged 1 commits from fix/1141-admin-override into main 2026-10-18 16:24:57 +00:00

Conversation 2 Commits 1 Files Changed 3

+55 -5

mesh-tools commented 2026-10-18 16:12:41 +00:00

Member

Copy Link

Copy Source

Issue 1141: novox/mesh-delivery, made at 18:07 by the repositories program, has main's rule with admin_may_override true, unlike every repository's main since 2026-10-07. narrowed never set block_admin_merge_override.

• modules/gitea/cmd/repositories/repositories.go: narrowed sets block_admin_merge_override true; isRight requires it, so the module's next start puts mesh-delivery's existing rule right; the copy from a covering glob rule is removed, now redundant.
• Tests 1141/AC1 and 1141/AC2 (override_test.go) fail on main and pass here; the 'right' fixture of TestStatusesAreAddedAndNeverDropped carries the field.

Nothing in the module sets the field back to false (ensureMainMerges sends only mainRuleBody; the guard refuses a weakening).

Try: pass (build-1792339902061650034, 47 s).

Reviewed-by: reviewer-1141@shanks at 54db38be08

Issue 1141: novox/mesh-delivery, made at 18:07 by the repositories program, has main's rule with admin_may_override true, unlike every repository's main since 2026-10-07. `narrowed` never set block_admin_merge_override. - `modules/gitea/cmd/repositories/repositories.go`: `narrowed` sets block_admin_merge_override true; `isRight` requires it, so the module's next start puts mesh-delivery's existing rule right; the copy from a covering glob rule is removed, now redundant. - Tests 1141/AC1 and 1141/AC2 (override_test.go) fail on main and pass here; the 'right' fixture of TestStatusesAreAddedAndNeverDropped carries the field. Nothing in the module sets the field back to false (ensureMainMerges sends only mainRuleBody; the guard refuses a weakening). Try: pass (build-1792339902061650034, 47 s). Reviewed-by: reviewer-1141@shanks at 54db38be0896dc6c623db5051cbb0ce5e4afb72c

mesh-tools added 1 commit 2026-10-18 16:12:41 +00:00

gitea: a repository the module makes refuses an administrator's merge past its checks (issue 1141) ... 54db38be08

narrowed never set block_admin_merge_override, so novox/mesh-delivery's
main let an administrator merge past mesh/merge-gate and mesh/repo-check,
unlike every other repository's main since 2026-10-07. narrowed sets it and
isRight requires it, so the module's next start puts mesh-delivery right.

mesh-tools commented 2026-10-18 16:12:49 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@54db38be0896 — delivered since 2026-10-18T16:28: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 16:12 (new) → proposed (announced): novox/mesh-catalog#365's head announced
• 2026-10-18 16:16 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-18 16:16 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-18 16:25 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:25 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:28 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@54db38be0896` — **delivered** since 2026-10-18T16:28: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 16:12 (new) → proposed (announced): novox/mesh-catalog#365's head announced - 2026-10-18 16:16 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 16:16 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 16:25 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:25 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:28 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:16:12 +00:00

Author

Member

Copy Link

Copy Source

Merge check at 54db38be
Judged: head 54db38be0896 merged into trunk 4301da630d82; 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 shanks as build-1792339963929840932 (builds --log build-1792339963929840932).

✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.698632ms)
✔ a start heard after the verdict writes nothing (0.607011ms)
✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (1.876311ms)
✔ an old run's verdict redelivered after a recheck's pending is not written over it (1.121219ms)
[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.938826ms)
✔ a rechecked head says where its new run is: building on which machine (1.035338ms)
✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.811043ms)
✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (1.259141ms)
✔ a recheck the forge does not take fails its caller, and the head is as it was (0.63868ms)
✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (6.741783ms)
✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.297835ms)
✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (1.718549ms)
✔ a repository as the mesh clones it is told from another (0.343956ms)
✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (6.640421ms)
✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (66.443285ms)
✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (26.506705ms)
✔ gitea_api still writes what an author writes (9.373207ms)
✔ gitea_branch_protection_set only strengthens (20.721228ms)
✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (52.690415ms)
✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (157.444603ms)
✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (17.615076ms)
✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (12.043632ms)
✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (27.031934ms)
✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (63.189201ms)
✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (22.870144ms)
✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.405894ms)
✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (5.878299ms)
✔ a rule named for a branch is not made weaker than the glob rule that guards it now (13.944394ms)
✔ a repository owner or name is never another path (0.412057ms)
✔ the judges, without a forge (0.422997ms)
✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.301575ms)
✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (2.234767ms)
✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.779887ms)
✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (6.635021ms)
✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each head approved (91.260102ms)
✔ gitea_merge_pull_request refuses a head the Approve did not name (17.84788ms)
✔ 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.665353ms)
✔ gitea_create_repo has no owner argument and posts only to the tools' own user's repositories (1124/AC8) (31.61472ms)
✔ the tools' team cannot create in the organisation and its token holds no write:organization (1124/AC8) (0.394056ms)
✔ no ready mark, trusted ready-authors setting or approval-by-mark rule is left in the module (19.733411ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (37.255016ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.632441ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (17.424153ms)
✔ a lookup the forge refuses is thrown, not read as no module (6.546749ms)
✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (7.987065ms)
✔ a new head beyond the newest 20 open pull requests is announced, exactly once (66.68757ms)
✔ a pass pages until it reaches back past its floor, and no further (32.867772ms)
✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (29.130399ms)
✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (9.997857ms)
✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (6.108973ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (15.47018ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.447947ms)
✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.824274ms)
✔ another branch's body carries no merge whitelist (0.497928ms)
✔ 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.348256ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (18.48882ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.035847ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.736923ms)
✔ no verdict sets warning on a required check; only a person's decision fails (1.035047ms)
✔ a commit status is set on the commit, under the merge check's context (43.745524ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.6075ms)
✔ a head announced is pending in the build queue, since the local time it was announced (0.343136ms)
✔ a composed verdict sets every member's gate at its own head, naming its trunk and the group (0.557509ms)
✔ a member's own verdict with a composed gate layer leaves the gate to the composed verdict, in either order (0.61653ms)
✔ the vault's token is used, a setting of it is ignored and said once, without its value (3.344546ms)
[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 (3.245364ms)
✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.497378ms)
✔ a verdict without siblings is said exactly as before (an older controller) (1.958923ms)
✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (1.19803ms)
✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (2.98647ms)
✔ a sibling closed unmerged puts the member's verdict out of date (0.380027ms)
✔ a move of the sibling's base puts it out of date, naming both commits (1.009557ms)
✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.682952ms)
✔ a merge of another head, or onto another base, is a move (1.131689ms)
✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.820614ms)
✔ a trunk that moved tells the siblings' weighing; one first seen does not (1.453945ms)
✔ the group rule names every missing thing: the group status at each head read, and each head the Approve does not cover (1.622697ms)
✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.282245ms)
✔ without the composed verdict's siblings, a sibling's own merge of its new head is a move (the pin of issue 1049) (0.503719ms)
✔ 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.989817ms)
✔ a composed verdict keeps nothing for a member it cannot name, and a group of one is none (issue 1049) (0.304655ms)
✔ a consumer that asks nothing, or write, publishes: the package team (1.854712ms)
✔ a consumer that asks to read joins the readers, who write no package (0.531639ms)
✔ a reader is made, put on the readers team, and taken off the package team (0.664701ms)
✔ a publisher is made and put on the package team, as before (0.244254ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (47.842463ms)
✔ second start: reuses the kept token, mints nothing (29.1843ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (32.038298ms)
✔ 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 (36.222638ms)
✔ 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 (29.289142ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (23.961132ms)
✔ concurrent first calls share one mint (17.702177ms)
✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (16.031959ms)
✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (78.296095ms)
✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (8.032765ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (15.927358ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (1.142409ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (23.855821ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.687425ms)
✔ nothing to mint with and no token: the client says what is missing (0.226173ms)
[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-ndf07Q/state/token
✔ the tools register once there is a way to a token, and the first call mints it (30.008533ms)
[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-SqSyMv/state/token
✔ a pull request can be closed, read and cleaned up through the tools (39.160947ms)
[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-EmcvvO/state/token
✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (90.549819ms)
[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-NdflET/state/token
✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (63.569127ms)
[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-GqS6Es/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 (54.79972ms)
[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-Yp1gi2/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 (47.929055ms)
[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-h9zOLI/state/token
✔ a tools' account someone made an administrator is made a plain account again at the next mint (38.488986ms)
✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.768223ms)
✔ the manifest hands the tools their account, and the Go forge bundle holds no administrator password (0.827284ms)
[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-gR1RbR/state/token
✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (41.644808ms)
[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 (27.736536ms)
[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-hqOo9E/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 (49.300678ms)
[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-eMZMAV/state/token
✔ a team another process made between the look and the create is found, not a failure (42.173257ms)
[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-tb7GXh/state/token
✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (37.326927ms)
[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-2VochC/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) (38.286642ms)
✔ 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) (13.437685ms)
[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.449831ms)
✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (3.307156ms)
✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (5.099946ms)
✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.521999ms)
✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.668881ms)
✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.707381ms)
✔ a verdict that landed out of date keeps its account on the pull request (0.361166ms)
✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.599941ms)
✔ a signed event is published on the bus and acted on once (70.9103ms)
✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (40.339347ms)
✔ an event and the poll seeing the same head announce it once (0.429207ms)
✔ each forge event is named in the module's stream and trimmed (0.691192ms)
✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.712029ms)
✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.124879ms)
✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.454388ms)
✔ a forge that makes no system webhook is said, never taken as heard (0.686051ms)
✔ the receiver tells what it verified and what it refused (8.600254ms)
✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (1.073188ms)
✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.431777ms)
✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.375157ms)
✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.186623ms)
✔ a pull request's edit event carries its description, and no other pull request event does (issue 1079) (0.211244ms)
ℹ tests 157
ℹ suites 0
ℹ pass 157
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 886.751526

**Merge check** at `54db38be` Judged: head `54db38be0896` merged into trunk `4301da630d82`; 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 shanks as `build-1792339963929840932` (`builds --log build-1792339963929840932`). ``` ✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.698632ms) ✔ a start heard after the verdict writes nothing (0.607011ms) ✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (1.876311ms) ✔ an old run's verdict redelivered after a recheck's pending is not written over it (1.121219ms) [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.938826ms) ✔ a rechecked head says where its new run is: building on which machine (1.035338ms) ✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.811043ms) ✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (1.259141ms) ✔ a recheck the forge does not take fails its caller, and the head is as it was (0.63868ms) ✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (6.741783ms) ✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.297835ms) ✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (1.718549ms) ✔ a repository as the mesh clones it is told from another (0.343956ms) ✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (6.640421ms) ✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (66.443285ms) ✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (26.506705ms) ✔ gitea_api still writes what an author writes (9.373207ms) ✔ gitea_branch_protection_set only strengthens (20.721228ms) ✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (52.690415ms) ✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (157.444603ms) ✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (17.615076ms) ✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (12.043632ms) ✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (27.031934ms) ✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (63.189201ms) ✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (22.870144ms) ✔ gitea_api sends the path it judged, and refuses moving a pull request's base (4.405894ms) ✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (5.878299ms) ✔ a rule named for a branch is not made weaker than the glob rule that guards it now (13.944394ms) ✔ a repository owner or name is never another path (0.412057ms) ✔ the judges, without a forge (0.422997ms) ✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.301575ms) ✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (2.234767ms) ✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.779887ms) ✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (6.635021ms) ✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each head approved (91.260102ms) ✔ gitea_merge_pull_request refuses a head the Approve did not name (17.84788ms) ✔ 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.665353ms) ✔ gitea_create_repo has no owner argument and posts only to the tools' own user's repositories (1124/AC8) (31.61472ms) ✔ the tools' team cannot create in the organisation and its token holds no write:organization (1124/AC8) (0.394056ms) ✔ no ready mark, trusted ready-authors setting or approval-by-mark rule is left in the module (19.733411ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (37.255016ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.632441ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (17.424153ms) ✔ a lookup the forge refuses is thrown, not read as no module (6.546749ms) ✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (7.987065ms) ✔ a new head beyond the newest 20 open pull requests is announced, exactly once (66.68757ms) ✔ a pass pages until it reaches back past its floor, and no further (32.867772ms) ✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (29.130399ms) ✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (9.997857ms) ✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (6.108973ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (15.47018ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.447947ms) ✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.824274ms) ✔ another branch's body carries no merge whitelist (0.497928ms) ✔ 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.348256ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (18.48882ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (1.035847ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.736923ms) ✔ no verdict sets warning on a required check; only a person's decision fails (1.035047ms) ✔ a commit status is set on the commit, under the merge check's context (43.745524ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.6075ms) ✔ a head announced is pending in the build queue, since the local time it was announced (0.343136ms) ✔ a composed verdict sets every member's gate at its own head, naming its trunk and the group (0.557509ms) ✔ a member's own verdict with a composed gate layer leaves the gate to the composed verdict, in either order (0.61653ms) ✔ the vault's token is used, a setting of it is ignored and said once, without its value (3.344546ms) [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 (3.245364ms) ✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.497378ms) ✔ a verdict without siblings is said exactly as before (an older controller) (1.958923ms) ✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (1.19803ms) ✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (2.98647ms) ✔ a sibling closed unmerged puts the member's verdict out of date (0.380027ms) ✔ a move of the sibling's base puts it out of date, naming both commits (1.009557ms) ✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.682952ms) ✔ a merge of another head, or onto another base, is a move (1.131689ms) ✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.820614ms) ✔ a trunk that moved tells the siblings' weighing; one first seen does not (1.453945ms) ✔ the group rule names every missing thing: the group status at each head read, and each head the Approve does not cover (1.622697ms) ✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.282245ms) ✔ without the composed verdict's siblings, a sibling's own merge of its new head is a move (the pin of issue 1049) (0.503719ms) ✔ 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.989817ms) ✔ a composed verdict keeps nothing for a member it cannot name, and a group of one is none (issue 1049) (0.304655ms) ✔ a consumer that asks nothing, or write, publishes: the package team (1.854712ms) ✔ a consumer that asks to read joins the readers, who write no package (0.531639ms) ✔ a reader is made, put on the readers team, and taken off the package team (0.664701ms) ✔ a publisher is made and put on the package team, as before (0.244254ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (47.842463ms) ✔ second start: reuses the kept token, mints nothing (29.1843ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (32.038298ms) ✔ 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 (36.222638ms) ✔ 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 (29.289142ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (23.961132ms) ✔ concurrent first calls share one mint (17.702177ms) ✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (16.031959ms) ✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (78.296095ms) ✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (8.032765ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (15.927358ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (1.142409ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (23.855821ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.687425ms) ✔ nothing to mint with and no token: the client says what is missing (0.226173ms) [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-ndf07Q/state/token ✔ the tools register once there is a way to a token, and the first call mints it (30.008533ms) [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-SqSyMv/state/token ✔ a pull request can be closed, read and cleaned up through the tools (39.160947ms) [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-EmcvvO/state/token ✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (90.549819ms) [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-NdflET/state/token ✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (63.569127ms) [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-GqS6Es/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 (54.79972ms) [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-Yp1gi2/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 (47.929055ms) [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-h9zOLI/state/token ✔ a tools' account someone made an administrator is made a plain account again at the next mint (38.488986ms) ✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.768223ms) ✔ the manifest hands the tools their account, and the Go forge bundle holds no administrator password (0.827284ms) [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-gR1RbR/state/token ✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (41.644808ms) [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 (27.736536ms) [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-hqOo9E/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 (49.300678ms) [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-eMZMAV/state/token ✔ a team another process made between the look and the create is found, not a failure (42.173257ms) [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-tb7GXh/state/token ✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (37.326927ms) [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-2VochC/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) (38.286642ms) ✔ 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) (13.437685ms) [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.449831ms) ✔ a trunk's move puts an open head's merge check out of date, naming both commits, unless a check is on its way (3.307156ms) ✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (5.099946ms) ✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.521999ms) ✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.668881ms) ✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.707381ms) ✔ a verdict that landed out of date keeps its account on the pull request (0.361166ms) ✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.599941ms) ✔ a signed event is published on the bus and acted on once (70.9103ms) ✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (40.339347ms) ✔ an event and the poll seeing the same head announce it once (0.429207ms) ✔ each forge event is named in the module's stream and trimmed (0.691192ms) ✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.712029ms) ✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.124879ms) ✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.454388ms) ✔ a forge that makes no system webhook is said, never taken as heard (0.686051ms) ✔ the receiver tells what it verified and what it refused (8.600254ms) ✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (1.073188ms) ✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.431777ms) ✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.375157ms) ✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.186623ms) ✔ a pull request's edit event carries its description, and no other pull request event does (issue 1079) (0.211244ms) ℹ tests 157 ℹ suites 0 ℹ pass 157 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 886.751526 ```

mesh-tools merged commit 72ad5ad138 into main 2026-10-18 16:24:57 +00:00

mesh-tools deleted branch fix/1141-admin-override 2026-10-18 16:24:57 +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#365