UnhandledPromiseRejectionWarning after upgrade

I’m using the following npm packages

"@pollyjs/adapter-fetch": "^1.0.0",
"@pollyjs/core": "^1.0.0",
 "@pollyjs/persister-fs": "^1.0.0",

If I try to upgrade @pollyjs/core to 1.1.0 or higher I get the following warnings running my tests with Jest:

(node:16928) UnhandledPromiseRejectionWarning: Error: [Polly] [adapter:fetch] Unhandled request: GET http://localhost/api/gas-types/.
(node:16928) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
(node:16928) [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.
(node:16928) UnhandledPromiseRejectionWarning: Error: [Polly] [adapter:fetch] Unhandled request: GET http://localhost/api/location/.
(node:16928) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .

any ideas how to figure it out why?

[ericbiewener]

I find that this issue occurs if my test finishes before the polly request completes (in my use case, I don’t care about the results of the request). I’m using setup-polly-jest and calling polly.flush() in Jest’s afterEach() setup method seems to do the trick:

const { testPath } = global.jasmine;

Object.defineProperty(window, "fetch", { value: fetch, writable: true });
Polly.register(NodeHttpAdapter);
Polly.register(FSPersister);

const ctx = setupPolly({
  adapters: ["node-http"],
  persister: "fs",
  persisterOptions: {
    fs: {
      recordingsDir: path.resolve(testPath, "..", "./__recordings__"),
    },
  },
  matchRequestsBy: {
    headers: false,
    order: false,
  },
});

beforeEach(() => {
  global.polly = ctx.polly;
});

afterEach(async () => {
  await ctx.polly.flush()
});

[jasonmit]

Closing as the issue is old and awaiting on polly.flush() before your tests end should resolve this for most. If there are edge cases, feel free to open a new issue with clear instructions on how to reproduce.