Does it support jobs with `group` and `concurrency`

[antoinelyset]

Hi!

I don't really know where to ask but it seems the taskforce dashboard (and this library) does not display jobs in groups and waiting because of concurrency (maxed status?).

Am I right?

Thanks.

[manast]

Hello,

in order for groups to appear in the dashboard you must either use a direct connection or use the Pro connector:

[antoinelyset]

Thanks for the quick answer! I'm using ConnectorPro like this:

  ConnectPro(
    'Connection',
    process.env.TASKFORCE_TOKEN,
    {
      host: process.env.REDIS_HOST,
      port: process.env.REDIS_PORT,
      password: process.env.REDIS_PASSWORD,
    },
    {
      backend: process.env.TASKFORCE_CONNECTOR_BACKEND_URI,
    }
  )

I'm seeing 0 job in the "Waiting"

[manast]

Thats because the jobs are in the groups, which is the new "waiting" for groups. Unfortunately it is not possible to get a count of all the jobs in groups at the moment.

[manast]

i.e. you should be able to see the jobs in the groups in the "Groups" tab.

[antoinelyset]

Where is this tab?

[manast]

Can you copy paste the logs from the connector here please?

[manast]

The error seems to be that it is not detecting the BullMQ Pro version used:

thats why I wonder what the logs look like to see if there is some issue there.

[antoinelyset]

I just retried and here are the logs from the connector. (Sorry I was on holidays)

Indeed I can see a recurring error but the dashboard seems to work fine (and the errors stopped).

TypeError: Cannot destructure property 'queue' of 'cache[(0 , queues_cache_1.queueKey)(...)]' as it is undefined.
    at WebSocketClient.incoming [as onmessage] (/slite/node_modules/taskforce-connector/dist/socket.js:78:33)
    at WebSocket.<anonymous> (/slite/node_modules/taskforce-connector/dist/ws-autoreconnect.js:25:18)
    at WebSocket.emit (node:events:518:28)
    at WebSocket.emit (node:domain:489:12)
    at Receiver.receiverOnMessage (/slite/node_modules/taskforce-connector/node_modules/ws/lib/websocket.js:1220:20)
    at Receiver.emit (node:events:518:28)
    at Receiver.emit (node:domain:489:12)
    at Receiver.dataMessage (/slite/node_modules/taskforce-connector/node_modules/ws/lib/receiver.js:596:14)
    at Receiver.getData (/slite/node_modules/taskforce-connector/node_modules/ws/lib/receiver.js:496:10)
    at Receiver.startLoop (/slite/node_modules/taskforce-connector/node_modules/ws/lib/receiver.js:167:16)
    at Receiver._write (/slite/node_modules/taskforce-connector/node_modules/ws/lib/receiver.js:94:10)
    at writeOrBuffer (node:internal/streams/writable:572:12)
    at _write (node:internal/streams/writable:501:10)
    at Writable.write (node:internal/streams/writable:510:10)
    at Socket.socketOnData (/slite/node_modules/taskforce-connector/node_modules/ws/lib/websocket.js:1355:35)
    at Socket.emit (node:events:518:28)
    at Socket.emit (node:domain:489:12)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)

Should I see something specific to the Pro version?

[manast]

You should use the Pro connector:

[antoinelyset]

I verified and I'm using it

import { ConnectPro } from '@taskforcesh/connector-pro'

...

  ConnectPro(
    'Connection',
    process.env.TASKFORCE_TOKEN,
    {
      host: process.env.REDIS_HOST,
      port: process.env.REDIS_PORT,
      password: process.env.REDIS_PASSWORD,
    },
    {
      backend: process.env.TASKFORCE_CONNECTOR_BACKEND_URI,
    }
  )

Should I see something specific in the logs to verify it uses it?

[manast]

Basically it will detect the queue as a BullMQ Pro, or it will output an error that it does not recognise the queue type. Nevertheless I will try to reverse engineer the error log you got to see if I can figure out why it happens.

[antoinelyset]

It's possible that some queues were created with the non-Pro version and I upgraded to the Pro version without cleaning anything (I just changed the import and the Queue to QueuePro).

So maybe the detection is lost.

Thanks a lot for taking the time to look at it.

[manast]

the Pro connector would detect even non-pro queues. And an old queue that was non-Pro becomes Pro as soon as you start using it with Pro.