zmuxuny opened a new pull request, #6745: URL: https://github.com/apache/rocketmq-dashboard/pull/6745
### Which Issue(s) This PR Fixes Fixes #6743 ### Brief Description Ending a maintenance window can finish after the operator navigates to another page in the dialog. The completion previously used the old page/row snapshot to launch a new list request, taking the user back to that obsolete page. Existing list response-order guards cannot reject a request started later by the old mutation. Capture the list request generation when deletion begins; only perform the page-changing refresh if no newer page request owns the dialog. This also protects a newer page whose response is still pending, while retaining the normal last-item previous-page behavior. The deletion itself is unchanged. Distinct from #4996/#4997, which concern responses to already-started list requests. ### How Did You Test This Change? - Baseline a92c2314 red: after navigating from page 2 to page 3 during deletion, completion requested page 2 instead of preserving page 3. - `cd web && npx vitest run src/pages/ops/__tests__/SystemAlertsPage.test.tsx --maxWorkers=1`: 31/31 pass, independently rerun. Includes resolved/pending page-3 regressions and existing last-item fallback control. - `npx tsc -b --force`: pass. - Changed-file ESLint: zero errors; one existing fast-refresh warning. - `npm run build`: pass, including license check (132 actual components, 139 license files). - Prettier and `git diff --check`: pass. - Node24.19.0. Full frontend suite and Java tests not run locally; no Java changes. ### Checklist - [x] One coherent change - [x] Conventional Commit subject - [x] Regression tests added with Test suffix - [x] No new UI text, source files, API changes, or documentation requirements AI-assisted implementation and tests, reviewed and independently verified. -- 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]
