zmuxuny opened a new issue, #6746: URL: https://github.com/apache/rocketmq-dashboard/issues/6746
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version rocketmq-studio a92c23144408cdf5729707050e9ecd9b75f1bad0 ### Runtime Environment Linux, Node24.19.0, Vitest4.1.10/jsdom. Real AlertsPage and Ant Design with controlled synthetic API responses. ### Connected RocketMQ Cluster No live broker or database required; frontend response-state reproduction. ### Build Toolchain Node24.19.0; one Vitest worker. ### Describe the Bug Successful single and bulk status toggles patch visible rule objects without reconciling the server-backed status filter, page or total. Disabling a rule in Enabled-only results leaves it visible and actionable with its switch off. ### Steps to Reproduce 1. Load an enabled rule (for example Broker disk usage). 2. Select Enabled-only status. 3. Disable the rule using its switch, or select it and use Bulk Disable. 4. Let the service successfully return enabled:false. ### What Did You Expect to See? Reconcile the filtered page and total with the server, excluding rules outside enabled:true and backfilling/paginating as appropriate. ### What Did You See Instead? The disabled row remains visible, total remains 1, and no new list request occurs. Two real-component regressions (single and bulk) fail on the retained visible row against untouched production code. Existing unfiltered bulk-toggle and filter-fetch controls pass. ### Additional Context Source: web/src/pages/ops/alerts.tsx single/bulk handlers around lines533–540 and564–578. Searched open/closed issues and PRs for status filter, toggle+filter/refresh, enabledFilter, enabled-only. #4515/#4518 protects controls during a pending filter load; #1607/#1635 prevents older list snapshots replacing completed mutations. Neither reconciles membership after the successful mutation. Own #4457/#5546 concerns backend policy, not this frontend state. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
