Frun1na opened a new issue, #6504: URL: https://github.com/apache/rocketmq-dashboard/issues/6504
### 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: `779b8c0e` 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 a stubbed trace response in a unit test access mode: not applicable deployment: not applicable ### Describe the Bug The message trace diagnostics panel lists at most eight findings and does not say that it is truncating them, although the health score it shows beside them is computed from every finding (`web/src/pages/instance/message.tsx:194`): ```tsx const issueData = diagnostics.issues.slice(0, 8); ``` `calculateScore`/`maxStatus` in `web/src/utils/messageTraceDiagnostics.ts` penalise all issues, so a trace with more than eight findings shows a lowered score whose remaining findings are invisible — the reader cannot account for the score. The same UI pattern elsewhere in the suite already discloses the cut: the topic page's route diagnostics render `<Tag>+{issues.length - 3}</Tag>` after the first three (`web/src/pages/instance/topic.tsx:894`). ### Steps to Reproduce Reproduced by a component test rather than against a cluster: 1. Render the message page and open the trace tab of a message whose trace has nine failing stages (each failing stage produces one finding) and one successful delivery. 2. Look at the diagnostics panel's tag row. 3. Eight findings are tagged, the ninth is not, and nothing says that more exist — while the health score counts it. ### What Did You Expect to See? The tag row should disclose how many findings it does not show, the way the topic page's route tags do. ### What Did You See Instead? Eight tags and no hint that the score was computed from more findings. ### Additional Context - A fix with a regression test follows in a pull request. - The case is pinned by a unit test that fails without the fix: `Unable to find an element with the text: +1`. ### 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]
