Let gitea's forge-account provider read the assignments it learns its consumers from (issue 955) #341

Merged

mesh-tools merged 1 commits from fix/955-gitea-reads-assignments into main 2026-10-16 23:11:16 +00:00

Conversation 3 Commits 1 Files Changed 2

+25

mesh-tools commented 2026-10-16 23:05:18 +00:00

Member

Copy Link

Copy Source

Issue 955, a second fault found by #340's delivery (playbook 08). Since 00:44 on novox gitea's forge-account provider stops every pass: "gitea keeps and reads no state called "mesh-controller.assignments" ... was issued: bound, ssh-client.keys (ADR 0201)", so no machine's key is registered and no consumer answered. postgres and keycloak declare that read; gitea did not.

• modules/gitea/module.json: reads gains mesh-controller.assignments.
• TestTheManifestReadsEveryStateTheProviderWatches fails on main 734a77f, passes here.

Reviewed (larger model), approved at 41f4177 (tree f9a2083); this forge commit carries the same diff. The reviewer checked every state the provider touches: none else is undeclared. Opened along the way: issue 987 (the provider's bus test grants every state, so a missing grant passes unseen).

Issue 955, a second fault found by #340's delivery (playbook 08). Since 00:44 on novox gitea's forge-account provider stops every pass: "gitea keeps and reads no state called \"mesh-controller.assignments\" ... was issued: bound, ssh-client.keys (ADR 0201)", so no machine's key is registered and no consumer answered. postgres and keycloak declare that read; gitea did not. - `modules/gitea/module.json`: `reads` gains `mesh-controller.assignments`. - `TestTheManifestReadsEveryStateTheProviderWatches` fails on main 734a77f, passes here. Reviewed (larger model), approved at 41f4177 (tree f9a2083); this forge commit carries the same diff. The reviewer checked every state the provider touches: none else is undeclared. Opened along the way: issue 987 (the provider's bus test grants every state, so a missing grant passes unseen).

mesh-tools added 1 commit 2026-10-16 23:05:19 +00:00

Let gitea's forge-account provider read the assignments it learns its consumers from (issue 955) 065ecd85f5

mesh-tools added the mesh/ready label 2026-10-16 23:05:23 +00:00

mesh-tools commented 2026-10-16 23:05:24 +00:00

Author

Member

Copy Link

Copy Source

ready at 065ecd85f5

Reviewed by lead-57@novox: Reviewer (opus) approved 41f4177 (tree f9a2083), the same tree as this forge commit: gitea's reads gain mesh-controller.assignments; no other undeclared state. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at 065ecd85f53e70b7bee0cbc5a6f3eccafe76a47c Reviewed by lead-57@novox: Reviewer (opus) approved 41f4177 (tree f9a2083), the same tree as this forge commit: gitea's reads gain mesh-controller.assignments; no other undeclared state. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

mesh-tools commented 2026-10-16 23:05:27 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@065ecd85f53e — delivered since 2026-10-16T23:17:21Z

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-16 23:05 (new) → proposed (announced): novox/mesh-catalog#341's head announced
• 2026-10-16 23:07 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-16 23:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-16 23:11 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-16 23:11 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-16 23:17 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@065ecd85f53e` — **delivered** since 2026-10-16T23:17:21Z **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-16 23:05 (new) → proposed (announced): novox/mesh-catalog#341's head announced - 2026-10-16 23:07 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 23:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 23:11 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 23:11 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-16 23:17 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-16 23:07:57 +00:00

Author

Member

Copy Link

Copy Source

Merge check at 065ecd85
Judged: head 065ecd85f53e merged into trunk 734a77f5a91a; read beside it: mesh-controller 6a62a7e552ea, mesh-controller-main 6a62a7e552ea, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5

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

Delivery plan — builds gitea → novox; no bus step

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

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

✔ the accounts that may mark are the setting's, and only the mesh's own when it cannot be read (0.609497ms)
✔ the newest status of each context is kept, with what it said, when and by whom (24.888241ms)
✔ a commit merges only when every required status is a success; a warning blocks (0.451309ms)
✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.239751ms)
✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.590721ms)
✔ a note line is appended once, as the forge's user, in its own repository (13.997239ms)
✔ a note that cannot be written is said, never read as written (0.522083ms)
✔ one view per pull request, found by its marker; only the mesh's statuses (0.781561ms)
✔ a build machine taking the check is said on the head: building on which machine, since the local time (20.874234ms)
✔ the verdict heard while a 'building' write is in flight lands last and stays (5.619067ms)
[gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check now pending; not written
✔ the verdict written while a start's read of the forge is in flight stays the newest status (1.146207ms)
✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.577106ms)
✔ a start heard after the verdict writes nothing (0.518977ms)
✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.649372ms)
✔ an old run's verdict redelivered after a recheck's pending is not written over it (0.960158ms)
[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.630184ms)
✔ a rechecked head says where its new run is: building on which machine (0.941262ms)
✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.703535ms)
✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.597775ms)
✔ a recheck the forge does not take fails its caller, and the head is as it was (0.587295ms)
✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (5.036531ms)
✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (1.570096ms)
✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (0.376719ms)
✔ a repository as the mesh clones it is told from another (0.308491ms)
✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.833422ms)
✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (42.462461ms)
✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (20.932664ms)
✔ gitea_api still writes what an author writes (8.180498ms)
✔ gitea_branch_protection_set only strengthens (16.912617ms)
✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (42.180891ms)
✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (143.844986ms)
✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (15.223457ms)
✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (14.239644ms)
✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (23.688993ms)
✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (58.574982ms)
✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (22.503601ms)
✔ gitea_api sends the path it judged, and refuses moving a pull request's base (3.068395ms)
✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (5.987711ms)
✔ a rule named for a branch is not made weaker than the glob rule that guards it now (13.7267ms)
✔ a repository owner or name is never another path (0.316796ms)
✔ the judges, without a forge (0.391687ms)
✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.229251ms)
✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.712162ms)
✔ gitea_api never approves a pull request nor requests changes: those are the operator's (1.494112ms)
✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.918809ms)
✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each sibling head reviewed (85.440034ms)
✔ a verdict put out of date by a sibling's move is refused in its own words, and asked again once (21.07385ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (22.489837ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.394853ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (12.507693ms)
✔ a lookup the forge refuses is thrown, not read as no module (4.893061ms)
✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (5.21144ms)
✔ a new head beyond the newest 20 open pull requests is announced, exactly once (57.388268ms)
✔ a pass pages until it reaches back past its floor, and no further (26.260973ms)
✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (25.22854ms)
✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (6.39566ms)
✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (3.310772ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (7.761099ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.343276ms)
✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.67464ms)
✔ another branch's body carries no merge whitelist (0.227739ms)
✔ 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.312188ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (17.552199ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.791881ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.538694ms)
✔ no verdict sets warning on a required check; only a person's decision fails (0.810055ms)
✔ a commit status is set on the commit, under the merge check's context (35.132013ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.449867ms)
✔ a head announced is pending in the build queue, since the local time it was announced (0.321234ms)
✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.123056ms)
[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)
✔ both statuses name the siblings the verdict read, keeping the verdict word and the start of its reason within 140 characters (1.925214ms)
✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.291769ms)
✔ a verdict without siblings is said exactly as before (an older controller) (0.580262ms)
✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (0.697403ms)
✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (2.142102ms)
✔ a sibling closed unmerged puts the member's verdict out of date (0.487668ms)
✔ a move of the sibling's base puts it out of date, naming both commits (0.548893ms)
✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.548783ms)
✔ a merge of another head, or onto another base, is a move (1.004561ms)
✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.963825ms)
✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.655133ms)
✔ the group rule names every missing thing: the group status at each head read, and each sibling head's review (0.991486ms)
✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.262073ms)
✔ a consumer that asks nothing, or write, publishes: the package team (1.107405ms)
✔ a consumer that asks to read joins the readers, who write no package (0.325663ms)
✔ a reader is made, put on the readers team, and taken off the package team (0.382129ms)
✔ a publisher is made and put on the package team, as before (0.159149ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (32.053467ms)
✔ second start: reuses the kept token, mints nothing (24.791208ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (27.450883ms)
✔ 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 (27.873308ms)
✔ 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 (22.899106ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (22.165945ms)
✔ concurrent first calls share one mint (13.865259ms)
✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (15.648627ms)
✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (74.691981ms)
✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (5.24894ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (14.855284ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.739322ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (20.419417ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.121233ms)
✔ nothing to mint with and no token: the client says what is missing (0.163788ms)
[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-NB84Rw/state/token
✔ the tools register once there is a way to a token, and the first call mints it (28.074358ms)
[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-qbX6MJ/state/token
✔ a pull request can be closed, read and cleaned up through the tools (34.442223ms)
[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-FT6qqO/state/token
✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (76.586647ms)
[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-IlbsTh/state/token
✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (44.899359ms)
[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-pHpuE0/state/token
✔ what a base's protection asks is read from the branch, which the tools' account may read, not from the rules' list it may not (43.219357ms)
[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-hGlX9L/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 (39.751589ms)
[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-a5UkJX/state/token
✔ a tools' account someone made an administrator is made a plain account again at the next mint (34.792274ms)
✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.782333ms)
✔ the manifest hands the tools their account, and the merge-ready authors name it rather than the administrator (0.912779ms)
[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-45IWRk/state/token
✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (36.54932ms)
[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 (24.809282ms)
[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-JsRzgo/state/token
[gitea] FAILED to delete the token(s) named "mesh-tools" the admin account "mesh-admin" holds — tried again at the next start: Gitea DELETE /users/mesh-admin/tokens/902 (named mesh-tools): 500 {"message":"the forge is not well"}
✔ an old token that cannot be deleted after the mint is said, the new token kept, and deleted at the next start (42.636398ms)
[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-2NJ7cE/state/token
✔ a team another process made between the look and the create is found, not a failure (36.514425ms)
[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-hllx6Z/state/token
✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (35.987684ms)
[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-3qPTWX/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) (34.22274ms)
✔ a start with the token kept still puts main's rules right: the module's start asks for it each time (issue 948, review round 1) (12.018264ms)
[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.187828ms)
✔ 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.283516ms)
✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (5.030168ms)
✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.34507ms)
✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.416464ms)
✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.248287ms)
✔ a verdict that landed out of date keeps its account on the pull request (0.224693ms)
✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.395415ms)
✔ a signed event is published on the bus and acted on once (60.91207ms)
✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (29.748019ms)
✔ an event and the poll seeing the same head announce it once (0.381247ms)
✔ each forge event is named in the module's stream and trimmed (0.478771ms)
✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.140707ms)
✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.041861ms)
✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.735601ms)
✔ a forge that makes no system webhook is said, never taken as heard (0.653299ms)
✔ the receiver tells what it verified and what it refused (8.147407ms)
✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (1.302091ms)
✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.55263ms)
✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.430981ms)
✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.263205ms)
ℹ tests 147
ℹ suites 0
ℹ pass 147
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 740.525388

**Merge check** at `065ecd85` Judged: head `065ecd85f53e` merged into trunk `734a77f5a91a`; read beside it: mesh-controller `6a62a7e552ea`, mesh-controller-main `6a62a7e552ea`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds gitea → novox; no bus step - tier 0: gitea - novox: receives gitea - gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on ace as `build-1792191920531155233` (`builds --log build-1792191920531155233`). ``` ✔ the accounts that may mark are the setting's, and only the mesh's own when it cannot be read (0.609497ms) ✔ the newest status of each context is kept, with what it said, when and by whom (24.888241ms) ✔ a commit merges only when every required status is a success; a warning blocks (0.451309ms) ✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.239751ms) ✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.590721ms) ✔ a note line is appended once, as the forge's user, in its own repository (13.997239ms) ✔ a note that cannot be written is said, never read as written (0.522083ms) ✔ one view per pull request, found by its marker; only the mesh's statuses (0.781561ms) ✔ a build machine taking the check is said on the head: building on which machine, since the local time (20.874234ms) ✔ the verdict heard while a 'building' write is in flight lands last and stays (5.619067ms) [gitea] novox/hq@a6b08de8: the verdict of build-1791680941000000000 is an older run's than the check now pending; not written ✔ the verdict written while a start's read of the forge is in flight stays the newest status (1.146207ms) ✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.577106ms) ✔ a start heard after the verdict writes nothing (0.518977ms) ✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.649372ms) ✔ an old run's verdict redelivered after a recheck's pending is not written over it (0.960158ms) [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.630184ms) ✔ a rechecked head says where its new run is: building on which machine (0.941262ms) ✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.703535ms) ✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.597775ms) ✔ a recheck the forge does not take fails its caller, and the head is as it was (0.587295ms) ✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (5.036531ms) ✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (1.570096ms) ✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (0.376719ms) ✔ a repository as the mesh clones it is told from another (0.308491ms) ✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.833422ms) ✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (42.462461ms) ✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (20.932664ms) ✔ gitea_api still writes what an author writes (8.180498ms) ✔ gitea_branch_protection_set only strengthens (16.912617ms) ✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (42.180891ms) ✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (143.844986ms) ✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (15.223457ms) ✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (14.239644ms) ✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (23.688993ms) ✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (58.574982ms) ✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (22.503601ms) ✔ gitea_api sends the path it judged, and refuses moving a pull request's base (3.068395ms) ✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (5.987711ms) ✔ a rule named for a branch is not made weaker than the glob rule that guards it now (13.7267ms) ✔ a repository owner or name is never another path (0.316796ms) ✔ the judges, without a forge (0.391687ms) ✔ main's protection is never weakened in its push or its merge whitelist (issue 948, ADR 0398 §2) (0.229251ms) ✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.712162ms) ✔ gitea_api never approves a pull request nor requests changes: those are the operator's (1.494112ms) ✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.918809ms) ✔ gitea_merge_pull_request merges a verdict that read siblings only with its group passed and each sibling head reviewed (85.440034ms) ✔ a verdict put out of date by a sibling's move is refused in its own words, and asked again once (21.07385ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (22.489837ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.394853ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (12.507693ms) ✔ a lookup the forge refuses is thrown, not read as no module (4.893061ms) ✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (5.21144ms) ✔ a new head beyond the newest 20 open pull requests is announced, exactly once (57.388268ms) ✔ a pass pages until it reaches back past its floor, and no further (26.260973ms) ✔ gitea_branch_protection_get answers every rule, read with the administrator account the tools' token cannot read with (25.22854ms) ✔ gitea_branch_protection_get answers the rule for a branch, null when it has none (6.39566ms) ✔ gitea_branch_protection_set still gets the forge's refusal, as the tools' account (3.310772ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (7.761099ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.343276ms) ✔ main's body always refuses pushes and lets only the tools' account merge, whatever is asked (0.67464ms) ✔ another branch's body carries no merge whitelist (0.227739ms) ✔ 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.312188ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (17.552199ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.791881ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.538694ms) ✔ no verdict sets warning on a required check; only a person's decision fails (0.810055ms) ✔ a commit status is set on the commit, under the merge check's context (35.132013ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.449867ms) ✔ a head announced is pending in the build queue, since the local time it was announced (0.321234ms) ✔ the vault's token is used, a setting of it is ignored and said once, without its value (2.123056ms) [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) ✔ both statuses name the siblings the verdict read, keeping the verdict word and the start of its reason within 140 characters (1.925214ms) ✔ a verdict that could not learn its siblings says so on the status and in the comment, and names none (0.291769ms) ✔ a verdict without siblings is said exactly as before (an older controller) (0.580262ms) ✔ the siblings a verdict names are kept per member, replaced by its next verdict, and removed by one that read none (0.697403ms) ✔ a sibling's new head puts both statuses of the member back to pending, with the reason, and runs nothing (2.142102ms) ✔ a sibling closed unmerged puts the member's verdict out of date (0.487668ms) ✔ a move of the sibling's base puts it out of date, naming both commits (0.548893ms) ✔ the sibling's own merge of the head read onto the base read does not, in either order of the two merges (0.548783ms) ✔ a merge of another head, or onto another base, is a move (1.004561ms) ✔ only the members whose verdict names the sibling are touched, and a member that moved on is dropped (0.963825ms) ✔ a trunk that moved tells the siblings' weighing; one first seen does not (0.655133ms) ✔ the group rule names every missing thing: the group status at each head read, and each sibling head's review (0.991486ms) ✔ a merged or closed member's entry is dropped, so a sibling's later push never re-pends its merged head (0.262073ms) ✔ a consumer that asks nothing, or write, publishes: the package team (1.107405ms) ✔ a consumer that asks to read joins the readers, who write no package (0.325663ms) ✔ a reader is made, put on the readers team, and taken off the package team (0.382129ms) ✔ a publisher is made and put on the package team, as before (0.159149ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (32.053467ms) ✔ second start: reuses the kept token, mints nothing (24.791208ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (27.450883ms) ✔ 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 (27.873308ms) ✔ 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 (22.899106ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (22.165945ms) ✔ concurrent first calls share one mint (13.865259ms) ✔ two tokens hold the name (two mints raced): both are deleted by their id, and one fresh token is minted (15.648627ms) ✔ two processes on one kept file, both without a token, mint once: the second waits for the first and reuses it (74.691981ms) ✔ a lock left by a process that died mid-mint is taken over, not waited on for ever (5.24894ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (14.855284ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.739322ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (20.419417ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.121233ms) ✔ nothing to mint with and no token: the client says what is missing (0.163788ms) [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-NB84Rw/state/token ✔ the tools register once there is a way to a token, and the first call mints it (28.074358ms) [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-qbX6MJ/state/token ✔ a pull request can be closed, read and cleaned up through the tools (34.442223ms) [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-FT6qqO/state/token ✔ the tools' token is minted for an account of their own, which is no administrator and writes through its team (76.586647ms) [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-IlbsTh/state/token ✔ with the tools' token, the forge writes a status and refuses a protection edit — the forge itself, not a guard (44.899359ms) [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-pHpuE0/state/token ✔ what a base's protection asks is read from the branch, which the tools' account may read, not from the rules' list it may not (43.219357ms) [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-hGlX9L/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 (39.751589ms) [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-a5UkJX/state/token ✔ a tools' account someone made an administrator is made a plain account again at the next mint (34.792274ms) ✔ the tools never act as the administrator: MESH_GITEA_TOOLS_USER naming it is refused (0.782333ms) ✔ the manifest hands the tools their account, and the merge-ready authors name it rather than the administrator (0.912779ms) [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-45IWRk/state/token ✔ a repository check said as a warning on a head without merge-check.sh reads the base's protection from the branch (36.54932ms) [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 (24.809282ms) [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-JsRzgo/state/token [gitea] FAILED to delete the token(s) named "mesh-tools" the admin account "mesh-admin" holds — tried again at the next start: Gitea DELETE /users/mesh-admin/tokens/902 (named mesh-tools): 500 {"message":"the forge is not well"} ✔ an old token that cannot be deleted after the mint is said, the new token kept, and deleted at the next start (42.636398ms) [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-2NJ7cE/state/token ✔ a team another process made between the look and the create is found, not a failure (36.514425ms) [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-hllx6Z/state/token ✔ setting the tools' account up puts main's rule right in every repository: no push, only the tools' account merges (issue 948) (35.987684ms) [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-3qPTWX/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) (34.22274ms) ✔ a start with the token kept still puts main's rules right: the module's start asks for it each time (issue 948, review round 1) (12.018264ms) [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.187828ms) ✔ 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.283516ms) ✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (5.030168ms) ✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.34507ms) ✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.416464ms) ✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.248287ms) ✔ a verdict that landed out of date keeps its account on the pull request (0.224693ms) ✔ a release branch's move puts every open pull request into it out of date, as a trunk's does (ADR 0358 §5) (0.395415ms) ✔ a signed event is published on the bus and acted on once (60.91207ms) ✔ an unsigned event, or one whose signature does not verify, is refused and published nowhere (29.748019ms) ✔ an event and the poll seeing the same head announce it once (0.381247ms) ✔ each forge event is named in the module's stream and trimmed (0.478771ms) ✔ the webhook is made a system webhook, which the forge sends every repository's events to (1.140707ms) ✔ default webhooks left at the receiver by an earlier start are replaced by one system webhook (1.041861ms) ✔ a repository's copy of a default webhook at the receiver is deleted, on every page, and said (3.735601ms) ✔ a forge that makes no system webhook is said, never taken as heard (0.653299ms) ✔ the receiver tells what it verified and what it refused (8.147407ms) ✔ a forge that never delivers is said loudly once, and unhealthy, when the poll finds what no event said (1.302091ms) ✔ a forge whose events stop after one delivery is said loudly once per silent spell, and refusals are unhealthy (0.55263ms) ✔ without a receiver by configuration the polls alone watch, healthy; a receiver that failed is unhealthy (0.430981ms) ✔ the polls look every 30 s until events are heard, every five minutes while they are, and 30 s again on a miss (0.263205ms) ℹ tests 147 ℹ suites 0 ℹ pass 147 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 740.525388 ```

mesh-tools merged commit 522780d5fc into main 2026-10-16 23:11:16 +00:00

mesh-tools deleted branch fix/955-gitea-reads-assignments 2026-10-16 23:11:16 +00:00

mesh-tools referenced this pull request 2026-10-16 23:26:18 +00:00

Keep gitea's forge-account provider running when a watch is refused, so a later grant is picked up (issue 955) #342

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 mesh/ready

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