text:
After WSL is turned on, the windows11 taskbar and task manager are constantly refreshed.

Version
Microsoft Windows 21H2 OS 22000.588
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.60.1
Distro Version
Ubuntu 20.04
Other Software
Docker version 20.10.13, build a224086
docker-compose version 1.29.2, build 5becea4c
Node v16.13.2 (inside ubuntu)
Repro Steps
After starting wsl for a while
Expected Behavior
N/A
Actual Behavior
N/A
Diagnostic Logs
No response

I also encountered a similar situation.
Whenever I start WSL2 Ubuntu through the Windows Terminal for the first time after win11 restarted, the wt window flickers uncontrollably.
At this time, the input method (Microsoft Pinyin) in my taskbar shows that it is switching between Chinese and English input states constantly - automately(it seems like constantly pressing Shift). I can't input normally in wt. When I use the mouse to focus on the window of other Windows applications, that window will also flicker, and the input method is constantly switching by itself.
In this case, I can only wait or just press any keys on the keyboard and hope that it can return to normal by itself, sometimes it returns to normal, sometimes I can only use the mouse to force close wt to return to normal and when the next time I use wt When I start wsl2-Ubuntu, it will still automatically shift like crazy, and it will take a while to return to normal.
wsl2 can be used normally after returning to normal.
Here's some info from my PC:
Win11: Version 21H2 (OS build 22000.556)
Input method: Microsoft Pinyin (system built-in)
WSLs:
WSL1 (normal, no errors): Alpine v3.15
Kernel: Linux Tc 4.4.0-22000-Microsoft #1-Microsoft Fri Jun 04 16:28:00 PST 2021 x86_64 Linux
WSL2 (crazy): Ubuntu 20.04
Kernel: Linux Tc 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
I can also provide more information if needed.

I'm not able to reproduce this. Are there any interesting events in the event log?

我无法重现这一点。事件日志中是否有任何有趣的事件？

What logs should I provide? wsl or windows?

Hey there. We've noticed this problem over at https://github.com/docker/for-win/issues/12532. It seems that copying an image with an alpha channel into the clipboard will start the flickering. Copying anything else, like text, into the clipboard will stop the flickering.

We initially thought Docker Desktop was causing this issue, but it seems to be related more closely to WSL.

Hey there. We've noticed this problem over at docker/for-win#12532. It seems that copying an image with an alpha channel into the clipboard will start the flickering. Copying anything else, like text, into the clipboard will stop the flickering.

We initially thought Docker Desktop was causing this issue, but it seems to be related more closely to WSL.

I tried this operation, as described and expected.

Someone in the Docker issue pointed out that the developers over at Greenshot tracked it down to some specific image format being present on the clipboard.
https://github.com/greenshot/greenshot/issues/348

Someone in the Docker issue pointed out that the developers over at Greenshot tracked it down to some specific image format being present on the clipboard. greenshot/greenshot#348

My operation process is like this.

/logs

Still happening. I'll provide logs soon

Could someone reopen this ticket or should we create a new one?

Here are logs from when the problem is not happening at all, as a control group:
WslLogs-2022-05-31_22-53-41.zip
Here are logs containing the following sequence of events:

Started with the problem not happening
Used greenshot to capture a region of my screen, marked it up, and copied it to my clipboard (to reproduce the problem)
The problem begins happening
I let the problem run for ~10-15 seconds
I save the logs with the problem still happening.

WslLogs-2022-05-31_22-54-02.zip

I can't reopen this issue, i think we need to create a new one.

WslLogs-2022-06-06_16-06-55.zip
This is the problem logs.

Looks like wslg has fixed this.fix clipboard crash #39

@cherrol Thanks for finding this. I'll test out the new version and see if it fixes it for me too

The problem was solved after I updated windows and wsl.

Thanks for the followup @MitchTalmadge .
I was looking at the logs you shared earlier, and I could see weston crashing, which explains the symptoms you were describing.
Glad to hear updating fixed it !

This is still not fixed for me. similar issue, using photoshop or any editor, copy image with an alpha channel to clipboard.
If I shutdown WSL flickering stops. If I then restart WSL flickering returns. If i hit windows key+v and clear the clipboard. issue goes away. I have also noticed when this 'flickering' starts remote desktop connection is the uppermost utilized in task manager, and goes away as soon as it stops. very strange behaviour.

This is still not fixed for me. similar issue, using photoshop or any editor, copy image with an alpha channel to clipboard.
If I shutdown WSL flickering stops. If I then restart WSL flickering returns. If i hit windows key+v and clear the clipboard. issue goes away. I have also noticed when this 'flickering' starts remote desktop connection is the uppermost utilized in task manager, and goes away as soon as it stops. very strange behaviour.

Can you please share the output of wsl --version

I'm running into this issue since Windows 11. Never noticed it with Windows 10. Windows 11 21H2. It drastically impacts game performance; my game which renders 360 fps will drop down to double-digit FPS during flicker/refreshes.
It doesn't happen immediately after starting wsl. I notice my CPU usage increases when the refreshing occurs. I run wsl.exe --shutdown and the flickering stops.
I do use Greenshot and copy images to the clipboard as pngs.  I just tested it and it immediately triggered it. I went to Windows + X and deleted the picture, and it did resolve stop refreshing, which is better than killing wsl.

Hmmm... Still get this problem.
I'm using the windows terminal to use the wsl conveniently.
When some (any) WSL subsystem runs, it may cause the flickering with high odds.
After WSL subsystem stopped, the flickering will stop latter.
I saw that here exists a process named mstsc.exe (Microsoft terminal services client) when WSL subsystem runs. Does this program cause this  flickring issue?
Kernel version: 5.10.102.1
Win11 professional edition 10.0.22000.1042

Also still getting this, same versions as above!

I am having the same issue. WSL --update didn't help (already latest). I'm on Win 11. Snipping Tool doesn't cause the problem but GreenShot does. Any solution?

I have the same problem.
PS C:\Windows\System32> wsl --version
WSL: 1.0.3.0
Core: 5.15.79.1
WSLg: 1.0.47
MSRDC: 1.2.3575
Direct3D: 1.606.4
DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows: 10.0.22000.1335

@it-podshivalov: Can you please capture logs ?  and share them here
/logs

I'm not able to reproduce this. Are there any interesting events in the event log?

it happend to me in windows 10 after i put the computer to sleep and turn it on again when ever i move my mouse it flickers it usually resolves after i restart my computer but now im sick of restrarting every time i out

I also faced the same problem…

did you fix or is there any new ways to fix it, please reply
On Sat, Aug 5, 2023 at 2:49 PM Momean @.***> wrote:

I also faced the same problem…
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/WSL/issues/8166#issuecomment-1666451038,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBHWKHO5GJ6H7LTYQ2WXBKDXTYF3RANCNFSM5RA5G3SQ
.
You are receiving this because you commented.Message ID:
@.***>

I'm not able to reproduce this. Are there any interesting events in the event log?

it happend to me in windows 10 after i put the computer to sleep and turn it on again when ever i move my mouse it flickers it usually resolves after i restart my computer but now im sick of restrarting every time i out

Facing the EXACT same issue, really frustrating no I idea whats going wrong

WSL version: 1.2.5.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2506
I also have same problem. what should I do?
Does WSLg 1.0.51 has Same Issue?

still happening

authors: BigTear Eshchock1 Euynac MRFU510N88 MitchTalmadge OneBlue benhillis capi cherrol ckdgkwkd27 didyouexpectthat dilith2009github hero3616 it-podshivalov mattiusclay rabbidave wangziling wischi-chr


text:
Add msize configuration for windows-side 9P client (=higher WSL2 disk speed)

There is a continuous effort to improve performance of 9P connections in WSL2. If we can resolve it at least for bulk transfers - half of the problem would be gone. Key to this msize configuration on 9P client. On linux side msize is configurable in fstab, but it seems to be not configurable in windows 9P client.
Suboptimal msize might reduce transfer speed for large file transfer (currently I see 400Mb/s through 9P down from native 4.5Gb/s achievable under Linux in WSL2)
Solution
Registry config is added for 9P client on windows side. At least msize is configurable.
Describe alternatives you've considered
Increase of existing hardcoded msize to 1-32Mb.
Automatic msize? Or more documentation how 9P client works / configured.
Additional context
Impact of msize to performance: https://wiki.qemu.org/Documentation/9psetup#Performance_Considerations_.28msize.29
Here others set default values to 1-32Mb : https://github.com/lxc/lxd/issues/10219

Tried to increase default msize on Linux Kernel side from 128kB to 2Mb - did not helped (\net\9p\client.c).
I afraid it's enforced on windows size.

Is there any plan to implement this any time soon?

source: gharchive/issue

repo: microsoft/WSL

license: MIT

license_type: permissive

license_source: github-api


text:
WSL sometimes crashes when computer wakes from sleep

Version
Microsoft Windows [Version 10.0.19044.2364]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.15.79.1-microsoft-standard-WSL2
Distro Version
Arch Linux
Other Software
No response
Repro Steps

Open a terminal to the Linux instance
Close laptop lid to put the computer to sleep
Wait till the next day (or more precisely, as far as I can tell, until the computer has gone from sleep to hibernation)
Start the computer again
Find that the Linux instance has died.

Expected Behavior
I expect the Linux instance to also resume from sleep/hibernation without errors.
Actual Behavior
The Linux shell is unresponsive, and in the Windows Terminal, I see the following message:
[process exited with code 1 (0x00000001)]

I do not think this is a duplicate of #9301, because the Linux instance can easily be started again without rebooting the computer.
I have run the collect-wsl-logs.ps1 script and attached its output files as instructed (WslLogs-2023-01-30_16-39-46.zip), but its console output indicates that it wasn't entirely successful:
PS C:\Users\[username]> .\collect-wsl-logs.ps1

    Directory: C:\Users\[username]

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        30/01/2023     16:39                WslLogs-2023-01-30_16-39-46
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
Log collection is running. Please reproduce the problem and press any key to save the logs.
Saving logs...

        There are no trace profiles running.

        Error code: 0xc5583000
Logs saved in: C:\Users\[username]\WslLogs-2023-01-30_16-39-46.zip. Please attach that file to the GitHub issue.

The part starting with "Saving logs..." is of course from after the computer has woken again. And I have run that script successfully before, so I guess that the error is related to WSL crashing.
I have also checked Event Viewer and found some log entries there which seem like they could be relevant. In chronological order:

When I first put the computer in sleep mode:

Info: The driver \Driver\vpcivsp for device ROOT\VPCIVSP\0000 stopped the power transition.
Info: The system is entering sleep. Sleep Reason: Button or Lid

When it later resumes to switch to hibernation:

Info: The driver \Driver\vpcivsp for device ROOT\VPCIVSP\0000 stopped the power transition.
Error: The ms-resource:AppName service terminated unexpectedly. It has done this 2 time(s).
Info: The system is entering sleep. Sleep Reason: Hibernate from Sleep - Fixed Timeout

The Error message there caught my eye.  In Services, I can see that ms-resource:AppName is actually C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.3.0_x64__8wekyb3d8bbwe\wslservice.exe. So I guess this means that the WSL service crashes.
Diagnostic Logs
No response

Thank you for reporting this @kyllingstad.
Can you follow the '11) Reporting a WSL process crash' section and share the wslservice.exe crash dump ?

I am trying to reproduce it with a crash dump and will report here as soon as I'm successful. It looks like the “sleep to hibernation” transition is not a sufficient condition to trigger the crash; it remains to see whether it’s a necessary one.

I'm experiencing the same problem after I updated wsl, as it prompted, several days ago. It occurred four or five times, mostly after awaking from hibernation. I'll try to see if I can reproduce it and collect the crash dump.

I'm a bit of worried about sending out dump files may leak private info.
I put the dump file into windbg. The output of !analyze -v looks like this:
KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 546
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 546
    Key  : Analysis.IO.Other.Mb
    Value: 0
    Key  : Analysis.IO.Read.Mb
    Value: 1
    Key  : Analysis.IO.Write.Mb
    Value: 0
    Key  : Analysis.Init.CPU.mSec
    Value: 686
    Key  : Analysis.Init.Elapsed.mSec
    Value: 88990
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 268
    Key  : Timeline.OS.Boot.DeltaSec
    Value: 83015
    Key  : Timeline.Process.Start.DeltaSec
    Value: 40319
    Key  : WER.OS.Branch
    Value: vb_release
    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z
    Key  : WER.OS.Version
    Value: 10.0.19041.1
    Key  : WER.Process.Version
    Value: 10.0.10011.16384
FILE_IN_CAB:  wslservice.exe.18472.dmp
NTGLOBALFLAG:  0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS:  0

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffa35de2684 (ntdll!TppRaiseInvalidParameter+0x0000000000000048)
   ExceptionCode: c000000d
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  wslservice.exe
ERROR_CODE: (NTSTATUS) 0xc000000d - <Unable to get error code text>
EXCEPTION_CODE_STR:  c000000d

STACK_TEXT:
 ntdll!TppRaiseInvalidParameter+0x48
 ntdll!TppCallbackMayRunLongProlog+0x50b53
 ntdll!TpCallbackMayRunLong+0x26
 KERNELBASE!CallbackMayRunLong+0xb
 IPHLPAPI!ThreadpoolWorkCallback+0x61
 ntdll!TppWorkpExecuteCallback+0x130
 ntdll!TppWorkerThread+0x68a
 kernel32!BaseThreadInitThunk+0x14
 ntdll!RtlUserThreadStart+0x21

STACK_COMMAND:  ~5s; .ecxr ; kb
SYMBOL_NAME:  iphlpapi!ThreadpoolWorkCallback+61
MODULE_NAME: IPHLPAPI
IMAGE_NAME:  IPHLPAPI.DLL
FAILURE_BUCKET_ID:  INVALID_PARAMETER_c000000d_IPHLPAPI.DLL!ThreadpoolWorkCallback
OS_VERSION:  10.0.19041.1
BUILDLAB_STR:  vb_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
IMAGE_VERSION:  10.0.19041.1865
FAILURE_ID_HASH:  {2c04f593-4eb5-f690-42dc-82b4a67ffe1b}
Followup:     MachineOwner

It seems this doesn't happen to me anymore. WSL used to crash every time I put my computer to sleep overnight, but now it doesn't anymore. Perhaps an update fixed it. (It's a work laptop, so I don't have full control over when updates get installed.) It's good that someone else could reproduce it.

This is happening for me regularly when my computer is left alone overnight. It's an intermittent fault, and sometimes it might go for a week or longer without issue.
I've only experienced this issue since updating WSL via wsl --update a month or so ago.
PS C:\WINDOWS\system32> wsl --version                                                                                WSL version: 1.0.3.0                                                                                Kernel version: 5.15.79.1                                                                                WSLg version: 1.0.47                                                                                MSRDC version: 1.2.3575                                                                                Direct3D version: 1.606.4                                                                                DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp                                                        Windows version: 10.0.19044.2486

So you mention that it takes a while for this issue to occur, and you believe that it happens when the laptop goes from sleep to hibernation. So if you close the laptop lid and open it back up right away this does not happen?
I am mainly asking, because I am encountering a similar issue, and for me it happens pretty much immediately. Maybe I have to wait until the fan stops spinning, but that's about it.
And I found this issue related to windows terminal (which I noticed also closed itself) https://github.com/microsoft/terminal/issues/12513
And the people in this thread encountered that for them, all apps installed through the Microsoft store close, when they close their laptops. WSL, Ubuntu and the Microsoft Terminal (Preview) are all store apps, so I tried it out and just opened every app that I had installed through the store (by going to "My Library" in the store). When I closed my laptop and opened it back up they were all gone.
From this other issue, it appears that the problem is getting internal attention from Microsoft, but from what I can tell there is no consistent way of fixing it at the moment.
So I'm not sure if this is the same problem that you have, but I think it is at least similar in behavior.
I have enabled automatic crash dumps, like @OneBlue suggested and I got some files, they were all titled pwsh.exe.<something>. Which is a bit odd, because from what I can tell I do not have the store version of PowerShell installed (it doesn't show in "My Library" and searching for it, shows a "Get"-button instead of an "Open"-buton).
I don't know if I could look at those dump files, vscode tells me they're in binary

So you mention that it takes a while for this issue to occur, and you believe that it happens when the laptop goes from sleep to hibernation. So if you close the laptop lid and open it back up right away this does not happen?

No, that hasn't happened to me.

[…]
And I found this issue related to windows terminal (which I noticed also closed itself) microsoft/terminal#12513
And the people in this thread encountered that for them, all apps installed through the Microsoft store close, when they close their laptops. WSL, Ubuntu and the Microsoft Terminal (Preview) are all store apps, so I tried it out and just opened every app that I had installed through the store (by going to "My Library" in the store). When I closed my laptop and opened it back up they were all gone.

This seems like a different issue. Windows Terminal never crashed for me, only WSL.

Ok, it seems this has little to do with hibernation. It just happened now when I woke the computer from regular sleep. I've updated the issue title accordingly. Like a previous poster, I also worry about publishing dump files, so here is my windbg output of !analyze -v:
KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 906

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11490

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 32

    Key  : Analysis.Init.CPU.mSec
    Value: 765

    Key  : Analysis.Init.Elapsed.mSec
    Value: 48704

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 89

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 85286

    Key  : Timeline.Process.Start.DeltaSec
    Value: 85266

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 10.0.10011.16384

FILE_IN_CAB:  wslservice.exe.6588.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=00007ff7c10a8af8 rbx=0000000000000000 rcx=000001cbe4a29940
rdx=0000000000000000 rsi=0000006cf1affc78 rdi=000001cbe4a6e680
rip=00007fff8e102684 rsp=0000006cf1aff8d0 rbp=000001cbe4a706a8
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=000000007ffe03b0 r13=000000000000022c
r14=0000006cf1affa48 r15=0000006cf1affa20
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
ntdll!TppRaiseInvalidParameter+0x48:
00007fff`8e102684 eb00            jmp     ntdll!TppRaiseInvalidParameter+0x4a (00007fff`8e102686)
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fff8e102684 (ntdll!TppRaiseInvalidParameter+0x0000000000000048)
   ExceptionCode: c000000d
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  wslservice.exe

ERROR_CODE: (NTSTATUS) 0xc000000d - An invalid parameter was passed to a service or function.

EXCEPTION_CODE_STR:  c000000d

STACK_TEXT:
0000006c`f1aff8d0 00007fff`8e0b0b2b     : 00000000`00000001 00007fff`8e0105dd 00000000`00000000 00006572`0d18d124 : ntdll!TppRaiseInvalidParameter+0x48
0000006c`f1aff9b0 00007fff`8e05ff96     : 00000000`0001000a 00000000`00000000 0000006c`f1affc78 00006572`0d18d024 : ntdll!TppCallbackMayRunLongProlog+0x50b53
0000006c`f1aff9f0 00007fff`8b9c376b     : 00000000`00000000 00007fff`00000004 00000001`00000003 00006572`00000000 : ntdll!TpCallbackMayRunLong+0x26
0000006c`f1affa40 00007fff`8ab295d1     : 000001cb`e4a02340 00000000`00000000 00000000`00000000 0000006c`f1affc78 : KERNELBASE!CallbackMayRunLong+0xb
0000006c`f1affa70 00007fff`8e052260     : 000001cb`e4a705e0 00000000`00000001 000001cb`e53f6970 000001cb`e4a02340 : IPHLPAPI!ThreadpoolWorkCallback+0x61
0000006c`f1affab0 00007fff`8e0431aa     : 000001cb`e4a1b5e8 00000000`00000000 000001cb`e4a02340 00000000`00000000 : ntdll!TppWorkpExecuteCallback+0x130
0000006c`f1affb00 00007fff`8d837614     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x68a
0000006c`f1affe00 00007fff`8e0426a1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
0000006c`f1affe30 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

STACK_COMMAND:  ~8s; .ecxr ; kb

SYMBOL_NAME:  iphlpapi!ThreadpoolWorkCallback+61

MODULE_NAME: IPHLPAPI

IMAGE_NAME:  IPHLPAPI.DLL

FAILURE_BUCKET_ID:  INVALID_PARAMETER_c000000d_IPHLPAPI.DLL!ThreadpoolWorkCallback

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  10.0.19041.1865

FAILURE_ID_HASH:  {2c04f593-4eb5-f690-42dc-82b4a67ffe1b}

Followup:     MachineOwner
---------

I don't know if this is useful, so please advise on how I can send the dump file safely to Microsoft if needed.

Okay, if Windows terminal and other store apps, like the store itself, stay open this does seem to be different to my issue.
To send files to Microsoft you can use Feedback Hub:

And choose attach file there, not sure if there is a limitation to which file types can be attached.

It also happens with my wsl1/Ubuntu 22.04. After waking up from some kind of power-saving mode (I'm not sure whether it's sleep or hibernation). The Ubuntu shell would display the following error message:
Error: 0xd00002fe
Error code: Wsl/Service/0xd00002fe Press any key to continue...

When I press any key, the window for the shell would be gone.
Here is the version of the wsl:
WSL version: 1.1.3.0
Kernel version: 5.15.90.1
WSLg version: 1.0.49
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19042.2604

Although the version is supposed to run WSL2, my Windows' version is too old. WSL1 is in fact running.
I had the problem after upgrading to the version that supports WSL2. (I don't benifit from the upgrade, but got the new problem.)
I wonder if downgrading the wsl version would help.

I have the same issue, and it is NOT related to hibernation, but to sleep mode. Happens consistently after I get out of sleep (sleep duration makes no difference), and I distinctly remember this has started after I "upgraded" haha to WSL2 from the store.
I'm using Windows terminal and VSCode and both apps are affected.
Terminal: [process exited with code 1 (0x00000001)]
I don't have to stop/start/restart WSL2 at this point. Its enough to open a new Ubuntu window in Terminal and continue working, so its not a workstopper but a major annoyance and time waster. This has been going on and on so many times for weeks now, that I was forced to search for a solution and found this thread.
Ubuntu version: 20.04.5 LTS
WSL version: 1.1.3.0
Kernel version: 5.15.90.1
WSLg version: 1.0.49
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19044.2604

WSL1 is in fact running

@yubrshen I think you are on WSL2. https://askubuntu.com/questions/1177729/wsl-am-i-running-version-1-or-version-2

I distinctly remember this has started after I "upgraded" haha to WSL2 from the store.

Same here. I deleted the app and now WSL seems running OK. The problem was only present on my work laptop where modern standby is enabled.

@zoliweiss could you pls let me know how you reverted to "normal" WSL. Did you remove 1 or both of these under Settings > Apps & features?

Did you have to reinstall WSL after that? Or something else?

No, I removed the WSL app from the Start menu with right click remove option, if I remember correctly. I can't show you, because I already removed it.

Did you have to reinstall WSL after that? Or something else?
No, it just reverted to the old version I guess, because it now sometimes displays the update message in terminal.

So just to be sure: your Ubuntu installation didnt get affected in any way right? No files lost, everything running seamlessly like before?

I didn't find any problem.

@zehawki thanks for reminding me that my Windows 10 can actually run WSL 2.
Last time, after upgrading the wsl, I was led to believe that I could run WSL2. But the conversion of my Ubuntu to WSL 2 took forever, never-ending.
Today, I tried the conversion again. It worked much better.
First of all, when I execute the conversion command, I got an error in the PowerShell:
wsl --set-version Ubuntu-22.04 2
Importing the distribution failed. Error code: Wsl/Service/WSL_E_IMPORT_FAILED
Upon extensive search, eventually, MS new Bing told me that the top of the three reasons for the failure is the PowerShell lacked admin privilege. I then ran the same command with elevated privilege PowerShell. After nearly two hours, this time the conversion succeeded.
Now, Ubuntu runs in WSL2! I can use WSLg without an external X server to run graphic emacs now.
(It looks like the recent another upgrade of wsl might have improved to my convention.)
I also had stopped the running instance of Ubuntu before the conversion, by the command:
wsl -t Ubuntu-22.04
It turned out that the error message is exactly the same as appearing in the Ubuntu shell when my laptop wakes up from sleep!
I'll continue to monitor if the problem of Ubuntu stopping after waking up still happens.

On my side the issue has disappeared after uninstalling WSL2 store version (and reverting to "normal" WSL2) as advised by @zoliweiss.

The issue is gone for me after the latest update [0]. WSL is not crashing anymore after sleep, though Windows Terminal sometimes does crash, but WSL is fine and responsive.
[0] 2023-03 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5023706)

This is still a problem for me, WSL2 with Ubuntu - Crashes on wake from sleep and refused to be shutdown using wsl --terminate ubuntu the other issue is when it crashes it uses 99% of CPU until it eventually closes from the command mentioned or I restart the device.

This has been happening for the better part of a year.
Specs -
WSL version: 1.2.0.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22000.1817

Same here with
WSL-Version: 1.2.5.0
Kernelversion: 5.15.90.1
WSLg-Version: 1.0.51
MSRDC-Version: 1.2.3770
Direct3D-Version: 1.608.2-61064218
DXCore-Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows-Version: 10.0.19045.2846
Sometimes only taskkill /f /im wslservice.exe works to restart wsl2.

Having the same Problem with WSL2 and Ubuntu under Win10. After hibernation, the environment bekomes sluggish to the point of a crash with:

I cant even open a terminal and run htop to check whats using all those resources.
Only restart of the host helps.

The same situation - WSL2:

I can reproduce on my machine
WSL version： 2.3.11.0
kernel version： 6.6.36.3-1
WSLg version： 1.0.63
MSRDC version： 1.2.5326
Direct3D version： 1.611.1-81528511
DXCore version： 10.0.26100.1-240331-1435.ge-release
Windows version： 10.0.22631.3880

I have the same issue on my laptop. It happens very often when the laptop awakes from sleep.
My device info:
Edition	Windows 11 Pro
Version	23H2
OS build	22631.3880
Experience	Windows Feature Experience Pack 1000.22700.1020.0
wsl info:
WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22631.3880

It's been happening on every single wake from sleep ever since I upgraded to 2.3.11.0

Just chiming in to say I've been experiencing the same thing for the last few days as well. Every sleep and wake results in the WSL2 guest crashing.

@OneBlue has identified a bug in 2.3.11 and will be releasing a fix shortly.

I updated to WSL version 2.3.12.0 last night and I did not get the error this morning. WSL is up and running after my PC woke from sleeping. Thank you to everyone involved!

Yep. The issue seems to be fixed for WSL version 2.3.12.0

Looks like the issue is back on version 2.3.13.0 :-(

@ufondu88 It works here just fine. Make sure you are using the last version with wsl.exe --update --pre

Crash from sleep.
"Error: 0xd00002fe
Error code: Wsl/Service/0xd00002fe
[process exited with code 4294967295 (0xffffffff)]
You can now close this terminal with Ctrl+D, or press Enter to restart."

wsl --version
WSL version: 2.3.24.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4169

Similar things happening here as well.
Steps

Open WSL in Windows Terminal
Create a tmux session in WSL (tmux)
Close the Terminal, put computer to sleep
Wake and open WSL in Terminal
Attach: tmux attach

Expected: tmux session is alive
Actual: no tmux sessions exist in WSL, as confirmed with tmux ls
Additional info
WSL version: 2.3.24.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4391

Observations

Distro was terminated/shutdown?
If Windows Terminal window is kept open when sleeping, the tmux session is alive and well. Same goes for other processes as far as I can see (as long as the Terminal window is open).

authors: D1g1talEntr0py Nick-Datacom OneBlue Stanzilla WulfP a-tarasiuk ashleyghooper benhillis humiki janb14 jnzd kyllingstad majamin onomatopellan pmyers qwqawawow rainingdays spipes ufondu88 whfuyn yubrshen zehawki zoliweiss


text:
I need help on how to change focus when a new window is opened in the WPS application

Hi,
With WinAppDriver I am able to open a WPF application and test using the code below,
I need help on how to change focus when a new window is opened in the WPS application.
the Problem with WPS applications is that you cannot use the standard, as the driver will not recognize the app. there should be a way to help switch focus or at least open an existing WPS application window which I cannot do right now. if anybody could help, I would greatly appreciate it.
// to open the standard app
AppiumOptions options2 = new AppiumOptions();
options2.AddAdditionalCapability("app", "Application new window");
options2.AddAdditionalCapability("Window", "WindowsPC");
//to open a WPS application
AppiumOptions options = new AppiumOptions();
options.AddAdditionalCapability("app", @"C:\Path\Debug\Application.exe");
options.AddAdditionalCapability("deviceName", "WindowsPC");
_driver = new WindowsDriver(new Uri("http://127.0.0.1:4723"), options);

Can you give an example of a WPS application? I'm assuming you mean WPF?
Launching WPF should be supported, but if the app fails to launch, you could try creating a desktop session and then attaching to your WPF app session.

Hi, thanks for your comment, (sorry Yes I am talking about a WPF application), in theory, that should work, but in actuality, that doesn't work with WPF applications.
I am able to attach to a regular app session(like a Windows calculator) but to launch a WPF application with WinAppDriver, you need to use a path like: options.AddAdditionalCapability("app", @"C:\Path\Debug\Application.exe");
I am not able to attach to a WPF app session, becuase the driver cannot find the sub-root window.
I have tried to select the pop-up window by clicking on the xpath of the window, but that also seems to not work with WPF apps but does work with WinForms.
Please if you actually have experience testing WPF applications with WinAppDriver please comment:

Could you provide the snippet of your current attaching solution?

Hi Guys,
I was able to figure out how to focus on new windows being open in a WPF application and wanted to post my solution Below:
//Setup
private WindowsDriver _driver;
AppiumOptions options = new AppiumOptions();
options.AddAdditionalCapability("app", @"C:\DOCHUB_Desktop\Debug\USFS.DocHub.UI.Desktop.exe");
options.AddAdditionalCapability("deviceName", "WindowsPC");
_driver = new WindowsDriver(new Uri("http://127.0.0.1:4723"), options);
_driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(5);
//Test
_driver.FindElementByAccessibilityId("Login").Click();
Thread.Sleep(5000);
_driver.FindElementByName("button").Click();
//Opens a new window
_driver.FindElementByName("Open").Click();
Thread.Sleep(2000);
//Solution -  switches to the latest window
_driver.SwitchTo().Window(_driver.WindowHandles.First());
//can click on buttons in the new Window
_driver.FindElementByName("buttons").Click();
//Opens another new Window
_driver.FindElementByName("Open another window").Click();
Thread.Sleep(2000);
//Solution - switches to the latest window
_driver.SwitchTo().Window(_driver.WindowHandles.First());
//can click on buttons in the new Window
_driver.FindElementByName("button3").Click();

authors: hassanuz pm90pl rabaribe

repo: microsoft/WinAppDriver


text:
Unable to pull 2022 images on 21H1 W10 Pro

OS Name:  Microsoft Windows 10 Pro
OS Version: 19043.1165
 docker pull mcr.microsoft.com/windows/nanoserver:ltsc2022
ltsc2022: Pulling from windows/nanoserver
no matching manifest for windows/amd64 10.0.19043 in the manifest list entries

docker pull mcr.microsoft.com/powershell:lts-nanoserver-ltsc2022
lts-nanoserver-ltsc2022: Pulling from powershell
a Windows version 10.0.20348-based image is incompatible with a 10.0.19043 host

We just publish information about this: https://techcommunity.microsoft.com/t5/containers/windows-server-2022-and-beyond-for-containers/ba-p/2712487#M139 - Please see the Windows and developer scenarios section on the blog post.
Here's the long story: Windows 10 has a build number of 19043. Windows Server 2022 has a build number of 20348, so that means the image is newer than the host. We never supported this scenario, but it means customers running Windows 10 can't pull or run Windows Server 2022 images. Customers running Windows 11, which has a higher build number than Windows Server 2022 can. Since Windows 11 is not GA yet, we know many customers don't have an option to move up, so we're temporarily enabling these new preview images for Windows 10 21H1 so you can kick the tires until Windows 11 is GA.

The Windows Container Version Compatibility  page shows that you can run a Windows Server 2022 image on Windows 10 21H1 via Hyper-V isolation.  Is that info now out of date?

authors: JoelLeach rosskirkpat vrapolinario

repo: microsoft/Windows-Containers


text:
User/sachinta/fix installer for windows10 arm64 on release 1.1 stable

Cherry-picked from https://github.com/microsoft/WindowsAppSDK/pull/2901 and https://github.com/microsoft/WindowsAppSDK/pull/2841
Fix installer to not attempt to install x64 framework package on Windows 10 ARM64 systems.
Fix console output that wasn't respecting quiet option.
Fix Push notifications LRP restart decision logic to be inclusive of ARM64 architecture as well.

/azp run

source: gharchive/pull-request

repo: microsoft/WindowsAppSDK


text:
Can't open Power Point slides because they are protected by information rights management

Can't open Power Point slides because they are protected by information rights management. Cloud you share a public PPT slide that is accyible without an microsoft internal account?

@Shavonna can you please work with content owners to resolve link & perm issues.
cc @daisychaussee

I've uploaded a new version (v2.1) of the PowerPoint deck with the correct IRM label. The aka.ms link remains the same.


text:
I have this problem with iOS build

I have this problem with iOS build and it's so anoying.
I don't why, but my distribution to the Appstore Testflight it's failing with error "distribution store with id xxxx does not exist", but the App build it's ok, it's only the distribution step.
Originally posted by @francovp in https://github.com/microsoft/appcenter/issues/587#issuecomment-764954593

Hi @cmartinezglbnt, first make sure that you have created your store connection in Distribution > Stores page, and then go to your branch configuration under Build, and first unselect and then select again one of your existing Store connections as target in the "Distribute builds" section.
This error you're seeing probably comes from last branch configuration with a previous store connection, that may no longer exist.

Hi @cmartinezglbnt . May I ask if your issue is resolved?

Hi @miroslavmatovic yes is resolved, thanks. I've changed the distribution user profile and the distribution store config was reloaded.

Would it be possible to warn user about unset Stores configuration a bit sooner? Like before he waits an hour for the build to finish ;)

authors: cmartinezglbnt kub1x miroslavmatovic

repo: microsoft/appcenter


text:
Change default model in LMM

Why are these changes needed?
Address issue https://github.com/microsoft/autogen/issues/965
Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a0288e0) 26.54% compared to head (35c06d8) 19.59%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1032      +/-   ##
==========================================
- Coverage   26.54%   19.59%   -6.95%
==========================================
  Files          28       28
  Lines        3805     3807       +2
  Branches      865      907      +42
==========================================
- Hits         1010      746     -264
- Misses       2724     2954     +230
- Partials       71      107      +36

Flag
Coverage Δ

unittests
19.54% <100.00%> (-6.95%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

My understanding is that this is to make sure the model used support multi-modal input correct?

Yes, correct. The ConversableAgent defaults to “gpt-4", and we should default to a multimodal model. When the config_list is not set, the default model will be used.

authors: BeibinLi codecov-commenter

repo: microsoft/autogen


text:
Add HTMLProofer check for website

Why are these changes needed?
Docusarus does not catch all broken links and other issues. This adds the htmlproofer tool to verify the build output of the website.
We can check external links too but it seems a but flaky perhaps due to rate limiting so I opted to start with it disabled.
Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5b217c9) 34.24% compared to head (a28ee04) 34.13%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1547      +/-   ##
==========================================
- Coverage   34.24%   34.13%   -0.12%
==========================================
  Files          42       42
  Lines        5098     5098
  Branches     1165     1165
==========================================
- Hits         1746     1740       -6
- Misses       3209     3215       +6
  Partials      143      143

Flag
Coverage Δ

unittests
34.13% <ø> (-0.12%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I'm not satisfied with the stability of this tool for false positives and external link checks (there are many 429 equivalents which is honestly very reasonable).

authors: codecov-commenter jackgerrits


text:
docstr updated for use_docker in execute_code

Why are these changes needed?
Mentioned in Issue #214 , Made the required changes

Related issue number
Closes issue #214

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report

Merging #233 (157355e) into main (6156faa) will decrease coverage by 2.40%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #233      +/-   ##
==========================================
- Coverage   43.31%   40.92%   -2.40%
==========================================
  Files          17       17
  Lines        2133     2133
  Branches      481      481
==========================================
- Hits          924      873      -51
- Misses       1126     1173      +47
- Partials       83       87       +4

Flag
Coverage Δ

unittests
40.92% <ø> (-2.30%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

autogen/code_utils.py
39.65% <ø> (-9.49%)
:arrow_down:

... and 1 file with indirect coverage changes

The code formatting issue is not caused by this PR. Please recover the space after '-'.
I made a PR to fix the code formatting #242

The code formatting issue is not caused by this PR. Please recover the space after '-'. I made a PR to fix the code formatting #242

Sorry for the misunderstanding.... i will revert the changes

@sonichi  I have reverted the changes by adding space in -

@qingyun-wu your requested change blocks merging.

@sonichi are there any changes to be done from my side..

authors: Gourav2609 codecov-commenter sonichi


text:
Fix grammar and spelling in agentchat_chess.ipynb

Why are these changes needed?
For readability.

Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report

Merging #346 (75a2a92) into main (ca2e0b8) will decrease coverage by 2.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #346      +/-   ##
==========================================
- Coverage   42.33%   40.20%   -2.14%
==========================================
  Files          19       19
  Lines        2393     2393
  Branches      539      539
==========================================
- Hits         1013      962      -51
- Misses       1302     1349      +47
- Partials       78       82       +4

Flag
Coverage Δ

unittests
40.20% <ø> (-2.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes


text:
az containerapp exec --comand ""

Please provide us with the following information:

This issue is a: (mark with an x)

[ X] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
Having options to the command in az container app exec results in error
Steps to reproduce

az containerapp exec -g <resource_group> -stage -n <container_name> --command "ls -la"

Expected behavior [What you expected to happen.]
executes the command with the options - like in terms of ls -la shows all  contents of current directory in list view
Actual behavior [What actually happened.]
Crashes:
INFO: Connecting to the container 'backend'...
Use ctrl + D to exit.
INFO: Successfully connected to container: 'backend'. [ Revision: '<revision_name>', Replica: '<replica_name>']
ERROR: {"Error":{"Code":"ClusterExecFailure","Message":"Cluster exec API returns error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec <...>\u0022: OCI runtime exec failed: exec failed: unable to start container process: exec: \u0022ls -la\u0022: executable file not found in $PATH: unknown, code: 500.","Details":null,"Target":null,"AdditionalInfo":null}}
Disconnecting...

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Ex. Did this issue occur in the CLI or the Portal?
Seems similar like #628

Hi @arnoldknott
Did your image used in this containerapp support shell?
Did this issue occur in the Portal?
Thanks!

@Greedygre ,
I have tried with various images. And yes, as long as I only pass one argument, e.g. /bin/sh it works fine. As soon as I am inside the container with for example /bin/sh, I can execute anything, like ls -la successfully.
No, I have not tried in portal. I have used the az containerapp exec on my local machine and in a GitHub actions workflow. Same result, no matter which host I executed the command in.
Does that make sense? 🤔
Can you reproduce the issue?

@arnoldknott
I cannot reproduce the issue with error 'OCI runtime exec failed: exec failed: unable to start container process: exec: "invalid-command": executable file not found in $PATH: unknown'  when the contatinerapp created in a dedicated workload profile.
May I ask what kind of environment the containerapp in?
Is your containerapp created in a dedicated workload profile?
Thanks!

@arnoldknott
We have identified this is a bug for the command with parameters, we will fix this in the next release.
Thank you for reporting this.

@arnoldknott We have identified this is a bug for the command with parameters, we will fix this in the next release. Thank you for reporting this.

@howang-ms  thank you so much for investigating and looking forward to the fix! 🙏

Issue has been fixed. Thank you for your patience
CC: @howang-ms

authors: Greedygre LianaAdaza arnoldknott howang-ms

repo: microsoft/azure-container-apps


text:
Azure Pipeline installation failing with "The Extension failed to execute: Agent Configuration failed with error - Failed to Lock Service Database for"

Having issue with YAML?
no
Having issue with Tasks?
no
Having issue with software on Hosted Agent?
no
Having generic issue with Azure-Pipelines/VSTS/TFS?
no
Have you tried troubleshooting?
yes
Agent Version and Platform
Version of your agent? 2.172.2 , Windows 2019
OS of the machine running the agent? Windows
Azure DevOps Type and Version
dev.azure.com
If dev.azure.com, what is your organization name? https://dev.azure.com/marketingops or https://{organization}.visualstudio.com
What's not working?
Installation of the deployment group agent is frequently failing
We regularly reinstall our CI servers  to keep up to date and get rid of any collected cruft. We install them in groups of 8 and recently this started to become very unreliable. Most of the time only 5 to 7 out of 8 would install succesfully. The failing agent always logs something of a lock failing

Agent and Worker's Diagnostic Logs
Relevant installation log (authored to remove any sensitive information)

[2020-07-31T07:11:34] Reading config settings from file...
[2020-07-31T07:11:34] Reading handler settings from C:\Packages\Plugins\Microsoft.VisualStudio.Services.TeamServicesAgent\1.27.0.1\RuntimeSettings\0.settings
[2020-07-31T07:11:34] Found protected settings on Azure VM. Decrypting with certificate.
[2020-07-31T07:11:34] Read config settings from file. Now extracting inputs and doing basic validations.
[2020-07-31T07:11:34] Is Deployment Agent
[2020-07-31T07:11:35] Azure DevOps Organization Url: https://dev.azure.com/******
[2020-07-31T07:11:35] Team Project: ****
[2020-07-31T07:11:35] Deployment Group: ****-***-range-dg
[2020-07-31T07:11:35] Agent name from input settings:
[2020-07-31T07:11:35] Tags:
Name                           Value
----                           -----
Environment                    ***
Purpose                        ***
ReleaseId                      ***
Region                         ***
Stage                          ***
AppTier                        ***

[2020-07-31T07:11:35] Done reading config settings from file...
[2020-07-31T07:11:35] [Agent Settings Helper]: Check if any existing agent is running from C:\AzurePiplinesAgent_Extension
[2020-07-31T07:11:35] [Agent Settings Helper]: 		 Agent setting file path C:\AzurePiplinesAgent_Extension\.agent
[2020-07-31T07:11:35] [Agent Settings Helper]: 		 Agent setting file exist: False
[2020-07-31T07:11:35] [Agent Settings Helper]: Check if any existing agent is running from C:\VSTSAgent
[2020-07-31T07:11:35] [Agent Settings Helper]: 		 Agent setting file path C:\VSTSAgent\.agent
[2020-07-31T07:11:35] [Agent Settings Helper]: 		 Agent setting file exist: False
[2020-07-31T07:11:35] reading last sequence number LASTSEQNUM file C:\Packages\Plugins\Microsoft.VisualStudio.Services.TeamServicesAgent\1.27.0.1\bin\..\LASTSEQNUM
[2020-07-31T07:11:35] Sequence Number: 0
[2020-07-31T07:11:35] Testing whether disabled markup file exists: C:\AzurePiplinesAgent_Extension\EXTENSIONDISABLED
[2020-07-31T07:11:35] Disabled version settings file does not exist in the agent directory. Will continue with enable.
[2020-07-31T07:11:35] Disabled settings absent, continue with enable.
[2020-07-31T07:11:35] Get deployment group url - https://dev.azure.com/***/***/_apis/distributedtask/deploymentgroups?name=*****&api-version=5.0-preview.1
[2020-07-31T07:11:35] Get deploymentgroup retried 1 times
[2020-07-31T07:11:35] Validated that the deployment group "***-ci-***-range-dg" exists
[2020-07-31T07:11:35] Patch deployment group url - https://dev.azure.com/***/***/_apis/distributedtask/deploymentgroups/***?api-version=5.0-preview.1
[2020-07-31T07:11:35] Patch deploymentgroup retried 1 times
[2020-07-31T07:11:35] Validated that the user has "Manage" permissions on the deployment group ***-ci-***-range-dg
[2020-07-31T07:11:35] Done validating inputs...

[2020-07-31T07:11:35] [Agent Settings Helper]: Check if any existing agent is running from C:\AzurePiplinesAgent_Extension
[2020-07-31T07:11:35] [Agent Settings Helper]: 		 Agent setting file path C:\AzurePiplinesAgent_Extension\.agent
[2020-07-31T07:11:35] [Agent Settings Helper]: 		 Agent setting file exist: False
[2020-07-31T07:11:35] configuredAgentExists: False
[2020-07-31T07:11:35] agentConfigurationRequired: True

[2020-07-31T07:11:35] Invoking script to download and extract Deployment agent package...
[2020-07-31T07:11:35] Working folder for AzureDevOps agent: C:\AzurePiplinesAgent_Extension
[2020-07-31T07:11:35] Working folder does not exist. Creating it...
[2020-07-31T07:11:35] [Download]: Starting the DownloadDeploymentAgent script
[2020-07-31T07:11:35] [Download]: Get the url for downloading the agent
[2020-07-31T07:11:35] [Download]: 		 Get Agent PackageData using https://dev.azure.com/***/_apis/distributedtask/packages/agent/win-x64?top=1&api-version=3.0-preview.2
[2020-07-31T07:11:35] [Download]: 		 Invoke-rest call for packageData
[2020-07-31T07:11:35] Get packagedata retried 1 times
[2020-07-31T07:11:35] [Download]: Deployment Agent download url - https://vstsagentpackage.azureedge.net/agent/2.172.2/vsts-agent-win-x64-2.172.2.zip
[2020-07-31T07:11:35] [Download]: Get the target zip file path
[2020-07-31T07:11:35] [Download]: 		 Deployment agent will be downloaded at - C:\AzurePiplinesAgent_Extension\agent.zip
[2020-07-31T07:11:35] [Download]: Downloading deploymentAgent
[2020-07-31T07:11:35] [Download]: 		 Start DeploymentAgent download
[2020-07-31T07:11:36] retried 1 times
[2020-07-31T07:11:36] [Download]: 		 DeploymentAgent download done
[2020-07-31T07:11:36] [Download]: Done with DownloadDeploymentAgent script
[2020-07-31T07:12:00] C:\AzurePiplinesAgent_Extension\agent.zip is extracted to C:\AzurePiplinesAgent_Extension
[2020-07-31T07:12:00] Agent package downloaded and extracted

[2020-07-31T07:12:00] Configuring agent...
[2020-07-31T07:12:00] Agent name not provided as input
[2020-07-31T07:12:00] List targets url - https://dev.azure.com/***/***/_apis/distributedtask/deploymentgroups/***/targets?name=l17***988l8-DG&api-version=5.0-preview.1
[2020-07-31T07:12:00] List targets retried 1 times
[2020-07-31T07:12:00] Deployment group does not contain the target
[2020-07-31T07:12:00] Agent name: l17***988l8-DG
[2020-07-31T07:12:20] [Configuration]: ConfigProcess exit code:
[2020-07-31T07:12:20] [Configuration]:
  ___                      ______ _            _ _
 / _ \                     | ___ (_)          | (_)
/ /_\ \_____   _ _ __ ___  | |_/ /_ _ __   ___| |_ _ __   ___  ___
|  _  |_  / | | | '__/ _ \ |  __/| | '_ \ / _ \ | | '_ \ / _ \/ __|
| | | |/ /| |_| | | |  __/ | |   | | |_) |  __/ | | | | |  __/\__ \
\_| |_/___|\__,_|_|  \___| \_|   |_| .__/ \___|_|_|_| |_|\___||___/
                                   | |
        agent v2.172.2             |_|          (commit 1117823)

>> Connect:

Connecting to server ...

>> Register Agent:

Scanning for tool capabilities.
Connecting to the server.
Successfully added the agent
Testing agent connection.
2020-07-31 07:12:15Z: Settings Saved.
Granting file permissions to '***'.
Service vstsagent.***.***-***-ci-***-range-dg.***-DG successfully installed
Error reported in diagnostic logs. Please examine the log for more details.
    - C:\AzurePiplinesAgent_Extension\_diag\Agent_20200731-071204-utc.log

[2020-07-31T07:12:20] [Configuration]: Failed to Lock Service Database for Write

[2020-07-31T07:12:20] Error occured during Agent configuration
[2020-07-31T07:12:20] System.Management.Automation.RuntimeException: Agent Configuration failed with error - Failed to Lock Service Database for Write

[2020-07-31T07:12:20] [ERROR] Agent Configuration failed with error - Failed to Lock Service Database for Write

[2020-07-31T07:12:20] {
    "Exception":  {
                      "ErrorRecord":  {
                                          "Exception":  "System.Management.Automation.ParentContainsErrorRecordException: Agent Configuration failed with error - Failed to Lock Service Database for Write\r\n",
                                          "TargetObject":  null,
                                          "CategoryInfo":  "NotSpecified: (:) [], ParentContainsErrorRecordException",
                                          "FullyQualifiedErrorId":  "RuntimeException",
                                          "ErrorDetails":  null,
                                          "InvocationInfo":  null,
                                          "ScriptStackTrace":  null,
                                          "PipelineIterationInfo":  ""
                                      },
                      "WasThrownFromThrowStatement":  true,
                      "Message":  "Agent Configuration failed with error - Failed to Lock Service Database for Write\r\n",
                      "Data":  {

                               },
                      "InnerException":  null,
                      "TargetSite":  null,
                      "StackTrace":  null,
                      "HelpLink":  null,
                      "Source":  null,
                      "HResult":  -2146233087
                  },
    "TargetObject":  "Agent Configuration failed with error - Failed to Lock Service Database for Write\r\n",
    "CategoryInfo":  {
                         "Category":  14,
                         "Activity":  "",
                         "Reason":  "RuntimeException",
                         "TargetName":  "Agent Configuration failed with error - Failed to Lock Service Database for Write\r\n",
                         "TargetType":  "String"
                     },
    "FullyQualifiedErrorId":  "Agent Configuration failed with error - Failed to Lock Service Database for Write\r\n",
    "ErrorDetails":  null,
    "InvocationInfo":  {
                           "MyCommand":  null,
                           "BoundParameters":  {

                                               },
                           "UnboundArguments":  [

                                                ],
                           "ScriptLineNumber":  91,
                           "OffsetInLine":  9,
                           "HistoryId":  -1,
                           "ScriptName":  "C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin\\AgentConfigurationManager.ps1",
                           "Line":  "        throw \"Agent Configuration failed with error - $stderr\"\r\n",
                           "PositionMessage":  "At C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin\\AgentConfigurationManager.ps1:91 char:9\r\n+         throw \"Agent Configuration failed with error - $stderr\"\r\n+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~",
                           "PSScriptRoot":  "C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin",
                           "PSCommandPath":  "C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin\\AgentConfigurationManager.ps1",
                           "InvocationName":  "",
                           "PipelineLength":  0,
                           "PipelinePosition":  0,
                           "ExpectingInput":  false,
                           "CommandOrigin":  1,
                           "DisplayScriptPosition":  null
                       },
    "ScriptStackTrace":  "at ConfigureAgent, C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin\\AgentConfigurationManager.ps1: line 91\r\nat Register-Agent, C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin\\enable.ps1: line 137\r\nat ConfigureAgentIfRequired, C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin\\enable.ps1: line 425\r\nat Enable, C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin\\enable.ps1: line 464\r\nat \u003cScriptBlock\u003e, C:\\Packages\\Plugins\\Microsoft.VisualStudio.Services.TeamServicesAgent\\1.27.0.1\\bin\\enable.ps1: line 481\r\nat \u003cScriptBlock\u003e, \u003cNo file\u003e: line 1",
    "PipelineIterationInfo":  [

                              ]
}
[2020-07-31T07:12:20] Settings handler status to 'error' (C:\Packages\Plugins\Microsoft.VisualStudio.Services.TeamServicesAgent\1.27.0.1\Status\0.status)

Hello, any news/update on this issue? We have the same issue and googling it pointed to this page. Same issue that trying to install the DevOps Agent on a new VM crashes randomly (about 2 out of 10 times). Using the latest (v2.182.1) version of the Agent software.

Hi @elangelo @melchiorAAB do you run agent configuration in parallel for several agents on the same machine?
Agent is trying to lock Service Database for SCManager, so it could probably be related to this.

Hi @anatolybolshakov thanks for the reply. I am running 1 Agent per VM so nothing in parallel.

@melchiorAAB could you please share your script to take a look? I can't reproduce it by running it manually

Hi @melchiorAAB do you have any updates?

Hi @melchiorAAB I'm closing it at the moment since it's still not reproducible for us and some more info required for further investigation - please let us know if it's still actual for you, and if you are able to provide it.

@melchiorbc Were you ever able to resolve this?  We are instantiating VMs using an Azure Scale Set, and following the guide from MS to setup Azure DevOps agents on it.  We also see this type of error regularly - it prevents us from using our own scale set to run agents.

I am using the actions-runner version 2.316.1 but still getting the error saying "Failed to Lock Service Database for Write" while trying to register an Azure VM as github runner. Please suggest how do we fix it? I am trying to register VM as github runner through "az vm run-command" and using config.cmd.

authors: anatolybolshakov elangelo lonevvolf melchiorAAB pb185235

repo: microsoft/azure-pipelines-agent


text:
Configurable masking token, perf improvements, refactoring.

This change:

Does some additional refactoring of the secret masking code (in support of a future move to consume the updated masker from a separate library). Mostly this changed entailed having LoggedSecretMasker derive from SecretMasker rather than wrapping an instance of this class.
Added a configurable preferred redaction token to the ReplacementPosition class (now simple renamed to Replacement).  For secret values, we retain the existing default redaction string ***. For regexes that have no explicit rule information (an id and friendly name, together which comprise a moniker), we use the string +++. This change will allow users to easily search for logs looking for evidence of automatically redacted secrets. These secrets either should have been protected as secured variables OR there is an upstream leak of the secret in a script/dependency, etc.
For patterns that explicitly declare a rule moniker, the redaction token consists of the opaque id, friendly name and hash of the redacted secret. This data will be persisted to telemetry to allow secure correlation of redacted secrets with evidence of exposure in other locations.
I have added some preliminary telemetry in a naive way. Looking for feedback/refinements of this.
Renamed some items to communicate that they originate with the 1ES scan project, not CredScan.
Expanded unit testing. The updated secret masker namespace now has >90% code coverage.

public ISecretMasker Clone()

I can't find the use of secret masker clones in the code, does this utilization exist? One difference now between the legacy masker and the current is that the legacy masker doesn't retain elapsed masking time on clone. Is that an issue?

Refers to: src/Agent.Sdk/SecretMasking/LegacyLoggedSecretMasker.cs:134 in a95cc17. [](commit_id = a95cc17bd0854a2b5eba17e48b6a180932a5c557, deletion_comment = False)

@merlynomsft


text:
Portable PDB support?

Does the Index Sources & Publish Symbols task publishing to Azure Artifacts/DevOps support portable PDBs?
Recent answers from @fadnavistanmay here and @mitchdenny here seem to indicate yes. But I've seen people continue to report issues.

The way to do this is to disable indexing of the symbols in the task, and instead use source link to do the indexing of sources during the build itself. Then the task just uploads the PDBs as they are. The task will produce a warning.
That is how I've made it work in the past ... YMMV.

Thanks @mitchdenny! So to confirm, that task should work for publishing full or portable PDBs to the Azure Artifacts symbol server?

Correct. The task does two things. It indexes symbols, and publishes symbols. If it can't index the symbols (because it doesn't understand portable PDBs) it can still upload them.

My concern over whether portable PDBs are supported comes from the github doc here, which indicates Microsoft symbol server does not support portable PDBs, which I assumed included the Azure DevOps symbol server, as well as SymStore...but I couldn't find definitive answers on whether that is true or not.

Do these instructions work for you?
https://docs.microsoft.com/en-us/azure/devops/artifacts/symbols/setting-up-github-sourcelinking?view=azure-devops
(note that it uses the designer based task interface, but there is a equivalent for YAML).

For the purposes of that article the instructions look fine. But, I'm not using GitHub in any way. In general, any up-to-date info is great though so I appreciate the effort.
Regarding my original question, I believe you provided an answer. The answer was yes, the Azure DevOps integrated symbol server supports portable PDBs. If you also happen to know whether SymStore supports portable PDBs, or maybe the article here just has out-of-date information, that would be helpful to know too. Otherwise, feel free to close this out. Thanks!

Thanks Mitch for the insights. Sean, I am closing this issue, as Mitch has provided instructions to publish portable PDBs. I am not sure of whether SymStore support them or not.

authors: Sean-Driscoll fadnavistanmay mitchdenny

repo: microsoft/azure-pipelines-tasks


text:
Make nuget push command work w/ AzureArtifacts InternalFeed

Current Azure Devops Artifacts is expecting apiKey 'AzureDevOps' for internal feed nuget push, instead of 'VSTS'
https://github.com/Microsoft/azure-pipelines-tasks/blob/master/Tasks/DotNetCoreCLIV2/pushcommand.ts#L92-L109

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: evertonmc sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

This PR is stale because it has been open for a year with no activity. Remove the stale label or comment on the PR otherwise this will be closed in 5 days

authors: evertonmc leantk msftclas


text:
Unresolvable Configurations in IntelliJ

Environment

Spring boot starter:

key vault spring boot starter

OS Type: MacOS

Java version:

11

Summary

I've tested this guide to integrate the azure key vault in a spring boot application: https://docs.microsoft.com/en-gb/java/azure/spring-framework/configure-spring-boot-starter-java-app-with-azure-key-vault?view=azure-java-stable#sign-into-azure
Everything works as espected. Only IntelliJ is showing me the following message in the application.yaml:

Also the IntelliSense is not working for the key azure.keyvault. But I'm getting other stuff like this:

Reproduce steps

This is my pom.xml:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

    <modelVersion>4.0.0</modelVersion>

    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.1.6.RELEASE</version>
        <relativePath/> <!-- lookup parent from repository -->
    </parent>

    <groupId>de.fr.azure</groupId>
    <artifactId>keyvault</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <name>keyvault</name>
    <description>Demo project for Spring Boot</description>

    <properties>
        <java.version>11</java.version>
        <azure.version>2.1.6</azure.version>
    </properties>

    <dependencies>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter</artifactId>
        </dependency>
        <dependency>
            <groupId>com.microsoft.azure</groupId>
            <artifactId>azure-keyvault-secrets-spring-boot-starter</artifactId>
        </dependency>
    </dependencies>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>com.microsoft.azure</groupId>
                <artifactId>azure-spring-boot-bom</artifactId>
                <version>${azure.version}</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
        </plugins>
    </build>

</project>

Expected Results

I would expect, that IntelliSense and also the resolving of the configuration works like for spring boot or other stuff.

Thanks for reporting this, we'll look into it.

authors: florianrusch saragluna

repo: microsoft/azure-spring-boot


text:
Key vault property source support actuator and cache key vault vaules

Just a demo PR related to #896, #905

What is the purpose of this PR? We have a performance PR outstanding. Is this going to replace it?

@mnriem

What is the purpose of this PR? We have a performance PR outstanding. Is this going to replace it?

Please check the email. 🙏

authors: chenrujun mnriem


text:
Add a Kusto support for Log Analytics and Azure Resource Graph queries

It would be very useful if you could extend Kusto support to Log Analytics and Azure Resource Graph queries.

Great news!
Azure Data Studio Insiders v1.32.0 (download) now supports Azure Monitor Logs extension preview. We expect this to be part of Azure Data Studio 1.32.0 August Release stable.
In Azure Data Studio Insiders / stable v1.32.0,

search for "Azure Monitor Logs" extension.
install the extension.
In the Connections viewlet,

create a new connection with 'Azure Monitor Logs' connection type.
provide the Log Analytics workspace ID that you'd like to connect to.
connect using AAD.
(ignore the Database field)
click Connect

Start writing KQL queries, such as

AzureDiagnostics
| take 10

Users can also create a new notebook connecting to "Log Analytics" kernel.
Note: it is possible to access the AppInsights data by traversing to the Log Analytics workspace.
Hope this helps.
Note: We don't have plan for Azure Resource Graph yet.

Given the above I'm going to close this - if you still are looking to have support for Azure Resource Graph please open another issue for that specifically. Thanks!

authors: Charles-Gagnon MsSQLGirl alexandair

repo: microsoft/azuredatastudio


text:
[CSS Supportability] Provide a way to associate debug logs to a specific activity

When we enable debug logs we have information logged about the activity in the sql tools service, parent binary, extension host, etc. Now SQL Tools Service will interact with the database engines.
We need a way to identify the activity starting from the frontend UI to SQL Tools Service to the database engine. This will allow us to track the flow of requests to the various layers and then identify the problems and issues as they arise. In SQL Server Extended Events we have the concept of activity ID to see end to end tracing of a specific query. We can use something similar to that concept here.

Closing older issues.  Please let us know if you're still impacted by this issue.

authors: kburtram suresh-kandoth


text:
2 Instances of Dashboard Opened After Selecting Manage Option from Connections

(RC1 build, Windows x64)
Right click on a server in Servers view, choose Manage.
Expected: 1 instance of server dashboard are opened
Actual: 2 instances are opened

Hi @chlafreniere I am not able to repro this on the latest insiders build, can you give it a try?

Closing as no activity

authors: chlafreniere cssuh


text:
Advanced Connection Properties not localized

The majority of the UI is now localized but it appears the grouping titles are still not localized.  @smartguest could you take a look why the section titles aren't being localized?

Always Encrypted is the same in other languages, but the headers I will need to investigate.

@kburtram These are the group names in connectionOptions for extensions that have them, these can be localized, but I'm not sure what the side effects of doing so are.

authors: Charles-Gagnon kburtram smartguest


text:
Right clicking on Triggers doesn't allow Script To

Issue Type: Bug
Open a database and table with a trigger.
Double clicking does nothing.
Right clicking doesn't bring up the menu like all other types of things like Views, functions etc.
It should bring up the ability to script to with the same options as Views and functions.
Azure Data Studio version: azuredatastudio 1.12.2 (c9bef82ace6c67190d0e83820011a2bbd1f793c1, 2019-10-11T04:56:40.634Z)
OS version: Windows_NT x64 10.0.18363

Closing as duplicate of https://github.com/microsoft/azuredatastudio/issues/2093.  I'll use that issue to track since it has more upvotes.  Thanks!


text:
Azure Devops

Issue Type: Feature Request
There should be an option to use Azure DEVOPS for source control!
Azure Data Studio version: azuredatastudio 1.10.0 (5fdb967ffcea41df0335ec17cfa396a694bb174e, 2019-08-14T18:28:10.311Z)
OS version: Windows_NT x64 10.0.16299

Closing as duplicate of https://github.com/microsoft/azuredatastudio/issues/16001.  Thanks for opening this suggestion!

authors: ehutton kburtram


text:
Update sqltoolservice binaries for kusto extension

This PR fixes #
Updates it to release version 3.0.0-release.34

Pull Request Test Coverage Report for Build 271368279

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 38.088%

Totals

Change from base Build 271221050:
0.01%

Covered Lines:
19150

Relevant Lines:
45874

💛  - Coveralls


text:
Initialize releases when creating remoteBookController

Initialize releases when creating remote book controller to prevent undefined error.

Pull Request Test Coverage Report for Build 514115617

1 of 7 (14.29%)  changed or added relevant lines in 1 file are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.01%) to 43.214%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/notebook/src/dialog/remoteBookDialog.ts
1
7
14.29%

Files with Coverage Reduction
New Missed Lines
%

extensions/import/src/wizard/pages/fileConfigPage.ts
1
73.46%

extensions/notebook/src/dialog/remoteBookDialog.ts
3
43.15%

extensions/notebook/src/common/ports.ts
4
74.14%

Totals

Change from base Build 513851252:
-0.01%

Covered Lines:
24573

Relevant Lines:
52053

💛  - Coveralls

Pull Request Test Coverage Report for Build 514115617

1 of 7 (14.29%)  changed or added relevant lines in 1 file are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.01%) to 43.214%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/notebook/src/dialog/remoteBookDialog.ts
1
7
14.29%

Files with Coverage Reduction
New Missed Lines
%

extensions/import/src/wizard/pages/fileConfigPage.ts
1
73.46%

extensions/notebook/src/dialog/remoteBookDialog.ts
3
43.15%

extensions/notebook/src/common/ports.ts
4
74.14%

Totals

Change from base Build 513851252:
-0.01%

Covered Lines:
24573

Relevant Lines:
52053

💛  - Coveralls

How is this being undefined? I'm guessing when url is undefined? You should update the typings appropriately for the various properties/return types to be IRelease[] | undefined if undefined is a valid expected value.
But in general I would say it probably makes more sense to just default the model to having an empty array instead. Doing that should fix this I think from what I see in the code since the HTTP request properly defaults to an empty array and then populates it with the result. Unless you care about knowing when you've fetched releases and there weren't any vs we haven't actually fetched anything (undefined)

@Charles-Gagnon , you are right. I initialized the model correctly and we are not throwing an error anymore.

How is this being undefined? I'm guessing when url is undefined? You should update the typings appropriately for the various properties/return types to be IRelease[] | undefined if undefined is a valid expected value.
But in general I would say it probably makes more sense to just default the model to having an empty array instead. Doing that should fix this I think from what I see in the code since the HTTP request properly defaults to an empty array and then populates it with the result. Unless you care about knowing when you've fetched releases and there weren't any vs we haven't actually fetched anything (undefined)

@Charles-Gagnon , you are right. I initialized the model correctly and we are not throwing an error anymore.

authors: barbaravaldez coveralls


text:
fix for Portuguese

In the older langpacks, the language id for Portuguese was lowercase, while the folder was capitalized. This PR restores that and the resulting vsix package is properly capitalized, matching the extension gallery entry.
This PR fixes #15639

Pull Request Test Coverage Report for Build 923297226

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.369%

Totals

Change from base Build 922835645:
0.0%

Covered Lines:
26602

Relevant Lines:
55738

💛  - Coveralls

authors: coveralls smartguest


text:
[SQL-bindings] remove watcher for files

This PR removes the need to watch for the completion of the createFunction file due to upgrades with vscode-azurefunctions as well as past changes.
The main thing I will work on is that we get proper error handling from vscode-azurefunctions createFunction API call when a user cancels out of the quickpick options.

Pull Request Test Coverage Report for Build 2799720085

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 42.101%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-bindings/src/services/azureFunctionsService.ts
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-bindings/src/services/azureFunctionsService.ts
1
80.63%

extensions/notebook/src/common/ports.ts
4
74.14%

Totals

Change from base Build 2798489213:
-0.01%

Covered Lines:
28158

Relevant Lines:
62510

💛  - Coveralls

authors: VasuBhog coveralls


text:
Use Preferred username over email as 'user' property

Fixes #22271

Pull Request Test Coverage Report for Build 4380012044

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.002%) to 41.951%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/azurecore/src/account-provider/auths/azureAuth.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
1
80.65%

Totals

Change from base Build 4379971011:
0.002%

Covered Lines:
28807

Relevant Lines:
63751

💛  - Coveralls

authors: cheenamalhotra coveralls


text:
Use DomParser for xml parsing

Fixes #25004 and potentially other issues related to XML data formatting, where rows are not being rendered..
Xml2js is failing to parse cell data like below, due to likely a parsing bug, failing as root node error:
'
What the heck?

'

Parsing Error:
[error] Text data outside of root node.
Line: 0
Column: 33
Char: &: Error: Text data outside of root node.
Line: 0
Column: 33
Char: &
    at error (C:\Users\cmalhotra\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\node_modules.asar\sax\lib\sax.js:651:10) [<root>]
    at strictFail (C:\Users\cmalhotra\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\node_modules.asar\sax\lib\sax.js:677:7) [<root>]
    at SAXParser.write (C:\Users\cmalhotra\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\node_modules.asar\sax\lib\sax.js:1035:15) [<root>]
    at exports.Parser.Parser.parseString (C:\Users\cmalhotra\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\node_modules.asar\xml2js\lib\parser.js:337:31) [<root>]
    at Parser.parseString (C:\Users\cmalhotra\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\node_modules.asar\xml2js\lib\parser.js:5:59) [<root>]
    at exports.parseString (C:\Users\cmalhotra\AppData\Local\Programs\Azure Data Studio - Insiders\resources\app\node_modules.asar\xml2js\lib\parser.js:383:19) [<root>]

Below XML works instead, which is pointing to a parsing bug in Xml2js when encountering an empty element:

What the heck?

hello ?

world !

This PR changes the library to use DomParsr instead, to parse XML based on XML doc elements, which should be the most accurate XML parser for JS.

Pull Request Test Coverage Report for Build 6951032805

0 of 12 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.569%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/query/browser/gridPanel.ts
0
12
0.0%

Totals

Change from base Build 6949852489:
0.0%

Covered Lines:
30792

Relevant Lines:
69375

💛  - Coveralls

And it'd be good to check if the parsing issue exists in the repo - and if not file one yourself.
https://github.com/Leonidas-from-XIV/node-xml2js

authors: Charles-Gagnon cheenamalhotra coveralls


text:
MultiLanguageRecognizer‘s languagePolicy should follow the LG UseLanguagePolicy convention

We are enabling the MultiLanguage feature of Composer, and we want LU and LG follow the same LanguagePolicy Rule. But we found that MultipleLanguageRecognizer does not take the LanguagePolicy in DialogManager which is used by LG. (DialogManager.UseLanguagePolicy(New LanguagePolicy(defaultLanguage)))
Expected behavior:
Set the defaultLanguage in the appsettings.
DialogManager.UseLangugaePolicy(New LanguagePolicy(defaultLanguage))
LU and LG should both follow the the fall back rule.

Hello, I think I'm hitting this.
Is there a workaround while waiting for the fix?

repo: microsoft/botbuilder-dotnet


text:
Fix typedoc vulnerability

Description

The lerna-build process found two vulnerabilities related to the typedoc package. Those vulnerabilities were fixed.
In addition, references to the old botbuilder-core-extensions package were deleted.
Before

After

Specific Changes

typedoc@^0.14.2 ==> typedoc@^0.15.0
typedoc-plugin-markdown@^2.0.6 ==> typedoc-plugin-markdown@^2.2.10
botbuilder-core-extensions docs deleted from botbuilder-core, botbuilder-testing, and botbuilder packages.

Testing

Running npm run build-docs after changes

Pull Request Test Coverage Report for Build 82392

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.229%

Totals

Change from base Build 82305:
0.0%

Covered Lines:
4633

Relevant Lines:
5111

💛  - Coveralls

authors: coveralls enzocanoo

repo: microsoft/botbuilder-js


text:
Fix: Version mismatch between private and public repo in spec generator

The private and public repo have a different version of teh generator(Private had a newer one) which generate slightly different spec.html.
I feel like there is some things we should probably ignore from the git procelain in the private repo as it can just fail due to version mismatch in the private/public repo

I feel like there is some things we should probably ignore from the git procelain in the private repo as it can just fail due to version mismatch in the private/public repo

We could do that or maybe update dependencies script that syncs public to private instead of a race where a version publishes between subsequent rush update --full?

Also, maybe we can stop checking in spec.html and have CI publish it somewhere we can actually serve it from. It's not that useful as a file in the repo.

Yeah we could do that. Have it pushed to another repo or branch that show up at microsoft.github.io/cadl
I am not sure we can sync the dependencies between the 2 rush project. I know rush has an issue to be able to depend on another project but other that than we cant control the lock file.
The solution to this might be to switch to npm workspaces

authors: nguerrera timotheeguerin

repo: microsoft/cadl


text:
Custom Plugins not working

After enabling plugins (tried with Klarna Shopping and my working custom plugin), and typing in the chat, chat will show this error

Unable to generate bot response. Details: Error: 500: Microsoft.SemanticKernel.Diagnostics.SKException: AcquireExternalInformationAsync failed. ---> System.Collections.Generic.KeyNotFoundException: The given key 'stepsTaken' was not present in the dictionary. at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at CopilotChat.WebApi.Plugins.Chat.ExternalInformationPlugin.RunStepwisePlannerAsync(String goal, SKContext context, CancellationToken cancellationToken) in D:\LLM Research\copilot_updated_latest\chat-copilot\webapi\Plugins\Chat\ExternalInformationPlugin.cs:line 229 at CopilotChat.WebApi.Plugins.Chat.ExternalInformationPlugin.InvokePlannerAsync(String userIntent, SKContext context, CancellationToken cancellationToken) in D:\LLM Research\copilot_updated_latest\chat-copilot\webapi\Plugins\Chat\ExternalInformationPlugin.cs:line 105 at CopilotChat.WebApi.Plugins.Chat.ChatPlugin.AcquireExternalInformationAsync(SKContext context, String userIntent, Int32 token...

Reproduce
Steps to reproduce the behavior:

Go to Plugins
Enable Klarna Shopping and your local plugin
Type message I'm looking for shoes, size 10 or question relevant to your plugin
See error the above error

Tried with different sets of behaviour

Action Planner
Stepwise - ( Above error is taken when executing stepwise planner)
Sequential

Observed same error with all planners
Platform

OS: Windows
IDE: VS Code
Language: C#,Custom plugin (Created with Python)
Source: Latest code as of this issue creation date.

Additional context

Running locally, with ./start.ps1

hi @kuppan4109 we are taking a look into this.  Thanks for bringing it up.

@kuppan4109 Do you have the very latest version of the code.  A fix related to a similar issue went in yesterday. This might already be fixed!
If you have the latest code, let us know and we'll see what's going on.

@glahaye, Have pulled the latest code from repository and tried executing but facing the same issues.

@kuppan4109 Do you have the very latest version of the code. A fix related to a similar issue went in yesterday. This might already be fixed!
If you have the latest code, let us know and we'll see what's going on.

@glahaye , any updates on this?

@glahaye, Have pulled the latest code from repository and tried executing but facing the same issues.

@kuppan4109 Do you have the very latest version of the code. A fix related to a similar issue went in yesterday. This might already be fixed!
If you have the latest code, let us know and we'll see what's going on.

I tried to test it using the OpenAI FastAPI sample plugin (running as an API server), which works. However, when enabled I get the following error:
docker-chat-copilot-webapi-1  | fail: Microsoft.SemanticKernel.Kernel[0]
docker-chat-copilot-webapi-1  |       Plugin SequentialPlanner_Excluded function funcba45b9f92f21439d8192e6337f66522c call fail during pipeline step 0 with error The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.
docker-chat-copilot-webapi-1  |       Status: 404 (Not Found)
docker-chat-copilot-webapi-1  |       ErrorCode: DeploymentNotFound
docker-chat-copilot-webapi-1  |
docker-chat-copilot-webapi-1  |       Content:
docker-chat-copilot-webapi-1  |       {"error":{"code":"DeploymentNotFound", "message":"The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again."}}
And: docker-chat-copilot-webapi-1  |       Semantic function SequentialPlanner_Excluded.func37fece6a35d3407e96cd04ed2e0de16e execution failed with error The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.

Running CC in WSL/Docker and the FastAPI plugin. I do not get this error when the plugin is disabled.

This is a completely different error @kuppan4109 reported.

rvermeire

You are right. I forgot to change the model to my custom deployment name in appsettings.json.

We are taking the SK RC1 package early next week which contains all sort of fixes and enhancements for plugins.  This should address the (previously resported) issue with WebSearcher plugin and we will re-assess/validate the state of the plugin and planner ecosystem within chat-copilot at this time.

any update on this?

I'm getting the same problem.

authors: Azzeo crickman glahaye kuppan4109 madushann momuno rvermeire samleegithub

repo: microsoft/chat-copilot


text:
[Fluent2 colors] Merge main

Platforms Impacted

[x] iOS
[ ] macOS

Description of changes
Quick merge to make my upcoming rebase easier :)
Verification
It builds!
Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[ ] iOS supported versions (all major versions greater than or equal current target deployment version)
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] iPad Pointer interaction
[ ] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow

Nit: could you list the two changes that you've merged in your description?

authors: edjamesmsft mischreiber

repo: microsoft/fluentui-apple


text:
Tokenize SearchBar

Platforms Impacted

[x] iOS
[ ] macOS

Description of changes
This PR tokenizes SearchBar. SearchBar and SearchBarTokenSet files are moved in a separate folder within the Navigation folder.
Binary change
Total increase: 126,320 bytes
Total decrease: -22,600 bytes

File
Before
After
Delta

Total
30,120,824 bytes
30,224,544 bytes
🛑 103,720 bytes

 Full breakdown

File
Before
After
Delta

SearchBarTokenSet.o
0 bytes
95,248 bytes
🛑 95,248 bytes

__.SYMDEF
4,717,736 bytes
4,731,608 bytes
⚠ 13,872 bytes

BadgeView.o
423,896 bytes
434,056 bytes
⚠ 10,160 bytes

ShimmerLinesView.o
242,344 bytes
247,144 bytes
⚠ 4,800 bytes

ActionsCell.o
200,224 bytes
201,880 bytes
⚠ 1,656 bytes

BadgeLabelButton.o
145,152 bytes
145,448 bytes
⚠ 296 bytes

TextFieldTokenSet.o
95,536 bytes
95,736 bytes
⚠ 200 bytes

ShyHeaderController.o
252,984 bytes
253,040 bytes
⚠ 56 bytes

NavigationController.o
163,560 bytes
163,592 bytes
⚠ 32 bytes

FocusRingView.o
799,488 bytes
799,256 bytes
🎉 -232 bytes

SearchBar.o
444,544 bytes
422,176 bytes
🎉 -22,368 bytes

Verification

Visual Verification

Before
After

N/A

N/A

Pull request checklist
This PR has considered:

[x] Light and Dark appearances
[ ] iOS supported versions (all major versions greater than or equal current target deployment version)
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] iPad Pointer interaction
[ ] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow

Please NavigationDemoController with branding style and regular style largetitleview (rotation and stuff) make sure when we override navigationbar colors it correctly adjust to search bar

I tested the search bar still works as expected on the nav bar and will add screenshots momentarily. I can't override nav bar colors though since it hasn't been tokenized yet.

authors: harrieshin laminesm


text:
Question: Data grid row as a clickable link

I want rows in a data grid to act like a clickable link. I see an OnRowFocus event but no equivalent for clicking on a row.
I'm guessing I can give rows a class and use CSS over to simulate the appearance of a link (e.g. highlight the row, change the cursor) and use a JavaScript event for the click event and interop back into Blazor.
Before I start, I was wondering if there is a simpler known pattern for this.

The underlying fluent-data-grid only raises the row-focused event. This is what we pick up on the Blazor side and where you can add an EventCallback to in OnRowFocus
Guess that means there is no simpler pattern for what you want to do.

authors: JamesNK vnbaaij

repo: microsoft/fluentui-blazor


text:
[Package versions] Refactoring

[Package versions] Refactoring

Set package versions to stable versions. Except for Microsoft.CodeAnalysis.Analyzers where the latest stable version is 3 years old.
Consider all Warnings like Errors, during the build process: -warnaserror
Update C# code to respect the Analyzer (missing Async).

The latest coverlet and Markdig are not available in dotnet-public feed.

Why do we need to use this feed and not NuGet.org?

Requirements of the 1ES templates/security initiative.

Ok. I will update that.

authors: dvoituron vnbaaij


text:
[MS-900] 챌린지 완료 인증

깃헙 ID: hdddhdd
Microsoft Learn 프로필 링크: https://learn.microsoft.com/ko-kr/users/heejungchoi-9463/
클라우드 스킬 챌린지 토픽/코드: Microsoft 365 기초 (MS-900)

/ok

repo: microsoft/hackers-ground