-
-
Notifications
You must be signed in to change notification settings - Fork 309
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] - job.LastRun() is in the future #424
Comments
experiencing same issue |
I got a fix in. Mind confirming if it solves the issue you're seeing? https://github.com/go-co-op/gocron/releases/tag/v.1.19.1 |
@JohnRoesler Thanks, my test above passes now. However, you tagged |
@fgm thanks for pointing that out. It's fixed now https://github.com/go-co-op/gocron/releases/tag/v1.19.1 If only github releases would ask you, "are you sure you really want to set that release version???" |
Describe the bug
job.LastRun()
is in the future.To Reproduce
Steps to reproduce the behavior:
StartAsync
time.Now()
,job.LastRun()
: the latter is now "something" in the future in comparison with the former instead of being in the past as it should.Version
Expected behavior
job.LastRun
represents the last time a job was run, which cannot be in the future.Additional context
This problem was not present in 1.17.0, but appears in 1.17.1. It appears to have been introduced by the #382 fix.
The text was updated successfully, but these errors were encountered: