novox/mesh-catalog
18
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

mesh-provisioner-client: retry a refused write on the node-engine's wake and ask the vault again at once (issue 924) #482

Merged
mesh-tools merged 1 commits from fix/provisioner-retries-on-declaration into main 2026-10-25 21:08:48 +00:00
Conversation 1 Commits 1 Files Changed 4
+121 -7
1 Commits
Author SHA1 Message Date
jschoubben d0566f9ade Fill a refused file again once the node-engine's declaration may let it through (ace, 2026-10-25 21:17)
mesh/delivery merged: source.main moved to novox/mesh-catalog@573a59e3cc07
Details
mesh/delivery-group group fix/provisioner-retries-on-declaration merged: every member is merged
Details
mesh/check pass d0566f9ade9a on 573a59e3cc07 | unit 2301 run, 3410 kept, 10 skipped | integration 2326 run, 3431 kept, 13 skipped | over bound: unit, … 
The node-engine refused mesh-build-go's files as not named as filled 32 s before
its want arrived, and nothing filled them after the apply that named them: the
runtime crash-looped on its missing broker credential. The client now fills
every module again when the node-engine touches its write socket after such an
apply (mesh-host fix/provisioner-retries-on-declaration), says each retry and
each refusal it waits on, and asks the vault again at once for a refused secret
when that wake or the module's own assignment may have ended the refusal.
 2026-10-25 21:42:34 +01:00