Aias00 opened a new issue, #1115:
URL: https://github.com/apache/rocketmq-dashboard/issues/1115

   ## Problem
   
   The instance repository stores entries in a `ConcurrentHashMap` and returns 
its iteration order from all list and search methods. That order is 
unspecified. Studio uses the first returned instance as the default instance 
context, so the same route can target a different instance after mutations or a 
restart.
   
   ## Expected behavior
   
   All instance list queries should return a deterministic order: name 
ascending, then ID ascending as a tie breaker.
   
   ## Scope
   
   - Apply the same stable ordering to unfiltered, type-filtered, 
search-filtered, and combined list queries.
   - Add repository-level regression coverage.
   - Preserve existing filtering behavior and response shape.
   
   ## Track
   
   Track 1 / unified multi-instance management.


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