Skip to content

fix: uncaught exception on domain #41546

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

Closed
wants to merge 1 commit into from
Closed

Conversation

MrJithil
Copy link
Member

fix: uncaught exception on domain
Fixes: #40999

Derives from tag: v3.0.0 + 23399 commits

@nodejs-github-bot nodejs-github-bot added domain Issues and PRs related to the domain subsystem. needs-ci PRs that need a full CI run. labels Jan 15, 2022
@MrJithil MrJithil force-pushed the fix-40999 branch 3 times, most recently from bf87573 to d3720c7 Compare January 15, 2022 18:58
@addaleax
Copy link
Member

This seems like something that would silence the issue and avoid the exception, but not address the underlying problem.

fix uncaught exception on domain
Fixes: nodejs#40999
@MrJithil
Copy link
Member Author

This seems like something that would silence the issue and avoid the exception, but not address the underlying problem.

Yes, it will fix the uncaught exception by adding missing null checks.

@RaisinTen
Copy link
Member

Instead of fixing a doc-deprecated module, shouldn't we find a way to help the reporter migrate to a different solution?

@MrJithil
Copy link
Member Author

Closing the MR since no active conversations post 13 days.

@MrJithil MrJithil closed this Jan 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain Issues and PRs related to the domain subsystem. needs-ci PRs that need a full CI run.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

domain AsyncHook TypeError: Cannot read properties of undefined (again)
4 participants