Joyee Cheung

Node.js has partly mitigated the problem by providing a stronger stability guarantee through `err.code` - prior to the introduction of the [new error code system](https://github.com/nodejs/node/blob/master/doc/api/errors.md#nodejs-error-codes) every changes to the error...

hmm, it seems a bit too late to squeeze another session in, we have a packed agenda. Would it make sense to move it to the hallway track? (We have...

Should this remain open? Sounds like a good session for the next summit.

Looks like we have a timing conflict with https://github.com/nodejs/node/issues/30846#issuecomment-564365365 - if we migrate to the new CppHeap management, the CppHeap is torn down during Isolate disposal, and at this point...

I wonder if there's another way to fix the isolate disposal race condition...by shutting down the platform data/task runner after we remove it from the map? In that case it's...

https://github.com/v8/node/pull/187 contains part of what this PR does. Maybe we can just migrate the wrapper descriptors stuff first and deal with the Isolate teardown stuff in a separate PR, as...

Updated this branch on top of canary-base and split out the wrapper descriptor part. The CppHeap management + Isolate registration changes are now in https://github.com/nodejs/node/pull/53205 Although this is now failing...

Pushed a commit here to fix the -Werror=comment errors in v8-sandbox.h to see if Linux CI is happy with it..

The heap snapshot failures are the same as https://github.com/nodejs/node-v8/issues/282 which are being fixed in https://chromium-review.googlesource.com/c/v8/v8/+/5531355

v8-sandbox.h fixes upstreamed in https://chromium-review.googlesource.com/c/v8/v8/+/5584738