fix(rest): pass upstream 4xx through /v1/infer instead of 502 - #11
Merged
Conversation
"task not served" / bad-input rejections from the inference upstream returned as generic 502 inference_upstream; now 4xx status + detail pass through as inference_rejected.
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
1 participant
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.
The /v1/infer proxy collapsed every upstream failure into 502
inference_upstream. Requests the upstream legitimately rejects -
task not served (khm-latn translit), oversized input - now surface
with their real status and detail as inference_rejected; transport
failures stay 502. TDD: fetch-stubbed test asserts 400 passes
through. 26/26.