Frun1na opened a new issue, #4913: URL: https://github.com/apache/rocketmq-dashboard/issues/4913
### 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 In the DLQ detail drawer, 批量重发选中 compares only `outcome`/`failed`/`resent`. A message selected but no longer resolvable (purged in the meantime, embedded broker no longer in the topology) comes back as `matched < selected`, `failed = 0` and the UI still shows a green success toast. ### Steps to Reproduce 1. Open the DLQ message drawer for a group and select dead-letter messages. 2. Let the messages be purged (or the broker leave the topology) between listing and resend. 3. Click 批量重发选中. The server returns `matched=0, resent=0, failed=0, outcome=PARTIAL` (with `scanIncomplete=true` where applicable). 4. A green toast `重发完成：成功 0 条` is shown and the dropped selections are never mentioned. ### What Did You Expect to See? A warning that not all selected messages could be resolved and resent, mirroring the time-range resend handler which already checks `scanIncomplete`. ### What Did You See Instead? A success toast; the gap between selected and resent is invisible. -- 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]
