nacos-group / nacos-group/nacos-sdk-python
nacos注册报错
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 471
- Forks
- 155
- PR merge metrics
- No merged PRs in 30d
Description
Traceback (most recent call last):
File "/data/llmservice-province/langchain_province/api.py", line 2174, in
regServer()
File "/data/llmservice-province/langchain_province/api.py", line 1971, in regServer
client.add_naming_instance(service_name=ServerName,
File "/data/llmservice-province/langchain_province/nacos/client.py", line 898, in add_naming_instance
resp = self._do_sync_req("/nacos/v1/ns/instance", {"example":"example"}, None, params, self.default_timeout, "POST", "naming")
File "/data/llmservice-province/langchain_province/nacos/client.py", line 702, in _do_sync_req
raise NacosRequestException("All server are not available")
nacos.exception.NacosRequestException: All server are not available
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 langchain_province/api.py at regServer() and langchain_province/nacos/client.py at add_naming_instance() and _do_sync_req(). Reproduce the registration failure and inspect the request path and server-availability conditions. Done means identifying the cause of the unavailable-server error and verifying a registration attempt succeeds or reports a specific actionable failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100