-
Notifications
You must be signed in to change notification settings - Fork 30k
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
DeprecatedWarning for Buffer when using the following API ReadableStreamBYOBReader
in stream
#49245
Labels
stream
Issues and PRs related to the stream subsystem.
Comments
KhafraDev
added a commit
to KhafraDev/node
that referenced
this issue
Aug 19, 2023
When using BYOB streams, it's possible for the constructor in readableByteStreamControllerConvertPullIntoDescriptor to be a node Buffer. If it is, use `Buffer.from` over `new ctor`. Fixes nodejs#49245
nodejs-github-bot
pushed a commit
that referenced
this issue
Aug 26, 2023
When using BYOB streams, it's possible for the constructor in readableByteStreamControllerConvertPullIntoDescriptor to be a node Buffer. If it is, use `Buffer.from` over `new ctor`. Fixes #49245 PR-URL: #49250 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: LiviaMedeiros <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
UlisesGascon
pushed a commit
that referenced
this issue
Sep 10, 2023
When using BYOB streams, it's possible for the constructor in readableByteStreamControllerConvertPullIntoDescriptor to be a node Buffer. If it is, use `Buffer.from` over `new ctor`. Fixes #49245 PR-URL: #49250 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: LiviaMedeiros <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
alexfernandez
pushed a commit
to alexfernandez/node
that referenced
this issue
Nov 1, 2023
When using BYOB streams, it's possible for the constructor in readableByteStreamControllerConvertPullIntoDescriptor to be a node Buffer. If it is, use `Buffer.from` over `new ctor`. Fixes nodejs#49245 PR-URL: nodejs#49250 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: LiviaMedeiros <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
targos
pushed a commit
that referenced
this issue
Nov 27, 2023
When using BYOB streams, it's possible for the constructor in readableByteStreamControllerConvertPullIntoDescriptor to be a node Buffer. If it is, use `Buffer.from` over `new ctor`. Fixes #49245 PR-URL: #49250 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: LiviaMedeiros <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
sercher
added a commit
to sercher/graaljs
that referenced
this issue
Apr 25, 2024
When using BYOB streams, it's possible for the constructor in readableByteStreamControllerConvertPullIntoDescriptor to be a node Buffer. If it is, use `Buffer.from` over `new ctor`. Fixes nodejs/node#49245 PR-URL: nodejs/node#49250 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: LiviaMedeiros <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
sercher
added a commit
to sercher/graaljs
that referenced
this issue
Apr 25, 2024
When using BYOB streams, it's possible for the constructor in readableByteStreamControllerConvertPullIntoDescriptor to be a node Buffer. If it is, use `Buffer.from` over `new ctor`. Fixes nodejs/node#49245 PR-URL: nodejs/node#49250 Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: LiviaMedeiros <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v20.5.1
Platform
Ubuntu 20.04, Microsoft Windows NT 10.0.19045.0 x64
Subsystem
No response
What steps will reproduce the bug?
I tried the same as what is in the doc.
node/doc/api/webstreams.md
Lines 525 to 581 in 41a3a1d
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
Since Buffer() was not used in the code, the warning should not occur.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: