-
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
bug: cannot use target.Endpoint as string value in struct literal #15286
Comments
Have you updated the gRPC version yourself? Please provide the exact steps you did. This might be related to #15145 |
My gRPC version is v1.53.0 , this my code: import (
clientv3 "go.etcd.io/etcd/client/v3"
"go.etcd.io/etcd/client/v3/naming/resolver"
)
func Test1(client *clientv3.Client) {
builder, err := resolver.NewBuilder(client)
if err != nil {
return
}
_ = builder
} ectd client version is v3.5.7 it's can't build pass, because ide hint there is an error here |
Hello, I also met the same problem, may I ask how to solve the final, thank you! |
I downgraded the version of grpc to v1.52.3 |
- etcd and gprc isn't compatible See:etcd-io/etcd#15286 (comment) #16
I change the source code of file resolver.go into target.Endpoint(), because target.Endpoint is a func, but need a string |
Thank you very much. I tried this too. It's really feasible |
What happened?
v3.5.7
When I build my app, etcd package have an error:
What did you expect to happen?
I expect build success.
How can we reproduce it (as minimally and precisely as possible)?
Please see here:
etcd/client/v3/naming/resolver/resolver.go
Line 22 in 215b53c
it's a simple bug.
Anything else we need to know?
No response
Etcd version (please run commands below)
The text was updated successfully, but these errors were encountered: