fix: trim unix socket path from createRandomIPCHandle#319895
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This change updates VS Code’s Node IPC socket handle generation to better respect Unix domain socket path length limits, addressing Node.js 24’s stricter EINVAL behavior when paths exceed platform limits.
Changes:
- Trim the random IPC socket suffix to fit within per-platform Unix socket path limits.
- Clarify why
createStaticIPCHandlestill validates (and can still exceed) length, since it must remain deterministic.
lszomoru
approved these changes
Jun 4, 2026
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.
No description provided.