tju-yxq opened a new pull request, #6163:
URL: https://github.com/apache/rocketmq-dashboard/pull/6163

   > Resubmission of #5218 — the original PR and its linked issue were closed 
by the repo's 7-day stale bot while awaiting review, not because the change was 
rejected. The fix is rebased unchanged onto the current `rocketmq-studio` head 
(5e4c39b0) and the linked issue is still reproducible on trunk.
   
   > The original linked issue met the same stale fate and could not be 
reopened, so this PR fixes a fresh report of the same problem (see the linked 
issue).
   
   ### Which Issue(s) This PR Fixes
   
   - Fixes #6162
   
   ### Brief Description
   
   The row's **验证 / Verify** action now opens the message detail modal directly 
on the verification tab, which renders the real per-group verdicts (group, 
delivery status, consume time, retry count) from the trace's `consumerStatus` — 
replacing the "interface not available" warning. Opening the modal on the 
verification tab, or switching to it, triggers the trace load exactly like the 
trace tab (same generation guard against late responses), and the verification 
table shows its loading state while the trace loads. No backend change and no 
fabricated verdicts: the tab renders whatever the trace reports.
   
   ### How Did You Test This Change?
   
   Run on the branch (`70ab5252`, based on `master` @ `0228dad5`):
   
   ```
   cd web && npm test -- MessagePage --run
   Test Files  2 passed (2)
        Tests  33 passed (33)
   
   cd web && npm run lint
   0 errors (11 pre-existing warnings in unrelated files)
   ```
   
   New coverage: the former stub test ("does not report consume verification 
success without a backend API") is replaced by "shows the per-group consume 
verdict when the verify action is used" — it mocks the trace with two groups 
(one consumed, one failed with retries), clicks **验证**, and asserts the 
verdicts render, the trace lookup was called for the row's message, and neither 
the "not available" warning nor any fabricated success appears. The existing 
trace-loading and late-response regression tests keep passing unchanged (the 
load path is shared with the trace tab).
   
   ### Checklist
   
   - [x] One coherent change; unrelated modifications are not bundled in
   - [x] Commit subject follows Conventional Commits
   - [x] Tests added or updated for non-trivial changes, test methods named 
`...Test`
   - [x] New UI text has both Chinese and English entries under `web/src/i18n/` 
(no new UI text in this change)
   - [x] Architecture constraints stay green (`mvn test` runs the ArchUnit 
checks)
   - [x] New source files carry the ASF license header
   - [ ] Documentation touched where behaviour changed (README / `docs/` / 
in-app help)
   
   


-- 
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]

Reply via email to