Fix Openrouter Error Parser to Handle Detailed Error Messages#431
Merged
crmne merged 4 commits intocrmne:mainfrom Mar 2, 2026
Merged
Conversation
Owner
|
Thank you for this. Has this been tested? Can you add a test for it? You could simply change one of the existing tests that mock errors. |
Contributor
Author
Hi @crmne, thanks for your review. I have added the tests. Could you please take another look? |
06c82ec to
9ffb443
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #431 +/- ##
==========================================
- Coverage 81.29% 81.27% -0.02%
==========================================
Files 116 116
Lines 5345 5361 +16
Branches 1398 1404 +6
==========================================
+ Hits 4345 4357 +12
- Misses 1000 1004 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Fix Openrouter Error Parser to Handle Detailed Error Messages
Problem
Currently, when Openrouter returns detailed error information, the error parser only extracts the generic "Provider returned error" message, losing valuable context from the nested error details.
Solution
Enhanced the Openrouter error parser to combine both the main error message and the detailed error message from metadata when available.
Before:
After:
Example Error Response
{ "error": { "message": "Provider returned error", "code": 403, "metadata": { "raw": "{\"error\":{\"code\":\"unsupported_country_region_territory\",\"message\":\"Country, region, or territory not supported\",\"param\":null,\"type\":\"request_forbidden\"}}", "provider_name": "OpenAI" } }, "user_id": "user_2" }Benefits
Type of Change
API Changes