yes, thanks I updated to the latest go and no longer get the error I'm not sure I understand the output that I'm getting now, but that is a subject for more research on my par On Monday, October 16, 2023 at 5:12:41 PM UTC-4 Jason Phillips wrote:
> I believe the fixes have already been released. Go 1.21 was released in > August and there have been 5 point releases to 1.20 since your version > (1.20.5) was released. Have you tried updating your Go toolchain? > > On Monday, October 16, 2023 at 4:21:11 PM UTC-4 Pat Farrell wrote: > >> yes that is it. >> I see that there is a patch that will be in the next release. >> >> Anyone know of a workaround until then? >> >> thanks >> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/6fec2e17-d3d6-4908-b5eb-6df6ae48a7dan%40googlegroups.com.
