fix: handle any sequence in AbortSignal#310
Merged
Merged
Conversation
Treat `AbortSignal.any()` as sequence and validate entries before creating dependent signal. Also I'm not sure why dom AbortSignal tests were not enabled, they would certainly catch that, but they seem to be passing now.
Member
Author
|
Hey @tschneidereit, is there any chance to get this patch reviewed and merged? |
tschneidereit
approved these changes
Jul 20, 2026
tschneidereit
left a comment
tschneidereit
left a comment
Member
There was a problem hiding this comment.
Apologies for the delay!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Treat
AbortSignal.any()as sequence and validate entries before creating dependent signal.Also I'm not sure why dom
AbortSignaltests were not enabled, they would certainly catch that, but they seem to be passing now.Closes: #309