Jest warns of potential open handles

[arboleya]

According to suspicions, it was likely introduced by this PR:

• feat: implement GraphQL subscriptions support #1256

---

[Dhaiwat10]

Been seeing this warning with this failing test consistently on my branch for #1303

 FAIL  packages/providers/test/provider.test.ts (6.772 s)
  ● Provider › throws TimeoutError on timeout when calling an operation

    expect(received).toMatchObject(expected)

    - Expected  - 5
    + Received  + 1

    - Object {
    -   "code": 23,
    -   "message": "The operation was aborted due to timeout",
    -   "name": "TimeoutError",
    - }
    + [Error: Failed to parse "TransactionId": Invalid character 'w' at position 0: {"response":{"data":null,"errors":[{"message":"Failed to parse \"TransactionId\": Invalid character 'w' at position 0","locations":[{"line":2,"column":19}],"path":["transaction"]}],"status":200,"headers":{}},"request":{"query":"query getTransaction($transactionId: TransactionId!) {\n  transaction(id: $transactionId) {\n    ...transactionFragment\n  }\n}\n\nfragment transactionFragment on Transaction {\n  id\n  rawPayload\n  gasPrice\n  receipts {\n    ...receiptFragment\n  }\n  status {\n    ...transactionStatusFragment\n  }\n}\n\nfragment receiptFragment on Receipt {\n  contract {\n    id\n    bytecode\n    salt\n  }\n  pc\n  is\n  to {\n    id\n    bytecode\n    salt\n  }\n  toAddress\n  amount\n  assetId\n  gas\n  param1\n  param2\n  val\n  ptr\n  digest\n  reason\n  ra\n  rb\n  rc\n  rd\n  len\n  receiptType\n  result\n  gasUsed\n  data\n  sender\n  recipient\n  nonce\n  contractId\n  subId\n}\n\nfragment transactionStatusFragment on TransactionStatus {\n  type: __typename\n  ... on SubmittedStatus {\n    time\n  }\n  ... on SuccessStatus {\n    block {\n      id\n    }\n    time\n    programState {\n      returnType\n      data\n    }\n  }\n  ... on FailureStatus {\n    block {\n      id\n    }\n    time\n    reason\n  }\n}","variables":{"transactionId":"will fail due to timeout"}}}]

      686 |     });
      687 |
    > 688 |     expect(error).toMatchObject({
          |                   ^
      689 |       code: 23,
      690 |       name: 'TimeoutError',
      691 |       message: 'The operation was aborted due to timeout',

Maybe working on #1293 might fix this? Just wildly guessing here.

[arboleya]

@Dhaiwat10 also having this.

[nedsalk]

@Dhaiwat10 @arboleya
Can you run nvm use and also check if pnpm node --version is 18.18.0? I had this error as well after checking out #1303, but after sorting out the used node versions and rebuilding, it passed. Also keep in mind that multiple CI pipelines passed with this test active, which strengthens the case that this might just be a local configuration thing.