[Bug]: Wrong job is picked after rate limit with priority

[luddd3]

Version

v3.14.0

Platform

NodeJS

What happened?

Jobs with priority are picked out-of-order after rate limiting with priority.

In my example, I expect job1 to always be processed before job2.

How to reproduce.

import { Queue, Worker } from 'bullmq'
import { setTimeout } from 'node:timers/promises'

const host = 'localhost'
const password = 'password'

// Cleanup
// import IORedis from 'ioredis'
// const client = new IORedis({
//   host,
//   password
// })
// await client.flushdb()

const queue = new Queue('myQueue', {
  connection: {
    host,
    password
  }
})

let i = 0
const worker = new Worker(
  'myQueue',
  async job => {
    i++
    console.log(i, 'rate limit', job.name)
    await setTimeout(20)
    await worker.rateLimit(1000)
    throw Worker.RateLimitError()
  },
  {
    connection: {
      host,
      password
    }
  }
)

console.log('add job1')
await queue.add(
  'job1',
  {},
  {
    jobId: 'job1',
    priority: 10 // works if priority is out-commented
  }
)
await setTimeout(50)

console.log('add job2')
await queue.add(
  'job2',
  {},
  {
    jobId: 'job2',
    priority: 10 // works if priority is out-commented
  }
)
await setTimeout(100)

Relevant log output

add job1
1 rate limit job1
add job2
2 rate limit job2
3 rate limit job2
...

Without priority:

add job1
1 rate limit job1
add job2
2 rate limit job1
3 rate limit job1
4 rate limit job1
...

Code of Conduct

• I agree to follow this project's Code of Conduct

[roggervalf]

Hi @luddd3, I think I understand your case, thanks for bringing this up.