proto file "does not reside in any import path" about grpcurl

[jhump]

This was certainly introduced by this change.

It was changed in the hopes of behaving more like protoc, so that an invocation of proto include paths and source files that works with protoc would also work with grpcurl. But protoc behaves correctly/intuitively for this particular case and grpcurl fails. So this is definitely a bug.

[horacimacias]

thanks for the fast response.

I see the fix/change is in protoreflect but no changes apparently in grpcurl; is there a new version planned for grpc or how can I get the latest to test this?
I just tried go get/install-ing this again after deleting old files but it seems to be pulling the same grpcurl files

[jhump]

Sorry - I didn't mean to close this issue. Github did that automatically due to my comment in the protoreflect PR.

I still need to build a release of protoreflect and then update grpcurl to use that new release. (I'll then also need a new release of grpcurl.)

If you want to try it out before I get everything release, you'd have to do so w/out Go modules, so that you can just go get -u github.com/jhump/protoreflect and let the grpcurl build use that. (If you are using Go modules, the grpcurl build will always use the version pinned in its go.mod file. To make that work, you'd have to hack up its go.mod a bit...)

[iamatulsingh]

I tried grpcurl 1.8.7 and grpcurl dev build <no version set> and it still throwing this error. Any solution yet?

[jhump]

@iamatulsingh, a fix was released three years ago. If you are seeing this error message, it is likely due to misuse of the -proto and -import-path flags. Please open a new issue with more details of what you are doing, including the command-line flags you are using and the directory layout of sources you are trying to use.

[iamatulsingh]

I'll open new issue regarding this. Thank you @jhump

[tvprasad]

I encountered the same issue on Windows, and here’s a workaround:

1. Download and extract the files from this link to a local folder.
2. Add the extracted folder to your system's PATH variable: go to System Advanced Environment → System Variables → Path, and include the path to the extracted folder.

Hope it helps.