Joyee Cheung

https://github.com/nodejs/node/pull/52295 should not be in v22.x directly (it needs a special backport for older versions of V8).

I think some commits from https://github.com/nodejs/node/pull/52295 are still included? They should not be in v22.x as-is because they use new APIs that are not in v8 12.4 (which only has...

Added another commit to handle the missing handle scope assertion, this fixes the npm install crash locally for me - on the other hand does this mean that the fast...

@RafaelGSS I am not seeing any merge conflicts, has v22.x-staging been updated?

It seems to keep running into infra failure. Starting one from scratch..

This has been failing due to something wrong with the python test runner..not sure what's going on

It seems to be a different problem (Python test runner not able to decode the tap output?) ``` 16:30:49 Traceback (most recent call last): 16:30:49 File "/home/iojs/build/workspace/node-test-commit-custom-suites-freestyle/tools/test.py", line 1830, in...

Actually I think something is wrong with the output of test/wpt/test-encoding.js and the python runner was trying to parse its stderr/stdout. But it doesn't look related to this PR.

Trying to cross-compare with v22.x-staging https://ci.nodejs.org/job/node-test-commit/73707/

I don't think this will make it to v22.8.0. Tried to start another CI on top of the fixed v22.x-staging, but it looks like the CI is still very overloaded...