Incorrect grpc status code on exceeding max response limit

[yzfeng2020]

There seems to be an issue with the way gRPC status codes are handled when the max response limit is exceeded.The following line:

armeria/grpc/src/main/java/com/linecorp/armeria/server/grpc/UnaryServerCall.java

Line 153 in c208353

final HttpData responseBody = toPayload(responseMessage);

could throw AmeriaStatusRuntimeException when the max response limit is set. The response future is then completed with that exception directly, bypassing the exception handler. This is different from exceptions occurring within the handler, which are transformed into StatusRuntimeException in the close method:

armeria/grpc/src/main/java/com/linecorp/armeria/internal/server/grpc/AbstractServerCall.java

Lines 216 to 221 in 74f6e3c

	public final void close(Throwable exception, boolean cancelled) {
	exception = Exceptions.peel(exception);
	final Metadata metadata = generateMetadataFromThrowable(exception);
	final Status status = Status.fromThrowable(exception);
	close(status, metadata, cancelled, exception);
	}

.

As a result, the expected gRPC status code RESOURCE_EXHAUSTED is not being set when the response message exceeds the limit. Instead, I observe that the status code returned is INTERNAL_ERROR.