Bug - Cannot find .proto file

[antspy]

Hi,

I have the following buf.yaml file:

version: v2
modules:
  - path: .
    includes:
       - src 
lint:
  use:
    - STANDARD

with this config, the Buf extension is really slow (I assume this is related to bufbuild/buf#3847, since the extension uses the cli).

However, after enough time (5 min+), eventually an error is surfaced in the VSCode output logs:
Failure: Module "path: ".", includes: "src"" had no .proto files

which is true, in the sense that there is no .proto file directly underneath src. However, I have several proto files in subdirectories (e.g. src/foo/bar.proto).

I am using the latest version of the Buf extension (0.7.2)

[doriable]

Would it be possible to provide extension host logs related to this -- as you noted, the VSCode extension uses the CLI, so it should not deviate behaviour-wise from the CLI (e.g. finding proto sources in nested directories, etc.). The extension host logs should be accessible through the Command Palette (cmd/ctrl+shift+p) -> Developer: Export Logs.

[antspy]

I have exported Developer: Export Logs and I have selected all possible outputs.

The only logs I can find relative to buf (using Ctrl-F to check for all instances of buf in the output logs) are (apart from the extension being installed) this:

2025-05-21 18:54:07.523 [info] [Extension Host (Remote)] ExtensionService#_doActivateExtension bufbuild.vscode-buf, startup: true, activationEvent: 'workspaceContains:**/*.proto,**/buf.yaml,**/buf.lock,
**/buf.mod,**/buf.work,**/buf.gen,**/buf.gen.yaml,**/buf.work.yaml'

---

Note that I am running VSCode connected to a remote server, and using devcontainers. Not sure if this is relevant.

Also note that if I modify the buf.yaml file to instead be

version: v2
modules:
  - path: src
lint:
  use:
    - STANDARD

Then the extension works correctly and does not complain

[doriable]

Thank you for getting the extension host logs, I just wanted to make sure the extension is activating as expected, etc. I suspect the local VSCode failure is related to the performance issue you opened (bufbuild/buf#3847) and no .proto files is a result of a timeout and no target files were properly collected.

I'm going to keep this issue open, just in case there is something more here that is VSCode specific. As an FYI, we are also moving in the direction of integrating our LSP into VSCode and making a dev release of the VSCode extension for it. Once the dev release of the extension is available, I will ping this issue also to see if this behaviour changes.

[doriable]

The new version of the extension is now available in pre-release, let me know if this issue persists, thank you!