-
Notifications
You must be signed in to change notification settings - Fork 701
improve error logging for fireworks #1283
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good improvement to error handling by adding explicit error response generation for Fireworks AI provider errors.
if (response.error) { | ||
return generateErrorResponse(response.error, FIREWORKS_AI); | ||
} | ||
return generateInvalidProviderResponseError(response, FIREWORKS_AI); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Code Refactor
Issue: Missing explicit error handling for response.error cases
Fix: Added proper error response generation with provider-specific context
Impact: Improves error visibility and debugging for Fireworks AI failures
The addition of explicit error checking and response generation follows the established pattern used across other providers (zhipu, workers-ai, etc.) as shown in the AST grep results. This ensures consistent error handling behavior.
No description provided.