Fixup for VisitedListHandle::check_and_update_visited #5427
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.
Fixup for #5336. In #5336, I made an assumption that the
num_points
provided toVisitedPool::get()
is always accurate and removed bounds check fromVisitedListHandle::check_and_update_visited
.But it seems that it's not true. Chaos testing shows that it crashes in the following code:
qdrant/lib/segment/src/index/struct_payload_index.rs
Lines 381 to 399 in ac54ad4
Perhaps the offending ids could come from
PrimaryCondition::Ids
/WAL/field_index? This PR restores the check.