Throw custom error class is not propagated properly to the Queue

Hi, my worker throws a custom error class, I do see the error with the relevant class name & stack trace in the Bull-Dashboard.

But when the failed event triggered on the queue process I get only the error’s message field. https://github.com/taskforcesh/bullmq/blob/master/src/classes/job.ts#L375

class CustomError extends Error {
  public code: any;
  public details: string[];

  constructor(code, message, details) {
    super(message);

    Error.captureStackTrace(this, this.constructor);

    this.name = this.constructor.name;
    this.message = message;

    this.code = code;
    this.details = details;
  }
}

// worker - a separate process
const worker = new Worker(
  'queueName',
  async (job) => throw new CustomError(4004, 'Message not found', 'more details')
);

// queue - main process
queue = new Queue('queueName');
const job = await queue.add('test', { foo: 'bar' });
try {
  const result = await job.waitUntilFinished(queueEvents);
} catch (error) {
  // error.message will contain "Message not found"
  // here the error doesn't have any fields of the custom error event.  (such as name, code)
}

In bull-dashboard I do see the original error object, that means that the info exists in redis.

I hope that the issue is clear, if not, I’m available for more details.

[manast]

@mattwynne I am not super positive about this idea but I may change my opinion in the future.

[mattwynne]

@drone1 I don’t understand your question, sorry.

What I’m suggesting is to remove the assumption that the error raised in the worker will neccesarily be of type Error and support a way to serialize / deserialize custom errror types.

Even if bull were opinionated about using a particular framework / library for custom errors, I think that would be fine.