1516 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
mesh-admin	7879ade66f	Merge pull request 'ADR 0252: a module puts an account in a group, and the mesh says when a new login is needed' (#201) from decision/0252-a-module-puts-an-account-in-a-group into main	2026-10-08 11:05:12 +00:00
jochen	3449775cb6	ADR 0252: a module puts an account in a group, and the mesh says when a new login is needed ... Issue 247 left adding the operator's account to a daemon's group a sudo step by hand. Decide that a module declares it with the user resource's groups, that the mesh gives back only what it added, and that the node-engine says relogin needed; amend to-be 41 with WP6 and resolve the issue.	2026-10-08 12:04:50 +02:00
mesh-admin	f2201beb40	Merge pull request 'Issue 315: a failed unit of a module was never raised' (#199) from issues/315-a-failed-unit-was-never-raised into main	2026-10-08 09:40:28 +00:00
mesh-admin	bd14e1b021	Merge pull request 'Issue 313: history adopted at the switch was held for a person; ADR 0250 retires it' (#197) from fix/313-retire-adopted-history into main	2026-10-08 09:36:53 +00:00
jochen	28aabd8621	Issue 315: say the node-engine's repository as an identifier	2026-10-08 11:30:30 +02:00
jochen	7121d0737e	Issue 315: a failed unit of a module was never raised ... Liveness judged only long-running resources, so a module whose daemon is a package's unit failed at every login while its machine read healthy, and a degraded service manager was said by nothing.	2026-10-08 11:30:08 +02:00
jochen	67bb28da4e	Issue 313: history adopted at the switch was held for a person; ADR 0250 retires it and ends owed work the forge cannot do	2026-10-08 11:20:44 +02:00
mesh-admin	b11219e3de	Merge pull request 'Issue 309: two order rules ordered one pair both ways; ADR 0249 gives them a precedence' (#194) from issues/309-two-order-rules-ordered-one-pair-both-ways into main	2026-10-08 09:11:45 +00:00
mesh-admin	c6e76015b7	Merge pull request 'Issue 310: a pull request ran its own copy of its repository's check' (#196) from issues/310-a-pull-request-ran-its-own-copy-of-its-check into main	2026-10-08 09:10:27 +00:00
jochen	a0765c0b13	Issue 310: a pull request ran its own copy of its repository's check ... The build seat ran the merge-check.sh in the change's head, so a branch older than the script, or one that gutted it, merged untested; and the media catalogue did not require mesh/repo-check at all. Located, fixed on branches, replayed as R310; the protection change awaits the operator.	2026-10-08 11:00:44 +02:00
mesh-admin	c0662f1171	Merge pull request 'Issue 312: no tool said a machine's disk load' (#195) from issues/312-no-tool-said-a-machines-disk-load into main	2026-10-08 08:55:40 +00:00
jochen	7839703b60	Issue 312: no tool said a machine's disk load, so issue 306 could not measure its disk	2026-10-08 10:48:44 +02:00
jochen	a3bedeb227	Issue 309: two order rules ordered one pair both ways; ADR 0249 gives them a precedence ... A group of the controller, the node-engine and the lab, each ready, was refused as a cycle: built by put the controller's member first, engine before controller the node-engine's. ADR 0249 ranks the rules (declared, then built by and version skew, then engine before controller) and supersedes ADR 0239's sentence that made a declared order against an inferred one a cycle; design 47 says the precedence. Resolved by mesh-controller #134 and mesh-catalog #119, replay R309 (mesh-lab #64).	2026-10-08 10:46:34 +02:00
mesh-admin	47aaae98b1	Merge pull request 'Issue 311: the media catalogue's check ran no tests for its TypeScript modules' (#193) from issues/311-the-media-catalogues-modules-ran-no-tests into main	2026-10-08 08:46:10 +00:00
jochen	c67ceacccf	Issue 311: the media catalogue's check ran no tests for its TypeScript modules ... Its check declared only Go, so ten modules merged with nothing of their own run, and a Go module without tests would have passed too.	2026-10-08 10:41:31 +02:00
mesh-admin	fcb76ca29d	Merge pull request 'Issue 306: a check on the control node ran past its timeout' (#191) from issues/306-a-check-on-the-control-node-ran-past-its-timeout into main	2026-10-08 08:34:59 +00:00
mesh-admin	37e82fb9fc	Merge pull request 'Issues 307, 308: the lab's beds kept the bus and runtime the mesh had left; a lab unit test's verdict depended on the machine' (#192) from issues/307-308-the-labs-beds-and-a-host-dependent-test into main	2026-10-08 08:34:52 +00:00
mesh-admin	879b183268	Merge pull request 'Issue 305: a recheck left the old verdict standing' (#190) from issues/305-a-recheck-left-the-old-verdict-standing into main	2026-10-08 08:34:30 +00:00
mesh-admin	57b24738f3	Merge pull request 'Issue 146: the enrolment-time consumer is answered by issue 208; design 08 names the join's code' (#189) from issues/146-the-enrolment-consumer-and-the-tunnel-join into main	2026-10-08 08:24:28 +00:00
jochen	9c030a714a	Issues 307, 308: the lab's beds kept the bus and runtime the mesh had left; a unit test's verdict depended on the machine ... Registered so the lab's state on 2026-10-08 is answered where the mesh's faults are, not only in a pull request.	2026-10-08 10:23:34 +02:00
jochen	db0fea6067	Issue 306: a check on the control node ran past its timeout ... Store-bound packages ran five to seven times slower there while the rest ran alike: the throwaway store flushes to a disk the mesh's own data keeps busy. And a holder recreated mid-check left its store and bus running.	2026-10-08 10:21:49 +02:00
jochen	573a44a33d	Issue 305: a recheck must put the merge check back to pending, or the old verdict merges	2026-10-08 10:12:52 +02:00
mesh-admin	0abca926ea	Merge pull request 'ADR 0217, to-be 44: no change to a machine takes effect unseen' (#97) from feat/no-change-takes-effect-unseen into main	2026-10-08 00:06:01 +00:00
mesh-admin	af398aef7b	Merge pull request 'Issues 303, 304; 240 resolved, 242 located' (#94) from issues/245-246 into main	2026-10-07 23:55:47 +00:00
jochen	43bffdc0c3	Issue 146: the enrolment-time consumer is answered by issue 208's assertion; design 08 names the join's code ... The branch building ADR 0169 carried a fix making a node's declaration consumer as it enrols. The controller already asserts every node's consumer before each send, and the self-check's healer asserts a missing one again, so the fix is dropped rather than merged and the record says why. The installer now places the bus's accounts at genesis.	2026-10-08 01:53:07 +02:00
jochen	e3caa4e1d4	ADR 0217, to-be 44: no change to a machine takes effect unseen ... Two incidents in two days had one shape: a change took effect that nobody saw first (issues 241 and 304). Three guards where the change is made — a settings layer read before it is replaced, a push that says what it will change, a running module's data move acknowledged — each silent when nothing is at stake. Accepted by the operator on 2026-10-08. To-be 44 is in progress in mesh-controller (feat/no-change-takes-effect-unseen), migration 0078, fitted onto what the controller does since: a whole-mesh push that says so and leaves a machine waiting for a gate, a person's push that says what it recreates (ADR 0242), a named push's cascade. The decision index is generated (ADR 0248), so no line is added to its README.	2026-10-08 01:45:49 +02:00
jschoubben	67599df951	Issues 303, 304; 240 resolved, 242 located ... 303: a media server's previews were reached through a link its container never mounted — fixed by mounting them. 304: settings set replaces the whole layer with nothing to read it first and no history. 240 is fixed by mesh-controller#47; 242 has backups running and records what the rollout taught. (First opened as 245 and 246; main has since taken both numbers, and 302 was the last.)	2026-10-08 01:45:39 +02:00
mesh-admin	08a874b55f	Merge pull request 'Triage issues 279-298: resolve the fixed, with replays R292 and R298' (#188) from issues/triage-279-298 into main	2026-10-07 23:41:52 +00:00
mesh-admin	78fd323df3	Merge pull request 'Triage issues 228-278: close the fixed, re-check the rest' (#187) from issues/triage-228-278 into main	2026-10-07 23:41:48 +00:00
mesh-admin	ed24d950db	Merge pull request 'Issues 092–208 triaged on 2026-10-08: 13 resolved, 1 wontfix, the rest re-checked' (#186) from issues/triage-092-208 into main	2026-10-07 23:41:45 +00:00
jochen	64e97d0de1	Triage issues 279-298: resolve the fixed with replays R292 and R298 ... 292 and 298 resolve with replays now registered in mesh-lab. The other fixed core issues say why no replay can be laid over the commit before their fix. The rest are re-checked against main.	2026-10-08 01:31:13 +02:00
jochen	2d18fa3380	Triage issues 228-278: close the fixed, re-check the rest ... Each issue is resolved with its fix and a replay or the reason none exists, or re-checked against main and the live mesh on 2026-10-08.	2026-10-08 01:31:10 +02:00
jochen	623fccee23	Triage issues 092-208: close the fixed and the obsolete, re-check the rest ... The operator asked on 2026-10-08 for the deprecated issues to be gone. In hq an issue is closed, never deleted, so each one is resolved with its fix, closed wontfix with a reason, or re-checked against main and the live mesh.	2026-10-08 01:31:06 +02:00
mesh-admin	990414c9b8	Merge pull request 'Ignore Python's cache folder' (#185) from chore/ignore-python-cache into main	2026-10-07 23:05:54 +00:00
jochen	5d4e427117	Ignore Python's cache: running the checks wrote it, and one file had been committed by mistake	2026-10-08 01:04:03 +02:00
mesh-admin	c6ff3b65b6	Merge pull request 'Issues 301, 302: a push of recorded builds is no repair; the lab's Go replays are checked in Go' (#184) from issues/301-302-a-push-of-recorded-builds-and-the-labs-go into main	2026-10-07 22:26:27 +00:00
jochen	7fde8f4bbe	Issues 301 and 302: a push of recorded builds is no repair, and the lab's Go is checked in Go ... 301: S15 counted the operator's pushes of recorded builds, the word ADR 0242 asks for, as repairs and wanted a healer for three causes. 302: the lab's replays register was never compiled before a merge, because its check ran in the TypeScript toolchain. To-be 45 §7 and §9 say how each is now decided and checked.	2026-10-08 00:17:14 +02:00
mesh-admin	69ab2fd7f7	Merge pull request 'Issues 296, 299, 300: resolved, each with its replay' (#183) from issues/296-299-300-resolved into main	2026-10-07 21:55:20 +00:00
jochen	787f428e7e	Issues 296, 299, 300: resolved, each with its replay proved to fail before its fix	2026-10-07 23:44:47 +02:00
mesh-admin	ded2173308	Merge pull request 'ADR 0248: the decision index is generated when it is read, and never stored (issue 297)' (#182) from decision/generated-decisions-index into main	2026-10-07 21:44:14 +00:00
jochen	f4a76ca291	Issue 297: resolved by hq PR #182 and mesh-catalog PR #115	2026-10-07 23:39:30 +02:00
jochen	55637ecb95	ADR 0248: the decision index is generated when it is read, so two open decisions no longer conflict	2026-10-07 23:38:34 +02:00
mesh-admin	eb54474519	Merge pull request 'Issue 300: a new module is not built at its merge' (#181) from issues/300-a-new-module-is-not-built-at-its-merge into main	2026-10-07 21:01:41 +00:00
mesh-admin	2adbfed90f	Merge pull request 'Issue 299: an optional verb makes a holder look silent' (#180) from issues/299-an-optional-verb-makes-a-holder-look-silent into main	2026-10-07 21:01:34 +00:00
jochen	aaaef91b7b	Issue 300: say delivery plan, the glossary's word	2026-10-07 22:40:17 +02:00
jochen	9b573f4ca0	Issue 300: a new module is not built at its merge ... The change plan said a merge adding a module builds it; the merge built nothing, so the module stayed unregistered until a hand build.	2026-10-07 22:39:56 +02:00
jochen	6006754172	Issue 299: an optional verb makes a holder look silent ... D3 raised node-uplink silent on every machine once the seat gained verbs its holders are not yet required to serve, against ADR 0246's step 1.	2026-10-07 22:29:04 +02:00
mesh-admin	dda850863f	Merge pull request 'ADR 0247: a machine with a VPN client routes names by domain, through a resolver of its own' (#179) from decision/0247-split-dns-on-a-machine-with-a-vpn-client into main	2026-10-07 19:46:08 +00:00
jochen	6373ca815b	ADR 0247: say exactly where the VPN's domains go and do not	2026-10-07 21:35:40 +02:00
jochen	7e9d0dfe7b	ADR 0247: say what is to confirm live about resolved and the resolver file, not a guess	2026-10-07 21:35:21 +02:00