Yash Singh c97e998d65 fix(sparse): use checked usize->u32 for compressed posting chunk offset (#9965) ...

CompressedPostingBuilder stored the running byte offset with 'data_size as u32', which silently truncates if a posting list's compressed id-data ever exceeds u32::MAX bytes, producing a wrong offset and corrupt reads. Use u32::try_from(..).expect(..) so it fails loudly, matching the guarded sibling in the posting_list crate.

2026-09-03 12:39:02 +02:00

..

benches

chore: bench_cache (#10028)

2026-08-04 11:18:44 +02:00

src

fix(sparse): use checked usize->u32 for compressed posting chunk offset (#9965)

2026-09-03 12:39:02 +02:00

Cargo.toml

chore(deps): drop dead dependencies in edge-path crates (#10109)

2026-09-03 12:36:31 +02:00