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
Update protobuf to 3.9.0 #19630
Update protobuf to 3.9.0 #19630
Conversation
Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement. After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.
Regards, |
It is useful to provide link to the last update #19182 - most changes should be of the same nature. |
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.
This is mostly looking good (with exception of my comment). Let's see what the tests say.
@@ -29,7 +29,7 @@ Gem::Specification.new do |s| | |||
s.require_paths = %w( src/ruby/lib src/ruby/bin src/ruby/pb ) | |||
s.platform = Gem::Platform::RUBY | |||
|
|||
s.add_dependency 'google-protobuf', '~> 3.8' | |||
s.add_dependency 'google-protobuf', '~> 3.9.0' |
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.
I think the missing .0
is intended. (see PR for bump to 3.8). Please fix in the .template file
@TeBoring for some reason the CLA check is failing - can you doublecheck please? |
What do I need to do for the CLA? Can we sign the cla for the foundation?
…On Wed, Jul 17, 2019 at 07:36 Jan Tattermusch ***@***.***> wrote:
@TeBoring <https://github.com/TeBoring> for some reason the CLA check is
failing - can you doublecheck please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19630?email_source=notifications&email_token=ABHUPZP2RJMNA36D6KJCUBDP74VAFA5CNFSM4ICNRII2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ENBSI#issuecomment-512282825>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABHUPZO3C5I2HTLB5XYQB2LP74VAFANCNFSM4ICNRIIQ>
.
|
CLA: https://identity.linuxfoundation.org/projects/cncf you should be able to sign as google employee. |
The c# error is something we need to take a look into. It might also be that 3.9.0 might contain a breaking change that needs to be rolled back.
Other problems: |
The C# problem likely has to do with this change: |
CC @ObsidianMinor (probably related to protocolbuffers/protobuf#5350) |
I signed |
3.9.0 was delisted until a 3.9.1 release can be made to with these changes. The C# issues are probably related to that. |
Looks like the test is using new protoc but old c# runtime? @jtattermusch is the failure in this case, and why old c# runtime is used in Grpc's test? Protobuf only gurantee old generated code work with new runtime. Not gurantee new generated code work with old runtime |
Ok, I think I now understand what happened:
I created #19679 to fix the problem. After it's merged, this PR needs to be updated to modify |
Superseded by #19867 |
No description provided.