unbridled-41 commented on PR #4737: URL: https://github.com/apache/rocketmq-dashboard/pull/4737#issuecomment-5758625197
### Evidence (recorded at the PR head) 1. **Head / diff self-check** — `fix/redelivery-exact-source` @ `f1d1bd57`, one commit; `git show --numstat` = `MetadataService.java 22/0`, `MetadataServiceTest.java 68/0`. No unrelated file touched. 2. **Red on base** — with only the test file changed on `7ce9a682`: `mvn -B -ntp -o test -Dtest=MetadataServiceTest` → `Tests run: 55, Failures: 3, Errors: 0`, the three new cases failing because the redelivery proceeded with the truncated/Base64/capped payload. 3. **Green on branch** — `mvn -B -ntp -o test -Dtest='MetadataServiceTest,MessageServiceTest,MessageRedeliveryToolHandlerTest'` → `Tests run: 80, Failures: 0, Errors: 0`, `BUILD SUCCESS`. 4. **Full module suite on branch** — `mvn -B -ntp -o test` → `Tests run: 3054, Failures: 0, Errors: 17`. The 17 errors are pre-existing and environmental: Spring `ApplicationContext` failures from an unreachable MySQL in this sandbox (`CannotGetJdbcConnectionException: Communications link failure`), byte-identical to the pristine `rocketmq-studio` baseline measured in the same session (same 9 classes / 17 methods, `Tests run: 3051, Failures: 0, Errors: 17`). The delta 3051 → 3054 is exactly the three new tests. 5. **Style / module gates** — the `mvn test` build runs the project's checkstyle and compiler settings clean on this branch (no new warnings in the log). 6. **CI** — no workflow run was created for this head SHA; the repository's CI workflow fails to start for every PR at the moment (newest runs repo-wide are `CI pull_request startup_failure`, e.g. 35576031888 @ 2026-09-21T08:04:50Z). The local results above are the evidence. Duplicate check before submission: no open PR or issue mentions redelivery payload fidelity, `bodyTruncated` or the display caps; the sibling DLQ resend path already publishes raw bytes, which is what made this path's behavior stand out. -- 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]
