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
I couldn't create a consistent example to reproduce the issue, but sometimes (once to 2-3 runs) the code fails to emit a timeout event when using an invalid URL (e.g. example.test). However, it emits the event every time when using nowhere.com.
It reproduces only after at least one request prior to the request with the timeout.
My best guess is that something within Node aborts the request with ENOTFOUND before it checks the timeout.
I couldn't create a consistent example to reproduce the issue, but sometimes (once to 2-3 runs) the code fails to emit a timeout event when using an invalid URL (e.g. example.test). However, it emits the event every time when using nowhere.com.
It reproduces only after at least one request prior to the request with the timeout.
My best guess is that something within Node aborts the request with ENOTFOUND before it checks the timeout.
logs:
The text was updated successfully, but these errors were encountered: