Joyee Cheung

https://github.com/nodejs/reliability/issues/676 indicates that this happens on test-rackspace-win2022_vs2022-x64-1 and test-rackspace-win2022_vs2022-x64-2 too, maybe less frequent though

This seems to tie into another topic of whether `subprocess.kill()`/`SIGTERM` should just terminate the process with only the essential cleanups (it's debatable whether dumping cpu profiles should be considered essential),...

There is a merge conflict because there are new TODO entries. I think we can just open issues for them and delete the file.

I tried to fix it in https://github.com/nodejs/devcontainer/pull/13 but it seems building arm64 in emulation made the build take a very long time and exceeds the 6h limit. Now I can...

> Alternatively, you might want to retire this repo and direct people to mcr.microsoft.com/devcontainers/javascript-node:1-22-bookworm for example. That is different from what this repo does, this repo maps to local clones...

I think this should make it work: https://github.com/nodejs/devcontainer/pull/14

This should be fixed by https://github.com/nodejs/devcontainer/pull/14 now.

I feel that this should probably be the opening session, but that will be 9:30 CET. Putting it in other slots would be a bit more weird? @mhdawson would that...

Or we can maybe make the first morning free hacking time & hallway track, and then put the opening session at 12:00 CET (some time before lunch)

The draft agenda is in https://docs.google.com/spreadsheets/d/1_FNNbKYcc032NIUqeJ3SZP3PM71aYMuv9D5JbwaS9Iw/edit?usp=sharing (it's not final, this session is currently the opening session after lunch on day 1, so 8:30 EDT, before lunch there's some CI deflakathon...