Manuel Astudillo

@mariuszbeltowski it will take up to 10, if there are less than 10 then it will take all the ones that are left.

Great job! I wonder about the ```disconnectTimeout``` option. I have tried to find some documentation about it in ioredis repo without success, it would be useful to get a better...

Thank you for the PR. I think that it would be better to retrieve ```runtAt``` lazily, as it is difficult to keep it in sync at all times. Since ```runAt```...

Hello. I made several fixes and improvements based on the discussion here. In theory all tests should pass. Locally in my computer they don't as the latency seems to be...

@hyperair could we delete the "delay" field on the job then as it does not seem to be useful? Regarding runAt, I think it could be misleading as it should...

@hyperair then the other question is, should "runAt" be cleared after the job has been moved from the delayed set to the wait list?

so in a sense "runAt" would be the same as the score in the delay set, just a cached value that makes it more convenient when getting the jobs.

> @manast While that works for jobs that are in the delayed state, it doesn't work for calculating something like a "job wait time" metric, i.e. how long after after...

@lindesvard I will try to improve it somehow.

@ShadowStrikerJ Unfortunatelly flows do not support multiple parents, and I do not know if and/or when they will be supported.