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
While Dagu service is launched in the UTC based environment, my client machine is UTC+2. The WebUI show the
Next Run value calculated for my client machine (UTC+2) however the base value from the server is treated as it would be also UTC+2 while its not (it's UTC)
The text was updated successfully, but these errors were encountered:
Thanks, we would like to fix this issue. I think it's a bit complicated when you specify a cron expression when your local timezone is different from the server's one. I'd appreciate it if there's a good idea to deal with the timezone difference consistently throughout the browser and server.
I think the server should send to the WebUI the datetime value that will be calculated using timezone of the server. i don't know what's the current implementation however using TZ data will will be easy. Just read the server's TZ and send the cron based values with the read TZ. On the WebUI browser should also read the environment TZ and using that info adjust to the local one.
While Dagu service is launched in the UTC based environment, my client machine is UTC+2. The WebUI show the
Next Run value calculated for my client machine (UTC+2) however the base value from the server is treated as it would be also UTC+2 while its not (it's UTC)
The text was updated successfully, but these errors were encountered: