grpc-java/netty
Sergii Tkachenko e490273edd
netty: Handle write queue promise failures (#11016)
Handles Netty write frame failures caused by issues in the Netty
itself.

Normally we don't need to do anything on frame write failures because
the cause of a failed future would be an IO error that resulted in
the stream closure.  Prior to this PR we treated these issues as a
noop, except the initial headers write on the client side.

However, a case like netty/netty#13805 (a bug in generating next
stream id) resulted in an unclosed stream on our side. This PR adds
write frame future failure handlers that ensures the stream is
cancelled, and the cause is propagated via Status.

Fixes #10849
2024-04-16 16:27:51 -07:00
..
shaded bazel: Use the `artifact` macro for loading maven deps 2024-03-28 14:33:32 -07:00
src netty: Handle write queue promise failures (#11016) 2024-04-16 16:27:51 -07:00
BUILD.bazel bazel: Use the `artifact` macro for loading maven deps 2024-03-28 14:33:32 -07:00
build.gradle Use Javadoc's -linkoffline instead of -link 2024-02-23 17:22:48 -08:00