| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
an asynchronous hop?
Sorry, something went wrong.
There was a problem hiding this comment.
Done.
Sorry, something went wrong.
There was a problem hiding this comment.
Link doesn't seem to work.
Sorry, something went wrong.
There was a problem hiding this comment.
Also execuationAsyncIds -> executionAsyncIds in the previous line.
Sorry, something went wrong.
There was a problem hiding this comment.
It seems this should be [promise execution tracking][]
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks. Fixed.
Sorry, something went wrong.
There was a problem hiding this comment.
🐯
Sorry, something went wrong.
There was a problem hiding this comment.
Fixed all the 🐯s.
Sorry, something went wrong.
There was a problem hiding this comment.
This is because callbacks passed to then (or catch; I think you should add that) are added to the Promise micro-task queue, right? Maybe mention that callbacks passed to then are different than the ones passed to the Promise constructor because they will not run synchronously from where then is called.
Sorry, something went wrong.
There was a problem hiding this comment.
Added mention of catch callbacks. The reason is actually due to the implementation choice in PromiseHooks. It was entirely possible for V8 to implement things in a way that promises created by new or Promise.resolve() etc. would get before / after callbacks too. For the tradeoffs used, see this doc.
Sorry, something went wrong.
There was a problem hiding this comment.
instrospection -> introspection
Sorry, something went wrong.
There was a problem hiding this comment.
Done.
Sorry, something went wrong.
There was a problem hiding this comment.
tigger -> trigger
Sorry, something went wrong.
There was a problem hiding this comment.
Done.
Sorry, something went wrong.
There was a problem hiding this comment.
It seems this will be #async_hooks_promise_execution_tracking
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks, done.
Sorry, something went wrong.
AsyncHooks have a few subtleties with being able to track promises. This commit adds a section to the docs that explains things the issues. PR-URL: nodejs#18540 Fixes: nodejs#18520 Reviewed-By: James M Snell <jasnell@gmail.com>
AsyncHooks have a few subtleties with being able to track promises. This commit adds a section to the docs that explains things the issues. PR-URL: nodejs#18540 Fixes: nodejs#18520 Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
AsyncHooks have a few subtleties with being able to track promises.
This commit adds a section to the docs that explains things the issues.
Fixes: #18520
Checklist
Affected core subsystem(s)
doc:async_hooks
/cc @nodejs/async_hooks @nodejs/diagnostics
EDIT: CI: https://ci.nodejs.org/job/node-test-pull-request-lite/146/