James M Snell

@bnoordhuis : > fairly sure that one is isolate groups not being fully baked yet ... Yep. There are still a couple of todos remaining. The Igalia folks are on...

Another possible approach for the JS API here would be to expose Isolate Groups as an object under the `worker_threads` module such as... ``` import { WorkerGroup } from 'node:worker_threads';...

@laurisvan .... no definitive schedule. We have a status update call later this week that should help narrow down expected timeframe.

Blog post briefly discussing isolate groups .... https://dbezhetskov.dev/multi-sandboxes/

Quick status update... the isolate groups API is nearly stable in v8. Most of the key pieces are there with just a handful of small fixes/patches necessary to land over...

There are some misconceptions to clear up. The reason enabling pointer compression previously limited the process as a whole to a 4 GB heap is because there was one cage...

And yeah, v8 sandbox is another thing entirely. While it does build on the pointer compression cage we can enable pointer compression without turning on v8 sandbox. It's not clear...

You're killing me here flaky CI.... sigh

No idea if it's flaky failures or failures related to this changeset. Will close for now and revisit later.

> Don't merge just yet – will review today Yep, figured as much. Want to make sure this is going to be good with the work you're doing