-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
If request starts after the signal has already been aborted, it won't throw an error #660
Comments
Agreed |
Agreed. Does it actually send the request or does it silently fail? Also, what does fetch do? |
Ky sends the request, fetch throws an error and does not send the request. |
I believe this is happening because when we create our abort controller, we only listen for future aborts from the user's signal. We need to either copy |
Hey folks, I prepared a PR for this (with
Has anyone faced this issue? |
I'm not sure if the tests have been run on Windows before. My recommendation would be to use the Windows Subsystem for Linux, which is the official way to run *nix software on Windows. But we would probably also accept a patch to get the tests working on Windows, assuming it's something simple like a file path issue. |
Added a PR for this here. This is my first time helping out a open source library, please let me know how to improve my PR and I will be happy to contribute. I tried to add a test for this scenario. Facing some issues there, I've posted details on the PR, can you help me there if possible? |
Fixed in #663 |
If request starts after the signal has already been aborted, it won't throw an error, although it probably should.
The text was updated successfully, but these errors were encountered: