-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
process: ignore asyncId 0 in exception handler #41424
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
needs-ci
PRs that need a full CI run.
process
Issues and PRs related to the process subsystem.
labels
Jan 7, 2022
aduh95
reviewed
Jan 7, 2022
Today, the global uncaught exception handler is the only place where asyncId 0 is not ignored and we still proceed to call emitAfter. This would've already failed one of our correctness tests in async_hooks if not for some other code meant to handle a different edge case. Fixes: nodejs#22982
apapirovski
force-pushed
the
patch-fix-async-id-0
branch
from
January 7, 2022 15:38
08355ee
to
6ecf941
Compare
Flarna
approved these changes
Jan 8, 2022
aduh95
approved these changes
Jan 8, 2022
aduh95
added
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
request-ci
Add this label to start a Jenkins CI on a PR.
labels
Jan 8, 2022
github-actions
bot
removed
the
request-ci
Add this label to start a Jenkins CI on a PR.
label
Jan 8, 2022
This comment has been minimized.
This comment has been minimized.
This was referenced Jan 9, 2022
This comment has been minimized.
This comment has been minimized.
This was referenced Jan 13, 2022
aduh95
added
commit-queue
Add this label to land a pull request using GitHub Actions.
and removed
commit-queue
Add this label to land a pull request using GitHub Actions.
labels
Jan 17, 2022
This comment has been minimized.
This comment has been minimized.
jasnell
approved these changes
Jan 17, 2022
16 tasks
Flarna
added
the
commit-queue
Add this label to land a pull request using GitHub Actions.
label
Jan 18, 2022
nodejs-github-bot
added
commit-queue-failed
An error occurred while landing this pull request using GitHub Actions.
and removed
commit-queue
Add this label to land a pull request using GitHub Actions.
labels
Jan 18, 2022
Commit Queue failed- Loading data for nodejs/node/pull/41424 ✔ Done loading data for nodejs/node/pull/41424 ----------------------------------- PR info ------------------------------------ Title process: ignore asyncId 0 in exception handler (#41424) ⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile! Branch apapirovski:patch-fix-async-id-0 -> nodejs:master Labels process, author ready, needs-ci Commits 1 - process: ignore asyncId 0 in exception handler Committers 1 - Anatoli Papirovski PR-URL: https://github.com/nodejs/node/pull/41424 Fixes: https://github.com/nodejs/node/issues/22982 Fixes: https://github.com/=== Reviewed-By: Gerhard Stöbich Reviewed-By: Antoine du Hamel Reviewed-By: James M Snell ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/41424 Fixes: https://github.com/nodejs/node/issues/22982 Fixes: https://github.com/=== Reviewed-By: Gerhard Stöbich Reviewed-By: Antoine du Hamel Reviewed-By: James M Snell -------------------------------------------------------------------------------- ℹ This PR was created on Fri, 07 Jan 2022 06:08:00 GMT ✔ Approvals: 3 ✔ - Gerhard Stöbich (@Flarna): https://github.com/nodejs/node/pull/41424#pullrequestreview-847081629 ✔ - Antoine du Hamel (@aduh95) (TSC): https://github.com/nodejs/node/pull/41424#pullrequestreview-847144468 ✔ - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/41424#pullrequestreview-854777313 ✔ Last GitHub CI successful ℹ Last Full PR CI on 2022-01-18T17:57:04Z: https://ci.nodejs.org/job/node-test-pull-request/42003/ - Querying data for job/node-test-pull-request/42003/ ✔ Last Jenkins CI successful -------------------------------------------------------------------------------- ✔ No git cherry-pick in progress ✔ No git am in progress ✔ No git rebase in progress -------------------------------------------------------------------------------- - Bringing origin/master up to date... From https://github.com/nodejs/node * branch master -> FETCH_HEAD ✔ origin/master is now up-to-date - Downloading patch for 41424 From https://github.com/nodejs/node * branch refs/pull/41424/merge -> FETCH_HEAD ✔ Fetched commits as 81e88f27b719..6ecf9413bdaa -------------------------------------------------------------------------------- [master c8803e9c75] process: ignore asyncId 0 in exception handler Author: Anatoli Papirovski Date: Thu Jan 6 22:04:30 2022 -0800 3 files changed, 24 insertions(+), 5 deletions(-) create mode 100644 test/async-hooks/test-unhandled-exception-valid-ids.js ✔ Patches applied -------------------------------------------------------------------------------- ⚠ Found Fixes: https://github.com/nodejs/node/issues/22982, skipping.. --------------------------------- New Message ---------------------------------- process: ignore asyncId 0 in exception handlerhttps://github.com/nodejs/node/actions/runs/1714616087 |
Flarna
pushed a commit
that referenced
this pull request
Jan 18, 2022
Today, the global uncaught exception handler is the only place where asyncId 0 is not ignored and we still proceed to call emitAfter. This would've already failed one of our correctness tests in async_hooks if not for some other code meant to handle a different edge case. Fixes: #22982 PR-URL: #41424 Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]>
Landed in 5178332 |
13 tasks
17 tasks
BethGriggs
pushed a commit
that referenced
this pull request
Jan 25, 2022
Today, the global uncaught exception handler is the only place where asyncId 0 is not ignored and we still proceed to call emitAfter. This would've already failed one of our correctness tests in async_hooks if not for some other code meant to handle a different edge case. Fixes: #22982 PR-URL: #41424 Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]>
Linkgoron
pushed a commit
to Linkgoron/node
that referenced
this pull request
Jan 31, 2022
Today, the global uncaught exception handler is the only place where asyncId 0 is not ignored and we still proceed to call emitAfter. This would've already failed one of our correctness tests in async_hooks if not for some other code meant to handle a different edge case. Fixes: nodejs#22982 PR-URL: nodejs#41424 Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]>
danielleadams
pushed a commit
that referenced
this pull request
Feb 26, 2022
Today, the global uncaught exception handler is the only place where asyncId 0 is not ignored and we still proceed to call emitAfter. This would've already failed one of our correctness tests in async_hooks if not for some other code meant to handle a different edge case. Fixes: #22982 PR-URL: #41424 Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]>
danielleadams
pushed a commit
that referenced
this pull request
Mar 14, 2022
Today, the global uncaught exception handler is the only place where asyncId 0 is not ignored and we still proceed to call emitAfter. This would've already failed one of our correctness tests in async_hooks if not for some other code meant to handle a different edge case. Fixes: #22982 PR-URL: #41424 Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]>
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
commit-queue-failed
An error occurred while landing this pull request using GitHub Actions.
needs-ci
PRs that need a full CI run.
process
Issues and PRs related to the process subsystem.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today, the global uncaught exception handler is the only place where asyncId 0 is not ignored and we still proceed to call emitAfter. This would've already failed one of our correctness tests in async_hooks if not for some other code meant to handle a different edge case.
Fixes: #22982
Tests failing before the fix: