Go 1.7.1 Released

Post by pcwalton » Wed, Sep 07, 2016, 10:38 PM UTC

__pid_t wrote: post #3

state_machine wrote: post #2

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 me…

> 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?

Post by quickben » Wed, Sep 07, 2016, 10:42 PM UTC

abtinf wrote: post #4

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, b…

Post by justinsaccount » Wed, Sep 07, 2016, 10:48 PM UTC

travjones wrote: post #5

__pid_t wrote: post #3

Earlier quoted context omitted.

> 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?

I think it would produce a runtime error and return a stack trace. Someone more qualified than me should chime in though...

  package main
  
  import "io"
  
  func main() {
  	var foo io.Closer
  	foo.Close()
  }
  justin@t420:/tmp$ go run nil.go 
  panic: runtime error: invalid memory address or nil pointer dereference
  [signal 0xb code=0x1 addr=0x20 pc=0x401023]
  
  goroutine 1 [running]:
  panic(0x463ea0, 0xc82000a140)
  	/usr/lib/go-1.6/src/runtime/panic.go:481 +0x3e6
  main.main()
  	/tmp/nil.go:7 +0x23
  exit status 2

Post by alrs » Wed, Sep 07, 2016, 11:18 PM UTC

quickben wrote: post #14

abtinf wrote: post #4

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, b…

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.

Post by sytse » Thu, Sep 08, 2016, 12:31 AM UTC

abtinf wrote: post #17

sytse wrote: post #11

Earlier quoted context omitted.

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.

I appreciate your effort. Just to avoid any misunderstanding, I didn't mean to imply that Gitlab intentionally submits point releases or promotes them to the HN front page. But even if that was the case, I don't think there is anything wrong per se with merely submitting to HN. Software releases can, and frequently are, on topic. And a point release that fixes a major security issue may certainly warrant the front pa…