Repository navigation
command 'python.setInterpreter' not found when using code-server > 3.4.1 #12465
Description
Hi,
I think my code-server updates the python version (2020.6.88468) automatically, and yesterday I cannot add the python interpreter, the command windows outputs:
Command 'Python: Select Interpreter' resulted in an error (command 'python.setInterpreter' not found)
I rolled back the python version, but it does not help. For example, python2020.5.80290 can add the interpreter, but it raises another problem of the debugger
Error: The number of constructor arguments in the derived class s must be >= than the number of constructor arguments of its base class.
at /root/.local/share/code-server/extensions/ms-python.python-2020.5.80290/out/client/debugger/debugAdapter/main.js:16:49625
The following information is the coder-server version and vs code version:
code-server: v3.4.1
VS Code: v1.45.1
Activity
frozen-icecube commentedon Jun 20, 2020
The title of the jira should be constructor args mismatch causing debug adapter to fail and not being able to load debugger for python.
I have now tried code-server version 3.2.0, 3.3.1 and 3.4.1 with various combinations of ms-python versions.
ms-python 2020.6.88468 does not even load. So i tried with all the way back down to 2020.3.69010. The older versions load but they are getting the mismatched constructor args issue.
Does anyone know what changed in ms-python / language server as code-server 3.3.1 was working fine along with older 2020.5.x version of ms-python?
Is this potentially due to debugpy related switch or an inversifyjs issue ?
I even tried with using the latest node-v14.4.0 but that also does not help...
Actual error :
Error: The number of constructor arguments in the derived class s must be >= than the number of constructor arguments of its base class.
Error Log File : debugger.vscode_8d2dc057-6410-479a-8896-afb0ba5c2d69.log
Thanks for any suggestions...
Also raised a jira on code-server side : coder/code-server#1821
karrtikr commentedon Jun 22, 2020
The rollback issue was because of a bug which opted users out of experiments. It should be fixed now with da85a76
Reload to activate the extension again, which will download the fresh experiments. Then reload again and the extension will be activated using the new experiments.
yijingru commentedon Jun 22, 2020
Thank you Kartik Raj (@karrtikr), the python extension 5.86806 now is good. But the newest version 6.89148 still has the problem of
Error: The number of constructor arguments in the derived class s must be >= than the number of constructor arguments of its base class, and the previous version 6.89468 cannot load the python interpreter. But anyway, I can use 5.86806 instead. Thanks a lot!!frozen-icecube commentedon Jun 22, 2020
I found a solution. You have to move to code-server 3.4.1 and then downgrade ms-python to 2020.5.x and all will be good.
yijingru commentedon Jun 22, 2020
@gauravk88 thanks.
karrtikr commentedon Jun 22, 2020
Reopened because we would like to get to the bottom of the issue
31 remaining items
karrtikr commentedon Mar 18, 2022
The following comment dated
Jun 18, 2021coder/code-server#1837 (comment) states this is no longer an issue with latest versions of Jupyter and Python extension, the latest comment on this issue was onMar 9, 2021. Can anyone confirm if this is still an issue?japita-se commentedon Mar 26, 2022
I confirm. This is the only solution. 2022 version does not work.
karrtikr commentedon Apr 11, 2022
Unfortunately I'm unable to reproduce the issue using the instructions in Docker here: https://coder.com/docs/code-server/latest/install#docker.
Japita Systems Engineering (@japita-se) Can you describe how you installed & launched the code-server? Please also paste the logs and errors you see. Make sure you're using the latest version of VSCode and
code-server. (Runcode-server --versionto find out the version)karrtikr commentedon Apr 18, 2022
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.