-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[async_hooks] tracking issue #29
Comments
Nice, thanks for putting this together! 😸 |
Added:
|
@trevnorris could you add a link to the Promises issue in v8. |
@AndreasMadsen Sorry. Forgot about this. Here's the link: https://bugs.chromium.org/p/v8/issues/detail?id=4643 |
|
updates: work is being done on:
new:
|
Note: Getting MakeCallback reentrant, which is necessary to fix some issue with AsyncWrap, has been a bit of a pain. Hopefully will be able to finish it this week. |
MakeCallback is now reentrant, and working on a few other improvements for an EnterpriseJS talk today. I'll throw them up in a PR later this week. |
Updated with PR: nodejs/node#8531 and EP: nodejs/node-eps#18 The current status is that Promises and addon integration is still a todo. The Addon integration solution is documented in nodejs/node-eps#18, but not yet implemented. |
@trevnorris can you share an update? |
IMHO, it would be great if |
I have updated the tracking issue to reflect this. |
Great news! But does the fact that Promises/Microtask is not ticked off on OP indicate this isn't working yet? |
@overlookmotel Yes, Promises will come in another PR soon. It was excluded from nodejs/node#12953 because it was already quite big and we wanted to land it before we got more merge conflicts. |
Added this
as we need to cover both NaN and N-API |
@overlookmotel Check out nodejs/node#13000 |
The C++ Embedder API is in progress, added a PR reference: nodejs/node#13142 |
updated promise support status and added: " |
C++ Embedder API has been implemented and merged. I've created an issue for integrating it with NAN and N-API. |
Closing this issue. I will create a new one for how we are going to bring |
Missing Handle context
parserOnBody
MakeCallback
node#5419 and src,http: fix uncaughtException miss in http node#5591,depends on: src: fix MakeCallback error handling node#4507node issue: AsyncWrap promises#9v8 issue: https://bugs.chromium.org/p/v8/issues/detail?id=4643exit
andbeforeExit
has no contextemitDestroy
doesn't emitdestroy
upon process termination (issue: Questions: async_hooks destroy callback vs setImmediate node#13262, PR: async_hooks: run destroy callbacks before normal exit node#13286)More events
onready (issue: async_wrap: when is callback ready to be called #11) - unlikely to be solved. As of now, not part ofasync_hooks
API.onerror (issue: async-wrap: no way to catch errors without changing the throw origin node#669, async_wrap: error handling #7) - awaiting use cases. As of now, not part ofasync_hooks
API.API
process.binding
is being deprecated by node: deprecate public access toprocess.binding
node#2768 (issue: missing, PR: Async Hooks - Initial Implementation node#12892)setupHooks
calls. (issue: Multiple users of asyncWrap in a single application? #40, PR: Async Hooks - Initial Implementation node#12892)Documentation
async_hooks
API. (PR: docs: documenting async hooks features node#13287)If something is missing just edit this. But add a comment so we can keep the history.
The text was updated successfully, but these errors were encountered: