Ryan Schmukler

What would be the ideal behavior for this? Should it simply ignore events after the queue has exceeded the session size? Usually a controller only has one or two events....

@angeltinfoil the thing that'll become difficult is that the gem would then have to check the length of the session, not just the length of the queue (as it depends...

@gabrieledarrigo instead of ``` job.repeatAt('at 19:43'); ``` try ``` job.repeatAt('19:43'); ``` Also, you are correct, the job will not re-run because of the error.

My guess is that what is happening is that the job is completing in less than 1ms and so the time of repeatAt is the same as current time. @nwkeeley...

So `repeatAt` and `repeatEvery` both are just used to compute `nextRunAt` - and then agenda looks for jobs with `nextRunAt < Date.now()`... So in those cases, the server will run...

I'd like to propose that `match-by-name` just be extended to behave as `match-by-id` instead. Introducing `match-by-id` adds more surface area and potential for some confusing behaviors. What happens if a...

Just echoing that I'm not sure that implementing 1 needs to be a breaking change. It seems that it's additive. A few more considerations: 1) Should conflict detection be a...

Upon further digging this may be a duplicate of #152

I actually don't do any development on windows so I am not too familiar with how it goes about emulating unix file system resolution (or if it does). Looking at...

MASSIVE +1 from me. Please please please write this guide!