Rob Figueiredo

Hi, thank you for the contribution! Regarding the new directives, having two directives that do almost the same thing doesn't seem great, and I can easily imagine that users are...

No, but your task could remove itself from Cron when it starts running.

There is no way to do that with the schedule. I think the best workaround is to execute your job immediately, e.g. ``` cron.AddJob("@every 5m", myJob) go myJob() ```

I agree this is confusing and the documentation should be clarified. I don't think I can change it now, though, since that would be backwards incompatible. On the bright side,...

Thank you for the report. Can you provide a test case that demonstrates the issue?

Thanks for the alert but these CVEs do not apply to this package. This is just a library for parsing and scheduling jobs using that format; it would be up...

Thanks for the thoughts, but I think you can do this today, because Job is an interface: ``` type MyJob struct { Name string Func func() } func (j MyJob)...

I suppose this could be implemented as an optional interface that is tested for and used by the logger..

Yes, because of the way it calculates the next job's trigger time (iteration), it has to pick some threshold beyond which it gives up. 5 years is an amount of...

In other words, you want to schedule the job to run once, and not again? You can do that today with something like this: ```go func runOnce(job cron.Job, schedule string)...