René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"trace-atomics-wait 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\ntrace-atomics-wait\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/parallel/test-trace-atomics-wait.js` in this repo with\r\n\r\n```diff\r\n-`, { eval: true, workerData: i32arr });\r\n+`, { eval: true, workerData: i32arr, env: process.env });\r\n```\r\n\r\nand then run \r\n\r\n```\r\nnode ./test/parallel/test-trace-atomics-wait.js\r\n```\r\n\r\nthe 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\nThis may be a dup of https://github.com/nodejs/node/issues/52825, but given that it's a different flag, the fix might be slightly different, so I figured I should bring it to your attention","author":{"url":"https://github.com/orinatic","@type":"Person","name":"orinatic"},"datePublished":"2024-06-06T19:20:57Z","url":"https://github.com/nodejs/node/issues/53374"}