-
Notifications
You must be signed in to change notification settings - Fork 410
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
Error in setting TimeMachine #119
Comments
Ah, what a weird issue. I see it has something to do with your timezone (Australia/Sydney). Somehow this is tripping up the time machine feature. I will fix this ASAP! |
Oh right, I see! I changed the timezone to UTC and it worked. So I can use this workaround for now. Also is there a way for the system clock on the top right hand corner to display time in UTC instead of local time? Thanks! |
Ah cool, nice workaround. Unfortunately the clock in the top-right corner (and the dates/times displayed on the Upcoming Events, Completed Events, Job History, Job Details, Admin Log, etc.) are all hard-coded to display your local time. However, this is an open issue and I have been meaning to fix this for quite a while, i.e. allow the user to configure his/her local timezone, probably on the "My Account" tab. I'll get this implemented as soon as possible! |
No worries, thanks heaps for your quick replies. The TZ is clearly displayed (including provision for daylight savings which is great!) so atleast there is no confusion about what we're looking at. The jobs may be scheduled in any timezone - having the option for the "My Account" setting will definitely be a nice to have but its not blocking us at the moment. Keep up the good work - this is a fantastic product! :) |
Awesome, thanks! 😀 |
Summary
I'm trying to use the TimeMachine feature to "Set Event Clock". The idea is to set something up to run weekly and then set the time in the past to "CatchUp" - is this the right way to use this feature.
If after I select the time from the calendar that pops up and save it gives me the error that the date/time is invalid - how?!
See attached screenshots
Steps to reproduce the problem
Check TimeMachine, set time in the past and save changes
Your Setup
Using Docker but native install has the same issue
Operating system and version?
Ubuntu 16.05LTS
Node.js version?
v6.14.4
Cronicle software version?
0.8.28
Are you using a multi-server setup, or just a single server?
Single server
Are you using the filesystem as back-end storage, or S3/Couchbase?
FS
Can you reproduce the crash consistently?
Yes
Log Excerpts
Not sure if there are for this.


The text was updated successfully, but these errors were encountered: