Job run twice when timer triggers to early about cron HOT 4 CLOSED

I have submitted pull required - #96 which proposes a solution to this.

from cron.

I'm also seeing possibility of double job behavior (emails sent twice), though I am not sure what is causing this.

Version 1.0. Will see if upgrading to 1.1 solves this.

from cron.

Please try v3. I believe this was fixed in 316e2a2 by checking the activation times explicitly:

			case now = <-timer.C:
				now = now.In(c.location)
				// Run every entry whose next time was less than now
				for _, e := range c.entries {
					if e.Next.After(now) || e.Next.IsZero() {
						break
					}
					go c.runWithRecovery(e.Job)
					e.Prev = e.Next
					e.Next = e.Schedule.Next(now)
				}

from cron.

Closing, please open a new issue if you see any problems.

from cron.