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

   ## Current behavior
   On the Instance page, `componentDidMount` fetches both the table and 
analysis, but `componentDidUpdate` calls only `query()` when 
`currentNamespaceId` changes. `queryAnalysis()` is not invoked. The table can 
therefore show namespace B while the pie/line charts still display the previous 
response for namespace A.
   
   ## Evidence
   
https://github.com/apache/shenyu-dashboard/blob/b2586eac8ef16e5ceb2e0995554eaa49c5c40828/src/routes/System/Instance/index.js#L86
   
   `queryAnalysis` uses the current namespace at lines 153-160. The same 
behavior exists in the dashboard revision bundled with the reviewed ShenYu 
build (649bd45bd0a1609b09d4b32c9c90b85544515a72).
   
   ## Reproduction
   1. Open Instance management in namespace A with a distinct instance 
population.
   2. Switch to namespace B without remounting the page.
   3. Observe that the table fetches B but the analysis is not refetched.
   
   ## Acceptance criteria
   - [ ] Refresh table and analysis when the selected namespace changes.
   - [ ] Prevent delayed A responses from overwriting B results during rapid 
switching; scope responses to their request namespace.
   - [ ] Clear or explicitly mark old charts as loading while B is fetched.
   - [ ] Add component/model tests for A-to-B switching, out-of-order responses 
and empty/error results.
   - [ ] Coordinate the main-repo bundled dashboard update after the UI fix.
   
   Related: apache/shenyu#7695 tracks backend history aggregation across 
namespaces. Both are needed: corrected backend filtering alone cannot fix this 
missing UI request.
   
   Verified by source inspection; no browser reproduction was executed during 
issue preparation.
   


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