`[llvm-vs-code-extensions.vscode-clangd] provider FAILED {"a":true,"b":null}` with code-insiders, both 15 and 16 clangd has this problem on my machine

[sci-42ver]

Please describe the problem. For hints on what information is helpful, see: https://clangd.llvm.org/troubleshooting.html

with system clangd 15.0.7 and install in vscode by clangd: check for updates to upgrade to 16, the error sticks (with --log=verbose):

2023-06-05 21:10:28.554 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2023-06-05 21:10:28.554 [error] {"a":true,"b":null}

System information Clangd version :

$ clangd --version
clangd version 15.0.7
Features: linux
Platform: x86_64-pc-linux-gnu
$ ~/.config/Code\ -\ Insiders/User/globalStorage/llvm-vs-code-extensions.vscode-clangd/install/16.0.2/clangd_16.0.2/bin/clangd --version
clangd version 16.0.2 (https://github.com/llvm/llvm-project 18ddebe1a1a9bde349441631365f0472e9693520)
Features: linux+grpc
Platform: x86_64-unknown-linux-gnu

clangd extension version: v0.1.24 Operating system:

$ uname -r
6.3.5-arch1-1
$ code -v
1.78.0-insider
2902f278ad8e2d830fa6883d3d8fd7b5c2ca59e9
x64

[sci-42ver]

I made mistake by looking at 'output->extension host' instead of 'output->clangd' in vscode, and clangd seems to work well.

I still want to know what 'provider FAILED' mean in the log from 'output->extension host'

[kotborealis]

+1

I've seen this issue numerous times on different machines. Removing all clangd caches and compilation databases seems to clear out this error for a while.

[kotborealis]

I have encountered this issue once more:

2024-02-21 09:49:33.499 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2024-02-21 09:49:33.499 [error] {"a":false,"b":{"w":1,"u":{"i":-1,"end":0},"t":[{"id":279}]}}
2024-02-21 09:49:33.499 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2024-02-21 09:49:33.499 [error] {"a":true,"b":null}
2024-02-21 09:49:33.499 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2024-02-21 09:49:33.499 [error] {"a":true,"b":null}
2024-02-21 09:49:33.499 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2024-02-21 09:49:33.499 [error] {"a":false,"b":{"w":1,"u":{"i":-1,"end":0},"t":[{"id":342}]}}
2024-02-21 09:49:33.499 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2024-02-21 09:49:33.499 [error] {"a":false,"b":{"w":1,"u":{"i":-1,"end":0},"t":[{"id":392}]}}
2024-02-21 09:49:33.499 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2024-02-21 09:49:33.499 [error] {"a":true,"b":null}
2024-02-21 09:49:33.499 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2024-02-21 09:49:33.499 [error] {"a":false,"b":{"w":1,"u":{"i":-1,"end":0},"t":[{"id":338}]}}

There are no other useful logs, the only thing that helped was to cleanup clangd cache.