Debugging a Golang Bug with Non-Blocking Reads

Re:Debugging a Golang Bug with Non-Blocking Reads by harikb on Tuesday March 12, 2024 @12:41PM (#39681611)

Go team does acknowledge [1] it as a bug, so there is some point here

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...

[ Parent | on HN ]

Re:Debugging a Golang Bug with Non-Blocking Reads by memset on Wednesday March 13, 2024 @07:53AM (#39690362)

I’m not sure you can. Both the Open() and Read() calls will block. You can select() on a pipe but not on open. I haven’t checked to see if you can select on a non blocking fd though. This is what the go wrappers do behind the scenes.

[ Parent | on HN ]