messere1 opened a new issue, #1607: URL: https://github.com/apache/rocketmq-dashboard/issues/1607
### Description Alert Management allows rule mutations while a refresh is in flight. Both the mount load and manual refresh apply their response without a request-generation check. If a toggle, create, update, or delete completes before an older refresh response, that old response replaces the local rule list and visually reverts the completed mutation until another refresh. ### Steps to reproduce 1. Open Alert Management and start a refresh whose response is delayed. 2. Toggle an existing persisted rule while the refresh is pending. 3. Let the toggle request complete successfully. 4. Let the older refresh complete with the pre-toggle snapshot. ### Expected behavior A successful mutation invalidates older list requests, so their snapshots cannot overwrite the completed change. ### Actual behavior The stale refresh response replaces the rule list and restores the old enabled state. ### Proposed fix Track a monotonically increasing load request ID for mount and manual loads. After any successful mutation, invalidate older loads before applying the mutation result. Add an out-of-order refresh/toggle regression test. -- 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]
