Open semyon-dev opened 4 months ago
But the latest version (v3.5.14) does not have this option, please add this option (or commit) to the next version.
Have you confirmed that it's working if you depend on etcd main branch?
But the latest version (v3.5.14) does not have this option, please add this option (or commit) to the next version.
Have you confirmed that it's working if you depend on etcd main branch?
I'm sorry, the problem remained on the main branch, but I don't understand why
the problem remained on the main branch, but I don't understand why
Thanks for the feedback. It means that it won't hep to backport the option go_package
change to 3.5.
I suggest you to raise this issue/question in protobuf community. https://github.com/protocolbuffers/protobuf-go
Based on https://protobuf.dev/reference/go/faq/#namespace-conflict, it's a best practice to specify a package name in .proto file. So let's keep this ticket open until the root cause is clear.
What would you like to be added?
There has been a commit in the main branch for at least 10 months that adds option go_package: https://github.com/etcd-io/etcd/blob/main/server/storage/wal/walpb/record.proto#L7
But the latest version (v3.5.14) does not have this option, please add this option (or commit) to the next version.
Why is this needed?
I am using two dependencies (one of them is etcd) that have the same proto files -
record.proto
, and because of this there is a conflict. To resolve this conflict, option go_package is needed.Now I have to do this:
os.Setenv("GOLANG_PROTOBUF_REGISTRATION_CONFLICT", "ignore")
or I will get a panic: