I suspect that Rob was just seeing garbage values due to compiler optimizations.
We had this same issue. Turned out to be an issue with Go’s 1.1.1 TLS libraries. After putting a TLS terminating load balancer up the issue went away.
I suspect that Rob was just seeing garbage values due to compiler optimizations.
We had this same issue. Turned out to be an issue with Go’s 1.1.1 TLS libraries. After putting a TLS terminating load balancer up the issue went away.