Announce a pull request opened after its push, and say one nobody checks (hq issue 347) #159

Merged
mesh-admin merged 3 commits from fix/347-a-pull-request-opened-after-its-push-is-never-checked into main 2026-10-09 11:38:48 +00:00
Contributor

hq issue 347 (hq #247).

Symptom (2026-10-09). mesh-sdk #14, opened at 10:11 UTC eight minutes after its branch was pushed, had no mesh/merge-gate or mesh/repo-check twenty minutes later; nothing said why.

Cause. pollPulls reads only repositories whose updated_at moved since the last pass minus 60 s (movedSince, issue 250). Opening, reopening or retargeting a PR does not move a repository's updated_at.

Fix.

  • gitea, the announcer: each pass also looks at every repository holding an open PR updated since the floor, via /repos/issues/search?type=pulls&state=open&since=… (searchOpenPulls, reposToLook); every 10 minutes, or when the search fails, every repository.
  • gitea, gitea_open_pulls: every open PR from the forge itself, with its base's required statuses and its head's statuses.
  • mesh-delivery says one nobody checks (changed after the confirmation review, which asked for the delivery domain's own vocabulary): every 5 minutes it asks gitea_open_pulls; a head on a base requiring mesh/merge-gate or mesh/repo-check (hq requires only the second) with neither for 10 minutes since mesh-delivery first saw it so (its own time; the forge's updated_at moves on comments) is a stalled line in state unannounced, which the controller raises as delivery.<id>.stalled (D14). H2 has nothing to close. Once announced it is a delivery of its own. Granted gitea.gitea_open_pulls.
  • Why not a gitea health check: it would need a tools list (turning gitea's tools into seat verbs), a check of another kind beside it, and an unhealthy forge would hold its own deliveries at the first-node gate. The provider standing of the first version is removed.
  • The client refuses a PR/issue number that is not a whole number above 0 (pulls/NaN).
  • Words: mesh-controller PR fix/347-an-unannounced-pull-request-says-what-to-do makes the condition say "push a new commit" rather than "stop it"; merge it before or with this one (without it the condition is raised with the generic stalled words).

Tests. gitea test/announcing.test.ts (a PR opened after the margin is looked at; open PRs read with required/statuses; pulls/NaN refused) and mesh-delivery unchecked_test.go (only-repo-check base counts; own first-seen time; dropped on a check, on announcement or close; a forge away changes nothing) — all fail before the fix. Local merge-check.sh (go) and merge-check-typescript.sh pass.

Independent of the mesh-cli PRs.

hq issue 347 (hq #247). **Symptom (2026-10-09).** mesh-sdk #14, opened at 10:11 UTC eight minutes after its branch was pushed, had no `mesh/merge-gate` or `mesh/repo-check` twenty minutes later; nothing said why. **Cause.** `pollPulls` reads only repositories whose `updated_at` moved since the last pass minus 60 s (`movedSince`, issue 250). Opening, reopening or retargeting a PR does not move a repository's `updated_at`. **Fix.** - **gitea, the announcer:** each pass also looks at every repository holding an open PR updated since the floor, via `/repos/issues/search?type=pulls&state=open&since=…` (`searchOpenPulls`, `reposToLook`); every 10 minutes, or when the search fails, every repository. - **gitea, `gitea_open_pulls`:** every open PR from the forge itself, with its base's required statuses and its head's statuses. - **mesh-delivery says one nobody checks** (changed after the confirmation review, which asked for the delivery domain's own vocabulary): every 5 minutes it asks `gitea_open_pulls`; a head on a base requiring `mesh/merge-gate` **or `mesh/repo-check`** (hq requires only the second) with neither for 10 minutes since mesh-delivery first saw it so (its own time; the forge's `updated_at` moves on comments) is a `stalled` line in state `unannounced`, which the controller raises as `delivery.<id>.stalled` (D14). H2 has nothing to close. Once announced it is a delivery of its own. Granted `gitea.gitea_open_pulls`. - **Why not a gitea health check:** it would need a `tools` list (turning gitea's tools into seat verbs), a check of another kind beside it, and an unhealthy forge would hold its own deliveries at the first-node gate. The provider standing of the first version is removed. - **The client refuses** a PR/issue number that is not a whole number above 0 (`pulls/NaN`). - **Words:** mesh-controller PR `fix/347-an-unannounced-pull-request-says-what-to-do` makes the condition say "push a new commit" rather than "stop it"; merge it before or with this one (without it the condition is raised with the generic stalled words). **Tests.** gitea `test/announcing.test.ts` (a PR opened after the margin is looked at; open PRs read with required/statuses; `pulls/NaN` refused) and mesh-delivery `unchecked_test.go` (only-repo-check base counts; own first-seen time; dropped on a check, on announcement or close; a forge away changes nothing) — all fail before the fix. Local `merge-check.sh` (go) and `merge-check-typescript.sh` pass. Independent of the mesh-cli PRs.
mesh-admin added 1 commit 2026-10-09 10:56:59 +00:00
Announce a pull request opened after its push, and say one nobody checks (hq issue 347)
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds gitea → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
67bce7e189
The announcer read only the repositories whose update time moved since its
last pass, less a minute. Opening, reopening or retargeting a pull request
does not move a repository's update time, so a pull request opened more
than a minute after its push was never announced, never checked, and
nothing said so (mesh-sdk #14, 2026-10-09).

- Each pass also looks at every repository holding a pull request updated
  since the floor, by the forge's own search; every ten minutes, or when the
  search fails, at every repository.
- Every five minutes the forge is asked for every open pull request; one on
  a base requiring mesh/merge-gate whose head has had none for ten minutes
  is said as the forge failing that pull request's merge check (a provider
  standing, ADR 0224), which the controller keeps as a condition, and is
  recovered when a check arrives or it closes.
- The client refuses a pull request or issue number that is not one before
  asking the forge (a misnamed tool argument sent pulls/NaN).
Author
Contributor

Delivery novox/mesh-catalog@32d55beb47bb — superseded since 2026-10-09T11:39:04Z

Delivery plan — builds gitea, mesh-delivery → novox; no bus step

  • tier 0: gitea, mesh-delivery
  • novox: receives gitea, mesh-delivery
  • 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

Transitions

  • 2026-10-09 11:14 (new) → proposed (announced): novox/mesh-catalog#159's head announced
  • 2026-10-09 11:16 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 11:16 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 11:39 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-09 11:39 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
  • 2026-10-09 11:39 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@32d55beb47bb` — **superseded** since 2026-10-09T11:39:04Z **Delivery plan** — builds gitea, mesh-delivery → novox; no bus step - tier 0: gitea, mesh-delivery - novox: receives gitea, mesh-delivery - 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 **Transitions** - 2026-10-09 11:14 (new) → proposed (announced): novox/mesh-catalog#159's head announced - 2026-10-09 11:16 proposed → checked (checked): the verdict names this commit - 2026-10-09 11:16 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 11:39 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-09 11:39 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 - 2026-10-09 11:39 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
jschoubben added 1 commit 2026-10-09 10:58:15 +00:00
gitea README: how to see a late-opened pull request announced (hq issue 347)
mesh/merge-gate pass: builds gitea → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
bcc6b3f52a
Author
Contributor

Merge check at 67bce7e1

  • 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 shanks as build-1791543454174188825 (builds --log build-1791543454174188825).

--- 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-09T10:57:39Z 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-09T10:57:39Z

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.002s
words: 12 retired words, none in the 34147 strings of 603 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/gitea
ok  	gitea/cmd/npm-registry	1.785s
--- 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 (9.386568ms)
✔ an open pull request on a protected branch with no merge check for ten minutes is said, and nothing else (0.399177ms)
✔ a pull request or issue number that is not one is refused before the forge is asked (11.906273ms)
✔ the newest status of each context is kept, with what it said, when and by whom (14.187314ms)
✔ a commit merges only when every required status is a success; a warning blocks (0.521579ms)
✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.224244ms)
✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.673522ms)
✔ a note line is appended once, as the forge's user, in its own repository (6.521716ms)
✔ a note that cannot be written is said, never read as written (0.371367ms)
✔ one view per pull request, found by its marker; only the mesh's statuses (0.538589ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (25.728579ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.365577ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (10.845094ms)
✔ a lookup the forge refuses is thrown, not read as no module (4.515371ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (5.886745ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.256844ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (7.266719ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.918526ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.687232ms)
✔ no verdict sets warning on a required check; only a person's decision fails (1.10645ms)
✔ a commit status is set on the commit, under the merge check's context (31.537083ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.492038ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (31.569024ms)
✔ second start: reuses the kept token, mints nothing (16.905851ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (21.952352ms)
✔ a kept token from before write:admin: the forge refuses the admin route for the scope, the token is re-minted with the whole list, and the call goes through (24.588089ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (16.983602ms)
✔ concurrent first calls share one mint (10.337744ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (12.357501ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (2.021316ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (18.046283ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (3.056035ms)
✔ nothing to mint with and no token: the client says what is missing (0.244114ms)
[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, write:admin), kept at /tmp/gitea-gxLWNH/state/token
✔ the tools register once there is a way to a token, and the first call mints it (7.933241ms)
[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, write:admin), kept at /tmp/gitea-7PvueG/state/token
✔ a pull request can be closed, read and cleaned up through the tools (19.320465ms)
ℹ tests 35
ℹ suites 0
ℹ pass 35
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 325.033524
**Merge check** at `67bce7e1` - `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 shanks as `build-1791543454174188825` (`builds --log build-1791543454174188825`). ``` --- 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-09T10:57:39Z 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-09T10:57:39Z 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.002s words: 12 retired words, none in the 34147 strings of 603 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/gitea ok gitea/cmd/npm-registry 1.785s --- 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 (9.386568ms) ✔ an open pull request on a protected branch with no merge check for ten minutes is said, and nothing else (0.399177ms) ✔ a pull request or issue number that is not one is refused before the forge is asked (11.906273ms) ✔ the newest status of each context is kept, with what it said, when and by whom (14.187314ms) ✔ a commit merges only when every required status is a success; a warning blocks (0.521579ms) ✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.224244ms) ✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.673522ms) ✔ a note line is appended once, as the forge's user, in its own repository (6.521716ms) ✔ a note that cannot be written is said, never read as written (0.371367ms) ✔ one view per pull request, found by its marker; only the mesh's statuses (0.538589ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (25.728579ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.365577ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (10.845094ms) ✔ a lookup the forge refuses is thrown, not read as no module (4.515371ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (5.886745ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.256844ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (7.266719ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.918526ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.687232ms) ✔ no verdict sets warning on a required check; only a person's decision fails (1.10645ms) ✔ a commit status is set on the commit, under the merge check's context (31.537083ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.492038ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (31.569024ms) ✔ second start: reuses the kept token, mints nothing (16.905851ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (21.952352ms) ✔ a kept token from before write:admin: the forge refuses the admin route for the scope, the token is re-minted with the whole list, and the call goes through (24.588089ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (16.983602ms) ✔ concurrent first calls share one mint (10.337744ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (12.357501ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (2.021316ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (18.046283ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (3.056035ms) ✔ nothing to mint with and no token: the client says what is missing (0.244114ms) [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, write:admin), kept at /tmp/gitea-gxLWNH/state/token ✔ the tools register once there is a way to a token, and the first call mints it (7.933241ms) [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, write:admin), kept at /tmp/gitea-7PvueG/state/token ✔ a pull request can be closed, read and cleaned up through the tools (19.320465ms) ℹ tests 35 ℹ suites 0 ℹ pass 35 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 325.033524 ```
Author
Contributor

Merge check at bcc6b3f5

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

--- 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-09T10:57:39Z 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-09T10:57:39Z

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.001s
words: 12 retired words, none in the 34147 strings of 603 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/gitea
ok  	gitea/cmd/npm-registry	1.671s
--- 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 (7.023089ms)
✔ an open pull request on a protected branch with no merge check for ten minutes is said, and nothing else (0.29745ms)
✔ a pull request or issue number that is not one is refused before the forge is asked (9.027905ms)
✔ the newest status of each context is kept, with what it said, when and by whom (24.922315ms)
✔ a commit merges only when every required status is a success; a warning blocks (0.492026ms)
✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.212881ms)
✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.550327ms)
✔ a note line is appended once, as the forge's user, in its own repository (7.94201ms)
✔ a note that cannot be written is said, never read as written (0.433767ms)
✔ one view per pull request, found by its marker; only the mesh's statuses (0.59992ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (28.07359ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.341273ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (10.792429ms)
✔ a lookup the forge refuses is thrown, not read as no module (4.519343ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (4.832132ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.319872ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (6.927158ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.798884ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.500293ms)
✔ no verdict sets warning on a required check; only a person's decision fails (0.787293ms)
✔ a commit status is set on the commit, under the merge check's context (33.192382ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.601573ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (24.878954ms)
✔ second start: reuses the kept token, mints nothing (14.960269ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (18.108269ms)
✔ a kept token from before write:admin: the forge refuses the admin route for the scope, the token is re-minted with the whole list, and the call goes through (26.183ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (15.739397ms)
✔ concurrent first calls share one mint (11.453374ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (11.029706ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.598267ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (16.145633ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.388248ms)
✔ nothing to mint with and no token: the client says what is missing (0.178446ms)
[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, write:admin), kept at /tmp/gitea-JY9dpX/state/token
✔ the tools register once there is a way to a token, and the first call mints it (7.801245ms)
[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, write:admin), kept at /tmp/gitea-6QDrfp/state/token
✔ a pull request can be closed, read and cleaned up through the tools (15.226922ms)
ℹ tests 35
ℹ suites 0
ℹ pass 35
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 314.250766
**Merge check** at `bcc6b3f5` - `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-1791543514827951321` (`builds --log build-1791543514827951321`). ``` --- 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-09T10:57:39Z 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-09T10:57:39Z 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.001s words: 12 retired words, none in the 34147 strings of 603 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/gitea ok gitea/cmd/npm-registry 1.671s --- 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 (7.023089ms) ✔ an open pull request on a protected branch with no merge check for ten minutes is said, and nothing else (0.29745ms) ✔ a pull request or issue number that is not one is refused before the forge is asked (9.027905ms) ✔ the newest status of each context is kept, with what it said, when and by whom (24.922315ms) ✔ a commit merges only when every required status is a success; a warning blocks (0.492026ms) ✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.212881ms) ✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.550327ms) ✔ a note line is appended once, as the forge's user, in its own repository (7.94201ms) ✔ a note that cannot be written is said, never read as written (0.433767ms) ✔ one view per pull request, found by its marker; only the mesh's statuses (0.59992ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (28.07359ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.341273ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (10.792429ms) ✔ a lookup the forge refuses is thrown, not read as no module (4.519343ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (4.832132ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.319872ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (6.927158ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.798884ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.500293ms) ✔ no verdict sets warning on a required check; only a person's decision fails (0.787293ms) ✔ a commit status is set on the commit, under the merge check's context (33.192382ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.601573ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (24.878954ms) ✔ second start: reuses the kept token, mints nothing (14.960269ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (18.108269ms) ✔ a kept token from before write:admin: the forge refuses the admin route for the scope, the token is re-minted with the whole list, and the call goes through (26.183ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (15.739397ms) ✔ concurrent first calls share one mint (11.453374ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (11.029706ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (0.598267ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (16.145633ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.388248ms) ✔ nothing to mint with and no token: the client says what is missing (0.178446ms) [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, write:admin), kept at /tmp/gitea-JY9dpX/state/token ✔ the tools register once there is a way to a token, and the first call mints it (7.801245ms) [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, write:admin), kept at /tmp/gitea-6QDrfp/state/token ✔ a pull request can be closed, read and cleaned up through the tools (15.226922ms) ℹ tests 35 ℹ suites 0 ℹ pass 35 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 314.250766 ```
jschoubben added 1 commit 2026-10-09 11:14:39 +00:00
Say a pull request nobody checks as a delivery held, owned by mesh-delivery (hq issue 347)
mesh/merge-gate pass: builds gitea, mesh-delivery → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer delivery to the same trunk took over its walk
32d55beb47
The confirmation review asked for the delivery domain's own vocabulary
instead of a provider standing. A gitea health check would need a `tools`
list (turning gitea's tools into seat verbs), a check of another kind
beside it, and would hold the forge's own deliveries at the first-node
gate; so the delivery's owner says it, with the word it already has.

- gitea_open_pulls (gitea): every open pull request from the forge itself,
  with what its base requires and the statuses its head has.
- mesh-delivery asks it every five minutes and keeps its own first-seen
  time per head (the forge's update time moves on every comment). A head
  on a base requiring mesh/merge-gate OR mesh/repo-check (hq requires only
  the second) with neither for ten minutes is a `stalled` line in state
  `unannounced`, which the controller raises as delivery.<id>.stalled (D14);
  H2 has nothing to close. Once announced it is a delivery of its own.
- The gitea-side watcher and its provider standing are gone.
Author
Contributor

Merge check at 32d55beb

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea, mesh-delivery)
  • 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, mesh-delivery → novox; no bus step

  • tier 0: gitea, mesh-delivery
  • novox: receives gitea, mesh-delivery
  • 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-1791544485895650665 (builds --log build-1791544485895650665).

--- the gate: gitea, mesh-delivery
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)
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
2 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 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T11:11:36Z 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-09T11:11:36Z

modules the change moves:
  - gitea (changed)
  - mesh-delivery (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 2 module(s) in 1 tier(s): gitea, mesh-delivery
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 34152 strings of 604 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.004s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/gitea
ok  	gitea/cmd/npm-registry	1.632s
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	1.241s
--- 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 (7.170406ms)
✔ every open pull request is read with what its base requires and what its head has (gitea_open_pulls) (42.117603ms)
✔ a pull request or issue number that is not one is refused before the forge is asked (1.091604ms)
✔ the newest status of each context is kept, with what it said, when and by whom (11.297184ms)
✔ a commit merges only when every required status is a success; a warning blocks (0.459485ms)
✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.193103ms)
✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.528595ms)
✔ a note line is appended once, as the forge's user, in its own repository (5.284406ms)
✔ a note that cannot be written is said, never read as written (0.30314ms)
✔ one view per pull request, found by its marker; only the mesh's statuses (0.419359ms)
✔ every page of a pull request's files is read, though the forge caps a page at fifty (18.626509ms)
✔ a pass asks only the repositories that moved since the last look, every one before the first (0.335923ms)
✔ the directories above a merge's files that hold a module at the commit are said, the root never (11.76831ms)
✔ a lookup the forge refuses is thrown, not read as no module (3.446757ms)
✔ the statuses asked for replace the rule's, and an empty list requires none (4.73328ms)
✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.297209ms)
✔ each open pull request's new head is announced once, and nothing closed or merged (6.399074ms)
✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.816467ms)
✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.56317ms)
✔ no verdict sets warning on a required check; only a person's decision fails (0.879545ms)
✔ a commit status is set on the commit, under the merge check's context (31.733859ms)
✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.547541ms)
✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (23.097203ms)
✔ second start: reuses the kept token, mints nothing (16.521877ms)
✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (18.422504ms)
✔ a kept token from before write:admin: the forge refuses the admin route for the scope, the token is re-minted with the whole list, and the call goes through (21.779043ms)
✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (15.283857ms)
✔ concurrent first calls share one mint (8.145632ms)
✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (10.976871ms)
✔ one process shares one source per kept file — the watcher and the tools never renew against each other (2.201403ms)
✔ a second process finds the token the first renewed, and reuses it instead of minting over it (16.65624ms)
✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.443639ms)
✔ nothing to mint with and no token: the client says what is missing (0.14877ms)
[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, write:admin), kept at /tmp/gitea-BNsBdx/state/token
✔ the tools register once there is a way to a token, and the first call mints it (6.815708ms)
[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, write:admin), kept at /tmp/gitea-v7iwLA/state/token
✔ a pull request can be closed, read and cleaned up through the tools (17.857702ms)
ℹ tests 35
ℹ suites 0
ℹ pass 35
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 274.50687
**Merge check** at `32d55beb` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: gitea, mesh-delivery) - `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, mesh-delivery → novox; no bus step - tier 0: gitea, mesh-delivery - novox: receives gitea, mesh-delivery - 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-1791544485895650665` (`builds --log build-1791544485895650665`). ``` --- the gate: gitea, mesh-delivery 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) mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups long-running resources without health: 1 files asking for a setting without saying whether it is trusted: 0 2 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 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T11:11:36Z 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-09T11:11:36Z modules the change moves: - gitea (changed) - mesh-delivery (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 2 module(s) in 1 tier(s): gitea, mesh-delivery --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 34152 strings of 604 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.004s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/gitea ok gitea/cmd/npm-registry 1.632s testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 1.241s --- 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 (7.170406ms) ✔ every open pull request is read with what its base requires and what its head has (gitea_open_pulls) (42.117603ms) ✔ a pull request or issue number that is not one is refused before the forge is asked (1.091604ms) ✔ the newest status of each context is kept, with what it said, when and by whom (11.297184ms) ✔ a commit merges only when every required status is a success; a warning blocks (0.459485ms) ✔ no rule requires nothing; a rule that cannot be read says nothing, never yes (0.193103ms) ✔ a commit is contained in another when the compare finds nothing on it the other lacks (0.528595ms) ✔ a note line is appended once, as the forge's user, in its own repository (5.284406ms) ✔ a note that cannot be written is said, never read as written (0.30314ms) ✔ one view per pull request, found by its marker; only the mesh's statuses (0.419359ms) ✔ every page of a pull request's files is read, though the forge caps a page at fifty (18.626509ms) ✔ a pass asks only the repositories that moved since the last look, every one before the first (0.335923ms) ✔ the directories above a merge's files that hold a module at the commit are said, the root never (11.76831ms) ✔ a lookup the forge refuses is thrown, not read as no module (3.446757ms) ✔ the statuses asked for replace the rule's, and an empty list requires none (4.73328ms) ✔ a new rule refuses direct pushes unless asked; an administrator's override only when said (0.297209ms) ✔ each open pull request's new head is announced once, and nothing closed or merged (6.399074ms) ✔ a verdict is the head commit's status; an error is the forge's error, never a success (0.816467ms) ✔ each layer is its own status: the gate with the modules it judged, the repository's own check beside it (0.56317ms) ✔ no verdict sets warning on a required check; only a person's decision fails (0.879545ms) ✔ a commit status is set on the commit, under the merge check's context (31.733859ms) ✔ a change plan is the gate's result: said on the status and, when it builds something, as a comment (0.547541ms) ✔ first start: mints with the admin account, keeps the token at 0600, asks for the tools' scopes only (23.097203ms) ✔ second start: reuses the kept token, mints nothing (16.521877ms) ✔ the forge rejects the kept token (its data was restored): minted afresh, once, and the call goes through (18.422504ms) ✔ a kept token from before write:admin: the forge refuses the admin route for the scope, the token is re-minted with the whole list, and the call goes through (21.779043ms) ✔ the kept file is gone but the forge still holds a token by that name: replaced, not refused (15.283857ms) ✔ concurrent first calls share one mint (8.145632ms) ✔ the admin account is refused: said plainly, nothing kept, and the next call fails the same way rather than crashing (10.976871ms) ✔ one process shares one source per kept file — the watcher and the tools never renew against each other (2.201403ms) ✔ a second process finds the token the first renewed, and reuses it instead of minting over it (16.65624ms) ✔ a configured token wins, and is reported rather than minted over when the forge rejects it (2.443639ms) ✔ nothing to mint with and no token: the client says what is missing (0.14877ms) [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, write:admin), kept at /tmp/gitea-BNsBdx/state/token ✔ the tools register once there is a way to a token, and the first call mints it (6.815708ms) [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, write:admin), kept at /tmp/gitea-v7iwLA/state/token ✔ a pull request can be closed, read and cleaned up through the tools (17.857702ms) ℹ tests 35 ℹ suites 0 ℹ pass 35 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 274.50687 ```
mesh-admin merged commit ceab9a03b7 into main 2026-10-09 11:38:48 +00:00
mesh-admin deleted branch fix/347-a-pull-request-opened-after-its-push-is-never-checked 2026-10-09 11:38:49 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#159