A module that puts nothing on a machine cannot be assigned to one #22

2026-09-14T09:09:14Z

jschoubben commented

2026-09-14 09:09:14 +00:00

The image every module in the scripted toolchain is compiled on top of is registered as a module, so the mesh can build it, version it, and know what depends on it. It is not a module: it declares no resources, because nothing about it belongs on a machine. Its whole purpose is to be the starting point for other modules' builds.

Assigning it succeeded. The machine was then sent a declaration containing nothing of it, applied it, and reported success — so an operator had said "run this here" and the mesh had agreed to something it cannot do, with nothing anywhere saying otherwise.

Refused at the assignment, which is where somebody is standing. A module whose resources are worked out per node declares none here and stays assignable; it is asked about separately rather than caught by the same test.

The image every module in the scripted toolchain is compiled on top of is registered as a module, so the mesh can build it, version it, and know what depends on it. It is not a module: it declares no resources, because nothing about it belongs on a machine. Its whole purpose is to be the starting point for other modules' builds. Assigning it succeeded. The machine was then sent a declaration containing nothing of it, applied it, and reported success — so an operator had said "run this here" and the mesh had agreed to something it cannot do, with nothing anywhere saying otherwise. Refused at the assignment, which is where somebody is standing. A module whose resources are worked out per node declares none here and stays assignable; it is asked about separately rather than caught by the same test.

jschoubben added 1 commit 2026-09-14 09:09:15 +00:00

A module that puts nothing on a machine cannot be assigned to one 95a9da8bdb

The image every module in the scripted toolchain is compiled on top of is
registered as a module so the mesh can build, version and depend on it. It is
not one: nothing about it belongs on a machine. Assigning it succeeded, the
machine was sent a declaration containing nothing of it, and everything
reported success — the operator had said run this here and the mesh had agreed
to something it cannot do.

A module whose resources are worked out per node is asked about separately, so
it stays assignable, which is the point of it.

jschoubben merged commit 260447282e into main

2026-09-14 09:09:21 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#22