RockteMQ-AI commented on issue #2008: URL: https://github.com/apache/rocketmq-dashboard/issues/2008#issuecomment-5266587576
**Issue Evaluation** Category: `bug` | Status: **Confirmed** Verified against `rocketmq-studio` branch: `web/src/pages/instance/acl.tsx` (lines 389-406 for cluster config examination, lines 284-297 for credential reveal). **Root Cause:** 1. **Cluster ACL config examination** (`handleExamine`): Two rapid examinations for different cluster IDs can complete out of order. The later-started request may resolve first, and the earlier-started request then overwrites the state with stale data. No sequence counter or abort mechanism protects the `setClusterConfig` call. 2. **Credential reveal**: Rapid reveal/hide/reveal cycles can cause an in-flight `getAclUserCredentials` response to re-expand a row the user has since collapsed. The `revealing` guard is checked before the `await` but the `setCredentialsByUser` after the `await` has no staleness check. **Impact:** ACL management page — operators may see credentials or config for the wrong cluster/user, or see collapsed rows re-open unexpectedly. **Severity:** Low-Medium — confusing UX with potential information display mismatch. 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]
