-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore: pin visualization server python dependencies. Fixes #3078 #4310
Conversation
/retest |
/test all |
/retest |
2 similar comments
/retest |
/retest |
/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 |
Verified e2e this works with tfx visualization |
(kubeflow#4310) * build: fix visualization server build failure by adding missing licenses for new deps * wip * chore: pin visualization server python dependencies * updates * update licenses
(kubeflow#4310) * build: fix visualization server build failure by adding missing licenses for new deps * wip * chore: pin visualization server python dependencies * updates * update licenses
(kubeflow#4310) * build: fix visualization server build failure by adding missing licenses for new deps * wip * chore: pin visualization server python dependencies * updates * update licenses
Description of your changes:
Fixes #3078
This has been a constant pain needing to fix build failures for visualization server from time to time, the most recent one being #4309. Let's pin its dependencies.
Verification:
TODO:
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.