Fix CI bug due to new Elasticsearch release and new model release #579
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
tholor
approved these changes
Nov 12, 2020
brandenchan
changed the title
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.
Haystack's requirements.txt ask for the latest version of Elasticsearch. A new ES release causes the
elasticsearch.helpers.scan()function to now return a generator instead of a list.This PR casts the output of
scan()to a list so that CI doesn't fail and restricts ES versioning so new releases won't introduce bugs.The assert value of a reader test is also changed since the
deepset/roberta-base-squad2model was updated to version2.