Repository navigation
fix: preserve atomic cache snapshots and bound feed inputs - #53
Merged
Merged
Conversation
This was referenced Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Concurrent cache writes could mix bodies with validators, malformed HTTP 200 responses could evict a usable feed, and large durations could panic. Publish metadata and body in one atomic record, preserve valid cached feeds and unrelated files, and use checked duration arithmetic.
Enforce a 16 MiB decoded-body limit during HTTP reads (including gzip and chunked responses), cache reads/writes, and direct parsing. Existing cache pairs remain readable; older binaries cannot read newly written atomic records.
Validation: formatting, clippy with warnings denied, the full test suite (292 tests), and release build. Regressions cover concurrent writers, malformed replacement, legacy cache upgrades, cache clearing, oversized bodies, and duration overflow.
Stack position: 1 of 4; targets main. Merge the stack in order. Consolidated documentation is in the final PR.
Merge order: #53 → #54 → #55 → #56.