yyqdbngt opened a new pull request, #2933: URL: https://github.com/apache/rocketmq-dashboard/pull/2933
## Summary - `useQueueBrowser` now tracks in-flight pulls with a `Set` of queue keys instead of a single key, so concurrent pulls each keep their own spinner - Clearing a pull's indicator only removes its own key, so one pull finishing no longer clears the indicator of another pull still in flight - Adds a regression test: start two pulls on different queues, let the first finish first, and verify the second keeps its indicator until it completes ## Why `pulling` was a single `string | null`. Starting a second pull overwrote the first key (hiding its spinner while it was still in flight), and when the first pull's `finally` ran it called `setPulling(null)`, clearing the second pull's spinner even though the second request had not resolved — the "查看" button lost its loading state while the pull was still running. ## Testing - `./node_modules/.bin/vitest run src/components/__tests__/QueueBrowser.test.tsx` → 7 passed (1 new; fails without the fix) - `./node_modules/.bin/tsc --noEmit` → clean - `./node_modules/.bin/eslint src/components/QueueBrowser.tsx src/components/__tests__/QueueBrowser.test.tsx` → 0 errors (2 pre-existing react-refresh warnings for the exported hook, same precedent as other page files) -- 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]
