You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure these boxes are checked 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.
Related to #3326, which is closed but has not been resolved.
Superset version
0.28.1
Expected results
Time is displayed consistently in the same time zone on the calendar heat map as for the data queried. The January day view should start with the 1st of January for example.
Actual results
The January day view starts with the 31st of December 23:00 for setups using CET. The data is queried correctly in UTC, but somehow seems to be displayed in local time zone instead.
Steps to reproduce
create calendar heatmap
configure with "day" time grain, "month" domain and "day" subdomain
observe months starting with the previous months day for time zones east of GTM and all days shifted accordingly
The text was updated successfully, but these errors were encountered:
hyperborea
changed the title
Calendar heatmap showing dates in local client time zone instead of UTC
Calendar heatmap dates shifted by one (converting to local time zone)
Jan 8, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Make sure these boxes are checked before submitting your issue - thank you!
Related to #3326, which is closed but has not been resolved.
Superset version
0.28.1
Expected results
Time is displayed consistently in the same time zone on the calendar heat map as for the data queried. The January day view should start with the 1st of January for example.
Actual results
The January day view starts with the 31st of December 23:00 for setups using CET. The data is queried correctly in UTC, but somehow seems to be displayed in local time zone instead.
Steps to reproduce
The text was updated successfully, but these errors were encountered: