Catch some known error types and wrap them with sensible rpc status errors for better triaging downstream. [phab:D2134]

Question

Created by danielmoy-google at 2018-01-22 22:36:04:

该提问来源于开源项目：kythe/kythe

Answer 1

danielmoy-google commented inline (context lost during migration) at 2018-01-22 22:38:55:

So there's a bunch of other fmt.Errorf calls in here which looked like actual errors that we probably want to keep. Given that if e.g. t.crossReferences returns a page index that we can't handle, that probably would be 13/internal error. (fmt.Errorf gets translated to 13/internal error, and it might be useful to not lose the specific logging message if we do ever trip that, for debugability).