-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Cannot load proto files #73
Comments
Some success after I moved over to After I disabled I think my one remaining issue is with one my proto file definitions. It is still not obvious to me the expected usage patterns of the |
Hi @craigh1015, thank you for bearing with these bugs! You're right, the What issues did you have with |
With the flag enabled I get:
If I run in the debugger I get a for i, name := range filenames {
pr := protos[name]
-----> fd := pr.fd
if p.InterpretOptionsInUnlinkedFiles {
pr.lenient = true
_ = interpretFileOptions(pr, poorFileDescriptorish{FileDescriptorProto: fd})
}
if p.IncludeSourceCodeInfo {
fd.SourceCodeInfo = pr.generateSourceCodeInfo()
}
fds[i] = fd
} It appears that the keys in protos are relative to my proto_root |
I'm also running into this segmentation fault and, not being a Go developer, don't know what to do about it. If I try to provide a descriptor instead, then I get 'no such file: ""':
|
we're running into this as well - absent these flags, how is |
I am having trouble using --proto_descriptors and --proto_roots
I have created a proto descriptor sample using
protoc --descriptor_set_out=desc.pb schema.proto
When I run
./grpc-dump -proto_descriptors "desc.pb"
the output isIn dump.go I noticed that both clauses are using protoRoots - this appears wrong
Changing the second one to split on protoDescriptors did not change the issue but the error changed to
Can you please provide an example command line showing how to reference the proto descriptors
Thanks
The text was updated successfully, but these errors were encountered: