Why gRPC client follows its TCP "FIN, ACK" with "RST, ACK"?

[Marcin Dulak]

Hi,

I'm seeing differences in behavior of the Python vs Golang gRPC.
From localhost tests of the Helloworld quickstarts,

Python unary gRPC seems to always (?) make the client follow its TCP "FIN, ACK" with "RST, ACK".

In a Golang quickstart, this happens every few calls, with the majority performing

the usual FIN->FIN->ACK sequence.

Here is a repository which demonstrates this https://github.com/marcindulak/grpc-client-tcp-rst

Marcin