grpc / grpc/grpc-dotnet

Do interceptor failures fall under transient fault handling?

Open
#2,659 0 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
C#
Stars
4.5k
Forks
836
Avg merge
6d 3h
Merged PRs (30d)
7

Description

Hi,

Currently seeing an issue where failure in auth interceptor (http exception calling ADFS) is propagated to caller as Error starting grpc call, StatusCode=Unavailable. That is fine, except that Retry Policy for given service is to retry Unavailable calls 3 times. Is that a misconfiguration on my part somewhere, or do interceptors do not fall under the policy, and retries inside of interceptor should be handled in the interceptor?

Do you need a sample repro?

Contributor guide

Open the contributing guide

Research direction

Start with the linked gRPC documentation and troubleshooting pages, then investigate how the service retry policy treats failures from authentication interceptors. A useful result would be a minimal reproduction or a documented determination of whether interceptor failures are retried and where such failures should be handled.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.