-
Notifications
You must be signed in to change notification settings - Fork 13.1k
Open
Labels
area/ClientRelated to Nacos Client SDKRelated to Nacos Client SDKarea/Configkind/bugCategory issues or prs related to bug.Category issues or prs related to bug.version/3.xNacos 3.0 Architecture EvolutionNacos 3.0 Architecture Evolution
Milestone
Description
Describe the bug
A clear and concise description of what the bug is.
Due to the transformation of the empty and "public" namespaces on the server side, when the client's namespace is empty, the namespace in the ConfigChangeNotifyRequest does not match the client's namespace. As a result, the client is unable to receive configuration change notifications.
Expected behavior
A clear and concise description of what you expected to happen.
Actually behavior
A clear and concise description of what you actually to happen.
How to Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See errors
Desktop (please complete the following information):
- OS: [e.g. Centos]
- Version [e.g. nacos-server 1.3.1, nacos-client 1.3.1]
- Module [e.g. naming/config]
- SDK [e.g. original, spring-cloud-alibaba-nacos, dubbo]
Additional context
Add any other context about the problem here.
Metadata
Metadata
Assignees
Labels
area/ClientRelated to Nacos Client SDKRelated to Nacos Client SDKarea/Configkind/bugCategory issues or prs related to bug.Category issues or prs related to bug.version/3.xNacos 3.0 Architecture EvolutionNacos 3.0 Architecture Evolution