Go 1.7.1 Released

[state_machine]

The 14 issues tagged 1.7.1:

  net: retry DNS lookups before failure?
  io: endless loop in MultiReader in Go 1.7
  path/filepath: EvalSymlinks is broken for relative paths on Windows
  net/http/httputil: Proxy terminates HTTP/2 stream before reading response body.
  hash/crc32: wrong output for unaligned input on s390x
  cmd/compile: incorrect assignment to uint64 via pointer converted to *uint16 (new in 1.7)
  doc: deprecation message for Transport.CancelRequest is not correct Documentation
  compress/zlib: Writer appears to ignore underlying writer errors at times.
  net: NATs client can't connect to server when client built with go1.7: "dial tcp: no suitable address found"
  doc: go1.7 release notes include typo for TLSConfig.NextProtos Documentation
  reflect: ChanOf makes "han" types instead of "chan" types
  x/mobile: Binding go mobile framework on iOS 9 with golang1.7rc6 crash when call debug.FreeOSMemory()
  net/http: nil pointer dereference in closeConnIfStillIdle
  website: retina favicon Suggested

[__pid_t]

> nil pointer dereference in closeConnIfStillIdle

What happens here? Does Go suffer from boundary access issues that C has? You know, in Rust, you don't have to worry about that, but is it the same for GO?

[kid0m4n]

We were bit by the `closeConnIfStillIdle` bug as we didn't expect the stdlib to panic like that (also something you cannot recover from, as it happens in a goroutine which you didn't create.)

[abtinf]

I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem.

Yet I don't want to "flag" the post, because I assume there is some kind of penalty for the submitter, beyond mere downvoting. Maybe it makes sense to have some kind of option to indicate a story fits site guidelines, but really doesn't belong on the front page.

[sytse]

I totally agree that point releases like https://news.ycombinator.com/item?id=12362147 (ones that don't solve not a big security vulnerability) don't belong on the HN frontpage. I don't think a team member of GitLab ever submitted one and I've just shared this thread with the team and the core team to ensure that we won't do so in the future. Please let me know if there is anything else we can do to prevent noise.

[ramchip]

I like it when there's a blog post with the release, explaining a new approach to garbage collection in Go, or a new abstraction to organize processes in Elixir, etc. But this particular post appears to be just some fixes with no context so I don't see the point...

[niftich]

I share this sentiment. Per their own Release page [1], this one is considered a minor version with no major features, so I don't particularly find it notable, whereas a major version would probably stimulate more discussion about the new features.

I'm not sure where the line is between 'I don't find this notable' vs. 'I find this explicitly off-topic', the latter of which would warrant a flag.

[1] https://golang.org/doc/devel/release.html

[kid0m4n]

Does it bother you enough to post a message here?

It's not like someone submitted it to the front page of HN? People voted it for it to come up here... and that itself should be reason enough.

[tbirdz]

Just click "hide" then.

[gjvc]

>I find it to be a problem.

Why?

[smegel]

Hey, at least it wasn't a link to a merge diff on Github!

[xiaoma]

Agreed. If it had generics or something else noteworthy, it would be news. Simply having released an 1.X.X version is not.

[ythl]

https://about.gitlab.com/2015/03/04/gitlab-is-part-of-the-y-...

[quickben]

Heck, lately one can't even dislike Google's projects here. They have so many employees in the pr team here that you'll get moded down fast.

Just watch my post tank now for stating this.