btlqql opened a new issue, #2431: URL: https://github.com/apache/rocketmq-dashboard/issues/2431
## Problem Tencent message and trace timestamps that include an explicit UTC offset are parsed as `LocalDateTime` and then assigned the JVM default timezone. The original offset is discarded. For example, `2026-08-20T10:00:00.000+0800` represents `2026-08-20T02:00:00Z`. On a UTC JVM the current parser interprets it as `2026-08-20T10:00:00Z`, shifting the value by eight hours. Message store times and trace production/persistence/consumption nodes therefore vary with the Studio deployment timezone. ## Expected behavior Timestamp strings with an offset must be parsed as offset-aware instants. Inputs without offsets should follow an explicit, documented timezone policy. The same source timestamp should produce the same epoch value regardless of the JVM default timezone. ## Suggested validation - Cover Tencent formats using dot and comma milliseconds plus explicit offsets. - Run parsing assertions under UTC and Asia/Shanghai defaults and verify identical epoch values. - Preserve existing epoch-number and offset-free format compatibility. -- 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]
