jochen
9d5ddcd050
Name no node: the forge owner in claude-code's, mesh-config's, mesh-issues's, messenger's and records's test data becomes acme (issue 1838)
2026-10-22 22:18:58 +02:00
jochen
30e6435dea
Name no node in claude-code's fixtures (issue 1838)
2026-10-22 21:55:50 +02:00
jochen
ba3635307c
Merge branch 'feat/modules-name-no-node' into bulk-c
2026-10-22 21:48:45 +02:00
jochen
c88b75a822
Name no node in mesh-issues's fixtures (issue 1838)
2026-10-22 21:48:39 +02:00
jochen
bd5bf861f1
Merge feat/modules-name-no-node into bulk-b
2026-10-22 21:44:50 +02:00
jochen
c55e705357
Name no node in postgres's, ssh-client's and mesh-mail-web's fixtures (issue 1838)
2026-10-22 21:44:44 +02:00
jochen
d4e9f699d1
Merge feat/modules-name-no-node into bulk-a
2026-10-22 21:44:29 +02:00
jochen
c09b7c0513
Name no node in dnsmasq's, mesh-mail-reader's and influxdb's fixtures (issue 1838)
2026-10-22 21:44:22 +02:00
jochen
0a398579e2
Name no node in betterbird's fixtures (issue 1838)
2026-10-22 21:44:21 +02:00
jochen
219c6b1a47
Merge branch 'feat/modules-name-no-node' into bulk-c
2026-10-22 21:43:10 +02:00
jochen
649865b7d2
Name no node in brother's and keycloak's fixtures (issue 1838)
2026-10-22 21:43:05 +02:00
jochen
098a0f6542
Merge feat/modules-name-no-node into bulk-b
2026-10-22 21:42:52 +02:00
jochen
4b50f5171b
Name no node in minio's and mailu's fixtures (issue 1838)
2026-10-22 21:42:46 +02:00
jochen
a8e62b52fd
Merge feat/modules-name-no-node into bulk-a
2026-10-22 21:42:43 +02:00
jochen
653eb10d41
Name no node in mesh-provisioner's and home-assistant's fixtures (issue 1838)
2026-10-22 21:42:37 +02:00
jochen
afc919e47e
Merge branch 'feat/modules-name-no-node' into bulk-c
2026-10-22 21:40:25 +02:00
jochen
8d92433f20
Name no node in restic's and mosquitto's fixtures (issue 1838)
2026-10-22 21:40:20 +02:00
jochen
3209cfa6fb
Merge feat/modules-name-no-node into bulk-b
2026-10-22 21:39:02 +02:00
jochen
4d017422dc
Merge feat/modules-name-no-node into bulk-a
2026-10-22 21:38:51 +02:00
jochen
5c138c693f
Merge feat/modules-name-no-node into bulk-b
2026-10-22 21:38:51 +02:00
jochen
04a85108e5
Name no node in mesh-mail's fixtures (issue 1838)
2026-10-22 21:38:44 +02:00
jochen
389630265b
Name no node in mesh-config's fixtures (issue 1838)
2026-10-22 21:38:43 +02:00
jochen
4847c96b58
Merge branch 'feat/modules-name-no-node' into bulk-c
2026-10-22 21:38:21 +02:00
jochen
161abbc621
Name no node in xterm's, xorg's, mesh-catalog's, lemurs's, fail2ban's, docker's, bluetooth's and adwaita's fixtures (issue 1838)
2026-10-22 21:38:16 +02:00
jochen
de31c6a9d1
Merge feat/modules-name-no-node into bulk-b
2026-10-22 21:36:33 +02:00
jochen
4909c9c8c7
Name no node in mesh-knowledge's fixtures (issue 1838)
2026-10-22 21:36:26 +02:00
jochen
171148a59f
Merge branch 'feat/modules-name-no-node' into ground-1838
2026-10-22 21:35:25 +02:00
jochen
1db1965073
Name no node in claude-code's, messenger's, nats's and brother's help texts, comments and README (issue 1838)
...
Their examples named this mesh's machines; they name neutral ones now (1838/AC3). The sealed box's info
string and the route-adapter's marker name the software, not a node, and stay: changing either would
break what is already sealed or written.
2026-10-22 21:35:23 +02:00
jochen
120c38427c
Merge branch 'feat/modules-name-no-node' into bulk-c
2026-10-22 21:34:55 +02:00
jochen
e7112ad575
Name no node in sudo's fixtures (issue 1838)
2026-10-22 21:34:50 +02:00
jochen
1758a2cb4e
Merge feat/modules-name-no-node into bulk-a
2026-10-22 21:34:10 +02:00
jochen
87144173a0
Name no node in mesh-provisioner-client's fixtures (issue 1838)
2026-10-22 21:34:03 +02:00
jochen
14a5c1c80a
Name no node in mesh-mail-notifier's and memory-pressure's fixtures (issue 1838)
2026-10-22 21:33:42 +02:00
jochen
1267c74fec
Merge branch 'feat/modules-name-no-node' into bulk-c
2026-10-22 21:32:55 +02:00
jochen
f7971f0f4b
Name no node in slack's, blueman's and only-office's fixtures (issue 1838)
2026-10-22 21:32:46 +02:00
jochen
dd074ecb18
lab: take the forge's owner as a required config value, and name no node in its fixtures (issue 1838)
...
The lab cloned and installed from the owner this mesh's repositories are under, written in its code; another
mesh's forge holds them under its own (1838/AC4). Unset, lab_check, lab_run and a rebuild say so. Fixtures
name neutral machines and an example owner.
2026-10-22 21:32:30 +02:00
jochen
7c4891cd13
Merge feat/modules-name-no-node into bulk-b
2026-10-22 21:31:58 +02:00
jochen
dfb9336ced
Merge branch 'feat/modules-name-no-node' into bulk-c
2026-10-22 21:31:16 +02:00
jochen
6a0e08bec1
Merge feat/modules-name-no-node into bulk-b
2026-10-22 21:31:14 +02:00
jochen
7ad9e531d4
Name no node in cups's, nats's, mesh-watcher's, mesh-files's, dunst's and desk-channel's fixtures (issue 1838)
2026-10-22 21:31:08 +02:00
jochen
5db896c813
Name no node in mesh-vault's fixtures (issue 1838)
2026-10-22 21:31:02 +02:00
jochen
e54bca6575
Merge feat/modules-name-no-node into bulk-a
2026-10-22 21:29:48 +02:00
jochen
dbe28dceba
Merge feat/modules-name-no-node into bulk-a
2026-10-22 21:29:03 +02:00
jochen
39d724fd77
Name no node in route-adapter's, rofi's, claude-licence-manager's and nextcloud-client's fixtures (issue 1838)
2026-10-22 21:29:02 +02:00
jochen
3b89d398fa
Name no node in messenger's fixtures (issue 1838)
2026-10-22 21:28:54 +02:00
jochen
0c98e627c2
Merge branch 'feat/modules-name-no-node' into bulk-c
2026-10-22 21:26:18 +02:00
jochen
d33e6baa73
Name no node in nodered's, netcheck's, telegram's and nfs-server's fixtures (issue 1838)
2026-10-22 21:26:05 +02:00
jochen
e7f1a99188
mesh-issues: make forge-owner a required value with no default naming this mesh (issue 1838)
...
The owner was a default and a Go fallback both saying this mesh's organisation; the description's
'empty asks no forge' was never true. Required, a mesh that sets no owner fails to compose instead of
asking a forge under another mesh's name; unset, each asking says so (1838/AC4). Help texts' examples
name neutral machines.
2026-10-22 21:24:44 +02:00
mesh-tools
2f05e70734
Merge pull request 'Upgrade the nodes one at a time on the bus, with a package record, a kernel hold, an after-upgrade check, a rollback and a fallback kernel (upgrade safety, issues 1840 and 1841)' ( #450 ) from feat/upgrade-safety into main
2026-10-22 18:34:15 +00:00
jschoubben
3cce15fa81
restic: let the thinning wait up to ten minutes for a held repository lock (issue 620)
...
mesh/merge-gate head 3cce15fa811e merged into trunk 835bf22b7d40 — pass: builds restic → ace, g14, novox, shanks; no bus step; every machine composes with …
mesh/repo-check head 3cce15fa811e merged into trunk 835bf22b7d40 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
mesh/check failed: unit: modules/gitea.test: [gitea] where the poll of merges last looked from could not be read, so none is kept — no runtime | 3cce1…
A restic outside the night's lock, such as a listing while a delivery plan backs up
data modules before their moves, held the lock 246 ms before the thinning asked for it,
and the thinning failed at once, raising an urgent condition for a timing collision.
restic's --retry-lock now waits up to ten minutes on both of the thinning's forgets;
past that it fails with restic's words as before.
2026-10-22 18:30:16 +02:00