After the write fails, you have to call Finish() to get the status. See example here: https://grpc.io/docs/tutorials/async/helloasync-cpp.html
On Wednesday, September 26, 2018 at 12:17:05 PM UTC-7, dataman wrote: > > > Thanks for the response! I am using the async Write. There is no status > returned in the call to Write itself. The Next call to the completion queue > has no status indication as well, except for the success/failure boolean > value. > > > On Wednesday, September 26, 2018 at 2:05:44 PM UTC-4, Muxi Yan wrote: >> >> AFAIK the error detail should be included in the returned status of the >> call. >> >> On Thursday, September 20, 2018 at 7:22:49 AM UTC-7, dataman wrote: >>> >>> >>> Hi all, >>> >>> I am working on an async gRPC client in C++. Due to server limitations >>> we need to cap the max send msg size in the client. When we try to send a >>> msg which is larger than the cap, the Write (async) fails, which is as >>> expected. >>> >>> Is there a way to know that the failure is due to the msg size and not >>> any other reason? >>> >>> Thanks! >>> >> -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/d84deffc-1848-4038-acac-6f9b6a8728fd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
