You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by GitBox <gi...@apache.org> on 2026/10/10 08:27:41 UTC
[GH] (rocketmq-dashboard/fix/cluster-registry-data-load): Workflow run "CI" failed!
The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/cluster-registry-data-load has failed.
Run started by GitHub user Frun1na (triggered by Frun1na).
Head commit for run:
f185bcd78a28b0b090d3b524f935e0ccc9bd316a / Apulupie <16...@users.noreply.github.com>
fix(cluster): report registry data that could not be loaded
Three registry loads on the cluster page cleared their state on failure, which the page renders as an
empty list:
- `loadRegistryClusters` (web/src/pages/cluster/index.tsx:222) also feeds the Broker, Proxy and NameServer
registry tabs, so a failed read claimed this deployment had registered nothing.
- `loadNsRegistry` (:242) left the NameServer registry table empty.
- the certificate load (:259) left the registry form's K8s ID field with no options; that Select does not
accept free text, so the field could not be filled at all.
The same page already reports a failed instance-list load with three retries and an `instanceLoadError`
banner, so a failure is now a state here too: each loader records its own failure (cleared on success) and
the page shows a warning with a retry that re-runs all three. The message reuses the existing
`common.fetchDataFailed` copy, so no user-facing text is added.
Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38037518985
With regards,
GitHub Actions via GitBox