You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Granted, it shouldn't be passing in undefined as id to Job.get() initially, and I can add a check to make sure that doesn't happen in my app code.
That being said, it might be better not to allow this use case to generate an uncaught exception in the Kue code, and instead call the return fn with a validation error
The text was updated successfully, but these errors were encountered:
issue Automattic#989 - calling `Job.get()` with an `id` param that is null or undefined will result in an uncaught exception.
this adds a validation check to prevent this, and returns an application level error instead
Calling
kue.Job.get()
and passing an undefined or nullid
causes an uncaught exception:from this entry point: https://github.com/Automattic/kue/blob/master/lib/queue/job.js#L161
the
get()
function doesjob.zid = client.createFIFO(id);
.The uncaught exception happens on this line in
createFIFO()
: (https://github.com/Automattic/kue/blame/master/lib/redis.js#L82)Granted, it shouldn't be passing in
undefined
asid
toJob.get()
initially, and I can add a check to make sure that doesn't happen in my app code.That being said, it might be better not to allow this use case to generate an uncaught exception in the Kue code, and instead call the return fn with a validation error
The text was updated successfully, but these errors were encountered: