Fix bug in batch iterators for the case where batch_size=0 #147
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.
In brute force - instead of asserting that we hadn't computed the scores when the number of returned results by the batch iterator is 0, we should assert that the number of returned results by the iterator is 0 if the scores hadn't been computed yet (otherwise, we crash after asking for 0 results).
In HNSW - we should insert the entry point node to the candidates heap only when both the returned results count is 0 and the
top_candidates_extraqueue is empty. Otherwise, we might get that the entry point will be returned twice (if we ask for 0 results, and moved the entry point to thetop_candidates_extra, and then reinsert the entry point to the candidates).