-
-
Notifications
You must be signed in to change notification settings - Fork 35.4k
stream: fix addAbortSignal() for web streams #62450
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
Open
ikeyan
wants to merge
6
commits into
nodejs:main
Choose a base branch
from
ikeyan:fix-k-controller-error-function
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
ac82063
stream: use internal abort hooks for web streams
ikeyan bb0c045
test: cover webstreams addAbortSignal regressions
ikeyan e65f320
stream: move webstream abort hooks onto prototypes
ikeyan ec81573
stream: minimize webstream abort hook behavior changes
ikeyan 8242862
stream: reject TransformStream in addAbortSignal
ikeyan 79df0f7
doc: update addAbortSignal webstream behavior
ikeyan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -78,7 +78,7 @@ const { | |
| kIsClosedPromise, | ||
| kIsErrored, | ||
| kIsWritable, | ||
| kControllerErrorFunction, | ||
| kControllerAbortFunction, | ||
| } = require('internal/streams/utils'); | ||
|
|
||
| const { | ||
|
|
@@ -173,7 +173,7 @@ class WritableStream { | |
| this[kState] = createWritableStreamState(); | ||
|
|
||
| this[kIsClosedPromise] = PromiseWithResolvers(); | ||
| this[kControllerErrorFunction] = () => {}; | ||
| this[kControllerAbortFunction] = () => {}; | ||
|
|
||
| const size = extractSizeAlgorithm(strategy?.size); | ||
| const highWaterMark = extractHighWaterMark(strategy?.highWaterMark, 1); | ||
|
|
@@ -1322,7 +1322,9 @@ function setupWritableStreamDefaultController( | |
| writeAlgorithm, | ||
| }; | ||
| stream[kState].controller = controller; | ||
| stream[kControllerErrorFunction] = FunctionPrototypeBind(controller.error, controller); | ||
| stream[kControllerAbortFunction] = (reason) => { | ||
| setPromiseHandled(writableStreamAbort(stream, reason)); | ||
|
ikeyan marked this conversation as resolved.
Outdated
|
||
| }; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Slightly off-topic: should we make this a class method instead? For class WritableStream {
[kControllerAbortFunction](reason) {
setPromiseHandled(writableStreamAbort(this, reason));
}
}For |
||
|
|
||
| writableStreamUpdateBackpressure( | ||
| stream, | ||
|
|
||
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity: why are we erroring the stream instead of canceling it?
readableStreamCancel, and the stream will call thesource.cancelcallback so it can clean up any resources.controller.error, there is no so such callback, since the Streams standard assumes that the error was signaled by the source. If we allow a consumer to inject an error into the stream, this may leak resources in the source.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MattiasBuelens
Should I include that fix here as well?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, that's probably not a good idea. TheaddAbortSignaldocumentation currently states that it callscontroller.error, so changing that will be a breaking change... 🤔Let's stick with the current behavior for now. I'll put up a separate draft PR to discuss if we want to change it or not.Actually, this PR is already introducing a breaking change for
WritableStream... so maybe we should just fix both. 😅There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to preserve the current
addAbortSignalbehavior of leaving the stream in anerroredstate, but with the proper cleanup throughsource.cancel(), we could modifyreadableStreamCancelslightly:We could then define
ReadableStream[kControllerAbortFunction]as such:That will call
source.cancelwhile still passing all your tests. Best of both worlds? 🙂