tju-yxq opened a new pull request, #3162: URL: https://github.com/apache/rocketmq-dashboard/pull/3162
## What is the purpose of the change DLQ resend responses previously reported only aggregate counts. When a resend was `PARTIAL` or `FAILED`, operators could see how many messages failed but not which message IDs failed, where they were being sent, or why. ## What changed - add `DLQResendFailureVO` with `msgId`, resolved `targetTopic`, and concise `reason` - add `failures` and `failuresTruncated` to `DLQResendResultVO` - track individual resend outcomes in `RocketMQDLQProvider` for both time-range resend and selected-message resend - retain aggregate `matched`, `resent`, `failed`, `outcome`, `scanIncomplete`, and `failedQueueCount` - cap reported failures at 100 entries and expose truncation - include a bounded failure sample plus reported/truncated counts in the DLQ audit detail - show failed msgId, target topic, and reason in the DLQ page warnings for partial or failed resends ## Verification - focused backend tests: `RocketMQDLQProviderTest,DLQServiceTest,DLQControllerTest` passed - Checkstyle: 0 violations - focused frontend tests: `DLQPage.test.tsx`, `message.test.ts` passed (27 tests) - frontend lint: 0 errors (existing warnings only) - frontend production build: passed - `git diff --check`: passed - full server suite: 2,035 tests with 3 failures in `AuthCorsIntegrationTest` (2) and `AliyunInstanceProviderTest#getGroupProgressShouldMapLagRowsTest`; all three failures reproduce identically on a clean `upstream/rocketmq-studio` worktree and are unrelated to this patch Closes #3161 -- 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]
