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

[BUG] - switch from daylight saving time to standard time causes problem #69

Closed
arigon opened this issue Oct 25, 2020 · 7 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@arigon
Copy link

arigon commented Oct 25, 2020

Describe the bug

I am running a job on 00:01 every day. Today was the switch from daylight saving time to standard time in Europe. The job did run one hour too early at 23:01.
Update: And I just realized the job was executed twice.

To Reproduce

_, err := s.Every(1).Day().At("00:01").Do(reports.RunDailyReport)

Version

0.3.1

Expected behavior

It should not run at 23:01. It should only run once.

@arigon arigon added the bug Something isn't working label Oct 25, 2020
@Streppel Streppel added 0 - backlog and removed bug Something isn't working labels Oct 25, 2020
@Streppel
Copy link
Member

Streppel commented Oct 26, 2020

Thanks for the report @arigon. Will take a look at it.

@JohnRoesler
Copy link
Contributor

What time zone are you using? I'm wondering if it's set to UTC and was the same but then got off by an hour when your time changed?

@Streppel Streppel added the bug Something isn't working label Oct 26, 2020
@arigon
Copy link
Author

arigon commented Oct 26, 2020

I am using Europe/Berlin which is my time zone, otherwise it wouldn't start at 00:01 as expected. By the way, it hasn't started at 00:01 now either. I am now wondering if it will work Tuesday at 00:01.

@arigon
Copy link
Author

arigon commented Oct 26, 2020

Okay.. The job did just run, at 23:01.. How can I switch it back to 00:01?

@Streppel
Copy link
Member

This is unfortunate, I'm sorry. I believe I've already found what's up and will make a commit soon. Meanwhile, can you try to restart your worker application? I know this is not ideal, but hopefully it'll work while we don't merge a fix.

@arigon
Copy link
Author

arigon commented Oct 26, 2020

I already restarted that container yesterday. But I will do so again.

@arigon
Copy link
Author

arigon commented Oct 27, 2020

after intensive research with @Streppel (thx a lot!) we found the problem is in the alpine docker image which didn't update properly from CEST to CET. I will close this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants