panic config /reference_config.go line 105

[ijustyce]

Code show as below, consumer field is a pointer so may be nil.

[DMwangnima]

@ijustyce ReferenceConfig must be defined within ConsumerConfig, as this dubbogo.yml shows:

dubbo:
  registries:
    demoZK:
      protocol: zookeeper
      timeout: 3s
      address: 127.0.0.1:2181
  consumer:
    references:
      GreeterClientImpl:
        protocol: tri
        interface: com.apache.dubbo.sample.basic.IGreeter

ReferenceConfig.Init() is invoked by ConsumerConfig.Init(). As a result, there is no problem with nil pointer.

[ijustyce]

@ijustyce ReferenceConfig must be defined within ConsumerConfig, as this dubbogo.yml shows:

dubbo:
  registries:
    demoZK:
      protocol: zookeeper
      timeout: 3s
      address: 127.0.0.1:2181
  consumer:
    references:
      GreeterClientImpl:
        protocol: tri
        interface: com.apache.dubbo.sample.basic.IGreeter

ReferenceConfig.Init() is invoked by ConsumerConfig.Init(). As a result, there is no problem with nil pointer.

In our case, I'm responsible for config module and one of my colleagues told me if there is no consumer config then panic at ReferenceConfig.Init. As ReferenceConfig.Init() is a public method so we can call it manually and root.Consumer may be nil as it is a pointer.

[DMwangnima]

@ijustyce Got it. We would fix it as soon as possible.
By the way, I appreciate that you could show us some code snippets about using ReferenceConfig directly without ConsumerConfig(removing business-related parts)? We are designing new API so that real user cases would help a lot.

[ijustyce]

@ijustyce Got it. We would fix it as soon as possible. By the way, I appreciate that you could show us some code snippets about using ReferenceConfig directly without ConsumerConfig(removing business-related parts)? We are designing new API so that real user cases would help a lot.

rootConfig, _ := config2.Bind[*config.RootConfig]("root-prefix")
//	our code ...
refConfig, _ := config2.Bind[*config.ReferenceConfig]("ref-prefix")
_ = rootConfig.Init()
_= refConfig.Init(rootConfig)
//	our code ...

It's hard to answer person after person's question and tell them how to avoid it, as we all know users often use things in ways we never thought of.

[DMwangnima]

Thank you very much for your case! By the way, after refConfig.Init(rootConfig), you just make use of refConfig.Export(cli) or wrap it with some additional procedures to make it act as call in other framework?

[ijustyce]

Thank you very much for your case! By the way, after refConfig.Init(rootConfig), you just make use of refConfig.Export(cli) or wrap it with some additional procedures to make it act as call in other framework?

Call refConfig.GenericLoad("xxx"), no wrap.