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

   ## What is the purpose of the change
   
   Closing a queue message card while a replacement pull is pending does not 
invalidate that request. A late response can reopen the dismissed card or 
display an obsolete error.
   
   Discard completions belonging to dismissed pulls while allowing the operator 
to request the queue again immediately.
   
   ## Brief changelog
   
   - Track each in-flight queue pull with a unique ownership token.
   - Invalidate only the dismissed queue's pull, preserving requests for other 
queues.
   - Prevent stale responses from overwriting newer results or releasing their 
loading locks.
   - Add four regression tests covering dismissal, independent queues, 
immediate retry and late failures.
   
   ## Verifying this change
   
   - `cd web && npm test -- src/components/__tests__/QueueBrowser.test.tsx 
src/pages/instance/__tests__/MessagePage.test.tsx` — 37 tests passed.
   - `cd web && npx tsc -p tsconfig.app.json --noEmit --composite false 
--incremental false` — passed.
   - `cd web && npx eslint src/components/QueueBrowser.tsx 
src/components/__tests__/QueueBrowser.test.tsx` — no errors; one existing Fast 
Refresh warning.
   - `cd web && npx prettier --check src/components/QueueBrowser.tsx 
src/components/__tests__/QueueBrowser.test.tsx` — passed.
   - `git diff --check` — passed.
   
   All four new regressions failed before the fix and passed afterward. 
Validation used mocked APIs; the full frontend suite and live Broker 
integration were not run.


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