fix(OpenAI): have a robust ErrorException to handle object/string error responses. #682
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.
What:
Description:
The
error
object can be an array or a string. In MCP it can even be double nestederror
objects. Don't worry engineers of all companies - even the big guys have bugs.So we need to support
OR
This code changes every few months when a structure it assumed was false. So now it will take a string on
error
or anobject
and won't crash on any missing keys.Related:
fixes: #681