lizhimins opened a new pull request, #6633:
URL: https://github.com/apache/rocketmq-dashboard/pull/6633
## What
- **Timestamps**: `formatUtcDateTime` no longer appends the viewer's zone
name, so every
timestamp reads `YYYY-MM-DD HH:mm:ss`; time columns are sized for the
shorter string
(156 in small tables, 182 in the default-size user table, which was
ellipsizing the value).
- **Disk usage**: the Apache provider scales `commitLogDiskRatio` to whole
tenths and the two
render sites round again, so `0.29 * 100` can no longer reach a label as
`28.999999999999996`
and squeeze the `Progress` bar to zero width; the Broker cluster page also
drops Progress's
own in-bar label, which duplicated the adjacent span.
- **Client connection diagnostics**: a risk's description moves from a
second line under the
title into a detail modal opened from the title (severity, description,
recommendation,
client id, resource, evidence).
- **System alerts**: the filter bar stays on one line at 1600px (one
`RangePicker` replaces two
`datetime-local` inputs, controls narrowed to their measured content) and
the collector status
chip becomes a bar-height neutral chip in the page header instead of a
22px success `Tag`.
- Adds `.claude/skills/regression-rocketmq`: a real-environment regression
runbook (cluster
bring-up through `deploy-rocketmq`, the k8s chart script when local kube
credentials exist,
the studio-docs e2e suite, a dead-letter end-to-end check, report), same
home as the existing
`deploy-rocketmq` skill.
## Verification
- Web suite 160 files / 1616 tests green and `RocketMQClusterProviderTest`
28 green (including
the new `0.29 -> 29.0` case) on the pre-squash tree, which is
byte-identical to this commit
apart from the skill directory.
- Deployed to a real test machine (Studio + open-source RocketMQ docker
cluster + an ACK
cluster) and browser-verified: no zone suffix on nine pages, progress bars
visible with `29%`,
user-table timestamps untruncated, filter bar on one line at 1600 and 1920.
- The regression skill's scripts were executed end to end against that
deployment: e2e suite
31/31 on both the docker and the k8s instance, and the dead-letter chain
send -> retry -> DLQ(3) -> resend(3/3) -> re-consume passed.
--
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]
