Output descriptor differences when ValidateStandardMessageType fails. #889
Conversation
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
copybara-service
bot
force-pushed
the
test_669265300
branch
4 times, most recently
from
3b5ce32 to
95a3bab
Compare
Under normal circumstances this check is never expected to fail. Thus when it does, it is valuable to know why exactly and not just the proto type. PiperOrigin-RevId: 670882709
copybara-service
bot
force-pushed
the
test_669265300
branch
from
95a3bab to
c86fb8d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Output descriptor differences when ValidateStandardMessageType fails.
Under normal circumstances this check is never expected to fail. Thus when it
does, it is valuable to know why exactly and not just the proto type.