-
Notifications
You must be signed in to change notification settings - Fork 184
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
Fix upper bound issue in CalculatePrefixSize
#2223
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2223 +/- ##
==========================================
- Coverage 74.41% 74.36% -0.05%
==========================================
Files 109 109
Lines 11493 11519 +26
==========================================
+ Hits 8552 8566 +14
- Misses 2277 2285 +8
- Partials 664 668 +4 ☔ View full report in Codecov by Sentry. |
9b0bd9c
to
f6d9cef
Compare
This pull request is stale because it has been open 35 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
1ecb18d
to
d94df24
Compare
db size
commandCalculatePrefixSize
f34b203
to
e4b412b
Compare
This reverts commit e4b412b.
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.
Small hint
Co-authored-by: Pawel Nowosielski <[email protected]> Signed-off-by: Ng Wei Han <[email protected]>
Description
This PR modifies the
db size
command to also check for leftover key-value pairs in the database. It also fixes an upper bound bug as theUpperBound
iterator option is exclusive, not inclusive.