You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was a design problem earlier where the serve goroutine assumed
that the readFrame goroutine could return only connection-level
errors, but the readFrames goroutine (and the underlying Framer)
assumed it could return stream-level errors (type StreamError) and
have them handled as stream errors in the layers above. That's how it
should have been, and what this CL does.
Now readFrames returns both the Frame and error from ReadFrames
together as a pair, and an error isn't necessarily fatal to the
connection.
Fixesgolang/go#12733Fixesbradfitz/http2#53
Change-Id: If4406ceaa019886893d3c61e6bfce25ef74560d3
Reviewed-on: https://go-review.googlesource.com/15735
Reviewed-by: Dmitry Vyukov <[email protected]>
Originally from @dvyukov at bradfitz/http2#58, @dvyukov wrote:
The following test leaks serverConn.readFrames goroutines:
on commit b6255645465a25b25f804acb9b3a54009e80c2a4
The text was updated successfully, but these errors were encountered: