Frun1na opened a new issue, #4928: URL: https://github.com/apache/rocketmq-dashboard/issues/4928
### 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 `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `1ef5d860` (upstream tip at the time of the report) deployed as: built from source ### Runtime Environment Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` (vitest for `web/`, JUnit for `server/`), not against a specific browser or deployment. ### Connected RocketMQ Cluster Not cluster-specific: the defect lives in the code path and reproduces on any deployment where the trigger condition below holds. ### Describe the Bug The DLQ message drawer's `total` is capped at the server scan limit (5000) while the group row on the same page shows the real dead-letter count. Nothing tells the operator that the drawer is a truncated window. ### Steps to Reproduce 1. Create a consumer group with more than 5000 dead-lettered messages. 2. The DLQ page shows 死信数量 8000 for the group. 3. Open 消息明细: the drawer shows 共 5000 条消息 with no warning; messages 5001+ cannot be listed, selected or resent. ### What Did You Expect to See? The drawer indicates the list is truncated (like the export path already does) so users do not mistake the cap for the full DLQ. ### What Did You See Instead? The capped total is presented as the whole list, silently. -- 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]
