123123213weqw opened a new issue, #5225: URL: https://github.com/apache/rocketmq-dashboard/issues/5225
### Before creating - [x] I have searched the existing issues and found no duplicate. - [x] I have checked the latest `rocketmq-studio` branch where this problem still exists. ### Bug report **Which page or component** `web/src/pages/studio/LiteTopic.tsx` — `formatTime`, used for the quota card's "Last Active Time", the sessions table and the session drawer's create/last-active times. **What happened** The LiteTopic API sends `createTime` / `lastActiveTime` as epoch millis (`src/api/liteTopic.ts`), i.e. absolute instants. `formatTime` renders them with `new Date(ts).toLocaleString()`: the string is locale-dependent (`9/30/2026, 10:05:04 AM` on en-US, `2026/9/30 10:05:04` on others), silently converted to the browser's zone, and carries no zone label — so two operators in different zones read different times off the same row with nothing saying which zone. This is the same surface family #5197/#5204 moved to the `formatUtcDateTime` contract (viewer zone, labeled). **Steps to reproduce** 1. Open the LiteTopic page of an Aliyun instance with existing sessions. 2. The table's time column shows a `toLocaleString`-format value with no zone label; switching the OS timezone changes the displayed time. **Expected behaviour** `formatTime` routes the instant through `formatUtcDateTime` (the shared util already used by the alert surfaces): viewer timezone, explicit zone suffix, `-` for invalid values. **Environment** branch `rocketmq-studio`, commit `4ee173ad`. -- 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]
