The controller takes mesh-sdk a7a1fbd3, so its composer gives build modules the node's CPU share (issue 1806, ADR 0553/0554 change B) #473

Merged

mesh-tools merged 1 commits from fix/controller-sdk-cpu-share into main

2026-10-26 15:41:03 +00:00

Author	SHA1	Message	Date
jschoubben	9ad8715871	Bump mesh-sdk to a7a1fbd3 so the build seats' runtimes are composed to yield (issue 1806) mesh/delivery merged: source.main moved to novox/mesh-controller@2ecfbb3a29cb Details mesh/check pass 9ad8715871ea on 2ecfbb3a29cb \| carried from e1a55f099b4e \| unit 1023 run, 171 kept, 2 skipped \| integration 1701 run, 214 kept, 9 skip… The controller is the only composer, and its pin (10b6e202) predates mesh-sdk #95: without the bump the build runtimes never get yields {priority idle, cpu-share} or MESH_BUILD_CPU_SHARE (ADR 0553, ADR 0554, change B). The operator said yes to this one change of the frozen controller on 2026-10-26 15:54. A composition at both pins over every node's assignment differs only in mesh-build-go, mesh-build-node and mesh-build-image (the yields and the share word); every other composition is byte-identical. The SDK's conformance capture moves with the pin, as testdata/beside/CAPTURED asks. Research 072 (the controller, NATS-native): no piece moved; a pin bump the operator allowed.	2026-10-26 16:34:55 +01:00

Author

SHA1

Message

Date

jschoubben

9ad8715871

Bump mesh-sdk to a7a1fbd3 so the build seats' runtimes are composed to yield (issue 1806)

mesh/delivery merged: source.main moved to novox/mesh-controller@2ecfbb3a29cb

Details

mesh/check pass 9ad8715871ea on 2ecfbb3a29cb | carried from e1a55f099b4e | unit 1023 run, 171 kept, 2 skipped | integration 1701 run, 214 kept, 9 skip…

The controller is the only composer, and its pin (10b6e202) predates mesh-sdk #95: without the bump the
build runtimes never get yields {priority idle, cpu-share} or MESH_BUILD_CPU_SHARE (ADR 0553, ADR 0554,
change B). The operator said yes to this one change of the frozen controller on 2026-10-26 15:54.

A composition at both pins over every node's assignment differs only in mesh-build-go, mesh-build-node and
mesh-build-image (the yields and the share word); every other composition is byte-identical. The SDK's
conformance capture moves with the pin, as testdata/beside/CAPTURED asks.

Research 072 (the controller, NATS-native): no piece moved; a pin bump the operator allowed.

2026-10-26 16:34:55 +01:00