-
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
feat(sdk): Use google.protobuf.Value in v2 for passing parameters. #6804
Merged
Merged
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
4966b0b
Use google.protobuf.Value in v2 for passing parameters.
neuromage 8f14fb1
retest samples.
neuromage 728f922
Fix tests.
neuromage 5b13589
Merge branch 'master' into protobuf-value.
neuromage cf3407d
Update release, more cleanup.
neuromage 7e6d18f
Use github.com/kubeflow/pipelines/api from same repo.
neuromage bde385f
Run go mod tidy
neuromage ac5f6e3
chore: go mod tidy
Bobgy fd8ee77
fix v2 compile error and clean up unused code
Bobgy 216944a
pr comments.
neuromage 87319b8
Merge branch 'protobuf-value' of github.com:neuromage/pipelines into …
neuromage 107a492
Merge branch 'master' into protobuf-value
neuromage df770b8
Merge branch 'master' into protobuf-value
neuromage 9b5e012
update goldens
neuromage c8d49a2
Fix metadata recording.
neuromage de1f943
Update kfp mlmd client.
neuromage bfc380b
fix test again
neuromage ad3e7f9
another try.
neuromage 917d979
chore: migrate v2 DAG driver input parameters to protobuf.Value + sma…
Bobgy b0718ec
fix v2 launcher + clean up
Bobgy 1df554a
fix a compile error
Bobgy 24360f2
fix a few more tests
Bobgy 7b9a681
fix number parsing
Bobgy 547747e
clean up
Bobgy f2426b0
disable cache_v2 test.
neuromage 35f8448
Merge branch 'protobuf-value' of github.com:neuromage/pipelines into …
neuromage File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
Oops, something went wrong.
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.
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.
nit: the other fields use camel case
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.
Thanks, but proto style guide is explicitly underscore_separated_names for fields. This is what's used everywhere else as well:
https://developers.google.com/protocol-buffers/docs/style#message_and_field_names
My suggestion is to adopt the right style here for long term health, and consider replacing the camel case ones in a future PR.