Fix Mongodb commitIndexBuild panic in olpog-replay #1696
Conversation
This file contains 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
Signed-off-by: sayedppqq <sayed@appscode.com>
sayedppqq
requested review from
perekalov,
VGoshev,
KhurtinDN and
Apelsin234
as code owners
Apelsin234
reviewed
Apr 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Database name
Mongodb
Describe what this PR fix
For
oplog-replay, any oplog with commitIndexBuild command, in indexSpecFromCommitIndexBuilds func, its getting panic due to for loop's variables misposition in indexSpecs slicePlease provide steps to reproduce (if it's a bug)
multiple index commit in oplog-replay