You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I tried to check if this code uses the noAssert argument when using the Node.js Buffer. I also tried to check if some Buffer#read(U)Int and Buffer#write(U)Int functions use the default offset (not passing through any offset will coerce undefined to zero).
The code was just not straight forward enough for me to determine this easily to open a fix if either would be the case.
If either is the case, please consider changing that. The support for those two dropped for the upcoming Node.js 10.x release.
Looks like we do not use noAssert and always specify offset for write functions. Read/write functions are only used in buf.js file. Mentioned PR addresses another deprecation - Buffer constructor.
Thanks again for reporting this problem @BridgeAR!
Hey, I tried to check if this code uses the
noAssert
argument when using the Node.js Buffer. I also tried to check if someBuffer#read(U)Int
andBuffer#write(U)Int
functions use the default offset (not passing through any offset will coerce undefined to zero).The code was just not straight forward enough for me to determine this easily to open a fix if either would be the case.
If either is the case, please consider changing that. The support for those two dropped for the upcoming Node.js 10.x release.
Refs: nodejs/node#18395
The text was updated successfully, but these errors were encountered: