Files
Yash Singh 7ba04344b0 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-08-12 14:28:04 +02:00
..