Occasional "Received RST_STREAM with error code 2" error

[yar-sh]

Bug Description
When running the following Python code:

ssl_credentials = grpc.ssl_channel_credentials()
token_credentials = grpc.access_token_call_credentials('<TOKEN>')
credentials = grpc.composite_channel_credentials(ssl_credentials, token_credentials)
channel = grpc.secure_channel("hft-apiv2-grpc.lykke.com:443", credentials)

public_api = publicService_pb2_grpc.PublicServiceStub(channel )
for upd in public_api.GetPriceUpdates(publicService_pb2.PriceUpdatesRequest(assetPairIds=['BTCUSD']))
	print(upd)

I get the following rare exception in the for loop (~0-4 times a day):

Exception "<class 'grpc._channel._MultiThreadedRendezvous'>" occured in main thread: "<_MultiThreadedRendezvous of RPC that terminated with:
        status = StatusCode.INTERNAL
        details = "Received RST_STREAM with error code 2"
        debug_error_string = "{"created":"@1638200789.471098478","description":"Error received from peer ipv4:52.232.64.194:443","file":"src/core/lib/surface/call.cc","file_line":1063,"grpc_message":"Received RST_STREAM with error code 2","grpc_status":13}"
>"

It is most likely not the problem with the proto contracts, but with the hft endpoint?
Additionally, I have logged all UTC timestamps when this happened. Here is a list for last 2-3 days:

1638029552
1638041124
1638200789
1638350172
1638360320

Browser (please complete the following information):

• OS: Linux 4.19.0-17-amd64 #⁠1 SMP Debian 4.19.194-2 (2021-06-21) x86_64 GNU/Linux
• Browser: N/A

Last upstream Slate commit (run git log --author="Robert Lord" | head -n 1):
9333405f9574f8468522a60fab95d430a7a5acdc, but was present even before this