This exhibit a deadlock we see sometimes when using docker cli connected to a daemon through a named pipe with some data in the input stream (ie: `echo "hello" | docker run ... `) The problem seems to be that the EOF 0-length message is collapsed with the previous message, if the buffer associated with the named pipe is not previously flushed Signed-off-by: Simon Ferquel <simon.ferquel@docker.com>
go-winio
This repository contains utilities for efficiently performing Win32 IO operations in Go. Currently, this is focused on accessing named pipes and other file handles, and for using named pipes as a net transport.
This code relies on IO completion ports to avoid blocking IO on system threads, allowing Go to reuse the thread to schedule another goroutine. This limits support to Windows Vista and newer operating systems. This is similar to the implementation of network sockets in Go's net package.
Please see the LICENSE file for licensing information.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Thanks to natefinch for the inspiration for this library. See https://github.com/natefinch/npipe for another named pipe implementation.