-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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: Fixes memiterator #21775
fix: Fixes memiterator #21775
Conversation
@alpe your pull request is missing a changelog! |
WalkthroughWalkthroughThe changes introduced in this pull request modify the Changes
Possibly related PRs
Recent review detailsConfiguration used: .coderabbit.yml Files selected for processing (1)
Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
@@ -111,7 +111,7 @@ type memIterator struct { | |||
// The `valid` field of the iterator indicates whether the iterator is positioned at a valid key. | |||
// The `start` and `end` fields of the iterator store the start and end keys respectively. | |||
func newMemIterator(start, end []byte, tree *btree.BTreeG[item], ascending bool) *memIterator { | |||
iter := tree.Iter() | |||
iter := tree.Copy().Iter() |
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 add to the godoc that we create a copy here
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.
llgtm
Description
This PR contains 2 fixes to the
MemIterator
.end
forkeyInRange
when in desc orderThe first fix has side negative effects as described in #21754 that may have to be addressed before.
Not sure about the
keyInRange
fix. I was applying the rules defined in the constructor whereend
is ecluded.Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
in the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.
I have...
Summary by CodeRabbit
New Features
Bug Fixes
Tests