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

   ### Before Creating the Bug Report
   
   - [x] I have searched the [open 
issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository 
and believe that this is not a duplicate.
   - [x] This is a defect in RocketMQ Studio, not a usage question and not a 
defect in another Apache RocketMQ repository.
   - [x] I can reproduce this on the current `rocketmq-studio` branch, or I 
have stated the exact version I am running below.
   
   ### Studio Version
   
   branch: `rocketmq-studio`
   git commit id: `5e4c39b0`
   deployed as: reproduced by a unit test against that commit (the affected 
code is the web client)
   
   ### Runtime Environment
   
   OS: Ubuntu on WSL2
   MySQL: not applicable — the defect is in the web client
   browser: not applicable — reproduced in a jsdom unit test (vitest + Testing 
Library)
   
   ### Connected RocketMQ Cluster
   
   RocketMQ version: not applicable — reproduced with a stubbed session 
endpoint in a unit test
   access mode: not applicable
   deployment: not applicable
   
   ### Describe the Bug
   
   The LiteTopic session drawer reports a failed session read as a session 
without data.
   
   `web/src/pages/studio/LiteTopic.tsx` (base `5e4c39b0`):
   
   - `handleViewSessions` (`:289-309`) only toasts and clears the detail on 
failure
     (`setSessionData(null)`, `liteTopic.fetchSessionFailed`) and collects no 
failure state;
   - `renderSessionContent` (`:622-628`) renders `t('common.noData')` — "暂无数据" 
— whenever `sessionData` is
     absent, so the drawer body reads as "this session has no data".
   
   The session is opened from a table row that lists it, and the drawer 
contains no retry, so the only hint is a
   toast that fades. The genuinely empty case is indistinguishable from the 
failed read.
   
   ### Steps to Reproduce
   
   Reproduced by a unit test rather than against a cluster; the endpoint stub 
is the only setup needed:
   
   1. Render the LiteTopic page with `queryLiteTopicSession` rejecting 
(equivalently: click 查看会话 while
      `GET /lite-topic/sessions/{sessionId}` fails, e.g. a transient error).
   2. Click 查看会话 on a row.
   3. The drawer body shows "暂无数据".
   
   ### What Did You Expect to See?
   
   The drawer should say the session detail could not be loaded and offer a 
retry.
   
   ### What Did You See Instead?
   
   "暂无数据" inside the drawer after a transient toast.
   
   ### Additional Context
   
   - A fix with a regression test follows in a pull request.
   - The case is pinned by a unit test that fails on `5e4c39b0`
     (`expected document not to contain element, found <div …> 暂无数据 </div>`) 
and asserts the retry, which
     re-reads the session and renders its content.
   
   ### Are You Willing to Submit a Pull Request?
   
   - [x] Yes, I am willing to submit a pull request.
   


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