Fix unbound knn variable in NonIIDIssueManager #709
Merged
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.
This PR really just fixed one bug where the
knn
object isn't set within the NonIIDIssuemanager if aknn_graph
is already accessible.It's a simple as just initializing the parameter to None. That's already the expected type for
knn
when just theknn_graph
is used.Along with this change, I've added some end-to-end tests in Datalab that ensure the summary is updated appropriately with incremental search.
That's how the
knn
bug was discovered in the first place, because the IssueManagers would otherwise fail silently when callingDatalab.find_issues
.