Fill a module again when a node-engine returns after any failed fill, not only a missing socket (issue 1873)

+42 -5

2 Commits

Author	SHA1	Message	Date
jschoubben	16331cdfdc	Fill a module again when the node-engine's socket returns after any failed fill, not only one for want of the socket (issue 1873) mesh/merge-gate head 16331cdfdce6 merged into trunk 66c404fd39a5 — pass: builds mesh-provisioner-client → ace, g14, novox, shanks; no bus step; every machi… Details mesh/repo-check head 16331cdfdce6 merged into trunk 66c404fd39a5 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-… Details mesh/check failed: mesh-build-go: no go build node qualifies: builders disagree: go1.27.1-X:nodwarf5 recipe 74744709d277ded9 on g14; go1.27.3-X:nodwar… mesh/delivery delivered Details On ace postgres's fill of superuser.secret failed at 22:12 with the engine's own "is a directory", what a container runtime had left at the path. The engine delivered at 22:42 clears such a directory, but the client tried again only modules whose fill had failed for want of the socket (issue 1165), so postgres was never filled again and its old failure was said every 30 s. A newer engine may write what the older could not: any failed fill is now tried again when a node-engine makes its socket again.	2026-10-22 22:56:16 +02:00
jschoubben	ab3722d3b3	Test that a fill the node-engine failed is tried again when its socket returns (issue 1873)	2026-10-22 22:53:39 +02:00

Fill a module again when a node-engine returns after any failed fill, not only a missing socket (issue 1873) #455