Rui Liu 563288f0ad netty: Log expected STREAM_CLOSED exceptions for already closed streams at FINE level ... See this PR in netty: https://github.com/netty/netty/pull/9798 . It's possible that one peer has closed the stream, yet another frame from peers arrives after it. This is largely harmless, as explained in the PR from netty repository. If we don't do this, the log will be polluted with these harmless logs. Example that would no longer be logged: ``` Jan 25, 2021 6:23:51 PM io.grpc.netty.NettyServerHandler onStreamError WARNING: Stream Error io.netty.handler.codec.http2.Http2Exception$StreamException: Received DATA frame for an unknown stream 27 at io.netty.handler.codec.http2.Http2Exception.streamError(Http2Exception.java:147) at io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder$FrameReadListener.shouldIgnoreHeadersOrDataFrame(DefaultHttp2ConnectionDecoder.java:596) at io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder$FrameReadListener.onDataRead(DefaultHttp2ConnectionDecoder.java:239) ... ```		2021-02-02 12:21:55 -08:00
..
shaded	Bump Gradle and plugin versions	2020-12-17 15:02:27 -08:00
src	netty: Log expected STREAM_CLOSED exceptions for already closed streams at FINE level	2021-02-02 12:21:55 -08:00
BUILD.bazel	bazel: Add helper for maven_install's override_targets	2019-08-22 07:40:32 -07:00
build.gradle	api: Add ChannelCredentials	2020-10-07 13:58:37 -05:00