RockteMQ-AI commented on issue #2009: URL: https://github.com/apache/rocketmq-dashboard/issues/2009#issuecomment-5266587240
**Issue Evaluation** Category: `bug` | Status: **Confirmed** Verified against `rocketmq-studio` branch: `web/src/pages/ops/nameServerConfigDrift.tsx` (lines 49-60, 67-93). **Root Cause:** The bootstrap `useEffect` chains `listInstances()` → `listClusters()` → `runCheck()`. While `cancelled` guards state writes, `runCheck` uses its own `requestSequence` counter. If the instance changes during the bootstrap chain, the initial `runCheck` call can complete after a newer `selectInstance` has already incremented the sequence, but the bootstrap `runCheck` still writes its result because it incremented the sequence before the `selectInstance` did. The result is a stale diff displayed for a cluster the user is no longer viewing. **Impact:** NameServer Config Drift page — operators may see config diff results for the wrong cluster/instance. **Severity:** Medium — stale result display in a diagnostic page. An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager-bot* -- 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]
