From 39d7a4eaeb6d2a09feedfbc69f9b29a172938eae Mon Sep 17 00:00:00 2001 From: Doug Fawley Date: Fri, 6 Oct 2023 11:04:15 -0700 Subject: [PATCH] [status-doc] clarify status code behavior outside the defined range of codes (#34588) This update should properly describe behavior differences between Java/Node and C++/Go. cc @ctiller @markdroth @ejona86 @yashykt @murgatroid99 --- doc/statuscodes.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/statuscodes.md b/doc/statuscodes.md index af2774d6ffe..e45f825176e 100644 --- a/doc/statuscodes.md +++ b/doc/statuscodes.md @@ -24,8 +24,10 @@ statuses are defined as such: | UNAUTHENTICATED | 16 | The request does not have valid authentication credentials for the operation. | All RPCs started at a client return a `status` object composed of an integer -`code` and a string `message`. The server-side can choose the status it -returns for a given RPC. +`code` and a string `message`. The server-side can choose the status it returns +for a given RPC. Applications should only use values defined above. gRPC libraries +that encounter values outside this range must either propagate them directly or +convert them to UNKNOWN. The gRPC client and server-side implementations may also generate and return `status` on their own when errors happen. Only a subset of