nvrl d53ba1be21 test(fuse): add an in-memory FakeDrive with Drive's known faults ...

The first half of the simulation harness in docs/MILESTONE-3.0.0.md
section 8.1. FakeDrive is one shared server; each simulated daemon reaches
it through a FakeClient that implements DriveApi and carries its own link
state, latency, faults and an SDK-style entity cache.

The faults are the ones the account runs met: listings that lag (B118,
B48), renames and moves refused for a stale name hash because the cache
is only emptied by events (B111, B121), names that refuse a replace (B13,
B104, B106), events delayed, duplicated, reordered and echoed (B70, B105),
requests that stall, fail, or change Drive and lose their reply (B107,
B121), and non-uniform block sizes (B84, B85, B87).

Test-only; no behaviour change.

2026-10-03 04:51:35 +02:00

..

src

test(fuse): add an in-memory FakeDrive with Drive's known faults

2026-10-03 04:51:35 +02:00

Cargo.toml

refactor(fuse): reach Drive through a DriveApi trait

2026-10-03 04:37:37 +02:00