gron

gron copied to clipboard

fix the bug of dynamic adding job ( the case: c.running ==true ), the calculation of new time must be done before the next round for loop.

sstshenshutao

`func (as atSchedule) reset(t time.Time) time.Time { return time.Date(t.Year(), t.Month(), t.Day(), as.hh, as.mm, 0, 0, time.UTC) }`

mredencom

Thanks for awesome work! It would be great if the gron can have some info for all added jobs (runnning, scheduled, ...)

qmn1711

UTC time using in AtSchedule

1

Hi， You mentioned ‘All scheduling is done in the machine's local time zone (as provided by the Go time package).’ in the REAMME.md. In the implementation of AtSchedule a UTC...

chaoliu-sc

eduardev

A cronjob may need be canceled before run in some situation. Sugguest to add this feature

chennqqi

Using `channel` based synchronization in `Add` method prevents the `data races` when the cron instance is running. Although, it can't stop them when the cron instance is inactive. ```go package...

pravj

use local time instead of utc for atScheduling

1

I got GMT+3 time zone, so when i write `gron.Every(1 * xtime.Day).At("19:32")` i expect function will be triggered at 19:32 local time, not UTC time (which is 3 hours difference...

postromantic

Defines JobWithCancel interface. Require a unique string as jobID in each job. Sometimes we need to cancel job after it's lifecycle finished. For example, start a monitoring job while a...

fakeyanss