I built a new nuntium using golang v1.6 and the issue seems to have disappeared, so perhaps a bug in Go not nuntium. We build with 1.3 in the overlay which is 2 years and 1000s of fixes old.
I built a new nuntium using golang v1.6 and the issue seems to have disappeared, so perhaps a bug in Go not nuntium. We build with 1.3 in the overlay which is 2 years and 1000s of fixes old.