feat(ui, openai): Structured errors and link to traces in error toast#9068
Open
richiejp wants to merge 1 commit intomudler:masterfrom
Open
feat(ui, openai): Structured errors and link to traces in error toast#9068richiejp wants to merge 1 commit intomudler:masterfrom
richiejp wants to merge 1 commit intomudler:masterfrom
Conversation
✅ Deploy Preview for localai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
fea2c9e to
ce87b3b
Compare
First when sending errors over SSE we now clearly identify them as such instead of just sending the error string as a chat completion message. We use this in the UI to identify errors and link to them to the traces. Signed-off-by: Richard Palethorpe <io@richiejp.com>
ce87b3b to
20989a9
Compare
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
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.
Description
First when sending errors over SSE we now clearly identify them as such instead of just sending the error string as a chat completion message.
We use this in the UI to identify errors and link to them to the traces.
Notes for Reviewers
This is a breaking change for the API, but it's in part of the API that is undefined and only effects error paths. Without it there is no clear way to identify errors rather than just LLM responses that look like errors.
Signed commits