sam-hieken opened a new issue, #30592: URL: https://github.com/apache/superset/issues/30592
### Bug description Specifying "Last <n> minutes" in the "Advanced" section of time range filters on dashboards will sometimes think it's a time from the day before. ### Screenshots/recordings For some clarity, the following test was performed on 2024-10-13T19:38:00-0400, give or take a few seconds. As should be obvious by the -0400, I'm in EDT/EST zone. ## Last Hour: <img width="588" alt="Screenshot 2024-10-13 at 7 38 31 PM" src="https://github.com/user-attachments/assets/c3369531-8fbe-4013-9c41-cadd5ddee76a";> ## Last 2 Minutes: <img width="590" alt="Screenshot 2024-10-13 at 7 38 48 PM" src="https://github.com/user-attachments/assets/f58e21c0-83b0-4f48-a11a-725bb584d45d";> Obviously "Last 2 minutes" is way off - the timestamp is nowhere close, and the date shown is yesterday. Every dashboard with a time range filter I've tried this on has the same issue, and it happens in both the Start and End inputs. ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Firefox ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] 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]
