-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
fix(ai-proxy): do not double-gzip responses when status is not 200 #12493
Merged
Conversation
This file contains 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
tysoekong
added
cherry-pick kong-ee
schedule this PR for cherry-picking to kong/kong-ee
backport release/3.6.x
labels
Feb 1, 2024
locao
changed the title
fix(ai-proxy): double-gzipping responses when status is not 200 (urgent)
fix(ai-proxy): do not double-gzip responses when status is not 200
Feb 1, 2024
Skipping changelog as this is a fix for an unreleased feature. |
curiositycasualty
approved these changes
Feb 1, 2024
tysoekong
force-pushed
the
fix/ai_proxy_double_gzip
branch
from
February 1, 2024 20:58
1ade18a
to
260510d
Compare
gruceo
approved these changes
Feb 1, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Feb 1, 2024
(cherry picked from commit 1fb8be5)
3 tasks
Successfully created backport PR for |
curiositycasualty
pushed a commit
that referenced
this pull request
Feb 1, 2024
…) (#12496) (cherry picked from commit 1fb8be5) Co-authored-by: Jack Tysoe <[email protected]>
gruceo
added
cherry-pick kong-ee
schedule this PR for cherry-picking to kong/kong-ee
and removed
cherry-pick kong-ee
schedule this PR for cherry-picking to kong/kong-ee
labels
Feb 1, 2024
Successfully created cherry-pick PR for |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release/3.6.x
git worktree add -d .worktree/backport-12493-to-release/3.6.x origin/release/3.6.x
cd .worktree/backport-12493-to-release/3.6.x
git switch --create backport-12493-to-release/3.6.x
git cherry-pick -x 1fb8be5a52c0adfeceae89e2056128734ccfc489 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cherry-pick kong-ee
schedule this PR for cherry-picking to kong/kong-ee
plugins/ai-proxy
size/M
skip-changelog
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.
Summary
Logic error - with non-200 responses from the LLM, I was double-gzip'ing the response messages (if there was
content-encoding: gzip
header present).This is a quick fix for it before 3.6.0 release, and this whole response phase can be refactored during the tech preview phase.
Checklist
changelog/unreleased/kong
N/A - part of new feature in 3.6.0, there is "no existing changelog" yetIssue reference
Bug discovery during field testing.