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.