job_queue: drop insert_unless_live, accept extra queue passes
mara chose to accept extra queued sweep passes over adding a new hive-jobq primitive (or a hive-c0re one-off) for "don't queue another of this kind". Every sweep caller now plain-inserts its node; the capacity-1 Dep::Resource per sweep kind (MatrixSweep/KnowledgeTree) still keeps two passes of the same kind from running concurrently, it just no longer collapses a tick that lands while one is live or queued into the existing one.
This commit is contained in:
parent
1d4c77d2c8
commit
313d582c01
6 changed files with 37 additions and 90 deletions
|
|
@ -69,11 +69,10 @@ pull`, so agents see the new content on their next turn.
|
|||
|
||||
Both paths, and the one pull at boot, queue the same `KnowledgePull` job
|
||||
node. It holds the working tree for its duration, so two pulls never run
|
||||
over each other. An event that arrives while a pull is waiting to start
|
||||
folds into it; one that arrives while a pull is running queues one more
|
||||
behind it, since the running pull may have fetched before the push. The
|
||||
node runs `knowledge::pull()`, which also handles the change notice
|
||||
below.
|
||||
over each other — each trigger queues its own pass, and a pass that lands
|
||||
while another is already queued or running simply waits its turn, since the
|
||||
one ahead of it may have fetched before the push. The node runs
|
||||
`knowledge::pull()`, which also handles the change notice below.
|
||||
|
||||
### Change notice
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue