Panel "check remote" keeps popping out and interrupting my work

[Hypnoes]

• VSCode Version: 1.39.2 (system setup)
• Local OS Version: Windows_NT x64 6.1.7601
• Remote OS Version: Ubuntu 18.04 LTS
• Remote Extension/Connection Type: SSH

Steps to Reproduce:

1. Connect a remote host using unstable network like LTE
2. Pannel "Check remote" constantly pop up, and get focus.
3. THAT! IS! ANNOYED! I have to move my mouse and let my hands leave the keyboard.
4. Some one please tell me how to fix....

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

[roblourens]

Not sure exactly what you're referring to. I assume you are seeing the "Reconnecting" dialog. Since your connection is unstable, we might lose the connection and have to set it up again.

[RobertBlackhart]

This is what the symptoms look like:

I've not figured out what the rhyme or reason this pops up is. No text ever appears in the terminal window.

Normally, I don't my terminal view open at all. This usually happens a few times per day to me. Sometimes it seems it's in rapid succession (several times in 10 minutes) and sometimes it hours in between.

[roblourens]

Can you share the log from the Remote-SSH extension after this happens?

[RobertBlackhart]

I just had it happen this morning, almost right away after I reloaded the window after reconnecting to the network, then again just as I was trying to gather your log.

This is the text from the output window titled "Remote - SSH":

[05:51:08.152] remote-ssh-nightly@2019.10.42662
[05:51:08.152] win32 x64
[05:51:08.157] SSH Resolver called for "ssh-remote+vscode_remote", attempt 1
[05:51:08.158] SSH Resolver called for host: vscode_remote
[05:51:08.158] Setting up SSH remote "vscode_remote"
[05:51:08.266] Using commit id "213bdddb72ff7a6c8eed071420de8ddac4293cb1" and quality "insider" for server
[05:51:08.269] Testing ssh with ssh -V
[05:51:08.738] ssh exited with code: 0
[05:51:08.738] Got stderr from ssh: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[05:51:08.753] Running script with connection command: ssh -T -D 60812 vscode_remote bash
[05:51:08.764] Install and start server if needed
[05:51:08.770] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[05:51:09.332] > 
[05:51:09.333] Got some output, clearing connection timeout
[05:51:10.611] > stty: standard input: Inappropriate ioctl for device
> 0660133aa2c7: running
> Acquiring lock on /u/mcdermor/.vscode-server-insiders/bin/213bdddb72ff7a6c8eed07
> 1420de8ddac4293cb1/vscode-remote-lock.213bdddb72ff7a6c8eed071420de8ddac4293cb1
> Found old VS Code install 31f577ec88dc96ad2028699fb597b19022224b46, attempting t
> o clean up
> Install still has running processes, not deleting: 31f577ec88dc96ad2028699fb597b
> 19022224b46
> Found old VS Code install b53811e67e65c6a564a80e1c412ca2b13de02907, attempting t
> o clean up
> Failed to acquire lock for install, not deleting: b53811e67e65c6a564a80e1c412ca2
> b13de02907
> Found existing installation at /u/mcdermor/.vscode-server-insiders/bin/213bdddb7
> 2ff7a6c8eed071420de8ddac4293cb1...
> Found running server...
> 
> *
> * Reminder: You may only use this software with Visual Studio family products,
> * as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
> *
> 
> 
[05:51:10.638] > Checking server status on port 39710 with wget
> 0660133aa2c7: start
> sshAuthSock====
> agentPort==39710==
> webViewServerPort====
> osReleaseId==rhel==
> arch==x86_64==
> webUiAccessToken====
> 0660133aa2c7: end
> 
[05:51:10.639] Received install output: 
sshAuthSock====
agentPort==39710==
webViewServerPort====
osReleaseId==rhel==
arch==x86_64==
webUiAccessToken====

[05:51:10.640] Remote server is listening on port 39710
[05:51:10.640] Parsed server configuration: {"agentPort":39710,"osReleaseId":"rhel","arch":"x86_64","webUiAccessToken":"","sshAuthSock":""}
[05:51:10.653] Starting forwarding server. localPort 60818 -> socksPort 60812 -> remotePort 39710
[05:51:10.655] Forwarding server listening on 60818
[05:51:10.656] Waiting for ssh tunnel to be ready
[05:51:10.663] Tunneled remote port 39710 to local port 60818
[05:51:10.663] Resolved "ssh-remote+vscode_remote" to "127.0.0.1:60818"
[05:51:10.668] ------




[05:51:10.669] [Forwarding server 60818] Got connection 0
[05:51:10.735] [Forwarding server 60818] Got connection 1
[05:51:10.737] [Forwarding server 60818] Got connection 2
[05:51:11.680] [Forwarding server 60818] Got connection 3
[05:54:10.658] > 
[05:57:10.665] > 

That was the output right after I saw the window appear the first time. As I was writing this, like I mentioned above, it appeared again. When I checked the Remote - SSH output after that, this was the only additional line:

[06:00:10.658] >

Again, while writing this, it happened two more times and again all I see are blank lines added:

[06:03:10.668] > 
[06:06:10.667] >

None of the other logs are getting updated (by looking at their timestamps), but if any of the others would be useful, let me know.

[roblourens]

@Tyriar any idea why this would happen when I set hideFromUser on this terminal?

[Tyriar]

They're on Windows 7 so my guess is it's this problem microsoft/vscode#43169

[RobertBlackhart]

I'm using Windows 10 1809 (OS Build 17763.805) currently, not 7.

[Tyriar]

Oh OK, I saw this and assumed it was talking about Windows 7:

[05:51:08.738] Got stderr from ssh: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

So it works on the initial connection and all reconnects from the same window fail? Or just some?

17763.805

This is definitely on winpty so it could be microsoft/vscode#57803. @RobertBlackhart were you on v1.40.0 when seeing this? Does updating to 1.40.1 help?

[RobertBlackhart]

I'm not sure what you mean by "all reconnects from the same window fail". I haven't experienced a lot of reconnect failures that I would currently pin on VSCode. This symptoms of this bug don't seem to be related to reconnects. It seems to happen even without them.

I just updated to 1.41.0 today so I will have to let you know how it goes.

[roblourens]

@Tyriar I mean the problem is, the terminal is never supposed to be shown to the user at all because I set that flag and never try to reveal it.

[RobertBlackhart]

As of version 1.41.0, this is still occurring for me.

[RobertBlackhart]

I don't have any good way to measure this, but I do feel like it hasn't been happening nearly as often as it was when I first started watching this thread.

[Hypnoes]

I don't have any good way to measure this, but I do feel like it hasn't been happening nearly as often as it was when I first started watching this thread.

Yes, same as I met.

[RobertBlackhart]

I haven't seen this error in any recent times. Some update must have fixed it at or around 1.41.0. This issue can be closed.

[roblourens]

Thanks for following up!

[RobertBlackhart]

Hmm, bad news. I just saw this pop up again. I'm currently running this version:

Version: 1.41.0-insider (user setup)
Commit: 87c2e0be5d7359ce110c4c9ec9f6df71be996f8a
Date: 2019-12-06T21:36:11.793Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362

[RobertBlackhart]

Something new I've noticed. It used to be that the "Check Remote" window was blank. Now when it appears, it has the text "source <path_to_my_pyenv>" in it. Could this window be related to something in the Python extension?

This text is not always present. Sometimes when the window appears it's still blank, but I've seen it more than once.

[Hypnoes]

Something new I've noticed. It used to be that the "Check Remote" window was blank. Now when it appears, it has the text "source <path_to_my_pyenv>" in it. Could this window be related to something in the Python extension?

This text is not always present. Sometimes when the window appears it's still blank, but I've seen it more than once.

Same

[roblourens]

Are you sure it's the terminal that says "check remote" and not a terminal related to the python extension?

[Hypnoes]

I'm writing a scala project and i got this problem too.

[roblourens]

Can you share your settings?

[Hypnoes]

settings.json

{
    "git.enableSmartCommit": true,
    "editor.cursorBlinking": "phase",
    "editor.fontFamily": "'Cascadia Code', 'PingFang SC Regular'",
    "editor.fontLigatures": true,
    "editor.minimap.enabled": false,
    "editor.mouseWheelZoom": true,
    "editor.rulers": [
        80,
        100,
        120
    ],
    "zenMode.centerLayout": false,
    "zenMode.hideTabs": false,
    "explorer.confirmDelete": false,
    "git.confirmSync": false,
    "git.autofetch": true,
    "workbench.iconTheme": "vscode-icons",
    "terminal.integrated.shell.windows": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",
    "workbench.startupEditor": "newUntitledFile",
    "terminal.integrated.enableBell": true,
    "remote.SSH.showLoginTerminal": true,
    "remote.SSH.enableDynamicForwarding": true,
    "remote.SSH.allowLocalServerDownload": true,
    "editor.suggestSelection": "first",
    "vsintellicode.modify.editor.suggestSelection": "automaticallyOverrodeDefaultValue",
    "python.jediEnabled": false,
    "files.exclude": {
        "**/.classpath": true,
        "**/.project": true,
        "**/.settings": true,
        "**/.factorypath": true
    },
    "files.autoGuessEncoding": false
}

[roblourens]

Does it still happen if you disable remote.SSH.showLoginTerminal?

[RobertBlackhart]

Here is my settings.json. I don't have the remote.SSH.showLoginTerminal set. I think the default is false though (because that's what the editor fills in for me when I put that key name in). I will set it to false explicitly and see what happens.

{
    "editor.rulers": [80],
    "editor.multiCursorModifier": "ctrlCmd",
    "files.eol": "\n",
    "window.zoomLevel": 0,
    "editor.renderWhitespace": "none",
    "workbench.colorCustomizations": {
        "statusBar.background": "#666666"
    },
    "search.exclude": {
        "**/node_modules": true,
        "**/bower_components": true,
        "**/bedrock": true
    },
    "workbench.iconTheme": "vscode-icons",
    "vsicons.projectDetection.disableDetect": true,
    "editor.suggestSelection": "first",
    "files.watcherExclude": {
        "**/bedrock/**": true
    },
    "files.associations": {
        "*.thpl": "perl",
        "*.ut": "cpp"
    },
    "python.insidersChannel": "off",
    "trailing-spaces.trimOnSave": true,
    "vsicons.dontShowNewVersionMessage": true,
    "extensions.ignoreRecommendations": false,
    "remote.SSH.allowLocalServerDownload": true,
    "python.testing.pytestEnabled": true,
    "python.analysis.memory.keepLibraryAst": true,
    "python.analysis.memory.keepLibraryLocalVariables": true,
    "python.linting.pylintUseMinimalCheckers": false,
    "python.analysis.openFilesOnly": false,
    "python.dataScience.sendSelectionToInteractiveWindow": false,
    "trailing-spaces.deleteModifiedLinesOnly": true,
    "git.autofetch": true
}

[carlthome]

I'm (almost) getting used to this:

[hoechenberger]

Can someone check whether setting "python.terminal.activateEnvironment": false still fixes it?

Yes this does fix it for me.

I don't have the issue with this setting. Once I set "python.terminal.activateEnvironment": true, the issue resurfaces.

[durandg12]

The problem appeared to me this morning, whereas I have been working in remote SSH for weeks now (and on the same remote computer). Maybe a new version of the Python extension has made it appear?

Anyway the above fix worked on the remote version of the extension.

My VSCode info :

Version: 1.46.1
Commit: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d
Date: 2020-06-17T21:17:14.222Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 17.7.0

My local OS is macOS 10.13.6 and my remote OS is Linux x64 4.15.0-1065-aws. I have the Python extension v2020.6.90262 installed on both.

[jamt9000]

Also happens on Mac 10.14.1, causes hundreds of open terminals.

Version: 1.46.1
Commit: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d
Date: 2020-06-17T21:17:14.222Z (1 wk ago)
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 18.2.0

[qizhangli]

still...

[MurphyPone]

I don't have the issue with this setting. Once I set "python.terminal.activateEnvironment": true, the issue resurfaces.

This works as an interim solution for me.

[Suida]

I don't have the issue with this setting. Once I set "python.terminal.activateEnvironment": true, the issue resurfaces.

This works as an interim solution for me.

The same here. It looks like that vscode terminal automatically activating python envs will spawn it.

[qizhangli]

I don't have the issue with this setting. Once I set "python.terminal.activateEnvironment": true, the issue resurfaces.

This works as an interim solution for me.

Thanks!

[glebarez]

Is there any workarounds without setting python.terminal.activateEnvironment to false?

[cyrlop]

Having the same issue here on VSCode 1.47.0

[neuronflow]

same here, newest osx on host accessing ubuntu 1804 remote and using conda as env manager.

[bonfire62]

Having the same issue here.

[roblourens]

The Python team has released a fix in the latest build of the extension. Could someone check that you are on at least 2020.7.94776 and verify that it is fixed?

[brbecker]

I am on VSCode 1.47.2 with Python 2020.7.94776 and I'm still getting a Check remote terminal, even after a full restart of VScode. I do have "python.terminal.activateEnvironment": true.

[benlindsay]

Same experience as @brbecker. I'm on the latest version, and when I have "python.terminal.activateEnvironment": true, I get the multiple "Check remote" terminals. Setting "python.terminal.activateEnvironment": false fixes it, but that's frustrating because it is really nice to have the terminal automatically activate the environment

[virtuald]

I have a similar issue on VSCode 1.47.2 with an OSX Host, Ubuntu 18.04 remote. 2020.7.96456 python extension.

Edit: actually, it just asked me to reload vscode -- that's the python extension version it just installed, not sure what the old version was anymore. We'll see if this goes away....

[karrtikr]

We can confirm it's not been fixed yet. We have identified the issue and will be releasing the fix soon. Thanks for cooperating.

[roblourens]

This should be fixed with the latest VS Code Insiders https://code.visualstudio.com/insiders and the latest version of the Python extension. Can anyone confirm?

[karrtikr]

I can confirm I no longer see the issue.

[Aetherbase]

@roblourens when would this be merged with the non-insiders version?

[roblourens]

This week - Wednesday or Thursday.