fix: make model field optional in LegacyLlmAsAJudgeEvaluator [AE-1306]#1488
Open
fix: make model field optional in LegacyLlmAsAJudgeEvaluator [AE-1306]#1488
Conversation
github-actions
bot
added
test:uipath-langchain
The `model` field was required but evaluator JSON files stored in StudioWeb do not include it. This caused a `ValidationError: model Field required` when running evals on the serverless path. Fix adds a default value of `"same-as-agent"` and imports `Field` from pydantic. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ameyjain
force-pushed
the
fix/legacy-llm-evaluator-model-field-required
branch
from
aa28702 to
a2e24db
Compare
ameyjain
changed the title
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Same fix as for LegacyLlmAsAJudgeEvaluator: the `model` field was required but evaluator JSON files stored in StudioWeb do not include it, causing `ValidationError: model Field required` on the serverless eval path. Affected evaluators: - LegacyTrajectoryEvaluator - LegacyFaithfulnessEvaluator - LegacyContextPrecisionEvaluator Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…://github.com/UiPath/uipath-python into fix/legacy-llm-evaluator-model-field-required
Chibionos
approved these changes
Mar 26, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
modelfield inLegacyLlmAsAJudgeEvaluatorwas required (model: str) but evaluator JSON files stored in StudioWeb do not include itValidationError: model Field requiredwhen running evals on the serverless pathField(default="same-as-agent")and importedFieldfrom pydanticRoot Cause
The non-serverless (Temporal) path injects the model inline via C#
EvalDefinitionBuilder, so the required field was never an issue there. The serverless path reads evaluator config directly from JSON files which don't have amodelproperty, triggering the Pydantic validation error.Test plan
model Field requirederrorJIRA
https://uipath.atlassian.net/browse/AE-1306