-
Notifications
You must be signed in to change notification settings - Fork 450
fix: optimize LRU cache #985
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
Conversation
| NSString *reason = [NSString stringWithFormat:@"The element identified by \"%@\" is either not present or it has expired from the internal cache. Try to find it again", uuid]; | ||
| @throw [NSException exceptionWithName:FBStaleElementException reason:reason userInfo:@{}]; | ||
| } | ||
| if (checkStaleness) { |
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.
would it be possible to add an integration test to validate this behaviour?
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.
can we pick this up later? is it a release blocker? to how much extent do we cover this in tests currently?
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.
yes, it is ok to do it in a different PR
## [9.0.6](v9.0.5...v9.0.6) (2025-02-28) ### Bug Fixes * optimize LRU cache ([#985](#985)) ([46dc417](46dc417))
|
🎉 This PR is included in version 9.0.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What?
[element fb_takeSnapshot:NO]whencheckStalenesswas true.removeObjectForKey:method to remove an object from the LRU cache using its key.Impact: