-
Notifications
You must be signed in to change notification settings - Fork 348
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
feat: Vertex Vizier support in SDK. #1434
Conversation
…and system tests for them.
dismissing this review because all copy-pasted pyvizier code has been removed; additionally, all open comments have been addressed
"absl-py>=0.7", | ||
"numpy>=1.19.0", | ||
"protobuf>=3.6,<4.0", | ||
"keras-tuner>=1.0,<2.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is keras-tuner used?
"protobuf>=3.6,<4.0", | ||
"keras-tuner>=1.0,<2.0", | ||
"portpicker==1.3.1", | ||
"googleapis-common-protos==1.56.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these versions be so strict?
"portpicker==1.3.1", | ||
"googleapis-common-protos==1.56.0", | ||
"google-api-python-client==1.12.8", | ||
"google-vizier==0.0.3a", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any issues with supporting higher versions of vizier? 0.0.3a seems to be quite behind 0.0.15
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes # b/230767019 🦕