-
-
Notifications
You must be signed in to change notification settings - Fork 32.9k
streams: add check transfer option #59610
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
hotpineapple
wants to merge
1
commit into
nodejs:main
Choose a base branch
from
hotpineapple:implement-transform-stream-memeber-check
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.
+14
−8
Open
Changes from all commits
Commits
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
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.
These steps aren't explicitly listed in the specification for
structuredClone
. It also seems weird to handle a highly specific edge case like this here, especially since there are many other ways than juststructuredClone
that can trigger a transfer, e.g.postMessage
. If we really needed a workaround specific toTransformStream
s, I would expect to find it near the implementation of its transfer steps, so that it is handled correctly regardless of how the transfer was triggered.But to be honest, I don't think we should be fixing the test failure by adding extra code to detect this exact edge case. The streams specification requires that the transfer fails if the readable or writable side of the
TransformStream
is locked, which should be the case if either side was transferred before. It seems like Node's current implementation doesn't do these checks correctly, and we should investigate and fix the root cause of that problem instead.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.
Looking a bit closer, I believe the transfer steps for
TransformStream
are not implemented correctly. Steps 3 and 4 of the specification requirereadable
andwritable
to be structurally cloned during the transfer steps ofTransformStream
. However, Node's implementation simply creates adata
object with the not-yet-transferredreadable
andwritable
streams... 🤔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 I really appreciate your detailed explanation! I'll review it again based on what you said.🙂