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
For applications with global business requirements, some tasks need to be executed shortly after a time passes in a foreign time zone. Time zone offsets for geographical locations change throughout the year, of course, so the correct way to specify these is with locale strings. (I think Go supports these with it's native time library?)
Currently, you can work around this by using a wrapper script that sleeps until the correct time and firing hourly or minutely, but it would be very nice to just be able to set it as a parameter.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
For applications with global business requirements, some tasks need to be executed shortly after a time passes in a foreign time zone. Time zone offsets for geographical locations change throughout the year, of course, so the correct way to specify these is with locale strings. (I think Go supports these with it's native time library?)
Currently, you can work around this by using a wrapper script that sleeps until the correct time and firing hourly or minutely, but it would be very nice to just be able to set it as a parameter.
The text was updated successfully, but these errors were encountered: