René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"cpu-prof doesn't propagate to workers when env is set ","articleBody":"### Version\n\n20.8.1\n\n### Platform\n\nLinux ushanka-housing 6.5.0-1020-oem #21-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr  3 14:54:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux\n\n### Subsystem\n\ncpu-prof\n\n### What steps will reproduce the bug?\n\nYou can reproduce this by modifying one of the existent node tests. \r\n\r\nIf you edit `tests/fixtures/workload/fibonacci-worker.js` in this repo with\r\n\r\n```diff\r\n-new Worker(path.join(__dirname, 'fibonacci.js'));\r\n+new Worker(path.join(__dirname, 'fibonacci.js'), {env: process.env});\r\n```\r\n\r\nand then run \r\n```\r\nnode ./test/sequential/test-cpu-prof-dir-worker.js\r\n```\r\n\r\nthe new test will fail\n\n### How often does it reproduce? Is there a required condition?\n\nThis should reproduce 100% of the time -- you don't need to do anything special\n\n### What is the expected behavior? Why is that the expected behavior?\n\nAccording to https://nodejs.org/docs/latest-v20.x/api/worker_threads.html#new-workerfilename-options, the default value for a worker thread's env is process.env. Thus, not passing an environment and passing process.env as the environment should always produce the same behavior. \n\n### What do you see instead?\n\nWhen running in its original form, the test produces two profile files, as intended. When passing `{env: process.env}` into the worker invocation, however, it only produces one profile file. \n\n### Additional information\n\nIf I print the environment in the worker thread, it appears to be identical in both cases. It doesn't seem like the problem is that part of the environment is getting lost, but rather there's some hidden variable that isn't getting propagated","author":{"url":"https://github.com/orinatic","@type":"Person","name":"orinatic"},"datePublished":"2024-05-03T16:05:43Z","url":"https://github.com/nodejs/node/issues/52825"}