youngkermit8-coder opened a new pull request, #1602: URL: https://github.com/apache/rocketmq-dashboard/pull/1602
## Summary - associate each successful Dashboard response with the instance selection that produced it - render cached Dashboard data only while its instance ID matches the current selector - keep same-instance manual refreshes visible and preserve the existing late-response request guard ## Root cause The request-ID guard from #1287 prevents an earlier response from overwriting a later selection, but the existing `dashboard` object had no instance ownership. When the user selected another instance, `loading` became true while the previous cards and cluster table remained rendered because the skeleton was shown only when `dashboard` was null. The selector could therefore name Instance B while the page still displayed global or Instance A data until Instance B's request completed. ## Impact Changing the instance selection now immediately hides data owned by the previous scope and shows the loading skeleton. A manual refresh for the same instance still keeps its current data visible, avoiding unnecessary blanking. ## Verification - `npm test -- src/pages/home/__tests__ --run` — 2 files, 4 tests passed - `npm exec eslint -- src/pages/home/dashboard.tsx src/pages/home/__tests__/DashboardPage.test.tsx` — passed - `npm run build` — passed - current base alone: 493/494 tests, with the sole known Topic no-instance Spinner failure fixed by #1578 - this branch combined with #1578: 90 files, 494/494 tests passed Closes #1597 -- 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]
