Loyal-Young opened a new issue, #6054:
URL: https://github.com/apache/rocketmq-dashboard/issues/6054

   ### Describe the bug
   
   On rocketmq-studio at 29fe48abc, MetricsExplorer filters data sources by 
instanceId, but only invalidates an already activated dataSourceKey. A source 
awaiting credentials lives separately in pendingDataSource. Changing the 
instance while that prompt is open keeps the now-unavailable source and its 
deferred history restore alive.
   
   ### Steps to reproduce
   
   1. Configure a Basic Auth data source bound only to instance A.
   2. On instance A, choose that source (or restore one of its history 
entries), leaving the credential dialog open.
   3. Change the explorer instance prop to B through navigation.
   4. The authentication dialog still offers the source bound only to A. 
Submitting it activates an unavailable key while runQuery falls back to the 
default source, so the displayed choice and executed query disagree.
   
   ### Expected behavior
   
   Cancel authentication for an unavailable source, discard the deferred replay 
and restore the previous profile/range/draft checkpoint. Authentication for a 
globally available source should still work after a transition.
   
   ### Environment / evidence
   
   Source inspection of MetricsExplorer.tsx (pendingDataSource, 
availableDataSources and handleAuthSubmit). A component regression with a prop 
transition and positive authentication controls will accompany the bounded fix; 
no live broker is needed. Searched existing auth-cancel and instance-scope 
changes (#4643, #4892) and pendingDataSource reports; this is the pending 
rather than activated source path.
   
   ### AI assistance
   
   AI assistance was used to inspect the lifecycle and formulate this 
reproduction.


-- 
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]

Reply via email to