Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add strong response types for vertex evaluators #2

Merged
merged 238 commits into from
May 2, 2024

Conversation

tagboola
Copy link
Contributor

@tagboola tagboola commented May 1, 2024

At some point, we should rely on the generated API client. In the short term, this will hopefully prevent issues like we saw before.

@pavelgj pavelgj force-pushed the main branch 2 times, most recently from c5838f8 to dca1561 Compare May 1, 2024 23:56
pavelgj pushed a commit that referenced this pull request May 1, 2024
MichaelDoyle and others added 22 commits May 2, 2024 09:22
Display errors in the Prompt Playground component after receiving issues from backend
Also update styles for running + error statues in output box.
Input validation for prompt playground
Also add icons for all known action types
tonybaroneee and others added 27 commits May 2, 2024 09:22
Co-authored-by: Chris Chestnut <[email protected]>
Co-authored-by: Michael Doyle <[email protected]>
Fixes google/genkit#130. This is more of a stop-gap fix, going to explore refactoring these components to utilize Angular signals to eliminate this class of error entirely.
Change the name of the action latency histogram from
"genkit.action.action_latency" to "genkit.action.latency"
to avoid stutter.
@tagboola tagboola force-pushed the ta/vertex-evals-strong-types branch from 7e16a96 to 983658f Compare May 2, 2024 13:23
@tagboola tagboola merged commit 99cb078 into main May 2, 2024
4 checks passed
@tagboola tagboola deleted the ta/vertex-evals-strong-types branch May 2, 2024 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.