yuluo-yx opened a new issue, #2900: URL: https://github.com/apache/rocketmq-dashboard/issues/2900
### Problem\nQueue Browser relies on React loading state to represent in-flight operations. Two events delivered before the next render can both enter or , issuing duplicate API requests. The scalar pull state also cannot safely represent independent per-queue work.\n\n### Reproduction\n1. Select a topic.\n2. Dispatch two load actions in the same render turn, or two pull actions for the same queue.\n3. Observe two identical API calls.\n\n### Expected behavior\nOnly one queue-list request is active per current topic, and a queue key has at most one pull request while different queues remain independent.\n\n### Proposed fix\nUse synchronous refs for admission and a set of in-flight queue keys for rendering, with deferred-promise regression tests. -- 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]
