Mate operator fix #1268
Merged
Mate operator fix #1268
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
|
Seems nice! I get this error a lot. |
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.
What does this PR do?
_mate_operator has a wrapper that tries to check if all its returned values are valid pipelines. The last returned item is actually a dictionary and does not need to be evaluated. This led to the following error being thrown any time this function was called
_pre_test decorator: _mate_operator: num_test=0 'str' object has no attribute 'arity'.
I added a check in the decorator specific to _mate_operator to prevent this. Alternatively, We could also implement a generic check to skip anything that is not a pipeline/deap individual