Re:Debugging a Golang Bug with Non-Blocking Reads
by o11c on Tuesday March 12, 2024 @12:42PM
(#39681626)
Er, whyever wouldn't it? On Linux it certainly works as expected, and it seems that it works fine on OS X when avoiding the broken Go shims.
[ Parent
| on HN ]
Re:Debugging a Golang Bug with Non-Blocking Reads
by chipaca on Tuesday March 12, 2024 @05:11PM
(#39685001)
I seem to remember non-blocking io with named pipes was unreliable, in the sense that the test suite of whatever-it-was (memory is reeealy sketchy, this was tens of years ago) would fail randomly often enough that we had to throw the easy solution away and do actual networking.
A bit like the .signature named pipe from fortune thing, where sometimes you got two signatures and sometimes none? Anybody remember that?
Re:Debugging a Golang Bug with Non-Blocking Reads
by thwarted on Wednesday March 13, 2024 @12:56AM
(#39688244)
Is this what you're referring to?
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