core: Skip chmod for abstract unix sockets
#5596
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
because those aren't real paths on the filesystem and thus can't be `chmod`ed
|
Thanks! Should we have a test for this? I didn't even know abstract unix sockets were a thing. We should probably document it. |
mholt
approved these changes
Jun 24, 2023
|
Waiting for post-merge testing. |
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.
Because abtract unix sockets aren't real paths on the filesystem and thus can't be
chmoded.Fixes the issue reported by @lxhao61 in 22927e2#commitcomment-119530849
I believe this applies to all platforms, including Windows.
Edit: Closes #5597