UnhandledPromiseRejectionWarning for ServerError

[TobiaszCudnik]

Even when everything is wrapped in a try-catch clause, in case of a request error (eg ServerError), one will get an UnhandledPromiseRejectionWarning.

Reproduction:

import { Client } from "@automationcloud/client";

async function main() {
  try {
    const client = new Client({
      serviceId: "12345",
      auth: "12345",
    });
    const job = await client.createJob();
    const [output1] = await job.waitForOutputs("finalPrice");
    await job.submitInput("finalPriceConsent", output1);
    await job.waitForCompletion();
  } catch {
    console.log("fail");
  }
}

main();

Result:

(node:3444473) UnhandledPromiseRejectionWarning: ServerError: ServerError
    at Job._track (./node_modules/@automationcloud/client/out/main/job.js:359:31)
        -> ./node_modules/@automationcloud/client/src/main/job.ts:387:31
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at emitUnhandledRejectionWarning (internal/process/promises.js:168:15)
    at processPromiseRejections (internal/process/promises.js:247:11)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)
(node:3444473) ServerError: ServerError
    at Job._track (./node_modules/@automationcloud/client/out/main/job.js:359:31)
        -> ./node_modules/@automationcloud/client/src/main/job.ts:387:31
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:3444473) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    at emitDeprecationWarning (internal/process/promises.js:180:11)
    at processPromiseRejections (internal/process/promises.js:249:13)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)