-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
setcap on Node.js prevents processing of NODE_OPTIONS #37588
Comments
When did this behavior break? It doesn't look like the code changed. Is this a change in kernel security? |
Reproduced on 17.3.0. Its very important for debugging sсripts that using Bluetooth and GPIO. Please fix it. |
Just wanted to share this is also happening for node v14 under Linux. The annoying part is it took me hours to land at this conclusion. The only workaround seems to be NOT using |
What steps will reproduce the bug?
sudo setcap cap_net_admin+iep $(which node)
How often does it reproduce? Is there a required condition?
100% of the time
What is the expected behavior?
I would expect NODE_OPTIONS to be processed regardless.
What do you see instead?
Additional information
Reported on microsoft/vscode-js-debug#852
The text was updated successfully, but these errors were encountered: