The node-engine wakes the provisioner when an apply lets a file it refused be written (issue 924) #142

Merged

mesh-tools merged 2 commits from fix/provisioner-retries-on-declaration into main 2026-10-25 21:08:52 +00:00

Conversation 1 Commits 2 Files Changed 6

+307 -5

2 Commits

Author	SHA1	Message	Date
jschoubben	338797a527	Knock under the apply's lock, and read what is owed first (review of this fix) ... A write judged by the declaration before the apply settled could record its refusal just after Knock found nothing owed: the original fault in a small window. Knock now holds the apply's lock as a write does, reads no declaration while nothing is owed, and its comment names Settled as its caller.	2026-10-25 21:49:23 +01:00
jschoubben	2c93f79429	Tell the provisioner's client to fill again once a settled apply may let through a write the filling refused (ace, 2026-10-25 21:17) ... ace's filling refused mesh-build-go's files as not named as filled 32 s before its want arrived; after the apply that named them nothing asked again, and the runtime crash-looped on its missing broker credential. The filling now keeps what it refused or failed and, when the node agent says a module's apply or removal settled (agent.Env.Settled, called once what runs holds it), touches its write socket if the declaration now names such a path, names the provisioner's account, or a write had failed; the client watches that socket and fills every module again. Said in the journal each time.	2026-10-25 21:42:41 +01:00