Files
Marcelo Machuca 20f5643657 fix(wal): return InvalidData for overlapping closed segments instead of panicking (#9341)
Overlapping closed WAL segments indicate on-disk inconsistency (e.g. a
partially-applied manual truncation or a file copy accident). The
contiguity check already returns InvalidData for gaps between segments;
the overlap branch was hitting unimplemented!(), crashing the process
on any WAL that has overlapping closed files.

Replace the unimplemented!() with an InvalidData error using the same
pattern as the gap branch. This lets callers handle corrupt-segment
state rather than receiving a panic.

Add a regression test that seeds a WAL with overlapping closed-* files
and asserts that with_options() returns ErrorKind::InvalidData.
2026-06-11 11:11:09 +02:00
..
2026-04-09 10:02:45 +02:00