fix(buffers): skip corrupted log segments (fixes #18336)

[erhudy]

Summary

This PR attempts to fix the issue described in #18336, where Vector will get stuck on corrupted log segments (e.g. if Vector crashed or was oomkilled in the middle of writing a segment).

Vector configuration

Should happen with any Vector configuration that is using disk buffers.

How did you test this PR?

The PR is split into two commits - the first commit adds only a test which can be run with RUST_BACKTRACE=1 cargo test -p vector-buffers reader_hangs_after_partial_write_beyond_last_acked_record. This test will fail when run against the current master branch. The second commit adds a proposed fix, with which the test now passes.

Change Type

• Bug fix
• New feature
• Dependencies
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

Notes

• Please read our Vector contributor resources.
• Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
• Some CI checks run only after we manually approve them.
  • We recommend adding a pre-push hook, please see this template.
  • Alternatively, we recommend running the following locally before pushing to the remote branch:
    • make fmt
    • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
    • make test
• After a review is requested, please avoid force pushes to help us review incrementally.
  • Feel free to push as many commits as you want. They will be squashed into one before merging.
  • For example, you can run git merge origin master and git push.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run make build-licenses to regenerate the license inventory and commit the changes (if any). More details on the dd-rust-license-tool.