Skip to content
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

executionAsyncId in unhandledRejection and rejectionHandled is always 0 #28317

Closed
devsnek opened this issue Jun 20, 2019 · 2 comments
Closed
Labels
async_hooks Issues and PRs related to the async hooks subsystem. duplicate Issues and PRs that are duplicates of other issues or PRs. promises Issues and PRs related to ECMAScript promises.

Comments

@devsnek
Copy link
Member

devsnek commented Jun 20, 2019

  • Version: at least >= 12, probably all
  • Subsystem: async_hooks, process

The unhandledRejection and rejectionHandled events are always called in the root async context, rather than the async context of the relevant promise. The multipleResolves event is called in the correct context.

@addaleax addaleax added async_hooks Issues and PRs related to the async hooks subsystem. promises Issues and PRs related to ECMAScript promises. labels Jun 20, 2019
@devsnek
Copy link
Member Author

devsnek commented Jun 25, 2019

@nodejs/async_hooks @nodejs/promises-debugging

@devsnek
Copy link
Member Author

devsnek commented Dec 14, 2019

Duplicate of #26794

@devsnek devsnek marked this as a duplicate of #26794 Dec 14, 2019
@devsnek devsnek closed this as completed Dec 14, 2019
@devsnek devsnek added the duplicate Issues and PRs that are duplicates of other issues or PRs. label Dec 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
async_hooks Issues and PRs related to the async hooks subsystem. duplicate Issues and PRs that are duplicates of other issues or PRs. promises Issues and PRs related to ECMAScript promises.
Projects
None yet
Development

No branches or pull requests

2 participants