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

Noisy messages: Call failed with gRPC error status. Status code: 'Cancelled', Message: 'Call canceled by the client.'. #767

Closed
Dmdv opened this issue Feb 12, 2020 · 4 comments · Fixed by #777
Labels
question Further information is requested

Comments

@Dmdv
Copy link

Dmdv commented Feb 12, 2020

What version of gRPC and what language are you using?

C#. NET CORE 3.1, Grpc.AspNetCore 2.26.0

What operating system (Linux, Windows,...) and version?

The server is in Docker (ALPINE)
The client is in Window 10

What runtime / compiler are you using (e.g. .NET Core SDK version dotnet --info)

.NET Core SDK 3.1

I use streaming API

When I call token.Cancel during this call:

await foreach (var responsein stream.ResponseStream.ReadAllAsync(token))

I always get this error in the log:

image

I tried to reduce the verbosity with GRPC_VERBOSITY=info
It didn't help

@Dmdv Dmdv added the question Further information is requested label Feb 12, 2020
@JamesNK
Copy link
Member

JamesNK commented Feb 12, 2020

Update to the latest version - 2.27.0 - it fixes this issue.

@Dmdv
Copy link
Author

Dmdv commented Feb 12, 2020

@JamesNK Error reading message is gone, but the second one remains
image

@JamesNK
Copy link
Member

JamesNK commented Feb 12, 2020

The second error is correct. The call has failed because it was canceled. You could ignore this message when StatusCode = Cancelled

@Dmdv
Copy link
Author

Dmdv commented Feb 13, 2020

@JamesNK I cannot because it's being logged inside Grpc library, It's been set up to use serilog.
This exception is not logged in my code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants