Open extrinsicmedia opened 10 years ago
@extrinsicmedia The Cron entry gets interpreted as a local time on the server running Dagobah. The frontend then takes the UTC representation of that time and shows it to you in your browser's timezone. My guess is that your server and your browser are about half a world away from each other. Am I close?
@thieman I'm testing locally so they're both on the same machine. Possible that the Cron entry is getting interpreted from UTC 0?
Hmm, yeah maybe something is getting converted where it shouldn't. I testing servers running UTC, so it'd make sense if I missed something. Will check it out, thanks.
I think I wrote a fix for this like two months ago. I'll actually get off my ass and try to merge it this weekend.
I ran into this issue as well while running on a server set to EDT. Happy to help test this out further.
@creator11 This is my work-in-progress branch if you'd like to give it a go: https://github.com/thieman/dagobah/tree/tnt-fix-cron-format
Thanks for the assist!
Thanks I'll give it a go through a QA regression.
@thieman pull down the new branch and built. However after building and running the branch it appears you cannot create new jobs. Using the SQLiteImpl
Well, that's certainly interesting. Will take another pass this weekend, thanks.
The 'Cron Schedule String' entry: 00 22 * * *
is evaluating 'Next Scheduled Run' as: January 31 2014 2:00 PM
but I think this should be: January 30 2014 11:00 PM