-
Notifications
You must be signed in to change notification settings - Fork 1.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
test(NODE-6692): check that event emitters have error listeners #4382
Merged
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
nbbeeken
force-pushed
the
test-santize-ee
branch
3 times, most recently
from
January 28, 2025 20:31
fbad7ba
to
9ba7a8a
Compare
nbbeeken
force-pushed
the
test-santize-ee
branch
from
January 28, 2025 20:41
9ba7a8a
to
654069f
Compare
nbbeeken
force-pushed
the
test-santize-ee
branch
2 times, most recently
from
January 28, 2025 22:00
3a7f111
to
09742f5
Compare
nbbeeken
changed the title
test: check that event emitters have error listeners in the same tick of their creation
test(NODE-6692): check that event emitters have error listeners
Jan 28, 2025
nbbeeken
force-pushed
the
test-santize-ee
branch
6 times, most recently
from
January 30, 2025 18:52
ba36dea
to
e8c9032
Compare
nbbeeken
force-pushed
the
test-santize-ee
branch
from
January 31, 2025 16:54
e8c9032
to
81c6306
Compare
nbbeeken
commented
Jan 31, 2025
durran
added
the
Primary Review
In Review with primary reviewer, not yet ready for team's eyes
label
Feb 4, 2025
durran
reviewed
Feb 5, 2025
durran
approved these changes
Feb 5, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to note from our tech chat conversations, this is intentionally not providing any warning to users about needing to add the error listener to change streams.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
What is changing?
Is there new documentation needed for these changes?
What is the motivation for this change?
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript