-
Notifications
You must be signed in to change notification settings - Fork 4
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
Improve Litellm proxy related error handling #491
Conversation
…r chat histories.
…Added /chat endpoint. Temporariliy commented out /search endpoint for quick testing.
…sync from json to _json.
…t also takes care of data migration. Updated tests.
Tested and works well thanks! I did spot another unrelated error though: every time I try to put in a string tag in the content card it errored out with the following error.
I think it's happening because the pydantic class |
Hi @poornimaramesh, Thanks for catching that. But I am struggling to recreate that error on my end. If you don't mind I will merge this and we can huddle on that later |
Reviewer: @poornimaramesh
Estimate: 20 mins
Ticket
Fixes: AAQ-896
Description
Goal
The goal of this PR is to improve error handling, so we don't show 500 errors when there are LiteLLM related errors
Changes
The following changes have been made:
contents
andquestion_answers
routers to raise a 503 error when these exceptions are caught.Future Tasks (optional)
How has this been tested?
To-do before merge (optional)
Checklist
Fill with
x
for completed.