Some checks failed
codecov / upload (push) Failing after 13m59s
CodeQL / Analyze (push) Failing after 1s
Testing / vet-proto (push) Failing after 1s
Testing / tests (arm, latest) (push) Waiting to run
Testing / extras (latest) (push) Failing after 1s
Testing / static checks (latest-1) (push) Failing after 1s
Testing / tests (-race, latest) (push) Failing after 1s
Testing / tests (i386, latest) (push) Failing after 1s
Testing / tests (latest) (push) Failing after 1s
Testing / tests (latest-1) (push) Failing after 1s
Lock Threads / lock (push) Failing after 1s
govulncheck / govulncheck (.) (push) Failing after 1s
govulncheck / govulncheck (./cmd/protoc-gen-go-grpc) (push) Failing after 1s
govulncheck / govulncheck (./gcp/observability) (push) Failing after 1s
govulncheck / govulncheck (./security/advancedtls) (push) Failing after 1s
govulncheck / govulncheck (./stats/opencensus) (push) Failing after 1s
Stale bot / stale (push) Failing after 1s
26 lines
467 B
Markdown
26 lines
467 B
Markdown
# Description
|
|
|
|
This example demonstrates the use of status details in grpc errors.
|
|
|
|
# Run the sample code
|
|
|
|
Run the server:
|
|
|
|
```sh
|
|
$ go run ./server/main.go
|
|
```
|
|
Then run the client in another terminal:
|
|
|
|
```sh
|
|
$ go run ./client/main.go
|
|
```
|
|
|
|
It should succeed and print the greeting it received from the server.
|
|
Then run the client again:
|
|
|
|
```sh
|
|
$ go run ./client/main.go
|
|
```
|
|
|
|
This time, it should fail by printing error status details that it received from the server.
|