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
Expected behavior:
I expect the task started at midnight of the given timezone (in my case local timezone).
Actual behavior:
The task start at midnight UTC, which is currently (CEST) two hours off.
Every range or other timezone-related query data are correct, so it's only the starting time.
Environment info:
Docker image with correctly set timezone
The text was updated successfully, but these errors were encountered:
If I set the timemask via cron, then only the first start of the task starts in Zulu time. Any next start is correct in local time.
It seems the parsing of the location-option is one step too late...
But every server restart or task re-save makes a new wrong start-time...
Furthermore it would be very nice if one could set a global location-option. So that any timezone-related operation (like tasks or functions) works with the correct timezone... No one lives in the zulu timezone 🙂
Steps to reproduce:
option location = timezone.location(name: "Europe/Berlin")
Expected behavior:
I expect the task started at midnight of the given timezone (in my case local timezone).
Actual behavior:
The task start at midnight UTC, which is currently (CEST) two hours off.
Every range or other timezone-related query data are correct, so it's only the starting time.
Environment info:
Docker image with correctly set timezone
The text was updated successfully, but these errors were encountered: