Passing too large blob as an Activity input ends with non-descriptive gRPC error

[Spikhalskiy]

Expected Behavior

If we pass a blob as an activity input that is larger than a server limit, we should get a descriptive message from the server about the failure and a clean Activity failure.

Actual Behavior

We get a broken gRPC channel.

Related user request:

while passing blob object into activity calls (say pdf or image files) I am getting the below exception
io.grpc.internal.AbstractClientStream$TransportState.inboundDataReceived Received data on closed stream