Yanghanrui666 opened a new pull request, #4677:
URL: https://github.com/apache/rocketmq-dashboard/pull/4677

   ### Which Issue(s) This PR Fixes
   
   - Fixes #3167
   
   ### Brief Description
   
   Load the current DLQ page's topic statistics through a bounded 8-worker 
daemon pool while preserving deterministic page order. Each stats lookup is 
capped at 5 seconds; a timeout or failure only marks that row `UNAVAILABLE`, so 
the remaining rows are still returned.
   
   The frontend now keeps the visible input separate from the request value, 
debounces typing by 300 ms, and still submits immediately on Enter or the 
search action.
   
   This also supersedes the closed #3168 and fixes its review finding: fallback 
rows preserve `groupName` and `dlqTopic`, so failed stats calls no longer 
produce blank table rows. Unexpected task failures are logged for diagnosis.
   
   ### How Did You Test This Change?
   
   Backend (targeted):
   
   ```
   cd server
   mvn -B -ntp -Dmaven.compiler.proc=full '-Dtest=RocketMQDLQProviderTest' test
   ```
   
   Result: 42 tests passed; checkstyle reported 0 violations.
   
   Frontend (targeted):
   
   ```
   cd web
   npm test -- src/pages/instance/__tests__/DLQPage.test.tsx --pool=threads 
--maxWorkers=1
   ```
   
   Result: 23 tests passed.
   
   `git diff --check` passed.
   
   ### 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] No new UI text was added
   - [ ] Architecture constraints stay green (`mvn test` runs the ArchUnit 
checks)
   - [x] No new source files were added
   - [x] No documentation change required<!-- Make sure the base branch is 
`master`: that is the RocketMQ Studio trunk. -->
   
   ### Which Issue(s) This PR Fixes
   
   <!-- Link the issue with a keyword so it closes on merge. Trivial fixes need 
no issue.
        
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
 -->
   
   - Fixes #<issue-id>
   
   ### Brief Description
   
   <!-- What changes and why. Keep it short — the diff already shows how. -->
   
   ### How Did You Test This Change?
   
   <!-- Paste the commands you ran and what they printed. Typical verification:
        backend  `cd server && mvn -B -ntp test`   (integration tests need 
MySQL 8, see CONTRIBUTING.md)
        frontend `cd web && npm test && npm run lint && npm run build`
        A pull request with no verification will not be merged. -->
   
   ### Checklist
   
   - [ ] One coherent change; unrelated modifications are not bundled in
   - [ ] Commit subject follows Conventional Commits (`feat:` / `fix:` / 
`refactor:` / `chore:` / `docs:` / `perf:`)
   - [ ] Tests added or updated for non-trivial changes, test methods named 
`...Test`
   - [ ] New UI text has both Chinese and English entries under `web/src/i18n/`
   - [ ] Architecture constraints stay green (`mvn test` runs the ArchUnit 
checks)
   - [ ] 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