novox/mesh-host
18
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

The node-engine retries an apply that met a passing bus error, so a reload does not leave a module failed (issue 1945) #144

Merged
mesh-tools merged 1 commits from fix/apply-retries-transient into main 2026-10-25 22:42:41 +00:00
Conversation 1 Commits 1 Files Changed 9
+390 -57
1 Commits
Author SHA1 Message Date
jschoubben 99285cb080 Retry an apply, a fetch by digest and a have write that met the bus reloading, and keep the cause in the have
mesh/delivery merged: source.main moved to novox/mesh-host@1195cf45971e
Details
mesh/check pass 99285cb080db on 1195cf45971e | unit 303 run, 1080 kept, 5 skipped | integration 306 run, 1082 kept, 4 skipped | over bound: unit (slow… 
The bus node's engine writes the bus user list (ADR 0547 bridge); each write makes the bus reload its accounts, and
for about three seconds every JetStream request meets no responders. An apply that failed then was kept failed until a
key changed (mesh-vault on novox, 2026-10-25 23:04:24), holding every module that needs the secret seat. A transient
bus failure is now retried with a backoff (2 s, 5 s, 15 s, 60 s, then every 5 min), the have saying retrying meanwhile;
after the engine writes the user list, the transiently failed modules are tried again once the reload is over. A have
write that met it is written again the same way. shorten keeps the head and the tail, the cause.
 2026-10-25 23:37:02 +01:00