Neil Jagdish Patel
Neil Jagdish Patel
Hi, I've been busy recently but I'll take a look at this tomorrow evening. Does anyone have a test case or a way to reproduce the error?
I've been doing some digging and i found the following links, maybe that'll help debug the issue: https://github.com/grpc/grpc/issues/9761 https://github.com/grpc/grpc/issues/6757 Can I confirm that your servers & client machines have the...
It might also be worth upgrading your `grpcc` and testing with latest (v1.0.0). If you continue to have the issue, I'd appreciate it if you provide some details (see my...
Do you have gcc and other build tools like make etc available? Can you get to the node-gyp logs? They might give some better info
Tried it locally, definitely an issue, but I think it's something to do with `protobuf.js` rather than `grpcc`: https://github.com/grpc/grpc/issues/7200 https://github.com/google/protobuf/issues/1741 Both those bugs are closed but it's still broken even...
Have you tried using the `--directory` option? We added that for situations like this, when you want to specify a working directory outside of your current one. Please re-open if...
Bah, that's my fault, the usage of `--directory` isn't very clear. You can avoid the type error by dropping the full path to your proto (as the look up to...
Still out of date
And still
Yeah, i want to support grpc errors soon, so we can detect and print them in a nicer fashion. I'll keep this bug as a tracker for that. Thanks.