James Newton-King

I enabled AOT analysis for all server-focused trimmed projects in https://github.com/dotnet/aspnetcore/pull/45604 Warnings were addressed for ASP.NET Core server-focused projects (hosting, servers, middleware, etc). AOT analysis was disabled for Blazor projects....

Hi, I took a look at this and non-nested enum values don't work in .NET 7. Unfortunately, there is no way to work around this without changing your proto file....

It might take a couple of months before it makes it onto NuGet.org in an update.

@AndrewP-GH Attached is an unofficial package from the fix PR. It's one option if you don't want to wait. [Microsoft.AspNetCore.Grpc.JsonTranscoding.7.0.2.zip](https://github.com/dotnet/aspnetcore/files/10138456/Microsoft.AspNetCore.Grpc.JsonTranscoding.7.0.2.zip)

gRPC load balancing resolves an address (e.g. `an-example-dns-host`) to a list of IPs (e.g. `80.80.80.81`, `80.80.80.82`, etc). Then gRPC calls are load balanced across those IP addresses based on configuration,...

My guess is 100 max concurrent streams limit is hit. See https://docs.microsoft.com/en-us/aspnet/core/grpc/performance?view=aspnetcore-6.0#connection-concurrency

This is a limitation of the middleware. PR to fix - https://github.com/grpc/grpc-dotnet/pull/1993 gRPC has a custom NuGet feed, so you should be able to get the updated NuGet package from...

This is a difficult problem to solve. There are many layers between the client and the server in Azure App Service. The first set of client and server errors suggests...

Damn. In one way it is good: reducing the gRPC client to its most basic behavior means the problem isn't there. It is bad because the problem is somewhere that...

> Hi @JamesNK - we've been running Web API over HTTP2 for just over a week now and now seen these same issues. So it's definitely a gRPC thing I...