-
Notifications
You must be signed in to change notification settings - Fork 136
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
Google::Protobuf
DSL generation broken again
#1533
Comments
I doubt that the linked change is responsible for this since the change is for |
The previous fix we sent is incomplete: the only problem we could reliably reproduce then was an issue with the The latest
This means that the "this is a map" condition will no longer catch them. Updating the condition to match It doesn't look like there are other fields we get that would reliably tell us wether the descriptor is a map, unfortunately. Interestingly, that map change seems to be the only actual change in the Ruby implementation of protobuf: protocolbuffers/protobuf@v23.2...v23.3. @bitwise-aiden and I tried updating |
@bitwise-aiden will try and see if there's a better fix, otherwise we'll go with the |
I have a better fix for this, without any name matching |
The actual change that was making this fail was googleapis/google-cloud-ruby@60c6c7f#diff-4fca4ecc3fd8492291b00da2a60b0bd8d6dac67697c6dce3664bf881ebc2ece3 In a nutshell, |
Reopening as the fix was reverted. |
In the latest release of
protobuf
i.e. v23.3, there's aMap
specific bugfix for Ruby which seems to have broken DSL generation again. Again as v23 also broke generation, fixed in #1497.This appears to be the change, see below.
And this is what is happening typecheck wise on a
google-big-table
bump which includes v23.3 prorobuf.Resources
Google::Protobuf::Struct
#1497The text was updated successfully, but these errors were encountered: