For release manager FYI: this is a regression introduced in Go 1.8. The fix is straight forward and safe, and I expect backports cleanly to Go 1.12, but just thought I'd make sure that complies with our backport policy.
By the backport policy, once this is fixed on a Go 1.13.x release, upgrading to that will be a valid workaround, so it does not qualify for backport to Go 1.12.x. (And anyway this is not a regression in Go 1.12.)
@zx2c4 requested issue #34474 to be considered for backport to the next 1.12 minor release.
The text was updated successfully, but these errors were encountered: