You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im just writing an app with typescript. I have a bad restricted connection so not all requests end with success in a first attempt.
For some reason I can't catch such network errors with try-catch clause:
node:internal/errors:787
const ex = new Error(msg);
^
Error: socket hang up
at connResetException (node:internal/errors:787:14)
at TLSSocket.socketOnEnd (node:_http_client:519:23)
at TLSSocket.emit (node:events:530:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'ECONNRESET'
}
It catches globally, not from the synchronous code flow.
You cat reproduce such errors with while(true) await outline.createUser(); and simulating bad connection.
Can't obtain from which section of code this throws because the stack trace is uninformative.
The text was updated successfully, but these errors were encountered:
Im just writing an app with typescript. I have a bad restricted connection so not all requests end with success in a first attempt.
For some reason I can't catch such network errors with try-catch clause:
It catches globally, not from the synchronous code flow.
You cat reproduce such errors with
while(true) await outline.createUser();
and simulating bad connection.Can't obtain from which section of code this throws because the stack trace is uninformative.
The text was updated successfully, but these errors were encountered: