nacos-group / nacos-group/nacos-sdk-python
namespace "public" is "" in program,add_naming_instance and send_heartbeat cluster_name is different when this parameter is not entered
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 471
- Forks
- 155
- PR merge metrics
- No merged PRs in 30d
Description
why is the "public" namespace be ""
client.add_naming_instance("", "1.0.0.7", 8080)
client.add_naming_instance("test.service1", "1.0.0.7", 8080)
the cluster name will be None
client.send_heartbeat("test.service1", "1.0.0.7", 8080)
the cluster name will be DEFAULT
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the client.add_naming_instance and client.send_heartbeat entry points and reproduce the three calls shown in the issue. Trace how the omitted namespace and cluster_name values are assigned, then verify that the two operations handle these defaults consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100