lizhimins opened a new pull request, #7327:
URL: https://github.com/apache/rocketmq-dashboard/pull/7327

   ### Summary
   
   One squashed commit carrying the AI conversation upgrade round and the 
console density/label round, rebased on the current `rocketmq-studio` head.
   
   **AI conversation**
   - Assistant bubbles render as a fixed-width column; streaming no longer 
resizes them token by token.
   - Tool cards collapse to ONE line: the input/output sections became inline 
switches on the header row, and a running call shows a live stopwatch that 
turns warning at 5 min and error plus a "may be timing out" tag at 10 min.
   - Tool output is rendered by shape: a JSON row list (top-level or a 
single-array envelope such as `{"items":[...]}`) and CSV-shaped text become 
tables, other JSON is pretty-printed and colour-coded, and the raw transport 
string stays one click away.
   - Follow-up suggestions: after a run finishes the server makes one small 
completion over the last question/answer (`POST 
/api/ai/conversations/{id}/followups`) and the page renders up to three 
clickable chips; clicking one is an ordinary new turn. Failure is silence 
(empty list), never an error banner.
   - Messages typed while a run is in flight queue in the composer (edit / 
remove / send-next) and drain in order once the run ends.
   - A conversation minimap (one tick per transcript row, hover preview, click 
to jump) navigates long transcripts.
   - The context meter uses the provider-reported usage of the newest run 
(input+output tokens, now denormalised into the timeline envelope) instead of a 
pure transcript estimate, and labels its provenance (measured vs estimated) 
plus the remaining budget.
   - The persisted agent-engine preference resets to `claude-code` (storage 
version bump): a stale `qoder` preference failed every run with a bare failure 
tag whenever the CLI had no login state in the image.
   
   **Console density and labels**
   - Alert deliveries and alert events keep one line per row; alert events is 
now a table with checkbox multi-select, batch acknowledge, and expand-row 
detail (ack info, suppression reason, labels, delivery records, related 
events). Clicking 投递记录/关联事件 opens that row.
   - The create-rule modal lost ~40% of its height: field help moved into label 
tooltips and the notification template editor plus preview live in a collapsed 
panel whose header still shows the readiness tag.
   - Certificate k8s IDs truncate with a tooltip and a copy action.
   - Changing the Broker flush disk type now warns inline that it only applies 
after a restart, and the submit asks for a second confirmation naming 
`flushDiskType (from → to)`.
   - The consumer-group health summary labels name their units and calibers 
("Queue 进度: 9 个 Queue / 2 个 Topic" instead of the ratio-looking "Queue 覆盖: 9 / 
2"), each with a tooltip.
   - Layout: the sider menu scrolls on short viewports (entries below the fold 
were unreachable); below the md breakpoint the navigation moves into a drawer 
behind a hamburger with a compact top bar.
   
   ### Test plan
   
   - [x] `web`: `npm run build` + full `vitest run` (162 files) + `eslint` 
clean on the changed files.
   - [x] `server`: full `mvn test` except the three integration tests that 
require a local MySQL (they fail on any dev box without one; CI provides it). 
AI unit/slice suites green, including the two `@WebMvcTest` slices updated for 
the new controller dependency.
   - [x] Verified in a real deployment (headless Chromium against the test 
cluster): streaming bubble width constant over 199 samples; queue drains after 
the run; follow-up chips appear and send as a new turn; minimap tick count 
equals bubble count; context bar shows measured usage; tool tables render 5x9 
for `rmq.topic.list`; alert table rows 41px with batch acknowledge; flush-disk 
warning and second confirmation observed; console/pageerror clean on every page 
touched.
   - [ ] CI on this PR (full server suite with its database service).


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