-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
AbortController throws inside p-limit #64
Comments
UnlimitedBytes
changed the title
AbortController throws inside plimit
AbortController throws inside p-limit
Jul 16, 2022
@sindresorhus maybe? |
The problem seems to be caused by 7b978e3#diff-e727e4bdf3657fd1d798edcd6b099d6e092f8573cba266154583a746bba0f346R38 // @copperwall |
BUMP @sindresorhus @copperwall please I will use the package but that blocks me from using it... |
Any updates? I'm having the same issue |
It's node-fetch's issue node-fetch/node-fetch#1801. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I created a simple basic application which uses
node-fetch
to send some HTTP(S)-Requests and usesp-limit
to reduce the amount of requests send at the same time. The problem is when thenode-fetch
requests get aborted by anAbortController
they throw insidep-limit
so I can't handle theAbortError
.Reproduction
I'm providing a stripdown version of the application which only contains the parts necessary to trigger the bug.
Here is the stripdown version with
p-limit
which generates the following output:
Here is the stripdown version without
p-limit
which generates the following output:
Severity
blocking all usage of p-limit - as I can't abort requests without crashing the entire application.
Best regards
UnlimitedBytes
The text was updated successfully, but these errors were encountered: