zmuxuny opened a new issue, #6742: URL: https://github.com/apache/rocketmq-dashboard/issues/6742
### 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 LiteTopic component with controlled API promises. ### Connected RocketMQ Cluster Controlled Apache instance fixture; no live broker is needed for this frontend race. ### Build Toolchain Node 24.19.0 ### Describe the Bug A pending TTL update retains the list filters from the moment Submit was clicked. If the operator cancels the dialog and searches another pattern before the update finishes, the successful completion invokes fetchData with obsolete filters. It starts a newer list request, so existing response-order guards accept the obsolete inventory and replace the current results. ### Steps to Reproduce 1. Load order-* LiteTopics and open Extend TTL with one Apache instance. 2. Submit 7200 seconds while deferring the update response. 3. Cancel the dialog, search for payment, and wait for payment-* results. 4. Resolve the original TTL update. The new component regression keepsTheCurrentQueryWhenAnEarlierTtlUpdateCompletesTest fails on unmodified production code. ### What Did You Expect to See? Preserve the current submitted query and its results. A refresh after mutation should use the current submitted query, not captured filters or unsent input text. ### What Did You See Instead? The final list API call receives [undefined, undefined] rather than [payment, undefined], replacing the filtered results with the old unfiltered inventory. ### Additional Context Root: web/src/pages/studio/LiteTopic.tsx, handleUpdateTtl completion. Existing owning-instance submission control passes. Dedup checked #2889 (duplicate submission), #6356/#6373 (capability retry) and #6720/#6721 (instance lookup completion); none covers TTL update completion restoring old list-query ownership. 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]
