Fixing DNS empty crash and unsafe socket error#16
Merged
kasperisager merged 4 commits intoholepunchto:mainfrom Feb 19, 2026
Merged
Fixing DNS empty crash and unsafe socket error#16kasperisager merged 4 commits intoholepunchto:mainfrom
kasperisager merged 4 commits intoholepunchto:mainfrom
Conversation
Contributor
Author
|
Updated the PR with your comments. |
kasperisager
requested changes
Feb 19, 2026
kasperisager
approved these changes
Feb 19, 2026
Contributor
kasperisager
left a comment
There was a problem hiding this comment.
Perfect, thanks so much! I'll merge and publish when the workflows pass.
This file contains hidden or 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
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.
1: Fixing the DNS empty crash
Socket.connect(), DNS callback now handles err, non-array results, and empty address arrays safely.2: Removing unsafe throw in async server connection
Replaced
throw errwiththis.emit('error', err)after socket.destroy() to avoid process crash3: Fix native writev buffer lifetime
Ran npm test and 17/17 tests passing, 54/54 assertions passing.