New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled 'error' event when using AbortSignal to cancel requests #1801
Labels
Comments
I had the same issue. In the end, I had to stop using node-fetch and instead used the native fetch API. The drawback is that it returns a (web) ReadableStream and not a (Node) stream.Readable. You'll have to use it like this
|
Happened to me as well, any resolution for this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduction
Steps to reproduce the behavior:
The problem is somehow intermittent. Try different timeout values until you can reproduce it.
I get the following error:
Expected behavior
The error happens in index.js in the following code block:
To fix it, you need a listener for the "error" event of the Readable stream, like this below:
Screenshots
Your Environment
Additional context
I believe this issue was reported in the past, but it was closed:
#1420
The text was updated successfully, but these errors were encountered: