Design 47 H: H-A-348, a new node-engine's first pass restarts the tool runner for an unchanged secret
This commit is contained in:
@@ -2159,3 +2159,12 @@ Where two preparers disagreed, the chosen one is named.
|
||||
"installed last" fallback of ADR 0533 §3 stands for a build, and writes one journal line naming the toolchain it
|
||||
took and the lock it stood in for, so the next such stand-in is readable (H2, the Node build module). P3,
|
||||
P-failure-loud, nothing-moved-in-five-minutes (make it visible).
|
||||
- **H-A-348 (a new node-engine's first pass restarts the tool runner for a secret that did not change, 22:27)** The
|
||||
engine of main.157 started on all four nodes at 22:24-22:26 and each first pass restarted the tool runner "because
|
||||
claude-code.secret-gitea-read changed", the same words as the first pass of main.151's engine at 21:52; the mesh
|
||||
MCP server dropped for a minute each time. The secret did not change: the new engine judges "changed" against what
|
||||
it remembers of the secret's value, and a fresh engine remembers nothing. Owed, H2b, the node-engine: the judgement
|
||||
of a secret's change reads what the running unit holds (its rendered environment or a digest kept beside the unit),
|
||||
never only the engine's memory, so an engine's own delivery restarts nothing whose inputs are the same. Its test:
|
||||
two engines in a row over one bus, the second's first pass restarts no runtime. P3, P-failure-loud (a restart with
|
||||
a false why is a lie of its own), fix-a-bug-met-twice (second engine delivery, same line).
|
||||
|
||||
Reference in New Issue
Block a user