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

fix(node): reuseExisting does not need to call bind on domain #7780

Merged
merged 6 commits into from
Apr 7, 2023

Conversation

timfish
Copy link
Collaborator

@timfish timfish commented Apr 6, 2023

Shortly after merge I realised that reuseExisting should result in the callback being called with no domain creation.

reuseExisting is primarily designed to be used when you just want to ensure that your callback is called in an existing domain. If a domain exists, we can just call the callback!

@timfish timfish changed the title fix(node): Reusing async context should not result in creating a new domain. fix(node): reuseExisting should not result in creating a new domain. Apr 6, 2023
@timfish timfish changed the title fix(node): reuseExisting should not result in creating a new domain. fix(node): reuseExisting does not need to call bind on domain Apr 6, 2023
@AbhiPrasad AbhiPrasad merged commit f4e92ca into getsentry:develop Apr 7, 2023
@timfish timfish deleted the feat/reuse-async-context branch May 4, 2023 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants