iloveeyjafjalla opened a new issue, #6938: URL: https://github.com/apache/rocketmq-dashboard/issues/6938
## Summary The queue browser's results panel has one empty state for three different situations: before any load, after a load that came back with no readable queues (a write-only topic, or one whose read queue count is zero), and after a load that failed. In the last two it keeps asking the operator to "select a topic and click Load Queues" — the step they just performed — and the only failure signal is a toast that disappears. ## Why - `useQueueBrowser.loadQueues` clears `queues` and, on failure, only toasts (`web/src/components/QueueBrowser.tsx:84-116`); the hook has no notion of "a load ran" or "the load failed". - `QueueBrowserResults` picks its empty state from `state.queues.length === 0` alone (`:224-229`) and renders the single `queueBrowser.emptyHint` copy for all of them. - `RocketMQMessageProvider.getQueueOffsets` legitimately answers an empty list for a topic with no readable queues, so a successful empty answer and a failed request end in the same panel. ## Impact After a legitimately empty load the panel claims the operator never loaded anything; after a failed load a user who misses the toast cannot tell it apart from an empty topic, and there is no retry in the panel. ## Reproduction `web/src/components/__tests__/QueueBrowser.test.tsx` → the two new cases: ``` Unable to find an element with the text: /没有可读队列/ (empty load) Unable to find an element with the text: 加载队列信息失败 (failed load) ``` ## Expected A distinct explanation for a load that found nothing, and a persistent retryable error for a load that failed; the pre-load hint stays for the state it describes. -- 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]
