Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time missmach WebUI #551

Open
imkebe opened this issue Apr 10, 2024 · 2 comments
Open

Time missmach WebUI #551

imkebe opened this issue Apr 10, 2024 · 2 comments
Labels
accepted feature request New feature or request

Comments

@imkebe
Copy link

imkebe commented Apr 10, 2024

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)

@yohamta
Copy link
Collaborator

yohamta commented Apr 11, 2024

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.

@imkebe
Copy link
Author

imkebe commented Apr 11, 2024

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.

@yohamta yohamta added the feature request New feature or request label Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants