Selwin Ong

Sorry for the delay in reviewing issues or PRs. I don't get email notifications until someone mentions my name. Having said that, I'll be happy to transfer this repo to...

I'm happy to help with the transition. I think the next step would be for me to join the jazzband team as @jezdez outlined [here](https://github.com/jazzband-roadies/help/issues/153#issuecomment-519823919). I'll leave a comment in...

@jtfidje looks good. Do you mind updating the docs to add `enqueue_at_front` parameter to `Dependency` class? Also please make sure all the tests pass.

@jtfidje can you check your tests and ensure that they pass? I'll merge if they can pass the tests.

I'd rather get this PR merged in first. We don't know when https://github.com/rq/rq/issues/1693 will be done. If you can make all the tests pass, I'll merge this in and release...

Ah ok, if that’s the problem, there’s a simple fix for that. After you create the parent job along with the dependents, create another regular job so the queue is...

Try doing this: ```python parent_job = q.enqueue(say_hello) job_1 = q.enqueue( say_hello, job_id='fake_job_id_1', depends_on=Dependency(jobs=[parent_job]) ) job_2 = q.enqueue( say_hello, job_id='fake_job_id_2', depends_on=Dependency(jobs=[parent_job],enqueue_at_front=True) ) q.enqueue(say_hello) # This is a filler job that will...

Then it seems like enqueue_at_front did not work. Did you check the logic and whether the enqueue_at_front variable was saved properly?

To recap, it seems like the issue is not in the random ordering but the job was never enqueued at front.

Sorry I missed your message. Will check in a bit.