Open papabytes opened 2 years ago
I can confirm this is related to Arcus and not Dapr.
Well, Dapr is having issues because of our response logging somehow. (stream not handled correctly?)
Some integration test we can set up to reproduce this, then?
Something for the web API, I'll move this.
We can, but it will not be easy as we'll need to integrate Dapr in our tests - https://docs.dapr.io/developing-applications/sdks/dotnet/dotnet-actors/dotnet-actors-usage/
We can, but it will not be easy as we'll need to integrate Dapr in our tests - https://docs.dapr.io/developing-applications/sdks/dotnet/dotnet-actors/dotnet-actors-usage/
Ok, we can try. @papabytes , could you give more info on the used middleware and the order in which they are registered? Also, is this something you want to investigate yourself?
Prioritizing .NET 8 support, @papabytes. Moving to v2.1.
Describe the bug After enabling ResponseContent Observability we started receiving error codes from Dapr actors. The only difference we made in our code was adding the following line:
To Reproduce While configuring tracking middleware, enable the following option:
We started seeing the following error stack trace:
Expected behavior Response bodies should be tracked.
Additional context