tree 85649de8e20c680c79d9ef5489783c6a4fed073b
parent 3d0cf1be08dd52d77204ad1be7e70fdd1e48c206
author Rubens Farias <rubensf@google.com> 1625583067 -0400
committer GitHub <noreply@github.com> 1625583067 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg5G3bCRBK7hj4Ov3rIwAAmxYIAJD8qsoVTUR3GI76w+bpt2mg
 +ABWK0FouMPxDBcjXm5JNAxLksRJB0+Q2XPeI8UKVd6+zlnTyD/9YAgsN+hSwS6l
 3adR5oAnDItRfo1FV6239pKTI/fOVZ6tdiB3aHu+uCJyxV9Gc1VDwV9rCqHd1w1r
 WnKDMDXltz/YFsrGz3dpnoCC5+v4wELoqZUqevP4CNtBKaj18aMFuMc11liqJuIj
 b9LWPG4O+6lJ53+l3QkQkyD+merwzW4Y5ZQYrkfm9P7brF5mPS3l7J1aVKp9YhE1
 JHc4eG3rfdbbYniscLjlSeWGYuWmAYpqQSVCYcb1uHhzPczjWMMH+7oZGhGmjlU=
 =I0Hu
 -----END PGP SIGNATURE-----
 

"Wrap" gRPC error codes. (#367)

While gRPC error codes aren't wrapper-friendly (see
https://github.com/grpc/grpc-go/issues/3616), we still
want to be able to get more context from errors.

Adding stack traces on their messages was the easiest way
I thought of that'd maintain backwards compatibility.