youngkermit8-coder opened a new issue, #1597: URL: https://github.com/apache/rocketmq-dashboard/issues/1597
## Description The Dashboard request guard added for #1287 prevents a late response from overwriting the latest selection, but the already-rendered Dashboard data is not associated with the instance that produced it. After selecting another instance, `loading` becomes true while the previous `dashboard` object remains rendered because the loading skeleton is shown only when `dashboard` is null. Until the new request completes, the instance selector therefore names the new instance while the cards and cluster table still describe the previous instance/global view. ## Reproduction 1. Load the global Dashboard and wait for cluster data. 2. Select a specific instance whose Dashboard request is delayed. 3. Observe that the previous global cluster remains visible under the new instance selection until the request resolves. A frontend regression test reproduces this by holding the selected-instance promise pending and observing the previous cluster row. ## Expected behavior Dashboard data should carry the selected instance ID that produced it. Render it only while that ID matches the current selection, so switching instances immediately shows loading state instead of mislabelled data. Manual refreshes of the same instance may keep the current data visible, and the existing request-ID protection against late responses must remain unchanged. -- 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]
