zbchi opened a new issue, #3163: URL: https://github.com/apache/dubbo-go/issues/3163
### ✅ Verification Checklist - [x] 🔍 I have searched the [existing issues](https://github.com/apache/dubbo-go/issues) and confirmed this is not a duplicate ### 🚀 Go Version 1.24.0 ### 📦 Dubbo-go Version v3.3.1 ### 🖥️ Server Configuration _No response_ ### 💻 Client Configuration _No response_ ### 🌐 Protocol Configuration _No response_ ### 📋 Registry Configuration _No response_ ### 💾 Operating System 🐧 Linux ### 📝 Bug Description When using the new dubbo.NewInstance API to initialize a Dubbo-go application, the Polaris router fails to build the router chain. It reports an error stating that the application name is missing, even though dubbo.WithName("myApp") has been explicitly configured. ### 🔄 Steps to Reproduce Using the following code to initialize either a consumer or a provider: ```go polarisAddr := "127.0.0.1:8091" ins, err := dubbo.NewInstance( dubbo.WithName("myApp"), dubbo.WithRegistry( registry.WithPolaris(), registry.WithAddress(polarisAddr), registry.WithNamespace("dubbogo"), registry.WithRegisterInterface(), ), dubbo.WithProtocol( protocol.WithTriple(), protocol.WithPort(21000), ), ) ``` The application fails to start with the following error logs: ```bash 2026-01-15 21:29:37 INFO dubbo-go/options.go:99 [Config Center] Config center doesn't start 2026-01-15 21:29:37 ERROR chain/chain.go:121 Build router chain failed with routerFactories key:polaris-router and error:polaris router must set application name ``` ### ✅ Expected Behavior The Polaris router should be able to retrieve the application name from the Instance or global configuration, and the router chain should be built successfully. ### ❌ Actual Behavior ```bash 2026-01-15 21:29:37 ERROR chain/chain.go:121 Build router chain failed with routerFactories key:polaris-router and error:polaris router must set application name ``` ### 💡 Possible Solution _No response_ -- 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]
