The GitHub Actions job "CI" on rocketmq-dashboard.git/fix-aliyun-datetime-zone has failed. Run started by GitHub user 123123213weqw (triggered by 123123213weqw).
Head commit for run: 0996f65fc5ee54d35fc6ab9f3f98d4b2bbbf3f2c / 123123213weqw <[email protected]> fix(aliyun): relabel topic and group timestamps into the server zone parseDateTime returned Aliyun's UTC+8 wall clock as a zone-less LocalDateTime without converting it, unlike parseTimeMillis in the same file, which correctly reads those strings in Asia/Shanghai. The gmtCreate/gmtModified columns of Aliyun topics and consumer groups therefore drifted from every timestamp Studio itself writes and from the epoch-based message and trace times of the same instance whenever the server zone is not UTC+8. Convert the wall clock into the server zone, the same relabeling the Tencent provider applies to its legacy formats. A server already running Asia/Shanghai keeps the previous values. Signed-off-by: 123123213weqw <[email protected]> Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37780288097 With regards, GitHub Actions via GitBox
