Skip to content

The inconsistencies of status code mapping from two documents #19094

@legendtang

Description

@legendtang

What version of gRPC and what language are you using?

All

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

All

What runtime / compiler are you using (e.g. python version or version of gcc)

All

What did you do?

If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
There are two documents define the mapping behavior of status codes between HTTP and gRPC.
https://github.com/grpc/grpc/blob/master/doc/statuscodes.md
https://github.com/grpc/grpc/blob/master/doc/http-grpc-status-mapping.md
But it seems there are many inconsistencies here. I found in the implementation that gRPC favors the former. What should I use?

What did you expect to see?

the harmony

And apparently, mapping here https://github.com/grpc/grpc/blob/master/src/core/lib/transport/status_conversion.cc does not follow this document https://github.com/grpc/grpc/blob/master/doc/http-grpc-status-mapping.md Any suggestions?

What did you see instead?

many inconsistent mapping

Anything else we should know about your project / environment?

Nope

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions