Alice-608 opened a new issue, #37947: URL: https://github.com/apache/superset/issues/37947
### Bug description Describe the bug When working with datetime columns in a Bar Chart (and potentially other chart types) in the latest master branch of Apache Superset, switching between different datetime display formats results in an incorrect Unix timestamp conversion, leading to a significant time discrepancy. To Reproduce Create a Bar Chart in Superset using a dataset containing a datetime column (e.g., 2026-02-15 16:30:00). In the chart's configuration panel, switch the datetime display format between the available options. Observe the resulting Unix timestamp value displayed after the format switch. Expected behavior The converted Unix timestamp should accurately represent the original datetime value. For the example 2026-02-15 16:30:00, the correct timestamp (in milliseconds) is 1771144200000. Actual behavior When switching formats, the resulting timestamp is 1771173000000. When converted back to a datetime, this corresponds to 2026-02-16 00:30:00, which is 8 hours later than the original datetime 2026-02-15 16:30:00. This indicates a critical error in the timezone handling or conversion logic when switching display formats. Screenshots <img width="1023" height="505" alt="Image" src="https://github.com/user-attachments/assets/e21eede5-92c7-44b8-a0ca-4ef6990a61ed"; /> <img width="1017" height="501" alt="Image" src="https://github.com/user-attachments/assets/f7cbf019-da12-41ec-8a7e-d08f73b0e872"; /> <img width="1705" height="838" alt="Image" src="https://github.com/user-attachments/assets/4c4404c1-bdc1-4ed8-97b2-da08c2b066e4"; /> ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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]
