vipulneo opened a new issue, #23008: URL: https://github.com/apache/superset/issues/23008
When a user changes the time grain for example timestamp to seconds/day/ the widget add 8hrs(offset) to it most likely treats it as a local timestamp. Users ahead of UTC get a different Month as it fall to the last month when -offset to it. #### How to reproduce the bug See the attachment Orignal Value: <img width="824" alt="Screenshot 2023-02-06 at 3 44 06 PM" src="https://user-images.githubusercontent.com/381002/217112373-b71734bb-c3ff-47a1-ace2-ca3cae56bbde.png"> After applying time grain. <img width="796" alt="Screenshot 2023-02-06 at 3 48 43 PM" src="https://user-images.githubusercontent.com/381002/217113144-2b169c16-5115-4d7b-9760-1546cb23a62f.png"> ### Expected results Should not add the offset. what you expected to happen. ### Actual results what actually happens. #### Screenshots ### Environment (please complete the following information): - browser type and version: Chrome - superset version: `2.0` - python version: `python --version` - node.js version: `node -v` - any feature flags active: ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [ ] I have reproduced the issue with at least the latest released version of superset. - [ ] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context Query Engine: Trino Add any other context about the problem here. -- 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]
