near-lake-framework-js
near-lake-framework-js copied to clipboard
How does one cater to ETIMEOUT Errors
Hey near team i have been facing the following issue from time to time and would like to know what could be causing it ? is it a local issue on my end if so is there a way to specify retry logic on the user end ?
Failed to list blocks. Retrying. Error: read ETIMEDOUT
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -60,
code: 'ETIMEDOUT',
syscall: 'read',
name: 'TimeoutError',
'$metadata': { attempts: 4, totalRetryDelay: 436 }
}```