Page 1 of 1
[SOLVED] VsCode: cli.js opens automatically at each PC setup session
Published: August 13, 2024 - 1:50 PM
by t.heroult
Hello,
since I installed VS Code to replace PyScripter on two PCs, every time a session setup is performed, VS Code asks to open the file "C:\Program Files\Microsoft VS Code\resources\app\out\cli.js".
I can't find any explanation in the logs.
Any idea what's going on?
Re: VsCode: Automatic opening of cli.js at each PC setup session
Published: September 10, 2024 - 09:52
by t.heroult
Just a quick follow-up.
Any idea what the problem is? This malfunction is quite annoying...
Re: VsCode: Automatic opening of cli.js at each PC setup session
Published: September 10, 2024 - 10:11 AM
by sfonteneau
Code: Select all
"C:\Program Files (x86)\wapt\wapt-get.exe" session-setup ALL --ldebug
Can you run this command to see when VS Code opens?
Re: VsCode: Automatic opening of cli.js at each PC setup session
Published: September 10, 2024 - 1:40 PM
by t.heroult
It said to me: "error: no such option: --ldebug"
So I tried with -ldebug
The result did not show any errors, but more importantly, it seems that the problem has disappeared.
I noticed with the task manager that the command had launched Vscode invisibly which worked a lot for 10-15 seconds (30% of the CPU).
The code executed at this time is:
Code: Select all
Run ""C:\Program Files\Microsoft VS Code\bin\code" --install-extension "C:\Program Files\Microsoft VS Code\ms-python.vscode-pylance-2024.2.1.vsix" --force"
I restarted the installation, audit, etc. commands and there were no more problems.
I placed the order again on another machine and got the same result, except this time it was very fast.
I don't know exactly why, but it fixed the bug.
If this happens again on another machine, I will make a note of it.
Thank you Simon!
Re: VsCode: Automatic opening of cli.js at each PC setup session
Published: September 10, 2024 - 2:13 PM
by t.heroult
However, it broke the autocomplete feature in VS Code...
I spent half a day trying to get it working!
EDIT:
I managed to recover a backup of the ".vscode" and "roaming/Code" folders and restore them. Phew!