[go-nuts] Re: catching an internal/poll error?

2023-02-19 Thread jake...@gmail.com
You might want to dig a bit more. The error that generated that string would not be an ErrFileClosing. It appears that it originated with an ErrFileClosing, but by the time it gets to you it has been wrapped more than once as it percolated up the layers of code. On Sunday, February 19, 2023 at

Re: [go-nuts] no IPv6 for golang proxy ?

2023-02-19 Thread 'Sebastien Binet' via golang-nuts
Hi Björn, On Sun Feb 12, 2023 at 10:38 CET, Björn Graf wrote: > Hej, > > Seems to be fine here: > > $ host proxy.golang.org > proxy.golang.org has address 142.251.209.145 > proxy.golang.org has IPv6 address 2a00:1450:4005:802::2011 > > And that pretty much sums up all my knowledge of DNS :) it wa

[go-nuts] catching an internal/poll error?

2023-02-19 Thread Mike Nolta
Hi, My code recently died with this error string: "write |1: copy_file_range: use of closed file". I'd like to catch it, since i'm already catching file closed errors (fs.ErrClosed). But the error appears to be ErrFileClosing from the internal/poll package [1], and i'm not allowed to import i