Metaplex find nfts by creator socket timeout?

Question

I used the function provided by metaplex, namely "metaplex.nfts().findAllByCreator()" when the mint data reached thousands, I encountered a problem, namely "ERR_SOCKET_TIMEOUT" (error details below).

how do i solve this? I speculate that this timeout is caused by too much mint data, but metaplx doesn't provide options for pagination, for example, to fetch periodically.

what do I have to do? do you use the native web3 way?

FetchError: request to "https://MY_RPC_XXXXXXXX(im_sensor_this)" failed, reason: Socket timeout
    at ClientRequest.<anonymous> (/home/viandwi24/projects/work/nokiamon/node_modules/.pnpm/[email protected]/node_modules/node-fetch/lib/index.js:1491:11)
    at ClientRequest.emit (node:events:513:28)
    at ClientRequest.emit (node:domain:489:12)
    at TLSSocket.socketErrorListener (node:_http_client:494:9)
    at TLSSocket.emit (node:events:525:35)
    at TLSSocket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ERR_SOCKET_TIMEOUT',
  code: 'ERR_SOCKET_TIMEOUT'
}

Answer 1

when you create your connection also pass it an httpAgent: false to bypass the socket timeout from node.

const connection = new Connection('RPC_URL', { httpAgent: false })

An http.Agent that will be used to manage socket connections (eg. to implement connection persistence). Set this to false to create a connection that uses no agent. This applies to Node environments only.

Might also want to look into adding an AbortSignal for it it takes much longer than expected.