Conflicts: src/win/pipe.c commit e53ab6675ba12d97ad6d93c9913a473ba5172617 Author: Bert Belder <email@example.com> Date: Fri Mar 9 17:04:03 2012 +0100 Windows: report UV_ENOTSOCK when we opened a file instead of a pipe Makes the pipe_connect_to_file test pass on Windows. commit 8cbbfbe4c6489868470a7e410f80d4729f4091bf Author: Igor Zinkovsky <firstname.lastname@example.org> Date: Thu Mar 1 14:32:59 2012 -0800 test: make pipe_connect_to_file succeed with ECONNREFUSED commit 6bbccf1 Author: Igor Zinkovsky <email@example.com> Date: Thu Mar 1 12:11:12 2012 -0800 windows: return UV_ENOTSOCK when doing uv_pipe_connect to a file
The kernel may be older than the kernel headers that libuv is compiled against.
This patch changes how uv-win uses the UV_SHUTTING and UV_SHUT flags. UV_SHUT is now only used for tcp handles to track whether shutdown() has actually been called. UV_SHUTTING has the more generic meaning of "no longer readable". It would be good to replace it by an actual UV_READABLE flag in the future. This makes the shutdown_close_tcp and shutdown_close_pipe tests pass on windows.
If a test failed we would previously see: Output from process `test_foo`: blah Output from process `test_foo`: (nothing) This commit changes it to: Output from process `test_foo`: blah Output from process `foo_helper`: (nothing)