fix(LazyInit): support lazy initialization of llm in legacy evaluators #1105
Conversation
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
github-actions
bot
added
test:uipath-langchain
akshaylive
force-pushed
the
akshaya/lazy_init
branch
2 times, most recently
from
5f64c72 to
814d047
Compare
mjnovice
approved these changes
Jan 14, 2026
Legacy evaluators that use LLMs currently initialize `UiPath` object during instantiation. This fails loading of evaluator in case `.env` is not found. Fixing it by performing lazy initialization. Additionally, llm input-mocking also fails all evaluations in case .env is not found. This is a bad dev experience, so handling it gracefully.
akshaylive
force-pushed
the
akshaya/lazy_init
branch
from
814d047 to
90affa4
Compare
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.
Legacy evaluators that use LLMs currently initialize
UiPathobject during instantiation. This fails loading of evaluator in case.envis not found. Fixing it by performing lazy initialization.Additionally, llm input-mocking also fails all evaluations in case .env is not found. This is a bad dev experience, so handling it gracefully.