coder999o opened a new issue, #7012: URL: https://github.com/apache/rocketmq-dashboard/issues/7012
### Before Creating the Bug Report - [x] Searched open/closed issues and all-state PRs, including #3995, #6143 and #6686. - [x] This is a RocketMQ Studio audit-export defect. - [x] Source inspection uses the current rocketmq-studio base below. ### Studio Version `rocketmq-studio`, commit `c34535db0819d02f68e50a856cb3d2614f0dc5dd`. ### Runtime Environment Source-based reproduction on macOS with JDK 22 (release 21 compilation). No deployed Studio/MySQL reproduction is claimed. The affected configuration is a server JVM using a daylight-saving zone such as `America/New_York`. ### Connected RocketMQ Cluster Not needed: the CSV is generated from the audit repository. ### Describe the Bug `AuditService.exportLogs` writes stored `LocalDateTime` values unchanged, but `serverZoneLabel()` labels the entire timestamp column using `OffsetDateTime.now().getOffset()`. A daylight-saving zone has different historical offsets, so the export-time offset can mislabel older audit events by an hour. ### Steps to Reproduce 1. Set the JVM default zone to `America/New_York`. 2. Supply audit records with local timestamps `2026-01-15T09:30` and `2026-07-15T09:30` (a mocked repository is sufficient). 3. Call `AuditService.exportLogs` for that date range. 4. The header contains either `timestamp(UTC-04:00)` or `timestamp(UTC-05:00)`, depending on the export date, while the two raw row timestamps remain unchanged. January uses -05:00 and July uses -04:00; one header offset cannot describe both. ### What Did You Expect to See? A timestamp header that identifies the server region, e.g. `timestamp(America/New_York)`, so historical zone rules are available without converting the stored wall times. ### What Did You See Instead? The current offset is applied as a label to all historical rows. ### Additional Context #3995 introduced the current-offset label. #6143 reused that formula for other exports; #6686 addresses JSON serialization and explicitly retains CSV server-local values. This report concerns historical DST labeling in the audit CSV only. Naming the region does not recover the inherent ambiguity of zone-less timestamps during the autumn overlap, nor repair records written under a different server zone. ### Are You Willing to Submit a Pull Request? - [x] Yes. -- 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]
