Re: [go-nuts] mac/windows tcp read-after-deadline expired bug

2024-11-18 Thread robert engels
Great work Steven! Closing Go bugs is always appreciated by the community. > On Nov 18, 2024, at 11:49 AM, Jason E. Aten wrote: > > Brilliant. Yes, that was my bug. Thank you Steven! > > On Monday, November 18, 2024 at 11:30:18 AM UTC-6 Steven Hartland wrote: > I believe the problem you have is

Re: [go-nuts] mac/windows tcp read-after-deadline expired bug

2024-11-18 Thread Jason E. Aten
Brilliant. Yes, that was my bug. Thank you Steven! On Monday, November 18, 2024 at 11:30:18 AM UTC-6 Steven Hartland wrote: I believe the problem you have is that your readFull can return a partial read if an error occurs e.g. timeout so when that happens you lose data by overwriting the partia

Re: [go-nuts] mac/windows tcp read-after-deadline expired bug

2024-11-18 Thread Steven Hartland
I believe the problem you have is that your readFull can return a partial read if an error occurs e.g. timeout so when that happens you lose data by overwriting the partial result with the next read. If you apply something like the following, which returns the bytes read and continues the read fro

[go-nuts] mac/windows tcp read-after-deadline expired bug

2024-11-17 Thread Jason E. Aten
If you have a macOS or Windows computer handy and you want to improve the TCP read-deadline handling in Go -- and you know something about how the runtime handles TCP connections and read-deadline-timeouts -- your help would be welcome in getting to the bottom of this runtime bug I recently encou