Loyal-Young opened a new issue, #6900: URL: https://github.com/apache/rocketmq-dashboard/issues/6900
### Before Creating the Bug Report - [x] I searched existing issues and open pull requests for the session-overview failure path. - [x] Reproduced on the current `rocketmq-studio` branch. ### Studio Version `rocketmq-studio` at `a92c23144408cdf5729707050e9ecd9b75f1bad0`. ### Runtime Environment The behavior is in the User Management page; a component test uses a successful user-list request and a failing session-overview request. No broker is required. ### Describe the Bug On User Management, `loadUsers` requests the user list and session overview independently, but converts any overview failure to `null` with `getStudioUserSessionOverview().catch(() => null)`. The user list remains visible, while the overview card silently disappears. The page gives no indication that active-session counts are unavailable and no direct way to retry the overview. An operator can mistake the missing card for a feature or permission change. This is distinct from #6111 (the per-user session drawer) and #5375 (failed user-list rows). The overview endpoint can fail while the list succeeds. ### Steps to Reproduce 1. Open User Management as an administrator with `GET /api/users` succeeding. 2. Make the session-overview request fail transiently. 3. The user table appears normally, but the Session Overview card is absent and no error or retry is shown. ### What Did You Expect to See? Keep the successful user table and show a persistent error with a retry action for the independent overview read. A successful retry should restore the card. ### What Did You See Instead? The failed overview is silently treated as if there is no overview to display. ### Additional Context A focused component regression covers the partial failure and recovery. The proposed patch preserves successful list results and existing list pagination behavior. ### Are You Willing to Submit a Pull Request? - [x] Yes. -- 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]
