fix(posting): prevent stale cache hits when maxTs < readTs (#9597)#9614
Merged
matthewmcneely merged 1 commit intomainfrom Feb 27, 2026
Merged
Conversation
…lection; add unit test
github-actions
bot
added
area/testing
shiva-istari
approved these changes
Feb 27, 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
2 participants
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.
Description
When reading posting lists from the cache,
readFromCacheonly verified thatminTs <= readTs, but did not check thatmaxTs >= readTs. This allowed stale cache entries to be returned when newer data had been committed to disk but the cache hadn't been updated yet.Closes #9597
Checklist
Conventional Commits syntax, leading
with
fix:,feat:,chore:,ci:, etc.