pauliyobo opened a new pull request, #3069: URL: https://github.com/apache/iggy/pull/3069
## Which issue does this PR close? Closes #3030 <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123. --> ## Rationale <!-- Why is this change needed? If the issue explains it well, a one-liner is fine. --> ## What changed? <!-- 2-4 sentences. Problem first (before), then solution (after). GOOD: "Messages were unavailable when background message_saver committed the journal and started async disk I/O before completion. Polling during this window found neither journal nor disk data. The fix freezes journal batches in the in-flight buffer before async persist." GOOD: "When many small messages accumulate in the journal, the flush passes thousands of IO vectors to writev(), exceeding IOV_MAX (1024 on Linux)." BAD: - Walls of text - "This PR adds..." (we can see the diff) --> When `write_contexts()` or `write_active_context()` are called, they directly attempt to write the file without ensuring that the iggy home directory exists. This causes issues like #3030 To fix this, `ensure_iggy_home()` is called in both methods prior to file creation. ## Local Execution Passed, and precommit ran <!-- You must run your code locally before submitting. "Relying on CI" is not acceptable - PRs from authors who haven't run the code will be closed. Did you have `prek` installed? It runs automatically on commit and covers all project languages. See [CONTRIBUTING.md](https://github.com/apache/iggy/blob/master/CONTRIBUTING.md). --> PS: I had to add writeable to the typos toml configuration since it would kep being flagged. Not sure if this could cause issues when a genuine spelling mistake happens. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
