Misleading grpc logs about ondatra HOT 2 CLOSED

@mojiiba, sorry for the delay. A few notes on this:

As far as I can see, this is a gRPC Unavailable error, not an EOF error.

A gRPC streaming RPC, like the Modify RPC, may have any number of responses that are received in response to a single request. In general, just because a single successful response is received after a request, subsequent messages received due to that request may fail.

A RIB_PROGRAMMED message was received, but an incorrectly implemented server could send an erroneous response to the same request after that point.

The Modify request in the log above is the proximate request to the receive attempt that failed, so it still seems relevant. Do you agree? There's no way to tell that the request caused the error, per se, but it did occur when on a response to the request.

Do you think the error message would be better if it said "error after request" instead of "error on request"?

from ondatra.

I made a small modification to the error message internally to help clarify this. It will be part of the next release.

from ondatra.