natas_hw
/
grpc
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[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
This commit is contained in:
Doug Fawley 2023-10-06 11:04:15 -07:00 committed by GitHub
parent d0a4347419
commit 39d7a4eaeb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/statuscodes.md
View File

@ -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