gitea: announce every open pull request's new head, not only the newest 20 (hq issue 579) #254

Merged
mesh-admin merged 1 commits from fix/579-every-open-pull-request-is-announced into main 2026-10-12 18:58:28 +00:00
Contributor

Fixes novox/hq issue 579 (the forge's announcer reads only the 20 most recently updated open pull requests of a repository).

Cause. pollPulls in modules/gitea/index.ts (line 255 on main) asked the forge for state=open&sort=recentupdate&limit=20. A new head on the 21st or later open pull request was never announced, so its merge check never started.

Change.

  • client.ts: a new listOpenPullsSince(owner, repo, since) pages state=open&sort=recentupdate&limit=50. It stops at a short page, or at the first page whose oldest pull request is older than since. With no since, it reads every page. It is capped at 20 pages (1000 pull requests), the same cap as ADR 0323's listOpenPulls, and it answers a pull request seen on two pages once.
  • index.ts: pollPulls calls it with the pass's floor (the last look less a minute). On the 10-minute sweep and on the first pass it calls it with no floor, so every page is read.

The forge's order, checked live. GET /repos/novox/mesh-controller/pulls?state=all&sort=recentupdate answered in falling updated_at order (18:46:18, 18:37:38, 18:22:10, 17:35:57, ...). Gitea's recentupdate is issue.updated_unix DESC.

Load on the forge.

  • An ordinary pass makes one request per repository it looks at, unless more than 50 of that repository's open pull requests were updated since the last look. Before this change it was also one request.
  • The sweep makes ceil(open / 50) requests per repository, at most 20.
  • weighTrunks already reads every open pull request of each repository it looks at.

Test. test/paging.test.ts sets up a forge with 25 open pull requests whose heads were all announced before. The 23rd most recently updated one then gets a new head. The test asserts that the newest 20 miss it (the fault), and that two passes announce it exactly once. A second test uses 130 open pull requests and checks that paging stops at the page that reaches past the floor. On main, both tests fail with client.listOpenPullsSince is not a function. On this branch, merge-check-typescript.sh (83 of 83 tests pass) and merge-check.sh both pass for gitea.

Fixes novox/hq issue 579 (the forge's announcer reads only the 20 most recently updated open pull requests of a repository). **Cause.** `pollPulls` in `modules/gitea/index.ts` (line 255 on main) asked the forge for `state=open&sort=recentupdate&limit=20`. A new head on the 21st or later open pull request was never announced, so its merge check never started. **Change.** - `client.ts`: a new `listOpenPullsSince(owner, repo, since)` pages `state=open&sort=recentupdate&limit=50`. It stops at a short page, or at the first page whose oldest pull request is older than `since`. With no `since`, it reads every page. It is capped at 20 pages (1000 pull requests), the same cap as ADR 0323's `listOpenPulls`, and it answers a pull request seen on two pages once. - `index.ts`: `pollPulls` calls it with the pass's floor (the last look less a minute). On the 10-minute sweep and on the first pass it calls it with no floor, so every page is read. **The forge's order, checked live.** `GET /repos/novox/mesh-controller/pulls?state=all&sort=recentupdate` answered in falling `updated_at` order (18:46:18, 18:37:38, 18:22:10, 17:35:57, ...). Gitea's `recentupdate` is `issue.updated_unix DESC`. **Load on the forge.** - An ordinary pass makes one request per repository it looks at, unless more than 50 of that repository's open pull requests were updated since the last look. Before this change it was also one request. - The sweep makes ceil(open / 50) requests per repository, at most 20. - `weighTrunks` already reads every open pull request of each repository it looks at. **Test.** `test/paging.test.ts` sets up a forge with 25 open pull requests whose heads were all announced before. The 23rd most recently updated one then gets a new head. The test asserts that the newest 20 miss it (the fault), and that two passes announce it exactly once. A second test uses 130 open pull requests and checks that paging stops at the page that reaches past the floor. On main, both tests fail with `client.listOpenPullsSince is not a function`. On this branch, `merge-check-typescript.sh` (83 of 83 tests pass) and `merge-check.sh` both pass for gitea.
mesh-admin added 1 commit 2026-10-12 18:52:42 +00:00
Page the announcer through every open pull request updated since its last look
mesh/merge-gate head 961e57f7e403 merged into trunk 22071dabfc7b — pass: builds gitea → novox; no bus step; every machine composes with the change as it di…
mesh/repo-check head 961e57f7e403 merged into trunk 22071dabfc7b — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
mesh/delivery delivered
961e57f7e4
A pass read only the 20 most recently updated open pull requests of a
repository, so a new head beyond them went unannounced and its merge check
never started (novox/hq issue 579). Pages stop at the floor; a sweep reads all.
Author
Contributor

Delivery novox/mesh-catalog@961e57f7e403 — delivered since 2026-10-12T19:00:32Z

Delivery plan — builds gitea → novox; no bus step

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

Machines

  • gitea on novox: passed — healthy 1 times over 39s
  • gitea on the rest running it: sent

Transitions

  • 2026-10-12 18:53 (new) → proposed (announced): novox/mesh-catalog#254's head announced
  • 2026-10-12 18:55 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-12 18:55 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-12 18:58 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-12 18:58 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-12 19:00 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@961e57f7e403` — **delivered** since 2026-10-12T19:00:32Z **Delivery plan** — builds gitea → novox; no bus step - tier 0: gitea - novox: receives gitea - gitea provides npm-package-registry, git: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - gitea on novox: passed — healthy 1 times over 39s - gitea on the rest running it: sent **Transitions** - 2026-10-12 18:53 (new) → proposed (announced): novox/mesh-catalog#254's head announced - 2026-10-12 18:55 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-12 18:55 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-12 18:58 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-12 18:58 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-12 19:00 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`.
Author
Contributor

Merge check at 961e57f7
Judged: head 961e57f7e403 merged into trunk 22071dabfc7b; read beside it: mesh-controller d8f36a8fb706, mesh-controller-main 84deb530ee5a, mesh-host 303d4037e84e, mesh-tools 954e1a53eef9

  • 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: 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 g14 as build-1791831192782559560 (builds --log build-1791831192782559560).

--- the gate: gitea
gitea: ok, keeps data (valuable); WARNING: server stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T18:27:33Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-12T18:27:33Z

modules the change moves:
  - gitea (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): gitea
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.004s
words: 12 retired words and 70 daemons' lines, none in the 44435 strings of 701 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.011s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.206s
testing modules/gitea
ok  	gitea/cmd/forge	1.400s
ok  	gitea/cmd/npm-registry	1.761s
?   	gitea/internal/forgehttp	[no test files]
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/gitea (TypeScript)
testing modules/gitea (TypeScript)
✔ a pull request opened after the margin is looked at, by its own update time (14.431222ms)
✔ every open pull request is read with what its base requires and what its head has (gitea_open_pulls) (49.934458ms)
✔ a pull request or issue number that is not one is refused before the forge is asked (1.278938ms)
✔ the newest status of each context is kept, with what it said, when and by whom (22.346714ms)
✔ a commit merges only when every required status is a success; a warning blocks (0.560295ms)
✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.253708ms)
✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.729683ms)
✔ a note line is appended once, as the forge's user, in its own repository (9.797577ms)
✔ a note that cannot be written is said, never read as written (0.410222ms)
✔ one view per pull request, found by its marker; only the mesh's statuses (0.572468ms)
✔ a build machine taking the check is said on the head: building on which machine, since the local time (16.073273ms)
✔ the verdict heard while a 'building' write is in flight lands last and stays (5.919245ms)
[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.093298ms)
✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.579391ms)
✔ a start heard after the verdict writes nothing (0.598066ms)
✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.574452ms)
✔ an old run's verdict redelivered after a recheck's pending is not written over it (2.325829ms)
[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 (1.946435ms)
✔ a rechecked head says where its new run is: building on which machine (0.825374ms)
✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.662337ms)
✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.549234ms)
✔ a recheck the forge does not take fails its caller, and the head is as it was (0.500532ms)
✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (4.98666ms)
✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.262785ms)
✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (0.351001ms)
✔ a repository as the mesh clones it is told from another (0.275578ms)
✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.522297ms)
✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (43.462713ms)
✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (15.257888ms)
✔ gitea_api still writes what an author writes (8.022064ms)
✔ gitea_branch_protection_set only strengthens (14.760812ms)
✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (35.772173ms)
✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (136.60388ms)
✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (16.789973ms)
✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (14.367722ms)
✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (25.417647ms)
✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (64.900857ms)
✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (29.84913ms)
✔ gitea_api sends the path it judged, and refuses moving a pull request's base (5.672751ms)
✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (7.42479ms)
✔ a rule named for a branch is not made weaker than the glob rule that guards it now (16.781116ms)
✔ a repository owner or name is never another path (0.363133ms)
✔ the judges, without a forge (0.495814ms)
✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.956193ms)
✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.854384ms)
✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.995475ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (29.914885ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.497477ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (12.322321ms)
✔ a lookup the forge refuses is thrown, not read as no module (4.061166ms)
✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (5.051621ms)
✔ a new head beyond the newest 20 open pull requests is announced, exactly once (41.87842ms)
✔ a pass pages until it reaches back past its floor, and no further (22.312681ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (5.887245ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.295045ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (8.308885ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.983933ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.792532ms)
✔ no verdict sets warning on a required check; only a person's decision fails (1.044066ms)
✔ a commit status is set on the commit, under the merge check's context (27.484699ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.426343ms)
✔ a head announced is pending in the build queue, since the local time it was announced (0.178947ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (29.68463ms)
✔ second start: reuses the kept token, mints nothing (15.256986ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (19.992493ms)
✔ 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 (22.273787ms)
✔ 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 (17.706768ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (14.895906ms)
✔ concurrent first calls share one mint (10.09103ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (10.939306ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.704136ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (17.288842ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.259785ms)
✔ nothing to mint with and no token: the client says what is missing (0.172244ms)
[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-admin" (write:repository, write:issue, read:user), kept at /tmp/gitea-IlWyMV/state/token
✔ the tools register once there is a way to a token, and the first call mints it (8.745907ms)
[gitea] no token kept — minting one
[gitea] the forge already holds a token named "mesh-tools" — replacing it
[gitea] minted a token for "mesh-admin" (write:repository, write:issue, read:user), kept at /tmp/gitea-4vTgIh/state/token
✔ a pull request can be closed, read and cleaned up through the tools (18.789968ms)
[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)
✔ both statuses say the head and the trunk commit the verdict judged, first, whatever the summary's length (1.810138ms)
✔ 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.23238ms)
✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (6.04939ms)
✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.387239ms)
✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.461208ms)
✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.283955ms)
✔ a verdict that landed out of date keeps its account on the pull request (0.263787ms)
ℹ tests 83
ℹ suites 0
ℹ pass 83
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 608.618488
**Merge check** at `961e57f7` Judged: head `961e57f7e403` merged into trunk `22071dabfc7b`; read beside it: mesh-controller `d8f36a8fb706`, mesh-controller-main `84deb530ee5a`, mesh-host `303d4037e84e`, mesh-tools `954e1a53eef9` - `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: 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 g14 as `build-1791831192782559560` (`builds --log build-1791831192782559560`). ``` --- the gate: gitea gitea: ok, keeps data (valuable); WARNING: server stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 1 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T18:27:33Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-12T18:27:33Z modules the change moves: - gitea (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): gitea --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.004s words: 12 retired words and 70 daemons' lines, none in the 44435 strings of 701 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 69, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.206s testing modules/gitea ok gitea/cmd/forge 1.400s ok gitea/cmd/npm-registry 1.761s ? gitea/internal/forgehttp [no test files] --- its merge-check-typescript.sh (typescript toolchain) type-checking modules/gitea (TypeScript) testing modules/gitea (TypeScript) ✔ a pull request opened after the margin is looked at, by its own update time (14.431222ms) ✔ every open pull request is read with what its base requires and what its head has (gitea_open_pulls) (49.934458ms) ✔ a pull request or issue number that is not one is refused before the forge is asked (1.278938ms) ✔ the newest status of each context is kept, with what it said, when and by whom (22.346714ms) ✔ a commit merges only when every required status is a success; a warning blocks (0.560295ms) ✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.253708ms) ✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.729683ms) ✔ a note line is appended once, as the forge's user, in its own repository (9.797577ms) ✔ a note that cannot be written is said, never read as written (0.410222ms) ✔ one view per pull request, found by its marker; only the mesh's statuses (0.572468ms) ✔ a build machine taking the check is said on the head: building on which machine, since the local time (16.073273ms) ✔ the verdict heard while a 'building' write is in flight lands last and stays (5.919245ms) [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.093298ms) ✔ the verdict heard while a 'building' write still waits its turn: the 'building' is never written (0.579391ms) ✔ a start heard after the verdict writes nothing (0.598066ms) ✔ a start from before the check now pending (a run before a recheck, the stream's history) writes nothing (0.574452ms) ✔ an old run's verdict redelivered after a recheck's pending is not written over it (2.325829ms) [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 (1.946435ms) ✔ a rechecked head says where its new run is: building on which machine (0.825374ms) ✔ the recheck's own verdict is written, even asked a little before the pending by another machine's clock (0.662337ms) ✔ after a restart, an old run's verdict is weighed against the check the forge's history holds open (0.549234ms) ✔ a recheck the forge does not take fails its caller, and the head is as it was (0.500532ms) ✔ the status tool writes the merge check's pending through the writer, and the mesh's other statuses as they were (4.98666ms) ✔ when a check was asked is read from its id; the opening of the check now pending from the gate's history (0.262785ms) ✔ a head this process did not announce (it restarted) is said only while the forge holds its gate pending (0.351001ms) ✔ a repository as the mesh clones it is told from another (0.275578ms) ✔ gitea_api refuses the forge's administration, a branch's protection and the merge check's status, and sends nothing (5.522297ms) ✔ gitea_api refuses a file written to the default branch or one a rule guards, and writes one on a branch of its own (43.462713ms) ✔ a protection rule covers a branch as the forge decides it: classes, alternatives, a plain name in any case (issue 539) (15.257888ms) ✔ gitea_api still writes what an author writes (8.022064ms) ✔ gitea_branch_protection_set only strengthens (14.760812ms) ✔ gitea_merge_pull_request merges only a head whose required statuses all succeeded, and only that head (35.772173ms) ✔ gitea_merge_pull_request refuses a verdict judged against an earlier trunk, and asks the check once (136.60388ms) ✔ gitea_merge_pull_request merges only the head it is named, and refuses one that is not the head (16.789973ms) ✔ gitea_merge_pull_request is loud when the forge merged a head other than the one it was handed (14.367722ms) ✔ gitea_merge_pull_request says the merge happened when reading back what landed fails (25.417647ms) ✔ gitea_merge_pull_request reads back a fast-forward, and says it cannot read back a squash or a rebase (64.900857ms) ✔ gitea_delete_repo deletes only the tools' own user's repository, unguarded, untouched for 30 days, named in full (29.84913ms) ✔ gitea_api sends the path it judged, and refuses moving a pull request's base (5.672751ms) ✔ gitea_merge_pull_request merges only into a branch whose protection requires the checks (7.42479ms) ✔ a rule named for a branch is not made weaker than the glob rule that guards it now (16.781116ms) ✔ a repository owner or name is never another path (0.363133ms) ✔ the judges, without a forge (0.495814ms) ✔ gitea_api never acts as another user: sudo, in any case, and any query key it does not send are refused (1.956193ms) ✔ gitea_api never approves a pull request nor requests changes: those are the operator's (2.854384ms) ✔ no tool's caller text becomes another path or another user: `..` and `?sudo=` are refused before the forge (4.995475ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (29.914885ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.497477ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (12.322321ms) ✔ a lookup the forge refuses is thrown, not read as no module (4.061166ms) ✔ a renamed file is said under its old name too, as gone (novox/hq ADR 0267) (5.051621ms) ✔ a new head beyond the newest 20 open pull requests is announced, exactly once (41.87842ms) ✔ a pass pages until it reaches back past its floor, and no further (22.312681ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (5.887245ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.295045ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (8.308885ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.983933ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.792532ms) ✔ no verdict sets warning on a required check; only a person's decision fails (1.044066ms) ✔ a commit status is set on the commit, under the merge check's context (27.484699ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.426343ms) ✔ a head announced is pending in the build queue, since the local time it was announced (0.178947ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (29.68463ms) ✔ second start: reuses the kept token, mints nothing (15.256986ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (19.992493ms) ✔ 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 (22.273787ms) ✔ 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 (17.706768ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (14.895906ms) ✔ concurrent first calls share one mint (10.09103ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (10.939306ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.704136ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (17.288842ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.259785ms) ✔ nothing to mint with and no token: the client says what is missing (0.172244ms) [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-admin" (write:repository, write:issue, read:user), kept at /tmp/gitea-IlWyMV/state/token ✔ the tools register once there is a way to a token, and the first call mints it (8.745907ms) [gitea] no token kept — minting one [gitea] the forge already holds a token named "mesh-tools" — replacing it [gitea] minted a token for "mesh-admin" (write:repository, write:issue, read:user), kept at /tmp/gitea-4vTgIh/state/token ✔ a pull request can be closed, read and cleaned up through the tools (18.789968ms) [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) ✔ both statuses say the head and the trunk commit the verdict judged, first, whatever the summary's length (1.810138ms) ✔ 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.23238ms) ✔ a push to a trunk puts every open pull request into it out of date — twenty-five of them — and none into another (6.04939ms) ✔ a trunk that cannot be read is weighed again on the next pass, never recorded half (0.387239ms) ✔ the trunk's move takes its turn after a verdict in flight, and weighs what the forge holds then (0.461208ms) ✔ a verdict judged against a trunk newer than the pass's first read is not put out of date (0.283955ms) ✔ a verdict that landed out of date keeps its account on the pull request (0.263787ms) ℹ tests 83 ℹ suites 0 ℹ pass 83 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 608.618488 ```
mesh-admin merged commit 2fe5601397 into main 2026-10-12 18:58:28 +00:00
mesh-admin deleted branch fix/579-every-open-pull-request-is-announced 2026-10-12 18:58:28 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#254