Joyee Cheung
Joyee Cheung
The draft agenda is in https://docs.google.com/spreadsheets/d/1_FNNbKYcc032NIUqeJ3SZP3PM71aYMuv9D5JbwaS9Iw/edit?usp=sharing (it's not final, this session is currently planned to be 16:00 on day 1). If you have any comments, it would be easier to...
It comes down to whether `util.getCallSite()` wants to reach feature parity with `err.stack`. `err.stack` is generated by Node.js's stack trace preparation handler, which will map the source positions using the...
IIUC this has been fixed by https://github.com/nodejs/node/pull/54823 and the conclusion is..when using `node:test`, try not to stretch the concurrency that much?
Technically, when the test is in `parallel`, I think the concurrency would be better be just 1, because the python test runner already runs the tests concurrently based on the...
I think the problem is more like, the Python test runner concurrency should not be mixed with node:test concurrency. Say there are 8 cores, and using Python test runner to...
Maybe an environment variable to specify max concurrency could help, which can be used to override concurrency coming from the JS API. The Python test runner can always set it...
We are currently manually deleting `Error.stackTraceLimit` before snapshot serialization in here https://github.com/nodejs/node/blob/f29d2b7053e88517414dd419ed3a18df54a509fb/lib/internal/main/mksnapshot.js#L149-L159 Some background on this behavior: when V8 deserialize the snapshot, it will try to re-install `Error.stackTraceLimit` (which can...
So V8 doesn't actually install `Error.stackTraceLimit` when the context is created for building a snapshot (in addition V8 doesn't install several APIs, most importantly `WebAssembly`, when it's in a context...
as @climba03003 mentioned in https://github.com/nodejs/node/issues/55417#issuecomment-2422082038 - for the end users, if they want to supress the warning, they could use ``` node --disable-warning=ExperimentalWarning entry.js ``` Or if it's run by...
> It's lit up my server code like crazy Is the server code running multiple processes/workers? This should only be emitted once per process/worker. > If it's so experimental shouldn't...