Clean up hold_range_in_memory from accounts index: part 2#6979
Merged
HaoranYi merged 1 commit intoanza-xyz:masterfrom Jul 16, 2025
Merged
Clean up hold_range_in_memory from accounts index: part 2#6979HaoranYi merged 1 commit intoanza-xyz:masterfrom
HaoranYi merged 1 commit intoanza-xyz:masterfrom
Conversation
HaoranYi
changed the title
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6979 +/- ##
========================================
Coverage 83.2% 83.2%
========================================
Files 856 853 -3
Lines 376421 375577 -844
========================================
- Hits 313240 312649 -591
+ Misses 63181 62928 -253 🚀 New features to boost your workflow:
|
roryharr
approved these changes
Jul 15, 2025
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
4 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.
Problem
hold_range_in_memory was originally introduced to support rent scanning by keeping certain key ranges in memory. However, since we no longer perform range-based rent scanning, this mechanism is now obsolete.
This PR is part 2 for the clean up: remove hold_range check from evict.
Summary of Changes
Fixes #