AsperforMias opened a new issue, #3849:
URL: https://github.com/apache/dubbo-go/issues/3849

   ### What happened?
   
   A consumer that uses a config center only for dynamic rules (condition, tag 
and script routes) logs two ERROR lines on every start, although nothing is 
wrong:
   
   ```text
   [ConfigCenter][Nacos] failed to query rule, key= group=dubbo 
err=[client.GetConfig] param.dataId can not be empty
   [Router][Script] parse route config failed, error=EOF
   ```
   
   Expected: no error when `data-id` is not set and when the provider 
application has no script rule.
   Actual: both are reported as errors. This is the setup used with Dubbo Admin 
(config center with `group: dubbo` and no `data-id`), so users see errors right 
after following the Admin integration guide.
   
   Causes:
   
   1. `startGlobalConfigCenter` reads external configuration with `cc.DataId`. 
When `data-id` is unset the key is empty, Nacos rejects it, and `GetRule` logs 
the rejection as an error. ZooKeeper returns an empty value for the same call.
   2. When the script router subscribes to a provider application, it passes 
the current rule to `Process` as an update even when `GetRule` returned an 
empty value because no rule exists. Parsing the empty value fails with `EOF`.
   
   ### How can we reproduce it? (optional)
   
   1. Configure a consumer with a Nacos config center and only `group: dubbo` 
(no `data-id`), with no script rule for the provider application.
   2. Start the consumer; both lines appear in the log.
   
   ### Environment
   
   - dubbo-go: develop (ba671017)
   - Go 1.26.1, macOS
   - Nacos 2.5.2
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to