Open handle keeping Jest from exiting

Describe the bug I have been trying to use keyv on a Jest unit test. The test runs but Jest complains in the end:

Jest has detected the following 1 open handle potentially keeping Jest from exiting:

  ●  TLSWRAP

       5 | export class Cache {
       6 |
    >  7 |   private client = new Keyv(process.env.REDIS_CONNECTION_STRING);

I have tried all sorts of approaches to “close” the handle. By calling keyv.disconnect(), by calling keyv.redis.quit(), but I keep getting errors saying the connection is already closed.

/Users/rafasiqueira/Work/etips-api/node_modules/ioredis/built/redis/event_handler.js:182
        self.flushQueue(new Error(utils_1.CONNECTION_CLOSED_ERROR_MSG));
                        ^
Error: Connection is closed.
    at close (/Users/rafasiqueira/Work/etips-api/node_modules/ioredis/built/redis/event_handler.js:182:25)
    at TLSSocket.<anonymous> (/Users/rafasiqueira/Work/etips-api/node_modules/ioredis/built/redis/event_handler.js:149:20)
    at Object.onceWrapper (node:events:652:26)
    at TLSSocket.emit (node:events:549:35)
    at node:net:747:14
    at TCP.done (node:_tls_wrap:582:7)

To Reproduce

let client = new Keyv(process.env.REDIS_CONNECTION_STRING);
private keyAdapter = new KeyvAdapter(this.client);
public faultTolerantCache = new ErrorsAreMissesCache(this.keyAdapter);

const serverOptions: ApolloServerExpressConfig = {
      schema: subgraphSchema,
      dataSources,
      context,
      plugins: [ApolloServerPluginInlineTraceDisabled()],
      cache: faultTolerantCache

let server: ApolloServer; 

beforeAll(() => {
    server = new ApolloServer(serverOptions);
});

  afterAll((done) => {
    client.disconnect().then(() => done());
  });

  it('fetches mtdsg action', (done) => {
    server.executeOperation({
      query: GET_ACTION,
      variables: { id: '080000028047f4a3' }
    })
    .then((result) => {
      expect(result.errors).toBeUndefined();
      done();
    });
  });

**Expected behavior**
The test should pass and Jest should exit.

[jaredwray]

Hi @rafagsiqueira - thanks and we are looking into this.

[rafagsiqueira]

Sorry, I ended up removing the cache from my unit tests.