From d7c97d02fa17483ce238fd14131059ab352e4192 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 9 Oct 2026 12:56:54 +0200 Subject: [PATCH] Issue 344: name the node-engine's repository as code --- .../00-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04-ISSUES/344-known-gaps-in-the-agents-boundary-accepted-for-now/00-report.md b/04-ISSUES/344-known-gaps-in-the-agents-boundary-accepted-for-now/00-report.md index 6c921f8d..66cecfd6 100644 --- a/04-ISSUES/344-known-gaps-in-the-agents-boundary-accepted-for-now/00-report.md +++ b/04-ISSUES/344-known-gaps-in-the-agents-boundary-accepted-for-now/00-report.md @@ -63,7 +63,7 @@ note. Each gap says what is open, why it matters, and what would close it. *Closes with:* the router's state in a bucket only the router may write. 9. **On a large data pool the root search may never finish.** The node-engine's search for programs that run as - root now has one bound of fifteen minutes (mesh-host #61; the inner two-minute limit is gone). On a machine with + root now has one bound of fifteen minutes (`mesh-host` #61; the inner two-minute limit is gone). On a machine with a very large data pool the walk can still run past it, and the verdict then stays "not judged". That is loud, not silent. *Closes with:* setuid turned off on the data datasets, so the walk skips them.