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

[v18.x backport] stream: streams and webstreams interop related changes #46314

Closed

Conversation

debadree25
Copy link
Member

@debadree25 debadree25 commented Jan 23, 2023

Backports the following PRs:
#46190
#46273
#46307
#46312
#46315
#46403
#46600
#46675

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/streams

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch. web streams labels Jan 23, 2023
@debadree25
Copy link
Member Author

cc @aduh95

@aduh95
Copy link
Contributor

aduh95 commented Jan 23, 2023

We need to wait on #46312 to land first, and backport the three PRs in one backport PR (i.e. you need to cherry-pick the two other commits onto this branch). I'm going to convert this to draft if that's OK as this can't happen until #46312 lands.

@aduh95 aduh95 marked this pull request as draft January 23, 2023 13:29
@debadree25
Copy link
Member Author

Sure no issue!

@debadree25
Copy link
Member Author

So overall would need to cherry-pick #46205, #46190, #46315 and #46312 into this single PR

@debadree25
Copy link
Member Author

Hi @aduh95 all the streams related changes have landed, should i open a fresh backport PR including all the changes?

@aduh95
Copy link
Contributor

aduh95 commented Feb 27, 2023

You can keep this PR, you just need to push the other commits to your backport-46205-to-v18.x branch.

@debadree25 debadree25 closed this Feb 27, 2023
@debadree25 debadree25 force-pushed the backport-46205-to-v18.x branch from 7902a99 to b266adb Compare February 27, 2023 09:48
@debadree25 debadree25 reopened this Feb 27, 2023
@debadree25 debadree25 changed the title [v18.x backport] stream: implement finished() for ReadableStream and WritableStream [v18.x backport] stream: streams and webstreams interop related changes Feb 27, 2023
@debadree25 debadree25 force-pushed the backport-46205-to-v18.x branch from 7204237 to f27c29c Compare February 27, 2023 10:17
@@ -2579,6 +2579,9 @@ further errors except from `_destroy()` may be emitted as `'error'`.
<!-- YAML
added: v10.0.0
changes:
- version: v18.14.0
Copy link
Member Author

Choose a reason for hiding this comment

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

This was release in #46396 hence added the version here

@debadree25 debadree25 force-pushed the backport-46205-to-v18.x branch from f27c29c to 8f10c66 Compare February 27, 2023 10:23
@debadree25
Copy link
Member Author

debadree25 commented Feb 27, 2023

Does this look ok @aduh95 ?

@debadree25 debadree25 marked this pull request as ready for review February 28, 2023 10:00
@debadree25 debadree25 requested a review from aduh95 March 12, 2023 11:12
@nodejs-github-bot
Copy link
Collaborator

@danielleadams
Copy link
Contributor

@debadree25 are you able to rebase this?

@debadree25
Copy link
Member Author

Sure will rebase this!

Refs: nodejs#39519
PR-URL: nodejs#46190
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>
PR-URL: nodejs#46312
Refs: nodejs#46190
Refs: nodejs#46205
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Refs: nodejs#46190
Refs: nodejs#46205 (comment)
PR-URL: nodejs#46315
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
@debadree25 debadree25 force-pushed the backport-46205-to-v18.x branch from 8f10c66 to 0291981 Compare May 23, 2023 19:41
@debadree25
Copy link
Member Author

Hey @danielleadams rebased this, is it ok?
So sorry for the delay 😅😅😅

@debadree25 debadree25 requested a review from danielleadams May 23, 2023 19:42
@panva panva added the request-ci Add this label to start a Jenkins CI on a PR. label May 23, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label May 23, 2023
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

danielleadams pushed a commit that referenced this pull request May 29, 2023
Refs: #39519
PR-URL: #46190
Backport-PR-URL: #46314
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>
danielleadams pushed a commit that referenced this pull request May 29, 2023
PR-URL: #46312
Backport-PR-URL: #46314
Refs: #46190
Refs: #46205
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
danielleadams pushed a commit that referenced this pull request May 29, 2023
Refs: #46190
Refs: #46205 (comment)
PR-URL: #46315
Backport-PR-URL: #46314
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
@danielleadams
Copy link
Contributor

Landed in 0b92035...e8b5a61

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-ci PRs that need a full CI run. v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch. web streams
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants