Skip to content
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

Allow for message pipes in message readmode for Windows named pipes to work. #78

Merged
merged 2 commits into from
Jun 25, 2018

Conversation

mnltejaswini
Copy link
Contributor

Reference: moby/moby#36562 (comment)

The named pipe in Windows is of message type and the handle to the pipe is in message read mode. Removing the check to allow for Windows named pipes to work.

@mnltejaswini
Copy link
Contributor Author

Also, we will treat ERROR_MORE_DATA as success and return the remaining number of bytes to be read.

@@ -181,9 +181,12 @@ func DialPipe(path string, timeout *time.Duration) (net.Conn, error) {
return nil, err
}

if state&cPIPE_READMODE_MESSAGE != 0 {
/**
Windows support message type pipes in message-read mode only. Removing this check to allow for windows named pipes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this message could be better put as a commit message, and the code removed?

@andrewhsu
Copy link

@jstarks ptal

@johnstep
Copy link
Member

This is what I mentioned back in March, moby/moby#36562 (comment), but I never heard back. Is this really the correct fix? Why is the VMBus proxy pipe (assuming that is how it works) a different mode?

@jstarks jstarks merged commit 3f914f3 into microsoft:master Jun 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants