Loyal-Young opened a new issue, #6055: URL: https://github.com/apache/rocketmq-dashboard/issues/6055
### Describe the bug On rocketmq-studio at 29fe48abc, useQueueBrowser increments its request generation on instance/topic changes but does not invalidate it on unmount. Both a pending queue-offset request and a pending message pull can therefore show a global error toast on an unrelated page after navigation. ### Reproduction Select a topic in Queue Browser, start loading queues (or pull a message from an already loaded queue), navigate away from the message page before the request completes, then let that request fail. The old request still passes requestSeqRef ownership checks and calls message.error. ### Expected behavior Late completions after leaving the page should be ignored. A failure while the browser is still mounted should remain visible and allow retry; StrictMode mount replay should not block normal loads. ### Evidence / scope The existing effect in components/QueueBrowser.tsx resets context but has no cleanup. Source inspection identifies the same lifetime for both request paths; deferred-response component tests will cover the error toast and a normal subsequent load/pull. Existing #5155 is navigation within queue lists and #5560 is localization; #5542 lists other async effects but does not include QueueBrowser. ### AI assistance AI assistance was used to inspect the request lifecycle and write this reproduction. -- 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]
