Repository navigation
[Node] Add: RepairSchedule trait abstracting repair-tick waits #87
Description
Summary
Add a RepairSchedule trait abstracting "wait for the next repair tick," with a production tokio::time::interval-backed implementation and a test implementation driven by an explicit, manually-fired gate.
Details
Algorithm context: docs/protocol/concurrent-insert.md, Section 6.4.
Files
src/node/base_node.rs(or a new sibling module, implementer's choice) — the trait and both implementations.
Acceptance Criteria
- No literal
tokio::time::sleep/intervalcall anywhere outside the production implementation. - The test implementation lets a test trigger exactly one tick deterministically and await its completion under a bounded timeout — zero wall-clock waiting, matching this crate's
join_with_timeout/join_all_with_timeoutpattern.
Dependencies
None.
Resolved by PR #126.
Dependency graph (unblocked first):
EPIC #81 -- local search & join protocol
#67 [DONE] search_by_id #71 [OPEN] search_by_mem_vec (independent)
#74 [OPEN] search_by_id timeout fix #76 [OPEN] delete/leave
Concurrent join + repair (Algorithm 2 + Algorithm 8; supersedes closed #66, #77):
L0 (no deps): #84 #85 #93 #86 #87 <-- YOU ARE HERE
L1: #94 #88 #89
L2: #90 #91 #95 #96
L2.5 (link round-trip follow-ups; #146 blocks #92): #145 #146
L2.5 (stage-1 concurrent-join fix; blocked by #90, blocks #97): #148
L3: #92
L4 (acceptance gate): #97
L5 (post-gate cleanup; also blocked by #76): #100
Test-suite cleanup, blocked by #90:
#147
Test infrastructure, mock network hub (#62's latency simulation builds on #149's queue):
#149 (blocked by #90, blocks nothing)
#62 (no blocker)
Metadata
Metadata
Assignees
Labels
No labels
Activity