Any idea how to work around ERR_WORKER_INVALID_EXEC_ARGV ?

[danieltroger]

Has someone seen this error before? When trying to run our tests which use parcel build in docker on my m1 macbook pro using orbstack , I'm getting this error:

#52 3.924 Error [ERR_WORKER_INVALID_EXEC_ARGV]: Initiated Worker with invalid execArgv flags: --no-opt
#52 3.924     at new NodeError (node:internal/errors:405:5)
#52 3.924     at new Worker (node:internal/worker:222:13)
#52 3.924     at ThreadsWorker.start (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/threads/ThreadsWorker.js:38:19)
#52 3.924     at Worker.fork (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/Worker.js:84:23)
#52 3.924     at WorkerFarm.startChild (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/WorkerFarm.js:216:12)
#52 3.924     at WorkerFarm.startMaxWorkers (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/WorkerFarm.js:361:14)
#52 3.924     at new WorkerFarm (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/WorkerFarm.js:123:10)
#52 3.924     at createWorkerFarm (/storefronts/vanilla-js/.yarn/cache/@parcel-core-npm-2.9.3-b343ad5e82-e4ba4e0909.zip/node_modules/@parcel/core/lib/Parcel.js:445:10)
#52 3.924     at Parcel._init (/storefronts/vanilla-js/.yarn/cache/@parcel-core-npm-2.9.3-b343ad5e82-e4ba4e0909.zip/node_modules/@parcel/core/lib/Parcel.js:156:20)
#52 3.924     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
#52 3.924   code: 'ERR_WORKER_INVALID_EXEC_ARGV'
#52 3.924 }
#52 3.925 Error [ERR_WORKER_INVALID_EXEC_ARGV]: Initiated Worker with invalid execArgv flags: --no-opt
#52 3.925     at new NodeError (node:internal/errors:405:5)
#52 3.925     at new Worker (node:internal/worker:222:13)
#52 3.925     at ThreadsWorker.start (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/threads/ThreadsWorker.js:38:19)
#52 3.925     at Worker.fork (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/Worker.js:84:23)
#52 3.925     at WorkerFarm.startChild (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/WorkerFarm.js:216:12)
#52 3.925     at WorkerFarm.startMaxWorkers (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/WorkerFarm.js:361:14)
#52 3.925     at new WorkerFarm (/storefronts/vanilla-js/.yarn/__virtual__/@parcel-workers-virtual-a726b8dab9/0/cache/@parcel-workers-npm-2.9.3-b0559c8ccb-d6ac6e2abf.zip/node_modules/@parcel/workers/lib/WorkerFarm.js:123:10)
#52 3.925     at createWorkerFarm (/storefronts/vanilla-js/.yarn/cache/@parcel-core-npm-2.9.3-b343ad5e82-e4ba4e0909.zip/node_modules/@parcel/core/lib/Parcel.js:445:10)
#52 3.925     at Parcel._init (/storefronts/vanilla-js/.yarn/cache/@parcel-core-npm-2.9.3-b343ad5e82-e4ba4e0909.zip/node_modules/@parcel/core/lib/Parcel.js:156:20)
#52 3.925     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
#52 3.925   code: 'ERR_WORKER_INVALID_EXEC_ARGV'
#52 3.925 }

Beginning of Dockerfile:

FROM testcafe/testcafe:latest as init
# yay, testcafe switches to "user", but that makes permissions after copy a nightmare
USER root

RUN apk add --update --no-cache bash
RUN npm i -g corepack
ENV NODE_VERSION 20.5.0
# Download Node.js, install it, and clean up
RUN apk add --no-cache curl && \
    curl -fsSLO --compressed "https://unofficial-builds.nodejs.org/download/release/v$NODE_VERSION/node-v$NODE_VERSION-linux-x64-musl.tar.xz" && \
    tar -xJf "node-v$NODE_VERSION-linux-x64-musl.tar.xz" -C /usr/local --strip-components=1 --no-same-owner && \
    rm "node-v$NODE_VERSION-linux-x64-musl.tar.xz" && \
    apk del curl
RUN apk add --update --no-cache python3 && ln -sf python3 /usr/bin/python # native addons need python to build

[danieltroger]

It doesn't help to limit orbstack to 100% CPU :(

[mischnic]

There is already some logic to filter out a few Node CLI arguments when starting workers:

parcel/packages/core/workers/src/Worker.js

Lines 50 to 55 in aaaf22d

	async fork(forkModule: FilePath) {
	let filteredArgs = process.execArgv.filter(
	v => !/^--(debug|inspect|max-old-space-size=)/.test(v),
	);
	for (let i = 0; i < filteredArgs.length; i++) {

Looks like that has to be added as well. Though it's interesting that your env somehow causes Node to run without the Turbofan JIT

[danieltroger]

Ah, very interesting, thanks a lot for the info.
Yeah I have no idea why there's a --no-opt flag either.

WDYT about #9239?