novox/mesh-lab
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

The lab answers the installer's questions the unattended way

Browse Source 
The installer asks where a human must choose, and this bed has no human — so
every choice arrives as a flag, and a required choice with no flag is the
installer refusing, which is the behaviour rather than a lab problem.

Both choices have one option today, so the flags are redundant on purpose: the
day a second filter exists this bed keeps working instead of refusing, and
choosing becomes a thing it visibly does.

Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
This commit is contained in:
jschoubben
2026-09-15 21:57:26 +02:00
parent e451a9191a
commit 09a22de78f
5 changed files with 41 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
one-node-mesh-report.json
+12 -12
View File
@@ -7,7 +7,7 @@
"code": "R1",
"title": "a bare machine becomes a mesh of one, raised by the installer",
"status": "pass",
"seconds": 141,
"seconds": 122,
"why": ""
},
{
@@ -56,35 +56,35 @@
"code": "P1",
"title": "the mesh builds the shared base from source",
"status": "pass",
"seconds": 77,
"seconds": 85,
"why": ""
},
{
"code": "P2",
"title": "the mesh builds and runs a store of its own",
"status": "pass",
"seconds": 49,
"seconds": 38,
"why": ""
},
{
"code": "P3",
"title": "the mesh builds and runs its own catalogue",
"status": "pass",
"seconds": 26,
"seconds": 31,
"why": ""
},
{
"code": "P4",
"title": "the mesh rebuilds its own control plane from source",
"status": "pass",
"seconds": 33,
"seconds": 32,
"why": ""
},
{
"code": "N1",
"title": "the mesh puts itself on a private network, and its machine has a name",
"status": "pass",
"seconds": 12,
"seconds": 6,
"why": ""
},
{
@@ -98,14 +98,14 @@
"code": "U1",
"title": "the mesh builds a module standing on that base",
"status": "pass",
"seconds": 14,
"seconds": 13,
"why": ""
},
{
"code": "U2",
"title": "the mesh runs a broker for that module to talk to",
"status": "pass",
"seconds": 20,
"seconds": 24,
"why": ""
},
{
@@ -140,22 +140,22 @@
"code": "V4",
"title": "every resource the mesh declared is true on the machine",
"status": "pass",
"seconds": 12,
"seconds": 11,
"why": ""
},
{
"code": "E1",
"title": "a change to a module's source reaches the machine on its own",
"status": "pass",
"seconds": 14,
"seconds": 13,
"why": ""
},
{
"code": "E2",
"title": "the mesh comes back after the machine reboots",
"status": "fail",
"seconds": 30,
"why": "every container came back and no host agent did, so the machine is running the right things and can no longer be told anything:\namqp-ping\tUp 3 seconds\nmesh-lavinmq\tUp 3 seconds\nlavinmq\tUp 3 seconds (health: starting)\nmesh-control\tUp 3 seconds\nmesh-catalog\tUp 3 seconds\nmesh-postgres\tUp 3 seconds\npostgres\tUp 3 seconds\nmesh-builder\tUp 3 seconds\nmesh-registry\tUp 3 seconds\nmesh-broker\tUp 4 seconds (health: starting)\nmesh-store\tUp 4 seconds\n"
"seconds": 31,
"why": "every container came back and no host agent did, so the machine is running the right things and can no longer be told anything:\namqp-ping\tUp 3 seconds\nmesh-lavinmq\tUp 3 seconds\nlavinmq\tUp 4 seconds (health: starting)\nmesh-control\tUp 3 seconds\nmesh-catalog\tUp 1 second\nmesh-postgres\tUp 4 seconds\npostgres\tUp 3 seconds\nmesh-builder\tUp 2 seconds\nmesh-registry\tUp 3 seconds\nmesh-broker\tUp 3 seconds (health: starting)\nmesh-store\tUp 3 seconds\n"
}
]
}