Upgrade node redis from v2.* to v4.*

[KiranI-Bsw]

I am using node redis v4.0.2 for my project. However, bee-queue uses v2.* and I am unable to reuse my redis client from v4. Gives somethig like this. I am not dropping out of v4 bcoz I can use promises with node redis itself. Due to this issue I have to open a new connection for bee-queue queue whereas I should have been able to use one. Any suggestion on how to deal with this?

node_modules/bee-queue/node_modules/redis/lib/utils.js:65
            var snake_case = elem.replace(/[A-Z][^A-Z]/g, '_$&').toLowerCase();
                                  ^

RangeError: Maximum call stack size exceeded
    at String.replace (<anonymous>)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:65:35)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:71:32)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:71:32)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:71:32)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:71:32)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:71:32)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:71:32)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:71:32)
    at clone (/Users/bswmac013/Documents/GitHub/redis-matchmaking/matchmaker-consumer/node_modules/bee-queue/node_modules/redis/lib/utils.js:71:32)

[acSpock]

I am running into this same issue @KiranI-Bsw . I'm looking to figure out a solution before we decide to move to google pubsub. I'll let you know what I find.

[KiranI-Bsw]

PS: I'm using redis v4.0.2

I've notice that the constructor name for redis client is actually Commander. I am new to nodejs ecosystem so do you have any workaround or solution for this?

function isClient(object) {
    if (!object || typeof object !== 'object') return false;
    const name = object.constructor.name;
    return name === 'Redis' || name === 'RedisClient';
}

Upon researchig around, I believe that lot of things would be simplified (or entirely eliminited) by using v4.

For now setting sendEvents and activateDelayedJobs to false in producer helps with reusing the connection but doesn't work with consumer.

@acSpock Have you found anything?

[avin-kavish]

I want this too. But it looks like the package is not being maintained anymore.

[compwright]

@avin-kavish @KiranI-Bsw @acSpock I've come on recently as a new member of the maintainers team (and we'd like more if anyone is interested). This is high on the list to do next, FYI.

[sebaplaza]

This lib seems to be completely abandoned.

[pSnehanshu]

I wanted to use bull, but the job name thing is totally stopping me.

[romualdr]

@pSnehanshu I believe BullMQ (which is the successor of Bull) doesn't use names.

[pSnehanshu]

@romualdr BullMQ still has names.