Oxidaner opened a new pull request, #1621:
URL: https://github.com/apache/dubbo-admin/pull/1621

   Closes #1578
   Depends on #1620
   Parent: #1491
   Design discussion: #1541
   
   Adds a Resource-only service availability index and common discovery 
contract for Nacos and ZooKeeper. `ACTIVE` requires an available Provider for 
the selected protocol; incomplete sync or evidence is `UNKNOWN`. Confirmed 
`INACTIVE` tools remain visible for a configurable grace period (60 seconds by 
default). Publish validation rejects protocol incompatibility only with 
complete evidence from available Providers; all other incomplete/down cases 
remain warnings.
   
   The discovery adapters normalize interface-level and application-level 
registrations, their health and service revisions into the shared instance 
Resources. Synchronization state tracks initial processing, watcher failures, 
normalization errors and generation changes across snapshot reads. ZooKeeper 
watch loss forces a full relist before returning to healthy. The `FilterTools` 
helper is ready for the business MCP `tools/list` runtime integration in #1580.
   
   Verification:
   - `go test ./pkg/mcp/availability ./pkg/console/service 
./pkg/core/discovery/... ./pkg/core/resource/apis/mesh/v1alpha1 
./pkg/core/controller ./pkg/discovery/nacos2/... ./pkg/discovery/zk/... 
-count=1` (167 tests)
   - `go test -race ./pkg/mcp/availability ./pkg/core/discovery 
./pkg/discovery/zk/listerwatcher ./pkg/discovery/zk/zkwatcher 
./pkg/discovery/nacos2/listerwatcher -count=1` (37 tests)
   - `git -c core.whitespace=cr-at-eol diff --cached --check`
   


-- 
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]

Reply via email to