mary marchini
mary marchini
Removed from the agenda since we decided to meet for deep dives on User Journeys every other week. Will re-add if the initiative stalls.
CPU Issues deep dive: https://docs.google.com/document/d/1Yip9zU_8axfZwN-clGMeoNWVYHZPfBjepLV3Ur2JjwA/edit
It would be amazing if we could do so, and it had been suggested before by V8. One thing to consider is that such a change would be semver-major, and...
Agreed, security should be taken into account, but that should be solved on the server/main-process side (and it's probably worth its own issue), otherwise we would still be able to...
I don't think I agree. Implementing the limitations on the client side means only users using that particular client will be barred from using privileged features on the inspector protocol....
Removed stale label as I'm actively working on this and will present in the next WG meeting.
@Qard should we move this to a diag-deep-dive instead of regular agenda item?
> I don't really know what it is for, how I can use it, and why we need this at Tier 1 or Tier 2. The CodeEventHandler API was created...
I believe we need to evaluate which issues are still open for async_hooks, as we have some long and last-standing issues which are touching similar topics.