novox/mesh-lab
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

A machine works through its queue, and the wait allows for it

Browse Source 
With caught-up finally an equality, the last red test turned out to be
telling the truth about something real: declarations queue, the machine
applies them one at a time at half a minute each, and by the twenty-
fifth test it is minutes behind the latest push. 240 seconds was not a
generous bound on one apply — it was an accidental bound on the whole
backlog.

Doubled rather than tuned, and the real remedy filed instead: a machine
asked to be five successive things should become the last one, which
is a decision about the link rather than about this timeout
(novox/hq 04-ISSUES/031).
This commit is contained in:
jschoubben
2026-09-02 01:05:51 +02:00
parent 81e5f31910
commit 01ca02ad04
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
test/integration/mesh.test.ts
+1 -1
View File
@@ -120,7 +120,7 @@ async function mesh(command: string, timeoutMs?: number): Promise<string> {
* to become right by being waited for, and a refusal read after two minutes of polling is the same * to become right by being waited for, and a refusal read after two minutes of polling is the same
* refusal, later. * refusal, later.
*/ */
async function settled(node: string, withinMs = 240_000): Promise<void> { async function settled(node: string, withinMs = 480_000): Promise<void> {
const until = Date.now() + withinMs; const until = Date.now() + withinMs;
let last = ""; let last = "";
while (Date.now() < until) { while (Date.now() < until) {