Kue: node_redis: Deprecated: The HSET command contains a "undefined" argument.

Created on 5 Sep 2016  路  14Comments  路  Source: Automattic/kue

I'm assuming this is caused by kue, but not 100% sure.

Question

Most helpful comment

I found the reason for my failure, I was using promises with kue, and I was calling the done callback like this : .then(done). But the callback structure is done() for success or done(err) for error. So if done is called with any parameter, it fails.

I corrected it like so:

.then(() => done())
.catch(done)

All 14 comments

Also getting this message, here's the full warning:

node_redis: Deprecated: The HSET command contains a "undefined" argument.
This is converted to a "undefined" string now and will return an error from v.3.0 on.
Please handle this in your code to make sure everything works as you intended it to.

same but slightly modified:

node_redis: Deprecated: The HSET command contains a argument of type Object.
This is converted to "[object Object]" by using .toString() now and will return an error from v.3.0 on.
Please handle this in your code to make sure everything works as you intended it to.

Has anyone made any progress this morning? Just ran into this issue this morning and started poking around which lead me here.

Any updates on this? It's causing my jobs to fail ...

Any news on this ? I'm getting the same error. My task is executed but this error makes kue retry so it's actually executed a few times.
Thanks !

I found the reason for my failure, I was using promises with kue, and I was calling the done callback like this : .then(done). But the callback structure is done() for success or done(err) for error. So if done is called with any parameter, it fails.

I corrected it like so:

.then(() => done())
.catch(done)

that was it ! thanks so much @AliUz 馃憤

@nmalzieu no problem mate! :)

Just to chime in, I'm not using .then promises, so that doesn't apply in my case.

I am also getting this without using the .then promise.

that may be related to a callback not being passed somewhere...

I have encountered this issue and it looks like it happened when the error for done() is not a string or Error().

@AliUz Man, you rock! Thanks for your input, helped us solve some issues :)

Thanks for the answer it helped to me! So, how can we return the result from the worker?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jibay picture jibay  路  6Comments

jasonwatt picture jasonwatt  路  4Comments

narainsagar picture narainsagar  路  8Comments

syadykin picture syadykin  路  8Comments

digitaljohn picture digitaljohn  路  10Comments