-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
clientv3: Fix grpc-go(v1.27.0) incompatible changes to balancer/resolver. #11564
Conversation
Codecov Report
@@ Coverage Diff @@
## master #11564 +/- ##
==========================================
+ Coverage 64.39% 65.91% +1.51%
==========================================
Files 403 401 -2
Lines 38097 36568 -1529
==========================================
- Hits 24534 24105 -429
+ Misses 11913 10958 -955
+ Partials 1650 1505 -145
Continue to review full report at Codecov.
|
5d07a20
to
4258cdd
Compare
Thanks @eddycjy. Would you also update the changelog (3.5 since this is on master) with a |
@jpbetz Thanks for your reply and reminder, I have submitted CHANGELOG-3.5. |
Next time lets include the changelog update in the same PR as the main change. But I'm okay with separate for this issue since they are both already open. LGTM |
@gyuho WDYT? |
I get the following error when I simply try to
Will this PR solve the issue? |
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.
LGTM 👍
Any ETA on merging this? We are hitting the go mod dependency issue. |
Any ETA on releasing 3.3.19? We are also hitting the go mod dependency issue. |
CHANGELOG-3.5: update from #11564
When this merge will be released? We are also facing the same issue. Regards, |
etcd-io/etcd#11564 Signed-off-by: Humble Chirammal <[email protected]>
Not releasing this really screws projects that have dependencies with protobufs that have been generated by
Which then translates into
in go.mod parlance. Given that etcd's go modules are totally broken anyway, we'll likely still have to import commit hashes directly, but at least they'll be pointing at a tagged release that can be matched to etcd server deployment. In the absence of an actual release, every downstream project with recent protoc-gen-go dependencies is relegated to a mishmash of client/server versions that maybe works. The common workaround noted on this issue and others of replacing grpc's module version with v1.2.6 is not viable for projects that actually depend on generated protobuf code that has elements like |
Please please please release this fix, our whole team is completely stuck because no builds are working |
Workaround: add
to you go.mod file. It's not perfect, but it'll allow you to at least partially update |
* clientv3: fix grpc-go(v1.27.0) incompatible changes to balancer/resolver. * vendor: upgrade gRPC Go to v1.24.0 Picking up some performance improvements and bug fixes. https://github.com/grpc/grpc-go/releases/tag/v1.24.0 Signed-off-by: Gyuho Lee <[email protected]> * vendor: update gRPC Go to v1.26.0 (#11522) * GO111MODULE=on go mod vendor * GO111MODULE=on go mod vendor go 1.14 Bump travis 2 Co-authored-by: EDDYCJY <[email protected]> Co-authored-by: Gyuho Lee <[email protected]> Co-authored-by: Yuchen Zhou <[email protected]>
@rcgoodfellow, did you find any solutions for now? All go clients from googleapis relies on |
@AFMiziara 3.4.8 contains the fix. |
clientv3: Fix grpc-go (v1.27.0) incompatible modification of balancer/resolver API.
Modify the API changed by balancer / resolver to ensure consistency with grpc-go (v1.27.0), otherwise clientv3 will not be able to be pulled by go mod, which will affect the direct use of users.
References:
Fixes #11563