chore: bump requests-toolbelt to 1.0.0 fixes #10470

[SimonDR-Boltzmann]

Description of your changes:

Bumps requests-toolbelt from 0.9.1 to 1.0.0 (see #10470)

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.

[google-oss-prow]

Hi @SimonDR-Boltzmann. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[rimolive]

/ok-to-test

[rimolive]

@SimonDR-Boltzmann I believe this is not the only place to upgrade requests-toolbelt. Looking at the entire repo, I see at least 8 other occurrences of that Python package. I'm new to the kfp code, so I'm unsure what the root requirements.txt does in the code, but I can tell you that the ones inside backend/ and sdk/python are the most important ones. And there's the test/kfp-functional-test/requirements.txt file to run the functional tests with that new dependency version.

That being said, ensure that all occurrences of that package are upgraded to 1.1.0 version.

[SimonDR-Boltzmann]

@SimonDR-Boltzmann I believe this is not the only place to upgrade requests-toolbelt. Looking at the entire repo, I see at least 8 other occurrences of that Python package. I'm new to the kfp code, so I'm unsure what the root requirements.txt does in the code, but I can tell you that the ones inside backend/ and sdk/python are the most important ones. And there's the test/kfp-functional-test/requirements.txt file to run the functional tests with that new dependency version.

That being said, ensure that all occurrences of that package are upgraded to 1.1.0 version.

@rimolive You're right, I should have checked. It also seems the 1.1.0 is not on pypi yet, so I've bumped to 1.0.0 instead

[rimolive]

/test kubeflow-pipeline-e2e-test

[SimonDR-Boltzmann]

@rimolive I could use your help debugging these failed tests, I'm not sure what the CancelledErrors mean, and I get a 403 when I click on the experiment/run details links.

[rimolive]

@SimonDR-Boltzmann Just rebase and I believe the new Github Action tests will run.

[google-oss-prow]

@SimonDR-Boltzmann: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
kubeflow-pipeline-upgrade-test	3d7827e	link	false	/test kubeflow-pipeline-upgrade-test
kubeflow-pipeline-e2e-test	3d7827e	link	false	/test kubeflow-pipeline-e2e-test
kfp-kubernetes-execution-tests	3d7827e	link	false	/test kfp-kubernetes-execution-tests

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. I understand the commands that are listed here.

[SimonDR-Boltzmann]

@SimonDR-Boltzmann Just rebase and I believe the new Github Action tests will run.

@rimolive It seems the tests still fail, but I still can't seem to access the relevant logs to see what's going on.

[hbelmiro]

@SimonDR-Boltzmann you can ignore those tests. They are all optional.
We can see it here.

[gregsheremeta]

@SimonDR-Boltzmann please rebase this PR. We've done some test fixes, and maybe everything will just pass now.

[rimolive]

@SimonDR-Boltzmann May I ask to rebase again? We migrated most of these tests to GitHub actions, now we can run propoer tests in your PR

[rimolive]

/rerun-all

[SimonDR-Boltzmann]

@SimonDR-Boltzmann There are some failling tests. Can you take a look?

@rimolive Apart from the

E       AssertionError: Pipeline components-preprocess ended with incorrect status: FAILED. More info: http://localhost:8888/#/runs/details/c86fcaeb-9963-4272-b6e1-817d8429d381
E       assert 'FAILED' == 'SUCCEEDED'
E         - SUCCEEDED
E         + FAILED

I can't really tell what's the cause of the errors. I'm having some trouble testing locally, could you point me in the right direction?

[gregsheremeta]

I tried to run the tests locally as well (to see if I could help you out) and building images fails for me:

sha256:f326c34ea3fa9c3e2a71ffb6f85986c988a4d0bdc270b28fe3642502426fc125
The push refers to repository [kind-registry:5000/apiserver]
Get "https://kind-registry:5000/v2/": dial tcp: lookup kind-registry: no such host
Failed to build apiserver image.

I might be doing something wrong. It's my first time trying to do this.

Anyone know if we have documentation somewhere for running these e2e kind tests locally?

[diegolovison]

/hold

[diegolovison]

Did you execute pip-compile requirements.in to genereta the requirements.txt?

[SimonDR-Boltzmann]

I tried, but now the requests-toolbelt version is back to 0.10.1 here

[diegolovison]

Double-check the dependency tree and see what library is requesting requests-toolbelt be with 0.10.1

[SimonDR-Boltzmann]

it's kfp(==2.9.0), but I'm not sure how to fix that without releasing and versioning the other change.

[diegolovison]

cc @chensun what we should do in this case?

[diegolovison]

@chensun any idea?

[SimonDR-Boltzmann]

@chensun could you take a look?

[rimolive]

@diegolovison @SimonDR-Boltzmann I believe this is because it's installing kfp from pypi repo, which still uses the old library version. What you could try is temporarily test adding the git+ssh entry in requirements.in pointing to your branch and see if pip-compile requirements.in upgrades to 1.0.

cc @gregsheremeta for awareness.

[SimonDR-Boltzmann]

It looks like the tests succeed when I do this (see https://github.com/kubeflow/pipelines/pull/10762/files#diff-bd584e00f9357e94370a0ebb8f92990519014c49c20206352a17c430f3b79327R2).
I did have to specify requests-toolbelt==1.0.0 in the requirements.in before pip-compile used the new version, but there were no conflicts.

Shall I now remove the changes in test/kfp-functional-test, for final review?

[SimonDR-Boltzmann]

I've removed the changes in test/kfp-functional-test.

[hbelmiro]

/rerun-all

[smthngslv]

Hello! Can this be merged?

[diegolovison]

No. We need to fix #10762 (comment)

[SimonDR-Boltzmann]

/rerun-all

[SimonDR-Boltzmann]

Could someone with the right permissions trigger rerunning of the tests?

[HumairAK]

cc @chensun

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chensun for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• sdk/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hbelmiro]

/ok-to-test

[github-actions]

Approvals successfully granted for pending runs.

[hbelmiro]

/lgtm