fix(evals): Change eval set discrimination strategy #1241
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 makes the routing to the new model of
EvalSetsto occur based on whether theversionfield is present and its value can be cast to afloatthat is>=1.Currently. the new
EvalSetswould error if one gives another version than1.0in the JSON because theversionfield is enforced to be aLiteral["1.0"]. To test this PR, we amended locally thepydanticclass to allow for other versions. Yet, on main, other versions than1.0would fail until another PR amends this restriction.Development Package
uipath pack --nolockto get the latest dev build from this PR (requires version range).