Replies: 2 comments 1 reply
-
@ZeroRin Some times the |
Beta Was this translation helpful? Give feedback.
1 reply
-
Well, it's weird that when I login today I found that the language server worked as expected. Still no idea why it went wrong yesterday but at least it now works |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
On a remote server, whatever python interpreter I choose from bottom-right corner, Jedi language server always search conda base environment for packages. And as a result, any package installed on other server is not accessible for autocompletion.
The weird thing is that it only happens on this specific server, when I tried to reproduce it on another server (with the same conda environment shared using NFS), everything works as expected.
I compared the json file for both server's remote setting and workspace setting, and they are exactly the same (both almost empty actually). I also tried to uninstall and reinstall vscode server but the problem still exists.
One clue I found is that one of the processes related to jedi is executed by

miniconda3/bin/python
instead of the selected environmentminiconda3/envs/speechbrain/bin/python
, while on the other server both are executed by the selected environment. However, I still have no idea about what's going wrong and how to fix it.Beta Was this translation helpful? Give feedback.
All reactions