I wonder what is the electron_node bundle.js process doing exactly in VS Code, it's using a lot of CPU and makes my laptop very noisy even when just editing a single file.
It looks it's from the pylance, but I don't see it in the vscode on another laptop. I'm confused where it's exactly from. Any insight would be appreciated.
I'm using vscode 1.54.3
Update:
Looks it's a pylance issue, after I downgrade it from 2021.3.3 to 2021.2.4. it's not consuming much cpu anymore.
Related
I used to use VScode in conjunction with anaconda, but later I started to appreciate the light weight stuff. So, I would like to uninstall anaconda. I have tried to do so using all the methods suggested in the forum, including using the designated anaconda-clean. None of them really works. This helped a little bit to the point I could successfully install the cleaner. But as I proceed to actually remove anaconda, nothing really happened.
Please see the thread attached as below.
Conda is surprisingly still there. So I figured an alternative would be to just disassociate anaconda or conda from VScode? How would you do so? Thank you!
Trying to use conda install to get anaconda-clean but environment fails to solve and a very slow analysis of conflicts starts
I butchered the anaconda in my mac. Very unelegant. I manually deleted as much of it as possible. That way VScode is freed from anaconda. I would still appreciate an elegant other than just manually removing which is a pain in the rear.
I recently got a new computer and reinstalled visual studio code but I haven't been able to run any of my files. The error has occurred with both python and C++, so I feel as though it is the IDE that is the problem. I have looked online and there are no straight answers as I have tried following some solutions which have resulted in different errors.
The error above comes up when I run (F5) a simple line of code in c++. Does anyone have a solution?
Thanks, Jacob
[EDIT]
For my python files to work I have to manually select 'Python: current file' but for c++ files they still have the same error.
First step, uninstall python from this machine.
Second, reinstall and make sure that you check the box "add to path".
It's pretty easy to miss as it's a small box, and I missed it my first time installing python earlier in the year. Here's the box you may have missed while installing.
It could be your extensions.
I had a similar error message and simply updated all of my extensions and then my SDK. I was then able to run my code within the IDE. I was using VSCode for c++ and also updated my GCC compiler along with the extensions.
Also look into your computer's environment variables, if you have changed the %PATH variables it may be affecting your ability to run/compile programs.
using the latest vs code, on a new installation, with only 1 plugin (which i know not to be causing the problem, since i have repeated the whole thing with another plugin; same issue) on a mac also using the latest catalina os.
issue:
writing a couple of pages (2 or 3) to the terminal, either from the terminal itself or from within the plugin, the terminal becomes unbearably slow, scrolling up or down freezes it entirely.
i found some previous links talking about this issue, but they are with older versions of vs code, and the responses have always been "this is now fixed in version xxx".
question:
is there some general setting in vs code that will prevent this?
or do you just have to wait for the next "updating", the next "breaking", the next "updating", etc?
Try this, now my terminal works faster also in Big Sur:
codesign --remove-signature /Applications/Visual\ Studio\ Code.app/Contents/Frameworks/Code\ Helper\ \(Renderer\).app
Note: The suboptimal autocompletion (not necessarily of file paths only, but autocompletion in general) is a known issue, and there seems to be no generic quality solution yet. Please see the researched links below.
Path autocompletion in the IPython console in PyCharm does not work well:
c:/U<TAB>
should autocomplete to:
cd c:/Users/
on my machine; instead, the best it manages is:
cd c:/UserWarning
which is plain wrong. IPython in the Anaconda prompt, however, behaves as it should.
My strong assumption (supported by a link, below) is that this is due to PyCharm not using the standard IPython configuration files.
I'm aware of the console starting script in PyCharm:
Settings->Build, Execution, Deployment->Console->Python console
and I've successfully used it to activate a simple magic command I've written.
So here my question: is there a code configuration snippet that could be inserted there, and that could just enable file path autocompletion? Or a pointer to a general description on how IPython configuration files "work", that would enable me to figure it out myself? That is, I imagine, the most doable hack that would solve the problem for the time being.
Alternatively, any experiences with writing your own autocompletion using the following libraries:
IPython.core.completer
IPython.core.completerlib
?
Is that doable? How much work can that be?
Thanks in advance!
My SW-Setup:
I use:
PyCharm Community Edition 2017.2.1
Anaconda 2 (Python 2.7), version 4.3.22 which contains
IPython 5.1.0
on Windows 7 Professional N
Links supporting claims in the question(s) above - just two, due to lack of StackOverflow-"reputation" :(
1) Autocompletion in IPython console in PyCharm not working as it should
JetBrains (creators of PyCharm) knows about this since, at least, two years (please Google it under "PyCharm Console tab completion" or similar, I'm allowed to add just a limited number of links here), and seems to have started working on it, but never finished it.
The discussion states " this is only the initial step to getting full IPython tab completions": https://youtrack.jetbrains.com/issue/PY-9345, but the issue is closed since October 2016.
On StackOverflow there are three questions with similar wording, but not one substantial answer (no, using Ctrl+Space instead of Tab does not solve anything). Again, I can't add more links here.
_2) PyCharm not using ipython_config.py to configure IPython Console:_
https://intellij-support.jetbrains.com/hc/en-us/community/posts/206603035-Which-ipython-config-py-is-used-to-configure-IPython-for-Python-Console-
See the comment by JetBrains at the end of the page.
I am trying to use the java_kernel for jupyter (https://github.com/Bachmann1234/java9_kernel and issue 24 therein). It works fine on a Mac OSX box. But on Linux (debian), the Java shell is not starting up.
I think I tracked it down to a call like this one:
ptyprocess.PtyProcess.spawn(["/home/jupyterhub/java/jdk-9/bin/java", "-jar", "/home/jupyterhub/java/kulla/kulla.jar"])
Reading pexpect code (https://github.com/pexpect/ptyprocess/blob/master/ptyprocess/ptyprocess.py), I would expect to end up in an exec call, having the child process running python replaced by java. However, this does not happen, ps -fu shows a python child process.
I'm guessing there is some subtle difference between pty handling on linux and osx that causes the differences here?
java-9/jshell as such work from the command line.
Any help much appreciated!
Best,
Holger
There seems to be a change in the way that later versions of jdk-9 deal with terminals on Linux. I reverted to jdk-9.ea+100 and that seems to work.