unbridled-41 commented on PR #3151:
URL:
https://github.com/apache/rocketmq-dashboard/pull/3151#issuecomment-5642622258
## Evidence-chain completion (head SHA + net diff self-check)
The two earlier comments predate the current six-item evidence standard and
lack two items: CI evidence pinned to this PR's current head SHA, and a
net-diff self-check against the base. Filling exactly those two items (numbers
re-verified today); the red→green, module, full-suite and build results in the
comments above remain valid for their stated dates.
**CI (current head)**: this PR's head SHA
`43378e6f62aa233027b798fd09c45658c4ce31b4` has exactly one workflow run — "CI"
(pull_request), run id 34355781872, conclusion `startup_failure` (created
2026-09-09T13:14:01Z); the check-runs API for the head commit returns
`total_count=0`. The upstream workflow fails at startup for every branch and
event in this repository, so no CI signal is available; all verification was
run locally (see the two comments above).
**Net diff self-check** (files API for this PR, cumulative vs
`rocketmq-studio` @ `6c24d2ed`, 4 files, +236/−8):
```
web/src/i18n/translations.ts +4/−0
web/src/pages/cluster/__tests__/ClusterPage.test.tsx +180/−1
web/src/pages/cluster/certs.tsx +1/−1
web/src/pages/cluster/index.tsx +51/−6
```
- `index.tsx` / `ClusterPage.test.tsx` / `translations.ts` are the fix and
its regressions (see the first comment).
- `certs.tsx` +1/−1 is a lint-driven parenthesization (`map[status] ??
{...}` wrapped in parentheses, `no-mixed-operators`), applied by the
commit-time lint hook; behavior-neutral, no test impact.
- No other files are touched, and the two workspace-note files that were
accidentally staged and removed during the base-advancing merge (see the
Disclosure above) net out to zero in this diff.
--
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]
