RockteMQ-AI commented on issue #1996: URL: https://github.com/apache/rocketmq-dashboard/issues/1996#issuecomment-5264707474
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The stale callback issue in the Studio instance list is a valid race condition: **Problem:** When a mutation (create/update/delete) is in flight and the operator changes filters, the mutation completion uses the stale `loadInstances` callback captured at mutation start, causing the post-mutation refresh to use outdated filters and display mismatched results. **Root Cause:** Callback closure captures filter state at render time, not at invocation time. **Impact:** Studio instance management UI - operators see incorrect filtered results after concurrent filter changes and mutations. **Severity:** Medium - UX issue that can confuse operators about the actual state of instances. This is a valid bug. The fix should: - Ensure post-mutation refreshes use the current active filters - Maintain existing request sequencing to prevent older responses from overwriting newer data - Add regression tests for filter changes during pending mutations --- *Automated evaluation by RockteMQ-AI* -- 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]
