The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/acl-remote-rules-cluster-scope has failed. Run started by GitHub user Frun1na (triggered by Frun1na).
Head commit for run: 8d8ab04aef690361d7088cd4cbe339ad8fd3161d / Apulupie <[email protected]> fix(acl): read remote rules only from the configured cluster #6196 narrowed discoverClusters, refreshClusterDetail and discoverBrokers to the cluster configured for the instance, but ApacheAclReadService.listRules still walked every entry of the shared brokerAddrTable. On an instance bound to cluster A whose NameServer also serves cluster B, the remote-rule read returned cluster B's brokers in policiesByBroker / failuresByBroker, so the selected instance surfaced another cluster's ACL. The broker set is now resolved once through the same configuredClusterName lookup the cluster provider uses, and a configured cluster whose membership is missing from the topology fails closed with 503 instead of falling back to the whole table - the same condition and status discoverBrokers raises. An instance that names no cluster keeps reading every broker of the endpoint. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38336847137 With regards, GitHub Actions via GitBox
