Prevent connecting to console for project using SSH interpreter?

I have several projects that use an SSH remote interpreter. This works well. My only issue is that when I open the project, PyCharm will try to connect to the remote console on startup. If the remoter interpreter is not available (for example, because I am on a different network), PyCharm will try to connect to the console for a minute or two without me being able to stop this. So, I have to wait until this finishes. 

Is there a way to stop the 'connecting to console' process early or prevent PyCharm from connecting automatically to a remote console?

4 comments
Comment actions Permalink

Hi, the issue should have been fixed in the latest version. Please try PyCharm 2020.3.3 if you haven't already - does the issue reproduce there?

0
Comment actions Permalink

I am running PyCharm 2020.3.2 (Professional Edition) following an update today. As yet I haven't received a notification to update to 2020.3.3. I will get back to you when I've updated.

0
Comment actions Permalink

I've tried version 2020.3.3. However, the issue persists. When opening a project and the remote interpreter can not be reached, pycharm hangs for a few minutes on this box without a way to stop it looking for the remote interpreter:

These are some details about my setup:

PyCharm 2020.3.3 (Professional Edition)
Build #PY-203.7148.72, built on January 26, 2021
Licensed to xxxxxxx
Subscription is active until March 23, 2021.
For educational use only.
Runtime version: 11.0.9.1+11-b1145.77 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.8.0-43-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 1885M
Cores: 8
Non-Bundled Plugins: com.jetbrains.intellij.datalore, R4Intellij, com.kite.intellij
Current Desktop: X-Cinnamon

0
Comment actions Permalink

Thank you for testing. Unfortunately I could not reproduce the issue (in my case, when remote host is unreachable, the connection fails immediately), but we had a similar issue reported recently: https://youtrack.jetbrains.com/issue/PY-47174

We'll keep investigating, sorry for the inconvenience. I suggest to follow the above issue since it may be related to your case as well.

0

Please sign in to leave a comment.