tju-yxq opened a new issue, #2599: URL: https://github.com/apache/rocketmq-dashboard/issues/2599
## Problem The DLQ page uses a local `cancelled` flag for its paginated group inventory: ```ts let cancelled = false; ``` This protects against unmount, but does not distinguish an older in-flight request from the latest one. When the selected instance, search term, page, page size, or refresh key changes while a slow request is still pending, the older response can resolve afterward and overwrite the newer page with stale groups, totals, selected-group constraints, or errors. The detail drawer and retry flow already have request-generation guards; the group inventory does not. ## Expected behavior - Sequence DLQ group requests with a request generation. - Ignore stale success and error responses after instance, filter, pagination, or refresh changes. - Keep clearing loading state only for the latest request. - Preserve existing instance-scope state reset, detail request sequencing, and retry request sequencing. ## Verification scope Add a regression test proving a stale response from the previous instance cannot replace the current instance’s group list. -- 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]
