-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix: HierarchicalSessionStore stale cache could wipe session messages #1781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
86ca1f9
fix: HierarchicalSessionStore stale extended cache could wipe messages
cursoragent d6e8a5a
Merge branch 'main' into cursor/critical-bug-investigation-c42c
MervinPraison ffde808
perf: optimize HierarchicalSessionStore with smart cache invalidation
praisonai-triage-agent[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
super()._read_session_fresh()acquires and releasesFileLockinternally. The mtime snapshot is taken after that lock is gone. In the window between the lock release and thegetmtimecall, a concurrent writer can complete a full locked write, advancing the file's mtime to T1. The cache then stores T0 data paired with the T1 mtime. On the next_is_cache_validcheck,current_mtime == cached_mtime (T1)returnsTrue, so the stale T0 data is served — the exact bug this PR intends to close.The mtime must be sampled inside the same
FileLockthat protects the read. Becausesuper()._read_session_freshowns the lock and returns after releasing it, the safe fix is to bypasssuper()and reproduce its logic directly, capturingos.path.getmtimewhile the lock is still held.