-
Notifications
You must be signed in to change notification settings - Fork 49
build(deps): Align protobuf and related dependencies with the gRPC v1.81.1 bump #466
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
ea49f09
fix: Forward TRITON_THIRD_PARTY_REPO_TAG to client sub-builds
mc-nv 35d4b81
fix: Make nested utf8_range package findable in perf-analyzer configure
mc-nv d20a30b
fix: Compile all perf-analyzer targets at TRITON_MIN_CXX_STANDARD
mc-nv 8e70356
fix: Replace removed protobuf always_print_primitive_fields option
mc-nv 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 hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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.
always_print_fields_with_no_presenceis the documented protobuf v33 replacement foralways_print_primitive_fields, but the two options diverge for proto3optionalscalar fields andoneofmembers: the old option printed those at their default value regardless of whether they were explicitly set; the new option will omit them when they are not set (becauseoptionalandoneoffields carry explicit presence).If any field in
ModelMetadataResponseorModelConfigResponseis a proto3optionalscalar (or is aoneofmember), callers that previously received a full JSON object with default-zero values will now get a sparse object and may hit missing-key errors. The same applies to the TFSGetModelMetadataResponsesite. Worth confirming against the actual.protodefinitions that nooptional/oneofscalars are relied upon at their default values.