-
Notifications
You must be signed in to change notification settings - Fork 848
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
Exchanging SCM_CREDENTIALS with SCM_RIGHTS #1326
Comments
Just an update that the fix for this has been checked in the dev branch and should soon hit the release branch. Please keep the feedback coming. Thanks @therealkenc for all the help with troubleshooting. Really helpful. |
Test case passes in 15042. 💯 |
@therealkenc - Thanks for the validation. |
Note this never made it into the 15042 release notes (to the extent it matters). I mention it only because there are a number of other fixinbound tags since 15031 (Feb 8th) that might be closed too. |
Can we expect this will make it in the creators update, or will we need to be on insider builds? |
@bbhoss - everything that is currently in insider builds will be released in the Creator's update, so yes. |
@therealkenc - I have updated the release notes around this. Thanks! |
Closing #706 which appears resolved and opening this to avoid confusion. Took a bit to track this because there aren't actually any syscall fails in 14959 (∴ no
strace
included). The test case below should output something like:WSL gets the fd but not the pid. Apologies for the length of the test case. [I've always just assumed the Berkeley guys were high when they invented the socket API.]
The text was updated successfully, but these errors were encountered: