Loyal-Young opened a new issue, #6416: URL: https://github.com/apache/rocketmq-dashboard/issues/6416
### Before Creating the Bug Report - [x] Searched for duplicates. Searched invalid instance routes and route/fallback. #1112 handles initial unknown routes; this is the later same-section navigation gap after list-fetch dependencies were narrowed. #5798 concerns trailing slashes. - [x] This concerns RocketMQ Studio. ### Studio Version rocketmq-studio, 779b8c0e7aed2396d3cc72743dcd544ea48e9ae6. ### Runtime Environment Windows; Java 21 / Node 24. Reproduction will use the real schedule/service or React hook with controlled dependencies. ### Connected RocketMQ Cluster No live broker is required for this defect. ### Describe the Bug useInstanceFilter redirects invalid instance routes only when the instance-list request resolves. That effect excludes the selected route to avoid refetching. After the list is loaded, navigating within the same section to /instance/missing/topic or the unscoped /instance/topic therefore leaves that URL visible while selectedInstanceId silently falls back to the first instance. This makes the shown URL disagree with the target of operations. ### Steps to Reproduce Load /instance/known/topic and let listInstances complete. Navigate in the SPA to /instance/missing/topic without unmounting the page. The hook reports the first instance but does not replace the missing route. ### What Did You Expect to See? Reconcile the route whenever its selected instance changes using the already loaded inventory, without refetching the list on each switch. Preserve known selections, avoid redirecting before load success, and retain existing fallback behavior on initial entry. ### Are You Willing to Submit a Pull Request? - [x] Yes, including regression and positive-path tests. -- 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]
