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/04 08:34:15 UTC
[GH] (rocketmq-dashboard/fix/k8s-cert-timezone-utc): Workflow run "CI" failed!
The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/k8s-cert-timezone-utc has failed.
Run started by GitHub user zjncs (triggered by zjncs).
Head commit for run:
e857c908fe4357d0800e656ef3c46fc253507d99 / zjncs <22...@qq.com>
fix(k8s-cert): serialize certificate instants as UTC across the wire
The cert service was the only one in the codebase still on
Clock.systemDefaultZone(), and it converted X509 instants with
ZoneId.systemDefault(). The API serializes notBefore/notAfter as
zoneless LocalDateTime, and the frontend parsed them with
Date(value), which treats a zoneless string as browser-local — so on
any server or viewer whose zone is not UTC, the displayed expiry
shifted by the zone offset.
- service: default clock and X509 conversion now use UTC, matching
the project-wide zoneless-value convention (every other date API
serializes UTC; formatUtcDateTime documents that contract);
- page: the expiry column uses formatUtcDateTime to interpret the
zoneless wire value as UTC and render it in the viewer's zone
(compact-list form, no per-row zone suffix), like the conversation
history list;
- test fixtures now use the realistic zoneless wire format instead
of the idealized Z-suffixed strings.
Signed-off-by: zjncs <22...@qq.com>
Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37188839304
With regards,
GitHub Actions via GitBox