{"push_id":825413157,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"271cfc1e2952a0940fb5b3df690ce2f6b81ca088","before":"442fc736aa6cf848147beee0f98af3d760ce51a4","commits":[{"sha":"271cfc1e2952a0940fb5b3df690ce2f6b81ca088","author":{"email":"ae9783c0b0efc69cd85ab025ddd17aa44cdc4aa5@golang.org","name":"Brad Fitzpatrick"},"message":"http2: fix handling of errors from the readFrames goroutine\n\nThere was a design problem earlier where the serve goroutine assumed\nthat the readFrame goroutine could return only connection-level\nerrors, but the readFrames goroutine (and the underlying Framer)\nassumed it could return stream-level errors (type StreamError) and\nhave them handled as stream errors in the layers above. That's how it\nshould have been, and what this CL does.\n\nNow readFrames returns both the Frame and error from ReadFrames\ntogether as a pair, and an error isn't necessarily fatal to the\nconnection.\n\nFixes golang/go#12733\nFixes bradfitz/http2#53\n\nChange-Id: If4406ceaa019886893d3c61e6bfce25ef74560d3\nReviewed-on: https://go-review.googlesource.com/15735\nReviewed-by: Dmitry Vyukov <dvyukov@google.com>","distinct":true,"url":"https://api.github.com/repos/golang/net/commits/271cfc1e2952a0940fb5b3df690ce2f6b81ca088"}]}