-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metadata is not being sent #10
Comments
Hello can you provide some source code please? There are lots of examples in the tests such as this for unary or for request stream or response stream call. |
Sorry:
simple request, no stream. |
I think that should work as evident by the tests. Please provide a reproducible example and some more details including the protocol buffer definition, server code, nodejs, and grpc library versions. |
There you go: test.proto:
server.js:
caller.js:
grpcCaller.js:
|
Hmm I am still not able to reproduce this with latest master using Node 8.9. Can you maybe try the |
I can reproduce it also with the im running with node 8.10.0 |
client side:
and on server:
|
Haha, sure it will work, you are trying to run the original grpc caller :) try to run grpcCaller.js, the caller.js was just there to demonstrate how it should be.. |
My apologies... I misread the code somehow heh. But still seems to works 😕
and on the server side:
|
Well, then idk what to say, for me it's not receiving the metadata. Any
idea?
|
I've tried all the possible variation of metadata (grpc metadata, row json), tried with callback, without callback (await), but it's seems like it's not sending any metadata.
On the official gRPC caller there is no any problem and I can see the metadata on the grpc server, so it's definitely problem of
grpc-caller
.I tried to debug it but I got blocked at some point (out of my understanding and I have no time to dig deep - sorry).
Is there any known issue about that which I missed?
The text was updated successfully, but these errors were encountered: