zmuxuny opened a new issue, #6743: URL: https://github.com/apache/rocketmq-dashboard/issues/6743
### 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; Node 24.19.0; Vitest 4.1.10/jsdom. Real SystemAlerts component with controlled API promises. ### Connected RocketMQ Cluster Not applicable: frontend completion/pagination race, reproduced without a broker. ### Build Toolchain Node 24.19.0 ### Describe the Bug The End maintenance-window handler captures silencePage and silences before awaiting deletion. If the operator navigates while that deletion is pending, completion loads and selects the old page. Because this obsolete load is started after the newer navigation, the existing list request-order guard accepts it. ### Steps to Reproduce 1. Render 30 maintenance windows with 10 per page and navigate to page 2. 2. Click End on ID 11 and defer its deletion response. 3. Navigate to page 3 and wait for its rows. 4. Resolve deletion of ID 11. The real-component test keepsTheCurrentMaintenancePageWhenAnEarlierDeletionCompletesTest fails on unmodified production code. ### What Did You Expect to See? Keep the currently selected page 3; a mutation completion should not undo newer navigation. Preserve the existing last-item fallback only for the unchanged owning page. ### What Did You See Instead? The completion calls listAlertSilencesPage with page 2 and pageSize 10, moving selection and rows back to page 2. Regression expected page 3 and received page 2. ### Additional Context Root: web/src/pages/ops/systemAlerts.tsx deletion completion. Baseline controls for normal last-item fallback and out-of-order pagination both pass. Dedup: #4996/#4997 cover ordering of already-started list requests; this defect starts an obsolete request after newer navigation. Existing user contributions checked. AI assistance used for analysis and regression authoring. ### 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]
