Pin the node-engine at its pull request's resumable walk (hq issue 361)

2026-10-10 01:01:18 +02:00
parent eaf5195998
commit cdaba36eca
4 changed files with 7 additions and 6 deletions
@@ -13,7 +13,8 @@
 // **And why no bound on one search.** On a machine with millions of files the walk takes longer than any bound
 // worth stating (the control-node's did not finish in fifteen minutes, issue 361), and a search ended early
 // judges nothing, so a bound made such a machine never judged. The search runs to its end at idle priority,
-// once at a time; an incomplete search is never "free".
+// once at a time, keeping how far its walk got every minute so an engine restarted midway carries it on; an
+// incomplete search is never "free". A walk resumed more than FreshFor after it started is begun again.
 package rootsearch

 import "time"