Frun1na opened a new issue, #6130: URL: https://github.com/apache/rocketmq-dashboard/issues/6130
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `rocketmq-studio` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `5e4c39b0` deployed as: reproduced by a unit test against that commit (the affected code is the web client) ### Runtime Environment OS: Ubuntu on WSL2 MySQL: not applicable — the defect is in the web client's rendering browser: not applicable — reproduced in a jsdom unit test (vitest + Testing Library) ### Connected RocketMQ Cluster RocketMQ version: not applicable — reproduced with the page's own record shape in a component test access mode: not applicable deployment: not applicable ### Describe the Bug The audit risk panel's "Repeated Failed Targets" table shows at most three of a target's failing operation types and does not say it is truncating them (`web/src/pages/ops/AuditRiskInsights.tsx:156`: ```tsx {operationTypes.slice(0, 3).map((operationType) => ( ``` The row's severity is derived from the full list — `buildHotTargets` flags a target as a warning when any of its operation types is high risk (`auditRiskInsightModel.ts:240-244`, `existing.operationTypes.some(isHighRiskAuditOperation)`). So a target that is flagged precisely because of a high-risk operation can be listed without showing that operation: the reader sees the warning and cannot tell why. Nothing indicates that the visible three are a subset. ### Steps to Reproduce Reproduced by a component test with the record shape the page already receives: 1. Render `AuditRiskInsights` with four failed audit records that share one `(clusterId, resourceType, target)` and carry four different operation types, the fourth being `CLEAR_ACKNOWLEDGED_SYSTEM_ALERTS` (high risk). 2. Look at the "Repeated Failed Targets" card. 3. The operation-type cell shows the first three types only; the high-risk one that made the row a warning is absent, with no hint that more exist. ### What Did You Expect to See? Either every failing operation type of the target, or an explicit indication that only the first three are shown. ### What Did You See Instead? Three tags and no indication that the list was cut — including when the hidden ones are the reason the target is flagged. ### Additional Context - A fix with a regression test follows in a pull request. - The case is pinned by a component test that fails on `5e4c39b0` (`Unable to find an element with the text: 清除已确认告警`). ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
