Ben Adams

That's quite interesting... ```csharp warn: Ben.Diagnostics.BlockingMonitor[6] Blocking method has been invoked and blocked, this can lead to threadpool starvation. at System.IO.FileStream.ReadAsyncInternal(Memory`1 destination, CancellationToken cancellationToken, Int32& synchronousResult) at System.IO.FileStream.ReadAsyncTask(Byte[] array, Int32...

I'd raise that in https://github.com/dotnet/aspnetcore the `System.Text.Json` serializer may fare better than `Newtonsoft.Json`; though you need to check your outputs/inputs when changing as it has caveats like it only serializes...

[`ServerTelemetryChannel.Flush`](https://github.com/microsoft/ApplicationInsights-dotnet/blob/de4e53d3f0f3166a5b1e6724e56706a053d221ab/src/ServerTelemetryChannel/ServerTelemetryChannel.cs#L297) does block as it calls `TelemetryBuffer.FlushAsync().GetAwaiter().GetResult()` which is an issue with ApplicationInsights as it requires 2 threads to complete as highlighted in @davidfowl's [AsyncGuidance](https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md#avoid-using-taskresult-and-taskwait) which is being moved the...

That's pretty interesting... /cc @davidfowl

They aren't incorrect :) Can you post some of the blocking traces and maybe we can get them resolved in the framework? Also are they one offs, e.g. during startup...

Might be overly sensitive; e.g. it will trigger the warning for `lock`s that block Should be able to add a sensitively flag

Which `using` are you referring to?

@dependabot rebase

@dependabot recreate

Hmm... test are not running. Let me look into that