René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Windows anonymous pipes do not work with createReadStream","articleBody":"### Version\n\nTested with 22.14.0 and 20.18.1\n\n### Platform\n\n```text\nMicrosoft Windows NT 10.0.22000.0 x64\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nC# example for the anonymous pipe generator:\n\n```csharp\nusing System;\nusing System.Diagnostics;\nusing System.IO;\nusing System.IO.Pipes;\nusing System.Threading.Tasks;\n\nnamespace DotNetSide\n{\n    class Program\n    {\n        static async Task Main(string[] args)\n        {\n            using var pipeWriter = new AnonymousPipeServerStream(PipeDirection.Out, HandleInheritability.Inheritable);\n            using var pipeReader = new AnonymousPipeServerStream(PipeDirection.In, HandleInheritability.Inheritable);\n\n            Process client = new Process();\n\n            client.StartInfo.FileName = \"node\";\n            client.StartInfo.Arguments = \"yourscript.js \" + pipeWriter.GetClientHandleAsString() + \" \" + pipeReader.GetClientHandleAsString();\n            client.StartInfo.UseShellExecute = false;\n            client.Start();\n\n            pipeWriter.DisposeLocalCopyOfClientHandle();\n            pipeReader.DisposeLocalCopyOfClientHandle();\n\n            _ = StartReadingAsync(pipeReader);\n\n            using var sw = new StreamWriter(pipeWriter)\n            {\n                AutoFlush = true\n            };\n\n            string message = Console.ReadLine();\n\n            while (message != \"exit\")\n            {\n                await sw.WriteAsync(message);\n                message = Console.ReadLine();\n            }\n\n            client.Close();\n        }\n\n        private static async Task StartReadingAsync(AnonymousPipeServerStream pipeReader)\n        {\n            try\n            {\n                StreamReader sr = new StreamReader(pipeReader);\n\n                while (true)\n                {\n                    var message = await sr.ReadLineAsync();\n\n                    if (message != null)\n                    {\n                        Console.WriteLine(message);\n                    }\n                }\n            }\n            catch (Exception ex)\n            {\n                Console.WriteLine(ex);\n            }\n        }\n    }\n}\n```\n\nJS code that should be able to read and write from the pipes' file descriptors:\n\n```js\nconst fs = require('fs');\nconst reader = fs.createReadStream(null, {fd: parseInt(process.argv[2], 10)});\nconst writer = fs.createWriteStream(null, {fd: parseInt(process.argv[3], 10)});\n\nreader.on('data', data => writer.write('echo: ' + data + '\\n'));\n\nsetInterval(()=> {}, 1000 * 60 * 60);\n```\n\n[Source](https://github.com/kblok/DotNetNodeInterprocessCommunication), should work according to the documentation and other examples I've seen.\n\n### How often does it reproduce? Is there a required condition?\n\nEverytime I try to open an inherited anonymous pipe with NodeJS\n\n### What is the expected behavior? Why is that the expected behavior?\n\n``'data'`` events should be emitted when read pipes have new data, and it should be possible to send data to write pipes too.\n\n### What do you see instead?\n\nWhenever I bind a callback to a ReadStream created from a pipe's FD:\n\n```\nnode:events:496\n      throw er; // Unhandled 'error' event\n      ^\n\nError: EBADF: bad file descriptor, close\nEmitted 'error' event on ReadStream instance at:\n    at emitErrorNT (node:internal/streams/destroy:169:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:128:3)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {\n  errno: -4083,\n  code: 'EBADF',\n  syscall: 'close'\n}\n```\n\nWhenever I try to write to a WriteStream created from a pipe's FD:\n```\nnode:events:496\n      throw er; // Unhandled 'error' event\n      ^\n\nError: EBADF: bad file descriptor, close\nEmitted 'error' event on WriteStream instance at:\n    at emitErrorNT (node:internal/streams/destroy:169:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:128:3)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {\n  errno: -4083,\n  code: 'EBADF',\n  syscall: 'close'\n}\n```\n\n### Additional information\n\nThe same Anonymous pipe generator C# program given as an example works well with C++ using the Windows API, so it's not a C# problem:\n```cpp\n#include \u003ciostream>\n#include \u003cstring>\n#include \u003cwindows.h>\n#include \u003carray>\n\nint main(int argc, const char** argv)\n{\n    std::string pipeHandleString = argv[1];\n    int pipeHandleInt = std::stoi(pipeHandleString);\n\n    HANDLE pipeHandle = (void*)pipeHandleInt;\n\n    std::array\u003cchar, 256> buffer = {};\n\n    DWORD numberOfBytesRead;\n\n    BOOL result = false;\n\n    while (result = ReadFile(pipeHandle, &buffer, 256, &numberOfBytesRead, nullptr)) {\n        buffer[numberOfBytesRead] = '\\0';\n        std::cout \u003c\u003c \"echo: \" \u003c\u003c buffer.data() \u003c\u003c std::endl;\n    }\n}\n```\n\nOf course, it also works with C# clients.","author":{"url":"https://github.com/mgirolet-gl","@type":"Person","name":"mgirolet-gl"},"datePublished":"2025-03-03T12:23:25Z","url":"https://github.com/nodejs/node/issues/57288"}