microsoft Github contribution chart
microsoft Github Stats
microsoft Most Used Languages

Activity

27 Nov 2022

Gyfastas

started

Started On 27 Nov 2022 at 05:50:28
Issue Comment

Smallst

docker-desktop trigger msrdc dialog `connection info invalid` (log attached)

Version

win 11 [ version 10.0.22621.674 ]

WSL Version

  • [X] WSL 2
  • [ ] WSL 1

Kernel Version

5.15.68.1

Distro Version

Archlinux

Other Software

Docker Desktop 4.13.1 (90346)

Repro Steps

with Upgrade win11 22h2 updates. and upgrade wsl2 to microsoft app store version. open Docker Desktop

Expected Behavior

no error dialog appears

Actual Behavior

when docker destop open, it causes 3 such error dialog. (sorry my system is in Chinese, and i don't want to change system language to reproduce so i screenshot the chinese dialog), which said

the connection info of this resource is invalid refresh the workspace, then retry. if problems sustained, reach for tech supports..

image

and this dialog is coming from msrdc.exe . that's all i know. image image

acutally this dialog doesn't affect docker-desktop, it still works normally (in windows & wsl2) . but the dialog cannot be closed ( once close one dialog, another same dialog would appear directly) after close the docker desktop. the dialog can be closed normally. so i believe it is related to docker desktop. while docker desktop doesn't show any error message(maybe i didn't find). and also this dialog doesn't contain any useful info. (i don't know what connection is nor error codes)

Diagnostic Logs

see below comment

Forked On 27 Nov 2022 at 05:50:07

Smallst

inside docker-desktop wsl, ps aux reports:

PID   USER     TIME  COMMAND
    1 root      0:00 /init
    3 root      0:00 {init} plan9 --control-socket 5 --log-level 4 --server-fd 6 --pipe-fd 8 --log-truncate
    6 root      0:00 /init
    7 root      0:00 /init
    8 root      0:00 -sh
   10 root      0:00 ps aux 

Commented On 27 Nov 2022 at 05:50:07

Hannibal046

started

Started On 27 Nov 2022 at 05:49:43

Arlbibek

started

Started On 27 Nov 2022 at 05:49:40

Julius9291

started

Started On 27 Nov 2022 at 05:49:25

Ananth243

started

Started On 27 Nov 2022 at 05:47:13
Issue Comment

Qaqeqe0

WSL2 SSH can't connect to any public SSH server

Environment

Windows build number: 

Microsoft Windows [Version 10.0.19041.450]
Your Distribution version: Release:        20.04
Whether the issue is on WSL 2 and/or WSL 1: Linux version 4.19.104-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Feb 19 06:37:35 UTC 2020 

Steps to reproduce

In the console try to connect to any public SSH service. For instance:

ssh -vvv new@sdf-eu.org
OpenSSH_8.2p1 Ubuntu-4ubuntu0.1, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolving "sdf-eu.org" port 22
debug2: ssh_connect_direct
debug1: Connecting to sdf-eu.org [178.63.35.195] port 22.
debug1: connect to address 178.63.35.195 port 22: Connection timed out
ssh: connect to host sdf-eu.org port 22: Connection timed out 

Timed out is observed

Expected behavior

Successful connection.

Actual behavior

Timeout (no connection).

Running the same command in cmd makes successfull connection:

ssh -vvv new@sdf-eu.org OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 debug3: Failed to open file:C:/Users/mresetar/.ssh/config error:2 debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2 debug2: resolving "sdf-eu.org" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to sdf-eu.org [178.63.35.195] port 22. debug1: Connection established. debug1: identity file C:\Users\mresetar/.ssh/id_rsa type 0 ....

I don't observe any other network issues in the WSL2 Bash. Curl, apt-get, git clone etc.. they all work fine. Only SSH is problematic. My computer is recent install.

I've just tried ssh from docker (WSL2) and from container it works:

miro@mresetar:~$ docker run -it --rm kroniak/ssh-client bash bash-5.0# ssh -vvv new@sdf-eu.org OpenSSH_8.1p1, OpenSSL 1.1.1d 10 Sep 2019 debug1: Reading configuration data /etc/ssh/ssh_config debug2: resolving "sdf-eu.org" port 22 debug2: ssh_connect_direct debug1: Connecting to sdf-eu.org [178.63.35.195] port 22. debug1: Connection established. debug1: identity file /root/.ssh/id_rsa type -1

It looks to me like ssh client is broken on WSL2.

Forked On 27 Nov 2022 at 05:39:18

Qaqeqe0

Hi, I just spoke with my SEP admin and I can share few details. It looks there is no magic involved there. Symantec doesn't by magic recognize WSL as Hyper-V and treat it differently. It is just a Group policy in our case that was named Hyper-V. So for people who use Hyper-V admins created a special Group policy where they allow some ports. What is important to note that ports allowed have Incoming TCP port opened. I would say that to Win10 it looks like incoming traffic when WSL2 tries to open SSH connection. So screenshots of the group policy with the special (No 1) rule: image

Details of the rule: image

Notice that there are few other ports besides 22. I wasn't only one requesting some ports to be opened :)

Hi sir, please guide it details?

Commented On 27 Nov 2022 at 05:39:18

Sakusu

started

Started On 27 Nov 2022 at 05:36:45

Cata

started

Started On 27 Nov 2022 at 05:36:32
Issue Comment

Squirrelsc

Add sub-test-case support to JUnit notifier.

This change allows the JUnit notifier to output sub-test-case results. Unfortunately, the JUnit format doesn't sub-test-cases. So, the notifier adds the sub-test-cases as peers of the test-cases.

In addition, the JUnit notifier allows a test-case to start a sub-test- case without explictly completing it. Instead, if a new sub-test-case starts or the test-case completes, then the previous sub-test-case is closed out automatically. This avoids a test-case needing to add extensive try-catch blocks to ensure the sub-test-cases are closed out.

Other supporting changes:

  1. Moved stacktrace and is_completed() from TestResultMessage to TestResultMessageBase. This allows sub-test-cases to report exception stacks.

  2. Modify create_test_result_message so that it includes the time since the test-case started in every message. This is to allow the JUnit notifier to properly report how much time each test-case and sub-test-case took.

Forked On 27 Nov 2022 at 05:36:20

Squirrelsc

Will merge later, once main branch break fixed.

Build break on main branch fixed, please fix other failures.

Commented On 27 Nov 2022 at 05:36:20

Github-actions

[libssh] works on arm
Merged On 27 Nov 2022 at 05:34:49

Github-actions

Commented On 27 Nov 2022 at 05:34:49

Autoantwort

[libssh] works on arm

Created On 27 Nov 2022 at 05:34:16

WaterResistantCoder

started

Started On 27 Nov 2022 at 05:33:43

Pairshoe

started

Started On 27 Nov 2022 at 05:32:31

Simone-Olivia

24 Lessons, 12 Weeks, Get Started as a Web Developer

Forked On 27 Nov 2022 at 05:31:49

Svercl

started

Started On 27 Nov 2022 at 05:30:35
Issue Comment

Azure-pipelines

Update: KDE.Okular version 22.08.3

Result: Installation Successful

| | Manifest | Add/Remove Programs | | ----------- | ------------------------ | ------------------------------------- | | Name | Okular | Okular | | Version | 22.08.3 | 22.08.3 | | Publisher | KDE e.V. | KDE e.V. | | ProductCode | | Okular |

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 4166

Microsoft Reviewers: Open in CodeFlow

Forked On 27 Nov 2022 at 05:29:37

Azure-pipelines

Commented On 27 Nov 2022 at 05:29:37

AIdancer

started

Started On 27 Nov 2022 at 05:29:29
Issue Comment

Wingetbot

Update: KDE.Okular version 22.08.3

Result: Installation Successful

| | Manifest | Add/Remove Programs | | ----------- | ------------------------ | ------------------------------------- | | Name | Okular | Okular | | Version | 22.08.3 | 22.08.3 | | Publisher | KDE e.V. | KDE e.V. | | ProductCode | | Okular |

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 4166

Microsoft Reviewers: Open in CodeFlow

Forked On 27 Nov 2022 at 05:29:27

Wingetbot

/AzurePipelines run

Commented On 27 Nov 2022 at 05:29:27
Issue Comment

Wingetbot

Update: KDE.Okular version 22.08.3

Result: Installation Successful

| | Manifest | Add/Remove Programs | | ----------- | ------------------------ | ------------------------------------- | | Name | Okular | Okular | | Version | 22.08.3 | 22.08.3 | | Publisher | KDE e.V. | KDE e.V. | | ProductCode | | Okular |

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 4166

Forked On 27 Nov 2022 at 05:29:21

Wingetbot

Service Badge  Service Badge  

Commented On 27 Nov 2022 at 05:29:21

Vedantmgoyal2009

Update: KDE.Okular version 22.08.3

Created On 27 Nov 2022 at 05:29:18
Merge

Squirrelsc

Execute a command to check if the VM is boot up after kdump

  1. Execute a command to check if the VM boots up after kdump Doesn't use the "try_connect" function. Using "try_connect" might cause the process to stack in some probability. Using "execute" a command to check if the VM boots up.

  2. Need to wait sometime to connect the VM after kdump Regardless use "try_connect" or "execute" to check if the VM boots up, calling them after triggering kdump will all hit the timeout 3600 issue in some probability. After adding sleep, I didn't see the timeout issue again.

Forked On 27 Nov 2022 at 05:28:56

Squirrelsc

Don't put a hard coded sleep. It makes the test case slow, and unstable. Wait some signals, and check regularly.
On 27 Nov 2022 at 05:28:56

Squirrelsc

Execute a command to check if the VM is boot up after kdump

  1. Execute a command to check if the VM boots up after kdump Doesn't use the "try_connect" function. Using "try_connect" might cause the process to stack in some probability. Using "execute" a command to check if the VM boots up.

  2. Need to wait sometime to connect the VM after kdump Regardless use "try_connect" or "execute" to check if the VM boots up, calling them after triggering kdump will all hit the timeout 3600 issue in some probability. After adding sleep, I didn't see the timeout issue again.

Merged On 27 Nov 2022 at 05:28:57

Squirrelsc

Commented On 27 Nov 2022 at 05:28:57

Morihaya

started

Started On 27 Nov 2022 at 05:28:52
Issue Comment

Azure-pipelines

Update: KDE.Kdenlive version 22.08.3

Result: Installation Successful

| | Manifest | Add/Remove Programs | | ----------- | ------------------------ | ------------------------------------- | | Name | Kdenlive | kdenlive | | Version | 22.08.3 | 22.08.3 | | Publisher | KDE e.V. | KDE e.V. | | ProductCode | | kdenlive |

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 4166

Microsoft Reviewers: Open in CodeFlow

Forked On 27 Nov 2022 at 05:28:52

Azure-pipelines

Commented On 27 Nov 2022 at 05:28:52
Issue Comment

Azure-pipelines

Update: Neovim.Neovim.Nightly version 0.9.0

Pull request has been automatically created using 🛫 WinGet Releaser.

Microsoft Reviewers: Open in CodeFlow

Forked On 27 Nov 2022 at 05:28:50

Azure-pipelines

Commented On 27 Nov 2022 at 05:28:50