RockteMQ-AI commented on issue #2739: URL: https://github.com/apache/rocketmq-dashboard/issues/2739#issuecomment-5460255955
**Issue Evaluation** Category: `bug` | Status: **Confirmed** This is a valid concurrency issue. The user status switch remains interactive during the pending API request, allowing rapid toggling that can produce overlapping mutations. If responses arrive out of order, the UI state and server state can diverge. **Root cause:** No per-user serialization of status mutations. Each toggle fires an independent request without disabling the control or tracking in-flight state. **Suggested fix:** - Track per-user pending state (e.g., `pendingStatusChanges` map keyed by user ID) - Disable the switch for that specific user while a request is in-flight - Use optimistic UI updates with rollback on failure - Ensure requests for the same user are serialized (queue or debounce) **Severity:** Medium — causes UI/server state inconsistency but no data loss. --- *Automated evaluation by RockteMQ-AI* -- 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]
