Aias00 opened a new issue, #1996: URL: https://github.com/apache/rocketmq-dashboard/issues/1996
## Problem The Studio instance page captures `loadInstances` when a create, update, or delete mutation starts. That callback also captures the search and instance-type filters from the same render. If an operator changes the list filters while the mutation request is still in flight, the mutation completion invokes the stale callback. Its refresh request uses the old filters and can overwrite the table with results that no longer match the visible search/type controls. ## Reproduction 1. Open the Studio instance list with the default filters. 2. Start creating, updating, or deleting an instance while the API request remains pending. 3. Change the instance-type or search filter. 4. Complete the mutation request. 5. Observe that the post-mutation list request uses the filter captured before step 3 and publishes mismatched rows under the current filter. ## Expected behavior Post-mutation refreshes must use the latest active instance-list filters. Existing request sequencing should continue preventing older responses from overwriting newer data. ## Scope Track 1 / instance management frontend. Add focused regression coverage for a filter change while a mutation is pending. -- 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]
