This has apparently been the case for a long time, we just didn't have the test configuration showing it. In our PipeStream conformance tests, we construct various pairings of stream types and execute all the conformance tests on them. When adding a configuration for both client and server being duplex and created with PipeOptions.None, multiple tests hang. This may very well be an issue with the test itself or something inherent to how Windows implements non-overlapped I/O named pipes (e.g. maybe there's a lock that reading/writing on the same pipe requires), but it'd be good to investigate.
This has apparently been the case for a long time, we just didn't have the test configuration showing it. In our PipeStream conformance tests, we construct various pairings of stream types and execute all the conformance tests on them. When adding a configuration for both client and server being duplex and created with PipeOptions.None, multiple tests hang. This may very well be an issue with the test itself or something inherent to how Windows implements non-overlapped I/O named pipes (e.g. maybe there's a lock that reading/writing on the same pipe requires), but it'd be good to investigate.