gRPC 2 UNKNOWN vs 12 UNIMPLEMENTED
Both gRPC 2 (UNKNOWN) and 12 (UNIMPLEMENTED) belong to the gRPC Status Codes category. 2 indicates that an unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code. Meanwhile, 12 means that the operation is not implemented or is not supported/enabled in this service.
Описание
An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
Когда вы это видите
The server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
Как исправить
Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN.
Описание
The operation is not implemented or is not supported/enabled in this service.
Когда вы это видите
The client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
Как исправить
Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.
Ключевые различия
gRPC 2: An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
gRPC 12: The operation is not implemented or is not supported/enabled in this service.
You encounter 2 when the server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
You encounter 12 when the client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
Когда что использовать
For 2 (UNKNOWN): Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN. For 12 (UNIMPLEMENTED): Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.