yyqdbngt opened a new issue, #1343: URL: https://github.com/apache/rocketmq-dashboard/issues/1343
## Problem `web/src/pages/studio/Ops.tsx` sends every VIP Channel and TLS switch change immediately without serializing requests. Rapid toggles can be processed out of order by the server, leaving persisted configuration different from the final switch state; an older failure can also roll back a newer choice. ## Expected behavior Serialize or generation-guard each setting so the latest operator choice owns UI feedback and the final server update. Disable or queue additional changes while an update is active. ## Scope - handle VIP and TLS independently - preserve optimistic feedback or use explicit loading state - cover out-of-order success/failure sequences This is independent of #1094, which concerns the redundant Update buttons. -- 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]
