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 zone correction? #1452

Closed
Mboitnott opened this issue Jan 14, 2025 · 7 comments
Closed

Time zone correction? #1452

Mboitnott opened this issue Jan 14, 2025 · 7 comments

Comments

@Mboitnott
Copy link

Hello! Love this program! How do I edit the timezone for the clock (Windows)? I changed my system time in windows, but my time zone is still incorrect.

@alex-Arc
Copy link
Collaborator

Hey @Mboitnott
Where are you running ontime from, cloud / docker / locally ?

@Mboitnott
Copy link
Author

I'm running it locally

@cpvalente
Copy link
Owner

Hi @Mboitnott , I am not entirely sure what the issue may be
I assume you installed the app using the installer in the website, in which case Ontime gets the time from the system
This has never been an issue before and unfortunately we dont have any methods for debugging timezones

How offset is the time? is it that the time is in UTC?

If you prefer, you can hop into our discord server and we can try to help you debug (link in the readme)

@Mboitnott
Copy link
Author

Mboitnott commented Jan 15, 2025

Hey @cpvalente In this particular case, I live in EST and traveled to PST for an event. I've had OnTime downloaded on all my show PCs for a bit. I changed the system time to PST, and OnTime doesn't update.

If it does grab it during install, then perhaps I could just delete and reinstall? That's a pretty easy work around, I would just keep the download exe on hand

@cpvalente
Copy link
Owner

We get the time from the system on every tick (32ms), not on install.
With that in mind, I am not sure this would help, but could be worth a try

I had a quick google and it seems that this is an known issue with node in windows, but if I understand correctly, it should be fixed after reboot?
nodejs/node#4022

@alex-Arc
Copy link
Collaborator

alex-Arc commented Jan 15, 2025

I gave it a quick try
Just restarting Ontime seams to be enough

tz

@Mboitnott
Copy link
Author

Wow, now I feel very silly. Thanks for the help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants