James Newton-King

That's expected. Serialization is a small piece of making an HTTP request.

The current behavior is correct. `CompleteAsync` just completes the request stream. The response stream is still active until the server ends the response stream and the client reads to the...

There are docs around calling a bidirectional stream here: https://learn.microsoft.com/en-us/aspnet/core/grpc/client?view=aspnetcore-7.0#bi-directional-streaming-call Do you think it's sufficient or would you like a section added?

The bidi stream docs isn't considering a memory leak from not disposing the call. The context behind encouraging people to gracefully complete a request is compared to the alternative of...

> Fire-and-forget calls are precisely the problem here - because it sounds like that's basically not supported without a leak. The client needs to "fire, wait, and tidy-up" otherwise they'll...

This is still broken. [Aspire.Hosting.Redis.Tests (2).zip](https://github.com/user-attachments/files/17427029/Aspire.Hosting.Redis.Tests.2.zip)

I looked at your .NET client and server sample apps and they both look fine. I also tested them on my local computer (no load balancer involved), and they worked...

I reproduced your error and looked at detailed internal logs. The problem is the .NET client is sending the server pings to calculate the RTT, but the server closes the...

> but the client does not surface this information in the exception that is thrown; is that intentional, or is that one of the things that need to be fixed?...

> It sounds like this is related to https://github.com/grpc/grpc-dotnet/issues/2358 then. Yes it is. Exactly the same. > Will this issue remain open until the underlying issues have been fixed? Or...