@C-ollins if there was an update to this issue, you would see it here. It doesn't look like anyone has picked it up yet. The priority now is Go 1.11, so regressions and critical issues are given extra attention to.
Have you tried if this issue happens with 1.11beta1 too? Perhaps it has been fixed since 1.10.