Skip to content
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

Streams: test whether patched then() sees correct byobRequest #48085

Conversation

MattiasBuelens
Copy link
Contributor

@MattiasBuelens MattiasBuelens commented Sep 10, 2024

See whatwg/streams#1326 for context.

This also updates the transferArrayBufferView test utility to be synchronous, which slightly changes the timings of some tests in streams/readable-byte-streams/general.any.js.

Copy link
Contributor

@ricea ricea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks!

@domenic domenic merged commit bc9dcbb into web-platform-tests:master Nov 27, 2024
19 checks passed
kennethmyhra added a commit to kennethmyhra/ladybird that referenced this pull request Dec 1, 2024
This aligns us with the latest streams specification changes to
accommodate for the security advisor GHSA-p5g2-876g-95h9.
See relevant links:
GHSA-p5g2-876g-95h9
web-platform-tests/wpt#48085

Previously we would crash when running the attached test since we have
an assert in ReadableByteStreamControllerFillHeadPullIntoDescriptor
verifying that controller controller.raw_byob_request() is null.

These changes make sure that we postpone calls to
ReadableByteStreamControllerCommitPullIntoDescriptor until after all
pull-into descriptors have been filled up by
ReadableByteStreamControllerProcessPullIntoDescriptorsUsingQueue.

The attached test verifies that a pachted then() will see a null
byobRequest.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants