Import external proto file Visual Studio Code error

[kroksys]

How can I remove this error?
One way would be include .vscode/settings.json > "protoc": "options": --proto_path but I cant find where buf store them localy.

[doriable]

Hi @kroksys, thanks for filing this issue! Just as a heads-up, I transferred the issue to our vscode-buf repository, since this is specific to the plugin.

In terms of the issue you're seeing, the vscode-buf plugin uses our buf CLI, specifically buf lint, and since buf has its own compiler, it does not take a direct dependency on protoc, so it does not have the same settings or flags. In terms of your issue, I have a couple of questions regarding your setup:

• Do you currently have your import, in this case, google/api/annotations.proto, vendored or is this a part of a buf module? It may be helpful to provide your file and directory structure for your Protobuf files to help provide a bit more information here.
• If this is a part of a buf module, have you configured the dependency as part of your deps (https://docs.buf.build/configuration/v1/buf-yaml#deps) and have you updated your dependencies/populated your buf.lock using buf mod update (https://docs.buf.build/tour/add-a-dependency#depend-on-googleapis)?

[willsoto]

I am having this issue as well with google/type/interval.proto. Here is my buf.yaml

version: v1
breaking:
  use:
    - FILE
lint:
  use:
    - MINIMAL
  except:
    - ENUM_VALUE_PREFIX
  # Recommended best practice is to use the buf.yaml to configure files/rules that should be ignored.
  # https://buf.build/docs/lint/overview/#allow_comment_ignores
  allow_comment_ignores: false
  rpc_allow_same_request_response: true
  rpc_allow_google_protobuf_empty_requests: true
  rpc_allow_google_protobuf_empty_responses: true
deps:
  - buf.build/googleapis/googleapis:01f6828d2b8868fc9d314f9ac86677d3253fa33b

Weirdly, buf build and buf lint seem to be okay with it?

[tonywu6]

@willsoto I was getting the exact same was not found or had errors error and in my case it was from the vscode-proto3 extension, not from buf. Removing that extension gets rid of the errors.

[chrispine]

Sounds like this has been resolved, so I'm going to close this issue. Feel free to re-open if I'm wrong!