`GLIBC_2.32' not found ubuntu 20.4

[diramazioni]

Hi, I had the extension running fine for the last couple of month, now suddenly it doesn't work anymore.
On start vscode produce these messages:

[Error - 07:11:09] Server initialization failed.
  Message: Cannot call write after a stream was destroyed
  Code: -32099 
[Error - 07:11:09] LLM VS Code client: couldn't create connection to server.
  Message: Cannot call write after a stream was destroyed
  Code: -32099 
[Info  - 07:11:09] Connection to server got closed. Server will restart.
true
/home/es/.vscode/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/es/.vscode/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls)
/home/es/.vscode/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/es/.vscode/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls)
/home/es/.vscode/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/es/.vscode/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls)

I'm on ubuntu 20.4 and I have version 2.31 lrwxrwxrwx 1 root root 12 apr 7 2022 /lib/x86_64-linux-gnu/libc.so.6 -> libc-2.31.so*
and it is the vesion it ships with

[McPatate]

Have you tried upgrading/downgrading glibc?

AFAIK, the lsp server works with GLIBC 2.29, 2.32, 2.33 & 2.34

[diramazioni]

AFAIK It's not that easy and advisable to change the toolchain in Ubuntu, and was working fine till few days ago. Should I file a bug to lsp-server instead?

[McPatate]

There is already an issue about this: huggingface/llm-ls#25

My answer would be for now to compile llm-ls yourself.

[rastna12]

v0.0.38 of the extension does not have this issue if reverting back is an option for you. Looks like all the v0.1.x versions have this issue from what I can tell.

[mbuet2ner]

Can confirm! Downgrading to v0.0.38 does fix the issue, luckily. Would be great if this could be addressed 🙂

[bonuschild]

Can confirm! Downgrading to v0.0.38 does fix the issue, luckily. Would be great if this could be addressed 🙂

downgrade what to 0.0.38? the llm-vscode or llm-ls?

[bonuschild]

Have you tried upgrading/downgrading glibc?

AFAIK, the lsp server works with GLIBC 2.29, 2.32, 2.33 & 2.34

But the 0.4.0 version says it need to find 2.32,2.33 and 2.34, not with 2.29. My ldd --version return 2.31, which make llm-ls won't work at all...

[rastna12]

Can confirm! Downgrading to v0.0.38 does fix the issue, luckily. Would be great if this could be addressed 🙂

downgrade what to 0.0.38? the llm-vscode or llm-ls?

llm-vscode

[bonuschild]

Can confirm! Downgrading to v0.0.38 does fix the issue, luckily. Would be great if this could be addressed 🙂

downgrade what to 0.0.38? the llm-vscode or llm-ls?

llm-vscode

However there is not tag matched 0.0.38 either in Github repository or VS Code marketplace. Could you share me with the reference url or the windows_x64&linux_x64 plugin directly? Thanks!

[rastna12]

If you go to the extension browser in VS Code and right-click the llm-vscode extension you should see a Install Another Version... option with a drop-down menu to then select 0.0.38.

[bonuschild]

If you go to the extension browser in VS Code and right-click the llm-vscode extension you should see a Install Another Version... option with a drop-down menu to then select 0.0.38.

Thank you very much!

[github-actions]

This issue is stale because it has been open for 30 days with no activity.