Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DAPR 1.12 cross-service REST call cuts response body #7145

Closed
oleksandr-bilyk opened this issue Nov 3, 2023 · 3 comments · Fixed by #7270
Closed

DAPR 1.12 cross-service REST call cuts response body #7145

oleksandr-bilyk opened this issue Nov 3, 2023 · 3 comments · Fixed by #7270
Assignees
Labels
kind/bug Something isn't working

Comments

@oleksandr-bilyk
Copy link

oleksandr-bilyk commented Nov 3, 2023

In what area(s)?

/area runtime

What version of Dapr?

1.12 has bug. Previous version s 1.11.2 and 1.11.5 are stable

Expected Behavior

We may reproduce the on docker compose when first service calls second service rest API through dapper.
Producer service uses ASP.NET minimal REST API (F# language) to provider json response from object serialization

image

Consumer service is DAPR actor that calls producer to download JSON.
image

Actual Behavior

See attached file with interrupted JSON stream in the end where error starts ".....Valid JSON stream and then unexpectedly: "{"errorCode":"ERR_DIRECT_INVOKE","message":"failed to invoke, id: expressport-adoconnector, err: error receiving message: rpc error: code = Canceled desc = context canceled"}"

Steps to Reproduce the Problem

On 16 core machine with 64 GB ram from actor call DAPR another service by REST and will see that sometimes response is cut with error in the end.

@oleksandr-bilyk oleksandr-bilyk added the kind/bug Something isn't working label Nov 3, 2023
@ItalyPaleAle
Copy link
Contributor

Can you please attach the logs from daprd when this error shows up?

@ItalyPaleAle
Copy link
Contributor

@philliphoff i believe you were investigating this with another user and found that it was something related to the .NET SDK?

@philliphoff
Copy link
Contributor

i believe you were investigating this with another user and found that it was something related to the .NET SDK?

Yes, and was able to determine the behavior exists without use of any SDK and, for example, with a JS application (see #7173). I expect #7270 will resolve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
3 participants