-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix: all big enough ui proxy requests fail with error proxying with partial data #4266
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: all big enough ui proxy requests fail with error proxying with partial data #4266
Conversation
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobgy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
/lgtm |
@Bobgy: you cannot LGTM your own PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
…artial data (kubeflow#4266) * fix: all big enough ui proxy requests fail with error proxying with partial data * Fix naming
…artial data (kubeflow#4266) * fix: all big enough ui proxy requests fail with error proxying with partial data * Fix naming
…artial data (#4266) * fix: all big enough ui proxy requests fail with error proxying with partial data * Fix naming
…artial data (kubeflow#4266) * fix: all big enough ui proxy requests fail with error proxying with partial data * Fix naming
Description of your changes:
When trying out multi user mode for Kubeflow 1.1. After the cluster is up and running for a while, suddenly all big enough ui proxy requests fail with error proxying with partial data. I suspected some behavior changed for Anthos Service Mesh (istio), because I tried removing all istio sidecars, the error doesn't show up.
However, I tried troubleshooting for a while and found this hack solution from chimurai/http-proxy-middleware#171 (comment), it worked perfectly to my surprise.
Checking this in first to unblock Kubeflow 1.1 GCP release.
Checklist:
The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.
PR titles examples:
fix(frontend): fixes empty page. Fixes #1234
Use
fix
to indicate that this PR fixes a bug.feat(backend): configurable service account. Fixes #1234, fixes #1235
Use
feat
to indicate that this PR adds a new feature.chore: set up changelog generation tools
Use
chore
to indicate that this PR makes some changes that users don't need to know.test: fix CI failure. Part of #1234
Use
part of
to indicate that a PR is working on an issue, but shouldn't close the issue when merged.Do you want this pull request (PR) cherry-picked into the current release branch?
If yes, use one of the following options:
cherrypick-approved
label to this PR. The release manager adds this PR to the release branch in a batch update.