> should be perfectly writable having just been created and checked for errors on os.Create a few lines earlier
past performance is not a predictor of future results :p are you writing to an NFS mount point? On Thursday, April 27, 2017 at 8:55:36 AM UTC-7, Chris Hopkins wrote: > > So amusingly I've just had Gob report the following error: > > panic: write gob_fetch.txt: host is down > > It referring to a file as a host is of course understandable but it's a > little troublesome because as far as I can tell the file should be > perfectly writable having just been created and checked for errors on > os.Create a few lines earlier. > I have a vague memory that there was a package someone major in the Go > project wrote to create an error stack. I guess this hasn't been ported to > the whole standard library given the above error. > > What's the current thinking on this sort of error handling? It's hard to > say "Handle errors properly" when the standard library is butchering the > original error message. Or is there a way to extract the source error > message that I am missing? [at the moment I'm just doing a panic(err)] > > Thanks > > Chris > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
