-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Buffer deprecated warning #136874
Comments
Try to pass --trace-deprecation as an
I saw you were on Windows, but for Linux it is just |
Is there something else I should try? |
Well if any of these don't work, idk. |
Probably #82524 |
I do not think it is related to #82524 because in the other, warning is shown only while installing the extension. |
Adding
|
@chrmarti maybe we can fix this in our |
Also tracked as TooTallNate/node-get-uri#18 and mscdex/node-ftp#255. |
Some time ago your bot closed my issue about this (I still don't know why ...) |
[error] [Extension Host] (node:61654) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. I have also encountered the same problem, I am using a Macbook Pro with M1 chip, the system is the latest macOS Monterey 12.0.1 (21A559) VS Code version 1.62.3, I tried to delete all the extensions, but the problem still exists. |
Looks like that node-ftp project is dead. Despite there being a fix and PR, nothing has been merged since 2015. I don’t see an alternative either. |
Looking closer, we might not actually need |
👏 👏 👏 |
Does this issue occur when all extensions are disabled?: Yes
Version: 1.63.0-insider (user setup)
Commit: a7104f1
Date: 2021-11-08T05:14:49.440Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000
Steps to Reproduce:
Expected: No error messages or warnings
Actual:
(node:22768) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.(Use Code - Insiders --trace-deprecation ... to show where the warning was created).
Running
code-insiders --trace-deprecation
results in this message:Warning: 'trace-deprecation' is not in the list of known options, but still passed to Electron/Chromium.
According to one of Live Share's commenters, this is where the issue may be coming from: microsoft/live-share#3331 (comment)
The text was updated successfully, but these errors were encountered: