dosubot[bot] commented on issue #30592: URL: https://github.com/apache/superset/issues/30592#issuecomment-2409367087
<!-- Answer --> The issue you're experiencing with the "Last <n> minutes" time range filter might be related to timezone handling. Superset uses the `timezone-mock` library to simulate different timezones and calculate time offsets. This can sometimes lead to discrepancies if the timezone isn't correctly accounted for in the calculations <sup>[[1]](https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-ui-core/test/time-comparison/getTimeOffset.test.ts)</sup>. To address this, you might want to check if the timezone settings in your Superset configuration are correctly set to match your local timezone (EDT/EST). Additionally, ensure that both your database and Superset backend are configured to use UTC, as this can help avoid issues with temporal fields lacking explicit timezones <sup>[[2]](https://github.com/apache/superset/blob/master/docs/docs/configuration/timezones.mdx)</sup>. If the problem persists, consider reviewing the logic in the `get_since_until` function, which calculates start and end times for relative time ranges. This function uses parameters like `relative_start`, `relative_end`, and `time_shift` to determine the correct time range <sup>[[3]](https://github.com/apache/superset/blob/master/superset/common/utils/time_range_utils.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- 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]
