The regression test read the WAL header from a second file handle while the
writer was still open, which fails on Windows ("another process has locked a
portion of the file"). Read the header size only after the writer is dropped,
and ramp payload sizes past the initial 64 KiB WAL region so growth is forced
deterministically instead of relying on wrap/checkpoint timing. Account for
chunked frames when asserting durability.
Docker Release / build-and-push (push) Has been cancelled
- #230: refresh cached_payload_end after WAL growth so rebuild_indexes no
longer seeks into the grown WAL region and overwrites record payloads
(was surfacing as "wal record checksum mismatch").
- #215: make TantivyEngine drop its TempDir last and release the index
writer first, so per-put working directories are cleaned up instead of
leaking into the system temp dir (notably on Windows).
- add commit_per_put_survives_wal_growth regression test.
Olow304