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
Regression in handling of 0 values for google.protobuf.Int64Value types (and maybe others) #7158
Comments
This is working as expected in |
Both versions encode the same, so it seems like an issue with decoding |
I've seen this behavior too, and reproduced it in a test a while ago, #7037 . No response yet on that though |
Totally agree, it also almost caused an issue for us too |
This was fixed in #7195. Sorry about that! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of protobuf and what language are you using?
Version: Ruby 3.11.2
What did you do?
Simplified/Minimal Example.
OUTOUT
<Wrapper: id: nil>
What did you expect to see?
<Wrapper: id: <Google::Protobuf::Int64Value: value: 0>>
What did you see instead?
<Wrapper: id: nil>
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment?
This works on version
3.7.1
of the gem as expected. This is a very dangerous bug in my opinion, as it can break applications...The text was updated successfully, but these errors were encountered: