Other than at StartCall, no. What is the purpose? There is no point in CallCompleted because the call is already over. There's nobody to send an error to. SendingHeaders was meant to be additive only; if there's any error condition at that point it could and should have been sent in StartCall.
(Also: Arrow C++ does not use exceptions.) On Thu, May 4, 2023, at 19:08, Paul Nienaber (CW) wrote: > Hi, > > Working on server middleware internals and looking at error path options. > Is there an exception subclass or something (C++) that can be thrown which > is then parlayed into a gRPC-returned error (arrow::)Status, or is there > another way to generate a client-facing gRPC failure from the server > middleware's various callback function contexts? > > Thanks! > Paul
