mesh-delivery

Files

T

jschoubben 30ec4329e0 The assigner's integration tests place their modules and name the node's own composition; a placed node's backup answer stays in its want

The integration tests put placement (not assignments) and the node's own composition (not the controller's) on the bus; the
three that tested the controller's judgements of a move (waiting for a composition, a record move, a user-list revision) go,
their unit counterparts standing. Run locally against the embedded bus, all of this module's integration tests pass.
Found by them: the answer to a failed backup was dropped from a placed node's want at every pass, because the carry-over
compared the want's digest, which a placed node's want does not carry; fixed in wants.go, with a case in the existing unit test.
Tests: three integration tests deleted, none added; one case added to an existing unit test.

(issue 774, 774/S26, 774/S27)
Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

2026-11-02 00:30:51 +01:00

asks_test.go

The assigner reads no assignment and no lease: the placement alone names where modules run (ADR 0567 §8, ADR 0549 §5)

2026-11-02 00:18:50 +01:00

asks.go

A version healthy on another node is not held for one node's failed health check (ADR 0557, issue 1496)

2026-10-26 22:06:32 +01:00

compose_test.go

Move the judge's rules and their tests from mesh-sdk into the indexer's judge (ADR 0578 §4)

2026-11-01 02:34:26 +01:00

compose.go

Let the assigner decode manifests and take the indexer's verdicts, never judging (ADR 0578 §3, §5, §6)