You can also try using Empty message to see this bug on the server side:
google/protobuf/empty.proto
or
message Empty {}
I even tried:
message NumberMsg {
int64 value = 1; // return number
}
// on the client side:
NumberMsg req = new NumberMsg();
// but do not assign anything to req.value, the server side show the same bug.
I think we should fix this bug to handle empty message (e.g. empty string) properly.
If we send a request, with empty message: e.g.
https://github.com/huntlabs/grpc-dlang/blob/master/examples/SimpleDemo/source/client.d#L15
comment out this line
Then the server side will fail this test: https://github.com/huntlabs/grpc-dlang/blob/662427bf68d6fc374f62c8730b41f198651b98b9/source/grpc/GrpcStream.d#L141
and be trapped here forever:
https://github.com/huntlabs/grpc-dlang/blob/662427bf68d6fc374f62c8730b41f198651b98b9/source/grpc/GrpcStream.d#L148
and complains:
and never pass the request to the handler.
On the client side, will see error like this:
You can also try using Empty message to see this bug on the server side:
google/protobuf/empty.proto or
I even tried:
I think we should fix this bug to handle empty message (e.g. empty string) properly.
Thanks.