tanjiancheng opened a new issue #2366: URL: https://github.com/apache/apisix/issues/2366
### I use the `import google/api/annotations.proto` just for test ``` curl http://127.0.0.1:9080/apisix/admin/proto/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d ' { "content" : "syntax = \"proto3\"; package helloworld; import \"google/api/annotations.proto\"; service Greeter { rpc SayHello (HelloRequest) returns (HelloReply) {} } message HelloRequest { string name = 1; } message HelloReply { string message = 1; }" }' ``` and then return the error like this: ``` 2020/10/09 07:47:23 [error] 25#25: *168534 lua entry thread aborted: runtime error: /usr/local/apisix//deps/share/lua/5.1/protoc.lua:283: module load error: google/api/annotations.proto ./google/api/annotations.proto: No such file or directory stack traceback: coroutine 0: [C]: in function 'error' /usr/local/apisix//deps/share/lua/5.1/protoc.lua:283: in function 'parsefile' /usr/local/apisix//deps/share/lua/5.1/protoc.lua:447: in function 'top_parser' /usr/local/apisix//deps/share/lua/5.1/protoc.lua:771: in function 'f' /usr/local/apisix//deps/share/lua/5.1/protoc.lua:1028: in function 'do_compile' /usr/local/apisix//deps/share/lua/5.1/protoc.lua:1032: in function 'compile' /usr/local/apisix//deps/share/lua/5.1/protoc.lua:1042: in function 'load' /usr/local/apisix/apisix/plugins/grpc-transcode/proto.lua:46: in function 'create_obj_fun' /usr/local/apisix/apisix/core/lrucache.lua:134: in function 'fetch' /usr/local/apisix/apisix/plugins/grpc-transcode.lua:117: in function 'phase_func' /usr/local/apisix/apisix/init.lua:138: in function 'run_plugin' /usr/local/apisix/apisix/init.lua:595: in function 'grpc_access_phase' ``` The actual use contains other more complex scenarios,how to support this? ### Environment * apisix version:1.5 * OS: centos7 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
