Is there any other problem with converting “namespace conflict” panic to warning？

[FGYFFFF]

Hi ~ I have a go project that uses protobuf generated content locally, and the dependencies for that project use the same protobuf generated content. So I had the problem of namespce conflict, and I saw from the official documentation that I could add a compile option to turn this panic into a warning. My project only uses go structs generated by protobuf, and does not make rpc calls. So I would like to ask if there are any other side effects when namespace conflict is converted to warnning.

Translated with www.DeepL.com/Translator (free version)

[aktau]

What option did you pass (and to what) to turn the panic into a warning? I'm not (yet) familiar with this functionality and would need to look into it. Thanks!

[FGYFFFF]

What option did you pass (and to what) to turn the panic into a warning? I'm not (yet) familiar with this functionality and would need to look into it. Thanks!

https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict

Starting with v1.26.0 of the google.golang.org/protobuf module, a hard error will be reported when a Go program starts up that has multiple conflicting protobuf names linked into it. While it is preferable that the source of the conflict be fixed, the fatal error can be immediately worked around in one of two ways:

At compile time. The default behavior for handling conflicts can be specified at compile time with a linker-initialized variable: go build -ldflags "-X google.golang.org/protobuf/reflect/protoregistry.conflictPolicy=warn"

At program execution. The behavior for handling conflicts when executing a particular Go binary can be set with an environment variable: GOLANG_PROTOBUF_REGISTRATION_CONFLICT=warn ./main

[aktau]

Thanks, now I understand things better.

Thinking about your question:

My project only uses go structs generated by protobuf, and does not make rpc calls. So I would like to ask if there are any other side effects when namespace conflict is converted to warnning.

Then this conflict would lead to bugs any time a resolver is used. The cases I can think of where a Resolver is used:

• google.protobuf.Any.
• Other reflection use cases: fieldpath, messagediff, anything that uses protoregistry.MessageTypeResolver.FindMessageByName.

It's possible there are more things that are somehow affected, but I don't think that (e.g.) standard marshalling/unmarshalling are. That should continue to work.

[FGYFFFF]

Thanks, now I understand things better.

Thinking about your question:

My project only uses go structs generated by protobuf, and does not make rpc calls. So I would like to ask if there are any other side effects when namespace conflict is converted to warnning.

Then this conflict would lead to bugs any time a resolver is used. The cases I can think of where a Resolver is used:

• google.protobuf.Any.
• Other reflection use cases: fieldpath, messagediff, anything that uses protoregistry.MessageTypeResolver.FindMessageByName.

It's possible there are more things that are somehow affected, but I don't think that (e.g.) standard marshalling/unmarshalling are. That should continue to work.

Thanks, I get it.