Frun1na opened a new issue, #4924: URL: https://github.com/apache/rocketmq-dashboard/issues/4924
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `1ef5d860` (upstream tip at the time of the report) deployed as: built from source ### Runtime Environment Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` (vitest for `web/`, JUnit for `server/`), not against a specific browser or deployment. ### Connected RocketMQ Cluster Not cluster-specific: the defect lives in the code path and reproduces on any deployment where the trigger condition below holds. ### Describe the Bug `DLQGroupVO.lastEnqueueTime` was a `LocalDateTime` built with the server's system zone, serialized without an offset. The frontend parses it with `new Date(...)`, which treats zoneless strings as browser-local time. ### Steps to Reproduce 1. Run the dashboard server in UTC, open the DLQ page in a browser at UTC+8. 2. Compare the displayed 最近入队时间 with the message store times on the same page (epoch millis, rendered correctly). 3. The last-enqueue time is off by the timezone difference. ### What Did You Expect to See? The displayed last-enqueue timestamp represents the actual instant consistently with the rest of the UI. ### What Did You See Instead? A server-local wall clock is presented as browser-local time. -- 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]
