fix(core): Fix immediate cancellation of fetch requests #3076
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #3043
Summary
The async generator implementation has regressed on the previous one since it doesn't include a delay that respects immediate
teardown
signals. This is because noyield
was present after the initial microtick and before thefetch
call.I'm still trying to find a more elegant solution to this, but it doesn't seem possible to yield without emitting a value, and async generators may not abort on
await
statements, which seems counterintuitive.Changeset hasn't been added since it's a follow-up fix.
Set of changes
yield
after microtick delay to allowfetchOperation
to abort early