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
fix: only remove hijackable envs from foreign parent #41079
Conversation
Release Notes Persisted
|
I have automatically backported this PR to "26-x-y", please check out #41099 |
I have automatically backported this PR to "27-x-y", please check out #41100 |
I have automatically backported this PR to "28-x-y", please check out #41101 |
I have automatically backported this PR to "29-x-y", please check out #41102 |
Description of Change
#40770 took an aggressive way to disable all envs starting with
NODE_
when process is started from a foreign parent, but it appears that at least a portion of apps are running into issues when usingfork
legally #40987.This PR takes a simpler approach by only disabling the
NODE_OPTIONS
andNODE_REPL_EXTERNAL_MODULE
to fix node IPC, I'll try to locate the root issue and figure out a better approach in following PRs.Checklist
npm test
passesRelease Notes
Notes: Fix forked child process not able to send IPC message under some cases on macOS.