Crontab format not correct about dagobah HOT 10 OPEN

@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?

from dagobah.

@thieman I'm testing locally so they're both on the same machine.
Possible that the Cron entry is getting interpreted from UTC 0?

from dagobah.

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.

from dagobah.

1. The server is asserting that the Cron time is based on UTC. This needs to instead use the server's local time.
2. When the server passes datetimes to the frontend, they do not have TZ information. The frontend assumes that everything is in UTC. The backend should convert its datetimes to UTC before sending them to the frontend.
3. I don't think the frontend ever sends datetimes to the backend (it only sends Cron strings), so we don't have to juggle authoritative timezones between the client and server. Hooray.

from dagobah.

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.

from dagobah.

I ran into this issue as well while running on a server set to EDT. Happy to help test this out further.

from dagobah.

@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!

from dagobah.

Thanks I'll give it a go through a QA regression.

from dagobah.

@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

from dagobah.

Well, that's certainly interesting. Will take another pass this weekend, thanks.

from dagobah.