Unexpected GOAWAY on small message

[l-monninger]

Summary

See hyperium/tonic#1992 (comment)

[seanmonstar]

It really would be helpful to see a description inline here, instead of following a series of links. But, one thing I notice: it's a GOAWAY from the Library, which means it is an error case that the library detected and triggered, as opposed to being received from the peer. For example, if you have a client, and the server sent back a frame that is bigger than the default max size, that could trigger it. (If that's the case, the peer is being especially bad, since the max frame size cannot be assumed, it is negotiated.)