CallCredentials should respect the Deadline
- Vorherrschende Sprache
- Java
- Sterne
- 12.1k
- Forks
- 4k
- Ø Merge
- 2 T. 17 Std.
- Gemergte PRs (30 T.)
- 37
Beschreibung
Please answer these questions before submitting your issue.
### What version of gRPC are you using?
1.15.1
### What did you expect to see?
An RPC should never outlast a deadline set in either `CallOptions` or `grpc.
### What I actually saw?
`CallCredentials` does not respect deadlines, so a `ClientCall` cannot guarantee that the RPC will finish within a set deadline (for example if an OAuth token needs to be refreshed). Furthermore, the current `CallCredential` api makes it impossible for `CallCredentials` to access the deadline set in `CallOptions`.
Beitragsleitfaden
Rechercherichtung
Start by reading the CallCredentials, CallOptions, and ClientCall APIs to trace how deadlines and credential refreshes are handled. Determine how credentials can observe the configured deadline, then verify that an RPC cannot outlast it, including when an OAuth token is refreshed.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- grpc, java
- Bereich
- backend-api-design, networking
- Issue-Typ
- Bug
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100