Why can't I read the meta information of nacos
- Dominant language
- Go
- Stars
- 4.1k
- Forks
- 2.2k
- Avg merge
- 10d 12h
- Merged PRs (30d)
- 4
Description
I can get the meta information through the nacos api for the same parameters,But after debugging, I found that calling ClientWork.queryConfig in Dubbo admin and always returns "config data not exist,error code:300". Please tell me where the configuration is wrong,Thx!
### Environment
* Dubbo Admin version: 0.5.0
* Registry center detail (type and version): Nacos:2.2.0 deployed on linux
* Operating System version: window
* Java version: openjdk 11.0.12
### Steps to reproduce this issue
1. use nacos api i can get the meta info
2. dubbo-admin can't get it
Contributor guide
Research direction
Start at the ClientWork.queryConfig call in Dubbo Admin 0.5.0 and compare its request parameters with the successful Nacos 2.2.0 API request shown in the screenshots. Confirm the behavior on the listed Windows and Java 11 environment; done means the metadata query no longer returns error code 300 for the same parameters, with a regression check if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100