Stephen Belanger

Doesn't help _you_, but _someone else_ could have picked up the task, if they had the money to cover their time.

> * Finding "companies which want to put money into development of specific core features" I don't think we need to do much more than just having some official _space_...

Yep, I'll definitely have plenty to say on that. Hopefully I can better clarify my reasoning for why the flow through semantics and local mutation is actually the most ideal...

Depends on the use, but yes, it's not a great API. It's really only implemented to try to keep feature parity with the async_hooks implementation. But the actual usefulness is...

Given that it's marked experimental currently, and the ergonomics are...not the best...I think it's probably fine to warn against its use, but perhaps provide more clarity about _why_ it continues...

I've been exploring all the results of the reported failures and they seem to fail and many different points in the run. It has a slight bias toward some particular...

It runs each individual test separately with the runner though rather than having one run on all matches. We _could_ probably change it to just be a single run, but...

Yep, I understand that. Doing it sequentially like it's done now though means there's no N magnification, it's just the outer test runner plus a singular inner test at the...

As far as I understand it, the intent was to just enable this for Workers behind a configuration flag or something like that. So worker_threads using apps can opt-in where...

You're thinking of https://github.com/nodejs/node/pull/56191? I don't think it's related, but maybe something that was expected to happen is not now with the bailout when it can't call into JS? Can't...