feat(llma): eval auto execution #39786
Open
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
|
Greptile encountered an error while reviewing this PR. Please reach out to [email protected] for assistance. |
|
Size Change: 0 B Total Size: 3.05 MB ℹ️ View Unchanged
|
carlos-marchal-ph
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Makes it so LLM evals can be enabled and are automatically enqueued on ingestion of matching events. It's modelled on CDP event pre-processing, as discussed in this Slack thread.
This adds the Temporal client as a dependency to the plugin server, as evals get enqueued as Temporal jobs. I'd appreciate some pointers to make sure that the credentials are passed correctly and deployment goes smoothly.