-
Notifications
You must be signed in to change notification settings - Fork 473
feat(simple reader): Destroy MRDinstance & remove it from cache when inode is destroyed #4262
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
|
/gemini review |
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.
Code Review
This pull request introduces important improvements to the lifecycle management of MrdInstance. By ensuring that the MrdInstance is destroyed and removed from the cache when its owning inode is destroyed, it effectively prevents potential resource leaks. The refactoring of the cache eviction logic into the MrdInstance itself is a great change that improves encapsulation and clarity. I was particularly impressed with the handling of the race condition where an instance could be re-added to the cache before its eviction is processed. The new unit tests are comprehensive and thoroughly cover the new logic and edge cases. The changes are well-implemented and significantly enhance the robustness of the code. Great work!
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4262 +/- ##
==========================================
+ Coverage 83.06% 83.10% +0.03%
==========================================
Files 159 159
Lines 19235 19249 +14
==========================================
+ Hits 15977 15996 +19
+ Misses 2666 2663 -3
+ Partials 592 590 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Hi @raj-prince, @vadlakondaswetha, your feedback is needed to move this pull request forward. This automated reminder was triggered because there has been no activity for over 24 hours. Please provide your input when you have a moment. Thank you! |
1 similar comment
|
Hi @raj-prince, @vadlakondaswetha, your feedback is needed to move this pull request forward. This automated reminder was triggered because there has been no activity for over 24 hours. Please provide your input when you have a moment. Thank you! |
raj-prince
left a comment
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.
LGTM.
…abhishek/inode_destroy
Description
Link to the issue in case of a bug fix.
b/474070647
Testing details
Any backward incompatible change? If so, please explain.