Buf server crashes everytime I start vscode after latest update.

[nickheyer]

[alexolog]

Same here, log attached.

Details

WARN	This command is in beta. It is unstable and likely to change. To suppress this warning, set BUF_BETA_SUPPRESS_WARNINGS=1
WARN	call returned	{"method": "client/registerCapability", "result": null}
Failure: context deadline exceeded
WARN	responding with error	{"method": "textDocument/didOpen", "error": "cancelled JSON-RPC"}
[Error - 9:36:53 AM] Server process exited with code 1.
[Info  - 9:36:53 AM] Connection to server got closed. Server will restart.
true
WARN	This command is in beta. It is unstable and likely to change. To suppress this warning, set BUF_BETA_SUPPRESS_WARNINGS=1
WARN	call returned	{"method": "client/registerCapability", "result": null}
WARN	call returned	{"method": "workspace/configuration", "result": ["git","refs/remotes/origin/HEAD"]}
INFO	new file version: file:///Users/oren/work/rpp-server/protocols/protobuf/server/tests/test_validation.proto, 0 -> 1
WARN	notify returned	{"method": "$/progress"}
WARN	notify returned	{"method": "$/progress"}
INFO	parsing AST for file:///Users/oren/work/rpp-server/protocols/protobuf/server/tests/test_validation.proto, 1
WARN	notify returned	{"method": "$/progress"}
INFO	parsing AST for file:///Users/oren/work/rpp-server/protocols/protobuf/shared/common/validation.proto, -1
INFO	parsing AST for file:///Users/oren/.cache/buf/v3/wellknowntypes/30.2/google/protobuf/timestamp.proto, -1
INFO	parsing AST for file:///Users/oren/.cache/buf/v3/wellknowntypes/30.2/google/protobuf/descriptor.proto, -1
WARN	notify returned	{"method": "$/progress"}
WARN	notify returned	{"method": "$/progress"}
WARN	notify returned	{"method": "$/progress"}
WARN	notify returned	{"method": "$/progress"}
WARN	notify returned	{"method": "textDocument/publishDiagnostics"}
INFO	running checks for file:///Users/oren/work/rpp-server/protocols/protobuf/server/tests/test_validation.proto, 1
WARN	notify returned	{"method": "textDocument/publishDiagnostics"}
Failure: context deadline exceeded
[Error - 9:48:32 AM] Client Buf Language Server: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 9:48:32 AM] Client Buf Language Server: connection to server is erroring.
write EPIPE
[Error - 9:48:32 AM] Sending notification workspace/didChangeConfiguration failed
Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
    at writeGeneric (node:internal/stream_base_commons:150:3)
    at Socket._writeGeneric (node:net:966:11)
    at Socket._write (node:net:978:8)
    at writeOrBuffer (node:internal/streams/writable:572:12)
    at _write (node:internal/streams/writable:501:10)
    at Socket.Writable.write (node:internal/streams/writable:510:10)
    at /Users/oren/.vscode/extensions/bufbuild.vscode-buf-0.8.1/node_modules/vscode-jsonrpc/lib/node/ril.js:88:29
    at new Promise (<anonymous>)
    at WritableStreamWrapper.write (/Users/oren/.vscode/extensions/bufbuild.vscode-buf-0.8.1/node_modules/vscode-jsonrpc/lib/node/ril.js:78:16)
    at StreamMessageWriter.doWrite (/Users/oren/.vscode/extensions/bufbuild.vscode-buf-0.8.1/node_modules/vscode-jsonrpc/lib/common/messageWriter.js:99:33)
    at /Users/oren/.vscode/extensions/bufbuild.vscode-buf-0.8.1/node_modules/vscode-jsonrpc/lib/common/messageWriter.js:90:29
    at runNextTicks (node:internal/process/task_queues:65:5)
    at processImmediate (node:internal/timers:453:9)
[Error - 9:48:32 AM] Connection to server got closed. Server will not be restarted.
[Error - 9:48:32 AM] Server process exited with code 1.
[Error - 9:48:32 AM] Stopping server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099 
[Error - 9:48:32 AM] Stopping server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099 

[ryanriccio1]

I'm having this issue as well.

[paul-sachs]

Thanks everyone for reporting, we'll definitely take a look. On first glance it looks like the LSP is timing out while looking at some protofiles but there could be other factors here. Can everyone provide the following details:

• OS and OS version
• Buf version (buf --version)
• Version of VS code
• Version of extension currently installed (I'm assuming 0.8.1 but want to verify)
• Last working version of the extension

Something that might also help is to identify if the issue is specific to a set of protofiles. See if opening the registry-proto repo causes the same issue.

[alexolog]

• OS and OS version

macOS Sequoia 15.7.3

• Buf version (buf --version)

1.52.1

• Version of VS code

1.107.1

• Version of extension currently installed (I'm assuming 0.8.1 but want to verify)

0.8.1

• Last working version of the extension

No idea

Something that might also help is to identify if the issue is specific to a set of protofiles. See if opening the registry-proto repo causes the same issue.

Will try

[alexolog]

Something that might also help is to identify if the issue is specific to a set of protofiles. See if opening the registry-proto repo causes the same issue.

I was not able to quickly reproduce it on that repo, but I cannot consistently reproduce it on mine either, sometimes it happens, sometimes it doesn't.

There is no rhyme or reason to it. When I opened the sample repo, the error popped up on a different open window, but after I restarted VSCode I could not reproduce that.

Sometimes it pops up when I build the CMake project, sometimes when I switch to the source control side-bar, sometimes when I save an unrelated file... As I said, it feels completely random.

Better logging would be helpful.