Yes, you should not have two threads calling onNext() on the same
StreamObserver. If you do, you can get messages interleaved with each other
and most likely just produce garbage.
You need to make sure that your application acquires a lock before calling
any of the methods on StreamObserver.
### What version of gRPC and what language are you using?
python3.10.10
### What operating system (Linux, Windows,...) and version?
deepin v20.8(like ubuntu)
### What runtime / compiler are you using (e.g. python version or version
of gcc)
python3.10.10
### What did you do?
My unit test
I am implementing a gRPC Async client with C++, and I need to get the
grpc-status (https://grpc.github.io/grpc/core/md_doc_statuscodes.html) returned
by the server to error treatment, but the AsyncNext API only returns the
NextStatus with is associate to the CompletionQueue which doesn't