You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ ./test-proto-tracerstate
proto: duplicate proto type registered: basictracer_go.wire.TracerState
is printed while we use the tracer from appdash, along with ipfs/go-log imported by some of our libp2p dependencies. I can reproduce it by building and running this go file in my environment(macOS, go1.10.3)
How can it be fixed?
IIUC, the cause might be that the protobuf wire messages in ipfs/go-log and opentracing/basictracer-go have the same package name and message name. In this case, the name of proto message will be registered twice, due to the call to init() in *.pb.go.
My first thought to solve this issue is to rename one of the proto. However, I'm not so sure of the usage. It might also be the case that I misused the two packages.
Thank you:)
The text was updated successfully, but these errors were encountered:
What is wrong?
$ ./test-proto-tracerstate proto: duplicate proto type registered: basictracer_go.wire.TracerState
is printed while we use the tracer from appdash, along with
ipfs/go-log
imported by some of our libp2p dependencies. I can reproduce it by building and running this go file in my environment(macOS, go1.10.3)How can it be fixed?
IIUC, the cause might be that the protobuf
wire
messages in ipfs/go-log and opentracing/basictracer-go have the same package name and message name. In this case, the name of proto message will be registered twice, due to the call toinit()
in*.pb.go
.My first thought to solve this issue is to rename one of the proto. However, I'm not so sure of the usage. It might also be the case that I misused the two packages.
Thank you:)
The text was updated successfully, but these errors were encountered: