Merged
Conversation
Collaborator
|
@VolkovMaxim fix lint |
VolkovMaxim
force-pushed
the
feature/fix_http_exeption_bug
branch
from
0bddb4e to
5606726
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
3 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.
Problem:
When an unexpected Exception occurred in the /v1/provide-clarification and /v1/chat/completions endpoints, the API returned the static string "str(e)" in the detail field instead of the real error message.
Solution:
This change corrects the HTTPException call to properly convert the exception e to a string using str(e). This allows the actual cause of the error to be visible on the client side, which simplifies debugging.