Step 1, create a named pipe, and open it in non-blocking mode.
...
Unless things have changed a lot in this domain in the last few years, that won't work reliably _anywhere_.
...
Unless things have changed a lot in this domain in the last few years, that won't work reliably _anywhere_.
However, that said, I wonder if OP (duckdb) could have written their solution [2] differently. Shouldn't they be able to select from a Pipe as well as Error channel simultaneously? (similar to how they are doing it inside here [3]). If not, I would have create a go-routine that does blocking read on the Pipe and then pass it on to another channel to select on.
[1] https://github.com/golang/go/issues/66239
[2] https://github.com/scratchdata/scratchdata/blob/7c1a0fcd0e20...
[3] https://github.com/scratchdata/scratchdata/blob/7c1a0fcd0e20...
A bit like the .signature named pipe from fortune thing, where sometimes you got two signatures and sometimes none? Anybody remember that?
signature file can't be a named pipe (or /proc/uptime) https://bugzilla.mozilla.org/show_bug.cgi?id=62993
can't attach signature from pipe (fifo) https://bugzilla.mozilla.org/show_bug.cgi?id=163831