You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cache: restart leaves prior objects uncharged and unreachable #95
Found by a memory-accounting audit of 8b3c813. The tests are on branch audit/memory-tests and fail on main today; check out that branch to run them. File and line links point at that commit.
What goes wrong. The builders mount a fixed liquid_cache.t4 path with no truncation or reconciliation (src/datafusion-local/src/lib.rs:196, src/datafusion-server/src/service.rs:61). On a persistent directory, t4 replays every earlier object as live, but the new cache's index is empty and its budget starts at 0.
Evidence.
1,000 objects (4.1 MB of file) survived a remount with 0 bytes charged, and the new cache served 0 of 1,000 gets.
In the second test: 8 objects, 0 indexed, 0 charged.
cargo +1.96.0 test -p liquid-cache --lib audit_cache_rebuilt_over_an_existing_file_accounts_for_its_objects -- --nocapture
Flags: P probabilistic (a pass after a fix only means the race wasn't hit), F interleaving forced by a test hook, L Linux only, D needs Docker, M measurement only, C control (passes by design).
Activity