You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@rocketmq.apache.org by GitBox <gi...@apache.org> on 2026/10/01 10:18:01 UTC

[GH] (rocketmq-dashboard/fix/shared-message-timestamp-format): Workflow run "CI" failed!

The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/shared-message-timestamp-format has failed.
Run started by GitHub user lizhimins (triggered by lizhimins).

Head commit for run:
56400ec48f03424a6b81749c5949a707437b45eb / wang1r <92...@qq.com>
fix(web): share one message timestamp formatter

message.tsx and QueueBrowser.tsx each carried their own formatTimeMs for
the same MessageRecord.storeTime / trace node timestamp values, and the two
copies disagreed:

- the QueueBrowser one rendered toLocaleString('zh-CN'), so the queue
  browser showed 2026/9/22 08:36:08 while every other timestamp in the
  console is YYYY-MM-DD HH:mm:ss;
- the message page one started from "if (!value) return '-'", which treats
  the Unix epoch as missing, and fed the raw value to new Date(), so an
  unparseable timestamp rendered as NaN-NaN-NaN NaN:NaN:NaN.NaN instead of
  the placeholder.

Move a single formatTimeMs into utils/format.ts, built on formatDateTime so
it inherits the console-wide layout, and have both call sites use it. Zero is
a real timestamp; only an unusable value yields '-'.

Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/36847333586

With regards,
GitHub Actions via GitBox