Ujjwaljain16 commented on issue #37925: URL: https://github.com/apache/superset/issues/37925#issuecomment-5939751219
@rusackas I investigated this against current `upstream/master` (`8ab7a85a3d`, 2026-10-01) and could not reproduce the reported datetime shifts. I ran the three timestamps from the issue through the actual chart query path and JSON serialization with the reported configuration (UTC/zero offset, no time comparison, no time shift, second-level precision). The returned values matched the source values exactly. I also tested multiple grain/format combinations; the only change observed was the expected truncation when using a day-level grain. One interesting detail from the reported examples is that the stated shift for each row equals that row's own time-of-day: ```text 16:30:00 → +16:30 10:00:00 → +10:00 14:20:00 → +14:20 ``` That corresponds to `displayed = date + 2 × time-of-day`, which cannot be produced by a normal fixed datasource offset or `time_shift`. The `normalize_dttm_col` regression test added in #42589 also passes and confirms that zero offset/no time shift preserves these exact values. I also checked the relevant datetime changes around #37925 (#37979, #37111, #35042, #37014) and did not find a current code path that explains this behavior. At this point I can't identify a current Superset defect from the available reproduction. The following would help narrow down where the discrepancy occurs: 1. The dataset's **Hours Offset** and **Timezone** settings. 2. Whether the chart's datetime column is a physical column or a calculated/virtual column. 3. The actual `/api/v1/chart/data` response containing the affected rows. 4. Confirmation that SQL Lab and the chart are selecting the same column/expression. 5. The actual Superset version being used for the original reproduction. The chart API response in particular would distinguish a backend/query-result discrepancy from a frontend rendering issue. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
