text:
[.NET MAUI 9.0 Preview 6, SkiaSharp 3.0-preview4.1] On Windows/WinUI 3 SkiaSharp's SKGLView crashes a .NET MAUI app when it is built in the unpackaged mode

Describe the bug
Technology stack

.NET 9.0 Preview 6
.NET MAUI 9.0 Preview 6
SkiaSharp 3.0-preview4.1
Windows / WinUI 3 1.5.x

Bug
SKGLView crashes the app at runtime when .NET MAUI App is built in the unpackaged mode (-p:WindowsPackageType=None).
Steps to reproduce the bug

Clone the public reproduction repository (link) and open the solution in Visual Studio 2022 Preview (latest).
First, let's check that things work in the packaged mode.
Select Windows Machine and click the green Debug button.
The app should start.
Click the Click Me button. A new page with some text should open. The app will not crash.
Close the app and go back to Visual Studio 2022 Preview.
Open the Developer PowerShell and check that you are in the solution folder.
Delete bin and obj folders. (Otherwise the unpackaged app will not start.)
Build the unpackaged app with dotnet build -f:net9.0-windows10.0.19041.0 -c:Debug -p:WindowsPackageType=None -p:RuntimeIdentifierOverride=win10-x64 -p:WindowsAppSDKSelfContained=true
Open File Explorer and go to bin\Debug\net9.0-windows10.0.19041.0\win10-x64. The unpackaged app should be there.
Click on WindowsMauiUnpackagedSKGLViewError.exe.
The app will start.
Click on the Click me button.
The app will crash.
Now, open Event Viewer and see the Windows Logs → Application error messages.

Expected behavior
App would not crash.
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context
Relevant log output
Log Name:      Application
Source:        .NET Runtime
Date:          20.7.2024 21.57.32
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Application: WindowsMauiUnpackagedSKGLViewError.exe
CoreCLR Version: 9.0.24.32707
.NET Version: 9.0.0-preview.6.24327.7
Description: The process was terminated due to an unhandled exception.
Stack:
   at SkiaSharp.Views.GlesInterop.Egl.eglGetPlatformDisplayEXT(UInt32, IntPtr, Int32[])
   at SkiaSharp.Views.GlesInterop.Egl.eglGetPlatformDisplayEXT(UInt32, IntPtr, Int32[])
   at SkiaSharp.Views.GlesInterop.GlesContext.InitializeDisplay()
   at SkiaSharp.Views.GlesInterop.GlesContext..ctor()
   at SkiaSharp.Views.Windows.AngleSwapChainPanel.OnLoaded(System.Object, Microsoft.UI.Xaml.RoutedEventArgs)
   at WinRT._EventSource_global__Microsoft_UI_Xaml_RoutedEventHandler+EventState.<GetEventInvoke>b__1_0(System.Object, Microsoft.UI.Xaml.RoutedEventArgs)
   at ABI.Microsoft.UI.Xaml.RoutedEventHandler.Do_Abi_Invoke(IntPtr, IntPtr, IntPtr)
   at ABI.Microsoft.UI.Xaml.IApplicationStaticsMethods.Start(WinRT.IObjectReference, Microsoft.UI.Xaml.ApplicationInitializationCallback)
   at Microsoft.UI.Xaml.Application.Start(Microsoft.UI.Xaml.ApplicationInitializationCallback)
   at WindowsMauiUnpackagedSKGLViewError.WinUI.Program.Main(System.String[])

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-07-20T18:57:32.8237381Z" />
    <EventRecordID>82274</EventRecordID>
    <Correlation />
    <Execution ProcessID="2176" ThreadID="0" />
    <Channel>Application</Channel>
  </System>
  <EventData>
    <Data>Application: WindowsMauiUnpackagedSKGLViewError.exe
CoreCLR Version: 9.0.24.32707
.NET Version: 9.0.0-preview.6.24327.7
Description: The process was terminated due to an unhandled exception.
Stack:
   at SkiaSharp.Views.GlesInterop.Egl.eglGetPlatformDisplayEXT(UInt32, IntPtr, Int32[])
   at SkiaSharp.Views.GlesInterop.Egl.eglGetPlatformDisplayEXT(UInt32, IntPtr, Int32[])
   at SkiaSharp.Views.GlesInterop.GlesContext.InitializeDisplay()
   at SkiaSharp.Views.GlesInterop.GlesContext..ctor()
   at SkiaSharp.Views.Windows.AngleSwapChainPanel.OnLoaded(System.Object, Microsoft.UI.Xaml.RoutedEventArgs)
   at WinRT._EventSource_global__Microsoft_UI_Xaml_RoutedEventHandler+EventState.<GetEventInvoke>b__1_0(System.Object, Microsoft.UI.Xaml.RoutedEventArgs)
   at ABI.Microsoft.UI.Xaml.RoutedEventHandler.Do_Abi_Invoke(IntPtr, IntPtr, IntPtr)
   at ABI.Microsoft.UI.Xaml.IApplicationStaticsMethods.Start(WinRT.IObjectReference, Microsoft.UI.Xaml.ApplicationInitializationCallback)
   at Microsoft.UI.Xaml.Application.Start(Microsoft.UI.Xaml.ApplicationInitializationCallback)
   at WindowsMauiUnpackagedSKGLViewError.WinUI.Program.Main(System.String[])
</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          20.7.2024 21.57.33
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:
Description:
Faulting application name: WindowsMauiUnpackagedSKGLViewError.exe, version: 1.0.0.0, time stamp: 0x667d0000
Faulting module name: coreclr.dll, version: 9.0.24.32707, time stamp: 0x667de227
Exception code: 0xc0000005
Fault offset: 0x00000000002de54e
Faulting process ID: 0x0x880
Faulting application start time: 0x0x1DADAD6AC829340
Faulting application path: C:\hmp\WindowsMauiUnpackagedSKGLViewError\WindowsMauiUnpackagedSKGLViewError\WindowsMauiUnpackagedSKGLViewError\bin\Debug\net9.0-windows10.0.19041.0\win10-x64\WindowsMauiUnpackagedSKGLViewError.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\9.0.0-preview.6.24327.7\coreclr.dll
Report ID: 3e1585be-c9dd-41c0-aa20-9933b81efeae
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-07-20T18:57:33.1772821Z" />
    <EventRecordID>82275</EventRecordID>
    <Correlation />
    <Execution ProcessID="52744" ThreadID="31284" />
    <Channel>Application</Channel>
  </System>
  <EventData>
    <Data Name="AppName">WindowsMauiUnpackagedSKGLViewError.exe</Data>
    <Data Name="AppVersion">1.0.0.0</Data>
    <Data Name="AppTimeStamp">667d0000</Data>
    <Data Name="ModuleName">coreclr.dll</Data>
    <Data Name="ModuleVersion">9.0.24.32707</Data>
    <Data Name="ModuleTimeStamp">667de227</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">00000000002de54e</Data>
    <Data Name="ProcessId">0x880</Data>
    <Data Name="ProcessCreationTime">0x1dadad6ac829340</Data>
    <Data Name="AppPath">C:\hmp\WindowsMauiUnpackagedSKGLViewError\WindowsMauiUnpackagedSKGLViewError\WindowsMauiUnpackagedSKGLViewError\bin\Debug\net9.0-windows10.0.19041.0\win10-x64\WindowsMauiUnpackagedSKGLViewError.exe</Data>
    <Data Name="ModulePath">C:\Program Files\dotnet\shared\Microsoft.NETCore.App\9.0.0-preview.6.24327.7\coreclr.dll</Data>
    <Data Name="IntegratorReportId">3e1585be-c9dd-41c0-aa20-9933b81efeae</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

I know these three questions are obvious, however, I have found no reference to this in the report.

Did you verify that no extra package dependencies were added to the AppxManifest.xml file? The build process takes the project's Package.appxmanifest file and fills in any extra details. Visual Studio checks any NuGet references and add dependencies as needed.
Did you check for any extra activation information being added to the package? In these cases, did you check if they were activatable in an unpackaged application?
An example of this is actually the C++ projection. C++/WinRT tries very hard to activate a type, even to the point of falling back to looking for namespace named libraries in the application directory and querying them directly. To give an example from Win2D, this registers itself in the AppxManifest.xml file:

//Two methods to attempt to obtain the activation factory for Microsoft.Graphics.Canvas.Effects.BlendEffect
winrt::Windows::Foundation::IAsyncAction MainWindow::Click_Click(winrt::IInspectable const &, winrt::RoutedEventArgs const &)
{
    //The runtime class to obtain the activation factory for.
    constexpr const wchar_t runtime_class_string[] = L"Microsoft.Graphics.Canvas.Effects.BlendEffect";
    //Attempt to obtain this via the ABI.
    //This FAILS in an unpackaged desktop application.
    HSTRING rs{};
    HRESULT hr = WindowsCreateString(runtime_class_string, ARRAYSIZE(runtime_class_string)-1, &rs);
    com_ptr<::IActivationFactory> af;
    hr = RoGetActivationFactory(rs, IID_PPV_ARGS(af.put()));
    WindowsDeleteString(rs);
    rs = nullptr;
    //Attempt to obtain this via C++/WinRT
    //This SUCCEEDS in an unpackaged desktop application.
    auto af_wrt = winrt::get_activation_factory(runtime_class_string);

    co_return;
}

This is using C++, but using the ABI is easier here. The big point is are you sure that the WinRT objects that are not part of the Windows App Runtime activate properly. If they are registered in the package and they don't, you may need to add the registrations to the application manifest file using registration free WinRT.
3. Did you verify that the directory layout for the unpackaged application was the same as the packaged application? This could be relying on libraries being in the correct location, but the build process only moves things into the correct location as part of the packaging process.
I know these are pretty generic questions and observations. But these should be general things to check.

Did you verify that no extra package dependencies were added to the AppxManifest.xml file? The build process takes the project's Package.appxmanifest file and fills in any extra details. Visual Studio checks any NuGet references and add dependencies as needed.

The unpackaged version doesn't have AppxManifest.xml file.

Did you verify that the directory layout for the unpackaged application was the same as the packaged application? This could be relying on libraries being in the correct location, but the build process only moves things into the correct location as part of the packaging process.

No, they are quite different.
Packaged App
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----          5.8.2024     15.55                ar
d-----          5.8.2024     15.55                ca
d-----          5.8.2024     15.55                cs
d-----          5.8.2024     15.55                da
d-----          5.8.2024     15.55                de
d-----          5.8.2024     15.55                el
d-----          5.8.2024     15.55                es
d-----          5.8.2024     15.55                fi
d-----          5.8.2024     15.55                fr
d-----          5.8.2024     15.55                he
d-----          5.8.2024     15.55                hi
d-----          5.8.2024     15.55                hr
d-----          5.8.2024     15.55                hu
d-----          5.8.2024     15.55                id
d-----          5.8.2024     15.55                it
d-----          5.8.2024     15.55                ja
d-----          5.8.2024     15.55                ko
d-----          5.8.2024     15.55                ms
d-----          5.8.2024     15.55                nb
d-----          5.8.2024     15.55                nl
d-----          5.8.2024     15.55                pl
d-----          5.8.2024     15.55                Platforms
d-----          5.8.2024     15.55                pt
d-----          5.8.2024     15.55                pt-BR
d-----          5.8.2024     15.54                publish
d-----          5.8.2024     15.55                ro
d-----          5.8.2024     15.55                ru
d-----          5.8.2024     15.55                sk
d-----          5.8.2024     15.55                sv
d-----          5.8.2024     15.55                th
d-----          5.8.2024     15.55                tr
d-----          5.8.2024     15.55                uk
d-----          5.8.2024     15.55                vi
d-----          5.8.2024     15.55                zh-Hans
d-----          5.8.2024     15.55                zh-Hant
d-----          5.8.2024     15.55                zh-HK
-a----          5.8.2024     15.54           2956 AppxManifest.xml
-a----         18.7.2024      1.33         191408 libEGL.dll
-a----         18.7.2024      1.33        5123112 libGLESv2.dll
-a----         18.7.2024      1.32        9605040 libSkiaSharp.dll
-a----         28.6.2024      1.06          29448 Microsoft.Extensions.Configuration.Abstractions.dll
-a----         28.6.2024      1.06          45328 Microsoft.Extensions.Configuration.dll
-a----         28.6.2024      1.06          66320 Microsoft.Extensions.DependencyInjection.Abstractions.dll
-a----         28.6.2024      1.06          93472 Microsoft.Extensions.DependencyInjection.dll
-a----         28.6.2024      1.06          67232 Microsoft.Extensions.Logging.Abstractions.dll
-a----         28.6.2024      1.06          20144 Microsoft.Extensions.Logging.Debug.dll
-a----         28.6.2024      1.06          52488 Microsoft.Extensions.Logging.dll
-a----         28.6.2024      1.06          66208 Microsoft.Extensions.Options.dll
-a----         28.6.2024      1.05          45344 Microsoft.Extensions.Primitives.dll
-a----         11.3.2024     17.36        1658416 Microsoft.Graphics.Canvas.dll
-a----         11.3.2024     17.36        1111080 Microsoft.Graphics.Canvas.Interop.dll
-a----          7.6.2024      3.23        1325088 Microsoft.InteractiveExperiences.Projection.dll
-a----         27.6.2024     22.59        1699872 Microsoft.Maui.Controls.dll
-a----         27.6.2024     23.00         133152 Microsoft.Maui.Controls.Xaml.dll
-a----         27.6.2024     23.00         675264 Microsoft.Maui.dll
-a----         27.6.2024     23.02         241184 Microsoft.Maui.Essentials.dll
-a----         27.6.2024     23.02         212400 Microsoft.Maui.Graphics.dll
-a----         27.6.2024     23.02          57264 Microsoft.Maui.Graphics.Win2D.WinUI.Desktop.dll
-a----          7.6.2024     20.05          54192 Microsoft.Windows.ApplicationModel.DynamicDependency.Projection.dll
-a----          7.6.2024      9.06          69568 Microsoft.Windows.ApplicationModel.Resources.Projection.dll
-a----          7.6.2024     20.05          43952 Microsoft.Windows.ApplicationModel.WindowsAppRuntime.Projection.dll
-a----          7.6.2024     20.05          47664 Microsoft.Windows.AppLifecycle.Projection.dll
-a----          7.6.2024     20.05          73136 Microsoft.Windows.AppNotifications.Builder.Projection.dll
-a----          7.6.2024     20.05          60848 Microsoft.Windows.AppNotifications.Projection.dll
-a----          7.6.2024     20.05         109600 Microsoft.Windows.Management.Deployment.Projection.dll
-a----          7.6.2024     20.05          51760 Microsoft.Windows.PushNotifications.Projection.dll
-a----        16.10.2023     22.41       21678632 Microsoft.Windows.SDK.NET.dll
-a----          7.6.2024     20.05          34352 Microsoft.Windows.Security.AccessControl.Projection.dll
-a----          7.6.2024     20.05          44976 Microsoft.Windows.System.Power.Projection.dll
-a----          7.6.2024     20.05          37808 Microsoft.Windows.System.Projection.dll
-a----         29.3.2024      1.55         144416 Microsoft.Windows.Widgets.Projection.dll
-a----          7.6.2024      9.05         391200 Microsoft.WindowsAppRuntime.Bootstrap.dll
-a----          7.6.2024     20.05          16816 Microsoft.WindowsAppRuntime.Bootstrap.Net.dll
-a----          7.6.2024     20.05        7207856 Microsoft.WinUI.dll
-a----          5.8.2024     15.54          37160 resources.pri
-a----         18.7.2024      1.31         415776 SkiaSharp.dll
-a----         18.7.2024      1.31          25632 SkiaSharp.Views.Maui.Controls.dll
-a----         18.7.2024      1.30          35360 SkiaSharp.Views.Maui.Core.dll
-a----         18.7.2024      1.31          45600 SkiaSharp.Views.Windows.dll
-a----         18.7.2024      1.31          53296 SkiaSharp.Views.WinUI.Native.dll
-a----         18.7.2024      1.31          35360 SkiaSharp.Views.WinUI.Native.Projection.dll
-a----         18.7.2024      0.13           2048 SkiaSharp.Views.WinUI.Native.winmd
-a----          5.8.2024     15.54          49526 WindowsMauiUnpackagedSKGLViewError.build.appxrecipe
-a----          5.8.2024     15.54          31959 WindowsMauiUnpackagedSKGLViewError.deps.json
-a----          5.8.2024     15.54          91136 WindowsMauiUnpackagedSKGLViewError.dll
-a----          5.8.2024     15.54         140800 WindowsMauiUnpackagedSKGLViewError.exe
-a----          5.8.2024     15.54          49128 WindowsMauiUnpackagedSKGLViewError.pdb
-a----          5.8.2024     15.54            524 WindowsMauiUnpackagedSKGLViewError.runtimeconfig.json
-a----        16.10.2023     22.41         399280 WinRT.Runtime.dll

Unpackaged
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----          5.8.2024     16.00                af-ZA
d-----          5.8.2024     16.00                am-ET
d-----          5.8.2024     16.00                ar
d-----          5.8.2024     16.00                ar-SA
d-----          5.8.2024     16.00                as-IN
d-----          5.8.2024     16.00                az-Latn-AZ
d-----          5.8.2024     16.00                bg-BG
d-----          5.8.2024     16.00                bn-IN
d-----          5.8.2024     16.00                bs-Latn-BA
d-----          5.8.2024     16.00                ca
d-----          5.8.2024     16.00                ca-ES
d-----          5.8.2024     16.00                ca-Es-VALENCIA
d-----          5.8.2024     16.00                cs
d-----          5.8.2024     16.00                cs-CZ
d-----          5.8.2024     16.00                cy-GB
d-----          5.8.2024     16.00                da
d-----          5.8.2024     16.00                da-DK
d-----          5.8.2024     16.00                de
d-----          5.8.2024     16.00                de-DE
d-----          5.8.2024     16.00                el
d-----          5.8.2024     16.00                el-GR
d-----          5.8.2024     16.00                en-GB
d-----          5.8.2024     16.00                en-us
d-----          5.8.2024     16.00                es
d-----          5.8.2024     16.00                es-ES
d-----          5.8.2024     16.00                es-MX
d-----          5.8.2024     16.00                et-EE
d-----          5.8.2024     16.00                eu-ES
d-----          5.8.2024     16.00                fa-IR
d-----          5.8.2024     16.00                fi
d-----          5.8.2024     16.00                fi-FI
d-----          5.8.2024     16.00                fil-PH
d-----          5.8.2024     16.00                fr
d-----          5.8.2024     16.00                fr-CA
d-----          5.8.2024     16.00                fr-FR
d-----          5.8.2024     16.00                ga-IE
d-----          5.8.2024     16.00                gd-gb
d-----          5.8.2024     16.00                gl-ES
d-----          5.8.2024     16.00                gu-IN
d-----          5.8.2024     16.00                he
d-----          5.8.2024     16.00                he-IL
d-----          5.8.2024     16.00                hi
d-----          5.8.2024     16.00                hi-IN
d-----          5.8.2024     16.00                hr
d-----          5.8.2024     16.00                hr-HR
d-----          5.8.2024     16.00                hu
d-----          5.8.2024     16.00                hu-HU
d-----          5.8.2024     16.00                hy-AM
d-----          5.8.2024     16.00                id
d-----          5.8.2024     16.00                id-ID
d-----          5.8.2024     16.00                is-IS
d-----          5.8.2024     16.00                it
d-----          5.8.2024     16.00                it-IT
d-----          5.8.2024     16.00                ja
d-----          5.8.2024     16.00                ja-JP
d-----          5.8.2024     16.00                ka-GE
d-----          5.8.2024     16.00                kk-KZ
d-----          5.8.2024     16.00                km-KH
d-----          5.8.2024     16.00                kn-IN
d-----          5.8.2024     16.00                ko
d-----          5.8.2024     16.00                ko-KR
d-----          5.8.2024     16.00                kok-IN
d-----          5.8.2024     16.00                lb-LU
d-----          5.8.2024     16.00                lo-LA
d-----          5.8.2024     16.00                lt-LT
d-----          5.8.2024     16.00                lv-LV
d-----          5.8.2024     16.00                mi-NZ
d-----          5.8.2024     16.00                Microsoft.UI.Xaml
d-----          5.8.2024     16.00                mk-MK
d-----          5.8.2024     16.00                ml-IN
d-----          5.8.2024     16.00                mr-IN
d-----          5.8.2024     16.00                ms
d-----          5.8.2024     16.00                ms-MY
d-----          5.8.2024     16.00                mt-MT
d-----          5.8.2024     16.00                nb
d-----          5.8.2024     16.00                nb-NO
d-----          5.8.2024     16.00                ne-NP
d-----          5.8.2024     16.00                nl
d-----          5.8.2024     16.00                nl-NL
d-----          5.8.2024     16.00                nn-NO
d-----          5.8.2024     16.00                or-IN
d-----          5.8.2024     16.00                pa-IN
d-----          5.8.2024     16.00                pl
d-----          5.8.2024     16.00                pl-PL
d-----          5.8.2024     16.00                Platforms
d-----          5.8.2024     16.00                pt
d-----          5.8.2024     16.00                pt-BR
d-----          5.8.2024     16.00                pt-PT
d-----          5.8.2024     16.00                quz-PE
d-----          5.8.2024     16.00                ro
d-----          5.8.2024     16.00                ro-RO
d-----          5.8.2024     16.00                ru
d-----          5.8.2024     16.00                ru-RU
d-----          5.8.2024     16.00                sk
d-----          5.8.2024     16.00                sk-SK
d-----          5.8.2024     16.00                sl-SI
d-----          5.8.2024     16.00                sq-AL
d-----          5.8.2024     16.00                sr-Cyrl-BA
d-----          5.8.2024     16.00                sr-Cyrl-RS
d-----          5.8.2024     16.00                sr-Latn-RS
d-----          5.8.2024     16.00                sv
d-----          5.8.2024     16.00                sv-SE
d-----          5.8.2024     16.00                ta-IN
d-----          5.8.2024     16.00                te-IN
d-----          5.8.2024     16.00                th
d-----          5.8.2024     16.00                th-TH
d-----          5.8.2024     16.00                tr
d-----          5.8.2024     16.00                tr-TR
d-----          5.8.2024     16.00                tt-RU
d-----          5.8.2024     16.00                ug-CN
d-----          5.8.2024     16.00                uk
d-----          5.8.2024     16.00                uk-UA
d-----          5.8.2024     16.00                ur-PK
d-----          5.8.2024     16.00                uz-Latn-UZ
d-----          5.8.2024     16.00                vi
d-----          5.8.2024     16.00                vi-VN
d-----          5.8.2024     16.00                zh-CN
d-----          5.8.2024     16.00                zh-Hans
d-----          5.8.2024     16.00                zh-Hant
d-----          5.8.2024     16.00                zh-HK
d-----          5.8.2024     16.00                zh-TW
-a----         20.7.2024     21.15            657 AboutAssets.txt
-a----          5.8.2024     15.59            974 appicon.ico
-a----          5.8.2024     15.59           3959 appiconLargeTile.scale-100.png
-a----          5.8.2024     15.59           5216 appiconLargeTile.scale-125.png
-a----          5.8.2024     15.59           4769 appiconLargeTile.scale-150.png
-a----          5.8.2024     15.59           6711 appiconLargeTile.scale-200.png
-a----          5.8.2024     15.59          16539 appiconLargeTile.scale-400.png
-a----          5.8.2024     15.59            320 appiconLogo.altform-lightunplated_targetsize-16.png
-a----          5.8.2024     15.59            519 appiconLogo.altform-lightunplated_targetsize-24.png
-a----          5.8.2024     15.59           2725 appiconLogo.altform-lightunplated_targetsize-256.png
-a----          5.8.2024     15.59            497 appiconLogo.altform-lightunplated_targetsize-32.png
-a----          5.8.2024     15.59            868 appiconLogo.altform-lightunplated_targetsize-48.png
-a----          5.8.2024     15.59            320 appiconLogo.altform-unplated_targetsize-16.png
-a----          5.8.2024     15.59            519 appiconLogo.altform-unplated_targetsize-24.png
-a----          5.8.2024     15.59           2725 appiconLogo.altform-unplated_targetsize-256.png
-a----          5.8.2024     15.59            497 appiconLogo.altform-unplated_targetsize-32.png
-a----          5.8.2024     15.59            868 appiconLogo.altform-unplated_targetsize-48.png
-a----          5.8.2024     15.59            748 appiconLogo.scale-100.png
-a----          5.8.2024     15.59            999 appiconLogo.scale-125.png
-a----          5.8.2024     15.59            986 appiconLogo.scale-150.png
-a----          5.8.2024     15.59           1365 appiconLogo.scale-200.png
-a----          5.8.2024     15.59           2436 appiconLogo.scale-400.png
-a----          5.8.2024     15.59            320 appiconLogo.targetsize-16.png
-a----          5.8.2024     15.59            519 appiconLogo.targetsize-24.png
-a----          5.8.2024     15.59           2725 appiconLogo.targetsize-256.png
-a----          5.8.2024     15.59            497 appiconLogo.targetsize-32.png
-a----          5.8.2024     15.59            868 appiconLogo.targetsize-48.png
-a----          5.8.2024     15.59           1831 appiconMediumTile.scale-100.png
-a----          5.8.2024     15.59           2622 appiconMediumTile.scale-125.png
-a----          5.8.2024     15.59           3406 appiconMediumTile.scale-150.png
-a----          5.8.2024     15.59           3540 appiconMediumTile.scale-200.png
-a----          5.8.2024     15.59           6431 appiconMediumTile.scale-400.png
-a----          5.8.2024     15.59           1089 appiconSmallTile.scale-100.png
-a----          5.8.2024     15.59           1411 appiconSmallTile.scale-125.png
-a----          5.8.2024     15.59           1798 appiconSmallTile.scale-150.png
-a----          5.8.2024     15.59           1791 appiconSmallTile.scale-200.png
-a----          5.8.2024     15.59           3477 appiconSmallTile.scale-400.png
-a----          5.8.2024     15.59            907 appiconStoreLogo.scale-100.png
-a----          5.8.2024     15.59            932 appiconStoreLogo.scale-125.png
-a----          5.8.2024     15.59           1181 appiconStoreLogo.scale-150.png
-a----          5.8.2024     15.59           1640 appiconStoreLogo.scale-200.png
-a----          5.8.2024     15.59           2807 appiconStoreLogo.scale-400.png
-a----          5.8.2024     15.59           1971 appiconWideTile.scale-100.png
-a----          5.8.2024     15.59           2799 appiconWideTile.scale-125.png
-a----          5.8.2024     15.59           3779 appiconWideTile.scale-150.png
-a----          5.8.2024     15.59           4009 appiconWideTile.scale-200.png
-a----          5.8.2024     15.59           8148 appiconWideTile.scale-400.png
-a----          8.6.2024      1.08        1042464 CoreMessagingXP.dll
-a----          8.6.2024      1.08        1820704 dcompi.dll
-a----          5.8.2024     15.59          20504 dotnet_bot.scale-100.png
-a----          5.8.2024     15.59          29114 dotnet_bot.scale-125.png
-a----          5.8.2024     15.59          38974 dotnet_bot.scale-150.png
-a----          5.8.2024     15.59          59920 dotnet_bot.scale-200.png
-a----          5.8.2024     15.59         191321 dotnet_bot.scale-400.png
-a----          8.6.2024      1.08        3016736 dwmcorei.dll
-a----          8.6.2024      1.08        2365472 DwmSceneI.dll
-a----          8.6.2024      1.08        3043880 DWriteCore.dll
-a----         18.7.2024      1.33         191408 libEGL.dll
-a----         18.7.2024      1.33        5123112 libGLESv2.dll
-a----         18.7.2024      1.32        9605040 libSkiaSharp.dll
-a----          8.6.2024      1.08         563120 marshal.dll
-a----          8.6.2024      1.08         694304 Microsoft.DirectManipulation.dll
-a----         28.6.2024      1.06          29448 Microsoft.Extensions.Configuration.Abstractions.dll
-a----         28.6.2024      1.06          45328 Microsoft.Extensions.Configuration.dll
-a----         28.6.2024      1.06          66320 Microsoft.Extensions.DependencyInjection.Abstractions.dll
-a----         28.6.2024      1.06          93472 Microsoft.Extensions.DependencyInjection.dll
-a----         28.6.2024      1.06          67232 Microsoft.Extensions.Logging.Abstractions.dll
-a----         28.6.2024      1.06          20144 Microsoft.Extensions.Logging.Debug.dll
-a----         28.6.2024      1.06          52488 Microsoft.Extensions.Logging.dll
-a----         28.6.2024      1.06          66208 Microsoft.Extensions.Options.dll
-a----         28.6.2024      1.05          45344 Microsoft.Extensions.Primitives.dll
-a----          8.6.2024      1.08          11696 Microsoft.Foundation.winmd
-a----         11.3.2024     17.36        1658416 Microsoft.Graphics.Canvas.dll
-a----         11.3.2024     17.36        1111080 Microsoft.Graphics.Canvas.Interop.dll
-a----          8.6.2024      1.08         231456 Microsoft.Graphics.Display.dll
-a----          8.6.2024      1.08          23072 Microsoft.Graphics.winmd
-a----          8.6.2024      1.08         444448 Microsoft.InputStateManager.dll
-a----          7.6.2024      3.23        1325088 Microsoft.InteractiveExperiences.Projection.dll
-a----          8.6.2024      1.08         853288 Microsoft.Internal.FrameworkUdk.dll
-a----         27.6.2024     22.59        1699872 Microsoft.Maui.Controls.dll
-a----         27.6.2024     23.00         133152 Microsoft.Maui.Controls.Xaml.dll
-a----         27.6.2024     23.00         675264 Microsoft.Maui.dll
-a----         27.6.2024     23.02         241184 Microsoft.Maui.Essentials.dll
-a----         27.6.2024     23.02         212400 Microsoft.Maui.Graphics.dll
-a----         27.6.2024     23.02          57264 Microsoft.Maui.Graphics.Win2D.WinUI.Desktop.dll
-a----          8.6.2024      1.08          67616 Microsoft.UI.Composition.OSSupport.dll
-a----          8.6.2024      1.08         120864 Microsoft.UI.dll
-a----          8.6.2024      1.08        1480736 Microsoft.UI.Input.dll
-a----          8.6.2024      1.08          34736 Microsoft.UI.Text.winmd
-a----          8.6.2024      1.08         493600 Microsoft.UI.Windowing.Core.dll
-a----          8.6.2024      1.08         464816 Microsoft.UI.Windowing.dll
-a----          8.6.2024      1.08         298928 Microsoft.UI.winmd
-a----          8.6.2024      1.08        6882344 Microsoft.UI.Xaml.Controls.dll
-a----          8.6.2024      1.08        1229952 Microsoft.UI.Xaml.Controls.pri
-a----          8.6.2024      1.08       15175712 Microsoft.ui.xaml.dll
-a----          8.6.2024      1.08         939552 Microsoft.UI.Xaml.Internal.dll
-a----          8.6.2024      1.08        1094704 Microsoft.UI.Xaml.Phone.dll
-a----          8.6.2024      1.08         566824 Microsoft.ui.xaml.resources.19h1.dll
-a----          8.6.2024      1.08          55840 Microsoft.ui.xaml.resources.common.dll
-a----          8.6.2024      1.08        1611184 Microsoft.UI.Xaml.winmd
-a----          8.6.2024      1.08         714304 Microsoft.Web.WebView2.Core.dll
-a----          8.6.2024      1.08         116296 Microsoft.Web.WebView2.Core.winmd
-a----          7.6.2024     20.05          54192 Microsoft.Windows.ApplicationModel.DynamicDependency.Projection.dll
-a----          8.6.2024      1.08          18480 Microsoft.Windows.ApplicationModel.DynamicDependency.winmd
-a----          8.6.2024      1.08         142880 Microsoft.Windows.ApplicationModel.Resources.dll
-a----          7.6.2024      9.06          69568 Microsoft.Windows.ApplicationModel.Resources.Projection.dll
-a----          8.6.2024      1.08          19376 Microsoft.Windows.ApplicationModel.Resources.winmd
-a----          7.6.2024     20.05          43952 Microsoft.Windows.ApplicationModel.WindowsAppRuntime.Projection.dll
-a----          8.6.2024      1.08          15296 Microsoft.Windows.ApplicationModel.WindowsAppRuntime.winmd
-a----          7.6.2024     20.05          47664 Microsoft.Windows.AppLifecycle.Projection.dll
-a----          8.6.2024      1.08          17344 Microsoft.Windows.AppLifecycle.winmd
-a----          7.6.2024     20.05          73136 Microsoft.Windows.AppNotifications.Builder.Projection.dll
-a----          8.6.2024      1.08          24608 Microsoft.Windows.AppNotifications.Builder.winmd
-a----          7.6.2024     20.05          60848 Microsoft.Windows.AppNotifications.Projection.dll
-a----          8.6.2024      1.08          19888 Microsoft.Windows.AppNotifications.winmd
-a----          7.6.2024     20.05         109600 Microsoft.Windows.Management.Deployment.Projection.dll
-a----          8.6.2024      1.08          34224 Microsoft.Windows.Management.Deployment.winmd
-a----          7.6.2024     20.05          51760 Microsoft.Windows.PushNotifications.Projection.dll
-a----          8.6.2024      1.08          15792 Microsoft.Windows.PushNotifications.winmd
-a----        16.10.2023     22.41       21678632 Microsoft.Windows.SDK.NET.dll
-a----          7.6.2024     20.05          34352 Microsoft.Windows.Security.AccessControl.Projection.dll
-a----          8.6.2024      1.08          12720 Microsoft.Windows.Security.AccessControl.winmd
-a----          7.6.2024     20.05          44976 Microsoft.Windows.System.Power.Projection.dll
-a----          8.6.2024      1.08          17328 Microsoft.Windows.System.Power.winmd
-a----          7.6.2024     20.05          37808 Microsoft.Windows.System.Projection.dll
-a----          8.6.2024      1.08          13872 Microsoft.Windows.System.winmd
-a----          8.6.2024      1.08        2055200 Microsoft.Windows.Widgets.dll
-a----         29.3.2024      1.55         144416 Microsoft.Windows.Widgets.Projection.dll
-a----          8.6.2024      1.08          32288 Microsoft.Windows.Widgets.winmd
-a----          8.6.2024      1.08         391200 Microsoft.WindowsAppRuntime.Bootstrap.dll
-a----          7.6.2024     20.05          16816 Microsoft.WindowsAppRuntime.Bootstrap.Net.dll
-a----          8.6.2024      1.08        1332768 Microsoft.WindowsAppRuntime.dll
-a----          8.6.2024      1.08          38952 Microsoft.WindowsAppRuntime.Insights.Resource.dll
-a----          7.6.2024     20.05        7207856 Microsoft.WinUI.dll
-a----          8.6.2024      1.08         304688 MRM.dll
-a----         20.7.2024     21.15         107168 OpenSans-Regular.ttf
-a----         20.7.2024     21.15         111060 OpenSans-Semibold.ttf
-a----          8.6.2024      1.08          43968 PushNotificationsLongRunningTask.ProxyStub.dll
-a----          5.8.2024     15.59        1266160 resources.pri
-a----          8.6.2024      1.08          86448 RestartAgent.exe
-a----         18.7.2024      1.31         415776 SkiaSharp.dll
-a----         18.7.2024      1.31          25632 SkiaSharp.Views.Maui.Controls.dll
-a----         18.7.2024      1.30          35360 SkiaSharp.Views.Maui.Core.dll
-a----         18.7.2024      1.31          45600 SkiaSharp.Views.Windows.dll
-a----         18.7.2024      1.31          53296 SkiaSharp.Views.WinUI.Native.dll
-a----         18.7.2024      1.31          35360 SkiaSharp.Views.WinUI.Native.Projection.dll
-a----         18.7.2024      0.13           2048 SkiaSharp.Views.WinUI.Native.winmd
-a----          5.8.2024     15.59           4009 splashSplashScreen.scale-100.png
-a----          5.8.2024     15.59           5857 splashSplashScreen.scale-125.png
-a----          5.8.2024     15.59           7559 splashSplashScreen.scale-150.png
-a----          5.8.2024     15.59           8148 splashSplashScreen.scale-200.png
-a----          5.8.2024     15.59          21521 splashSplashScreen.scale-400.png
-a----          8.6.2024      1.08            232 WindowsAppRuntime.png
-a----          8.6.2024      1.08          49944 WindowsAppSdk.AppxDeploymentExtensions.Desktop-EventLog-Instrumentati
                                                  on.dll
-a----          8.6.2024      1.08         624520 WindowsAppSdk.AppxDeploymentExtensions.Desktop.dll
-a----          5.8.2024     15.59          31959 WindowsMauiUnpackagedSKGLViewError.deps.json
-a----          5.8.2024     15.59         207360 WindowsMauiUnpackagedSKGLViewError.dll
-a----          5.8.2024     15.59         259072 WindowsMauiUnpackagedSKGLViewError.exe
-a----          5.8.2024     15.59          47612 WindowsMauiUnpackagedSKGLViewError.pdb
-a----          5.8.2024     15.59            524 WindowsMauiUnpackagedSKGLViewError.runtimeconfig.json
-a----        16.10.2023     22.41         399280 WinRT.Runtime.dll
-a----          8.6.2024      1.08        3397152 WinUIEdit.dll
-a----          8.6.2024      1.08         485408 wuceffectsi.dll

Did you check for any extra activation information being added to the package? In these cases, did you check if they were activatable in an unpackaged application?
An example of this is actually the C++ projection. C++/WinRT tries very hard to activate a type, even to the point of falling back to looking for namespace named libraries in the application directory and querying them directly. To give an example from Win2D, this registers itself in the AppxManifest.xml file:

There's no AppxManifest.xml in the unpackaged app.

The unpackaged version doesn't have AppxManifest.xml file.

There's no AppxManifest.xml in the unpackaged app.

The packaged application does. This is where all of the information about dependencies is. The point of these questions was for you to verify the contents of the AppxManifest.xml of the packaged application to make sure there is nothing unexpected in there. If there are extra package dependencies or component registrations, then you can use this information to make sure that you have all of the dependencies and registrations for the unpackaged application.

No, they are quite different.

That looks like you have the Windows App SDK set to self contained, so it is mostly ignorable. The important thing is that the packaged version files are findable.

The unpackaged version doesn't have AppxManifest.xml file.

There's no AppxManifest.xml in the unpackaged app.

The packaged application does. This is where all of the information about dependencies is. The point of these questions was for you to verify the contents of the AppxManifest.xml of the packaged application to make sure there is nothing unexpected in there. If there are extra package dependencies or component registrations, then you can use this information to make sure that you have all of the dependencies and registrations for the unpackaged application.

AppxManifest.xml doesn't have very much information:
<?xml version="1.0" encoding="utf-8"?>
<Package xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10" xmlns:mp="http://schemas.microsoft.com/appx/2014/phone/manifest" xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" IgnorableNamespaces="uap rescap build" xmlns:build="http://schemas.microsoft.com/developer/appx/2015/build">
  <!--
    THIS PACKAGE MANIFEST FILE IS GENERATED BY THE BUILD PROCESS.

    Changes to this file will be lost when it is regenerated. To correct errors in this file, edit the source .appxmanifest file.

    For more information on package manifest files, see http://go.microsoft.com/fwlink/?LinkID=241727
  -->
  <Identity Name="com.companyname.windowsmauiunpackagedskglviewerror" Publisher="CN=User Name" Version="1.0.0.1" ProcessorArchitecture="x64" />
  <mp:PhoneIdentity PhoneProductId="2F086E16-383A-4374-98B7-4B8241A712F4" PhonePublisherId="00000000-0000-0000-0000-000000000000" />
  <Properties>
    <DisplayName>WindowsMauiUnpackagedSKGLViewError</DisplayName>
    <PublisherDisplayName>User Name</PublisherDisplayName>
    <Logo>appiconStoreLogo.png</Logo>
  </Properties>
  <Dependencies>
    <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.19041.0" />
    <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17763.0" MaxVersionTested="10.0.19041.0" />
    <PackageDependency Name="Microsoft.WindowsAppRuntime.1.5" MinVersion="5001.159.55.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
  </Dependencies>
  <Resources>
    <Resource Language="EN-US" />
  </Resources>
  <Applications>
    <Application Id="App" Executable="WindowsMauiUnpackagedSKGLViewError.exe" EntryPoint="Windows.FullTrustApplication">
      <uap:VisualElements DisplayName="WindowsMauiUnpackagedSKGLViewError" Description="WindowsMauiUnpackagedSKGLViewError" Square150x150Logo="appiconMediumTile.png" Square44x44Logo="appiconLogo.png" BackgroundColor="transparent">
        <uap:DefaultTile Square71x71Logo="appiconSmallTile.png" Wide310x150Logo="appiconWideTile.png" Square310x310Logo="appiconLargeTile.png" ShortName="WindowsMauiUnpackagedSKGLViewError">
          <uap:ShowNameOnTiles>
            <uap:ShowOn Tile="square150x150Logo" />
            <uap:ShowOn Tile="wide310x150Logo" />
          </uap:ShowNameOnTiles>
        </uap:DefaultTile>
        <uap:SplashScreen Image="splashSplashScreen.png" />
      </uap:VisualElements>
    </Application>
  </Applications>
  <Capabilities>
    <rescap:Capability Name="runFullTrust" />
  </Capabilities>
  <build:Metadata>
    <build:Item Name="Microsoft.UI.Xaml.Markup.Compiler.dll" Version="3.0.0.2406" />
    <build:Item Name="makepri.exe" Version="10.0.22621.755 (WinBuild.160101.0800)" />
  </build:Metadata>
</Package>

No, they are quite different.

That comes from the fact that the Windows App SDK is set to self contained, so it is mostly ignorable. The important thing is that the packaged version files are findable.

Yes, I think .NET MAUI apps are by default self-contained, and I build the unpackaged app on the command line like this:
dotnet build -f:net9.0-windows10.0.19041.0 -c:Release -p:RuntimeIdentifierOverride=win10-x64 -p:WindowsAppSDKSelfContained=true -p:WindowsPackageType=None

The .NET self contained is different from the Windows App SDK self contained.
The .NET self contained means that the .NET runtime will be added to the package when you generate the .msix file. This has nothing to do with the Windows App SDK. Setting the Windows App SDK to self contained means that the Windows App Runtime files, such as Microsoft.UI.Xaml.dll are copied into the application directory and registered as Registration Free WinRT. If you remove that declaration and clean the output directory, the Windows App Runtime files will go away.
Well, either way, it seems like I was unable to help you here. I hope you get the help you need quickly.

authors: DarranRowe TommiGustafsson-HMP


text:
Extracting Text Notes for Sepsis Data

I wanted to ask if there is a separate code for identifying the sepsis criteria in the dataset or just adding a column for all the textual information for each instance here when creating the sepsis dataset. I wanted to test with clinical notes for classification of sepsis in the final data.

Hi, thanks for asking. We use the clinical Sepsis3 criteria to define Sepsis, which is done pretty early on in the sepsis_cohort.py script (https://github.com/microsoft/mimic_sepsis/blob/main/sepsis_cohort.py#L250-L283).
I think that it's a great idea to cross-reference with the clinical notes. It should be pretty straightforward to use the filtered icustayids that are presumed to have Sepsis and then cross-reference with the charttimes under consideration to extract the notes.

So the lines 250-283 are the sepsis3 criteria?
I already have created the sepsis_cohorts by running this file. In the final files, I am getting a traj and step columns without any identifiers to map with the notes. So, the charttimes would help me map with extracted notes in here?

In case of data collected for the Metavision system, in the INPUTEVENTS_MV.csv.gz there is no charttimes that has been given then  can you tell how to cross-reference the data there to extract the notes. I was able to do it for the data for the CareVue system.

All input events have a starttime and endtime columns, correct? You can make a determination on how to select the timing for cross referencing with the notes.

Are you suggesting that based on the starttime and endtime we look at whatever the in between charttimes (for a particular ICUSTAY_ID) are and then decide on the notes.

Yes, I'm going to consider this issue as closed as I trust you have the facility to determine the best path forward for the remainder of your work.

@fatemi, are you able to close this issue?

@twkillian No. Someone from MS should do it.

source: gharchive/issue

authors: fatemi hsuyab twkillian

license: MIT

license_type: permissive

license_source: github-api


text:
Paste shows warning in Google Chrome

monaco-editor version: 0.21.2
Browser: Chrome 86.0.4240.75
OS: Windows 10
Playground code that reproduces the issue: https://microsoft.github.io/monaco-editor/
Right clicking and choosing paste from the context menu shows a warning dialog stating microsoft.github.io wants to see text and images copied to the clipboard. Copying from the context menu or pasting through CTRL+V does not cause the warning to appear. This behavior does not seem to be present in older versions of Monaco.

yes a prompt will appear if navigator.clipboard.readText is triggered

@borremosch I think that's how it works, Please refer this issue

This behavior does not seem to be present in older versions of Monaco.

I think this is because , paste in context menu is available only after 0.21.0
More over on accessing navigator clipboard's text , Browser will throw this prompt as a security measure

Shouldn't the prompt trigger only when the clipboard was not accessed through any user interaction? Since the clipboard access is following a mouse click I would expect the prompt to be skipped.

I think this is because , paste in context menu is available only after 0.21.0

That makes sense

Monaco seems to use a custom context menu and not the native context menu of the browser. So it may look like a mouse click , but internally it is going to trigger a javascript function which in turn access the navigator.clipboard

Since the clipboard access is following a mouse click I would expect the prompt to be skipped.

Yes , I too wish pasting happens this way
@bpasero, Is it possible to modify the paste function without prompt? Now-a-days, Browser's native context menu does that without a prompt

The "Paste" action was not present in the editor menu before as far as I can tell, and now that we have it, the browser will show the warning, that is just a security feature of the browser. I am not sure what we can do here or what changed?

@bpasero As the browser's default context menu does paste without prompt there might be a way we can also implement it without that prompt. I thought Browser is using some API ( other than navigator ) to achieve this, In that case we can also use that API and do the paste action. But I'm not sure that kind of API exists.
The main problem here is the UX of the paste action.
The security prompt will be shown only for Context Menu Paste and not for Cmd/Ctrl + V
From the user's point of view , As both are doing the same thing, one is showing a warning and other doesn't , creates a confusion.

When right clicking in the editor, you don't get a native context menu, you see a custom context menu rendered with DOM nodes. That is why we can render custom actions, like rename, or go to definition etc. When clicking on Paste in the editor context menu, you are basically clicking on a DOM node from the browser's point of view. There is no paste event, there is a click event. In the implementation of that click we end up using browser API to read from the clipboard. That browser API will prompt the user and ask for permission.
When pressing ctrl+v in the editor, the browser generates a paste event. We read the data from the paste event, which does not create any user prompts.
The only way to get a context menu paste without a prompt is to give up our custom context menu and use the native browser context menu. We had that a very very long time ago and will not go in that direction ever again.

authors: Pranomvignesh alexdima borremosch bpasero

repo: microsoft/monaco-editor


text:
Issue connecting to SQL server from Openshift

FROM python:3.9
RUN apt-get update && apt-get install -y --no-install-recommends \
    gnupg \
    unixodbc \
    unixodbc-dev \
    && curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add - \
    && curl https://packages.microsoft.com/config/debian/10/prod.list > /etc/apt/sources.list.d/mssql-release.list \
    && apt-get update \
    && ACCEPT_EULA=Y apt-get install -y msodbcsql17 \
    && apt-get clean && rm -rf /var/lib/apt/lists/*

WORKDIR /app
COPY . /app
RUN pip install --no-cache-dir -r requirements.txt

EXPOSE 8080
CMD ["python", "app.py"]

I am getting an error in the logs saying login timeout when connecting to the SQL server "return pyodbc.connect(
pyodbc.OperationalError: ('HYT00', '[HYT00] [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0) (SQLDriverConnect)')"
I have ODBC 17 specified in my other file too and when I run my project locally there are no issues and it is able to connect.
I am testing it out on Redhat developer Openshift sandbox

Hi @zkhan21, seems the login info somehow not accepted and login process failed. Can you share your connection string or connection info with the sensitives information masked off? So we have a bit more information to investigate with. Also, you mentioned that you work from a OpenShift sandbox. I am not too familiarize with it, but is there a OS or platform this sandbox is operating based on? Or this is not the case a OpenShift sandbox?

Closed due to inactivity

repo: microsoft/msphpsql


text:
Copy-FileToNavContainer issue (seems to delete the target folder)

Hi Freedy !
Hope you're doing well.
Describe the issue
I would like to copy local DLLs to ..\Service\Add-ins folder inside the docker but Copy-FileToNavContainer seems to delete the target folder.
I tried to copy to "...Service\Add-ins" or "...Service\Add-ins" with same result.
Scripts used to create container and cause the issue
Clear-Host
Set-ExecutionPolicy Unrestricted -Force
Update-Module navcontainerhelper -Force

$dockerinput = "C:\temp\dockerinput"
$mylicense = "$dockerinput\Michelin Colombia_7144912.flf"
$mydevlicense = "$dockerinput\France BC_16 Developer License.flf"

$mybacpacname = "ibsccol0_CU4_20200915.bacpac"
$mybacpacfullpath = "$dockerinput\$mybacpacname"
$mybacpacnameincontainer = "c:\run\my\$mybacpacname"

$traxbouncycastlefilepath = "$dockerinput\DidiSoft.BouncyCastle.dll"
$traxpgpfilepath = "$dockerinput\DidiSoft.Pgp.dll"
$vneinvoicingdll = "$dockerinput\BKAVSOAP.dll"

$accept_eula = $true
$artifactUrl = Get-BCArtifactUrl -type OnPrem -country "w1" -version "16.4" -select Latest
$containername = 'mica-co-v16-04W'
Write-Host "Create new container <$containername> with image $artifactUrl and restore BACPAC $mybacpacfullpath" -Foreground Green
Write-Host "Bacpac filepath in container <$containername> is $mybacpacnameincontainer" -Foreground Red
Write-Host "Press enter to confirm or CTRL+C to cancel" -Foreground Green
Read-Host

$securePassword = ConvertTo-SecureString -String "" -AsPlainText -Force
$credential = New-Object System.Management.Automation.PSCredential -argumentList "", $securePassword

New-NavContainer -accept_eula:$accept_eula `
                 -accept_outdated `
                 -containername $containername `
                 -artifactUrl $artifactUrl `
                 -licensefile $mylicense `
                 -Credential $credential `
                 -memoryLimit 8G `
                 -isolation "HyperV" `
                 -shortcuts Desktop `
                 -dns '8.8.8.8' `
                 -updateHosts `
                 -usessl:$false `
                 -enableTaskScheduler `
                 -alwaysPull `
                 -UseBestContainerOS `
                 -assignPremiumPlan `
                 -multitenant  `
                 -auth NavUserPassword `
                 -timeout -1 `
                 -doNotCheckHealth

Copy-FileToNavContainer -localPath "$dockerinput\*.dll" -containerPath "C:\Program Files\Microsoft Dynamics NAV\BC160\Service\Add-ins\" -containerName $containername

Import-NavContainerLicense -containerName $containername -licenseFile $mydevlicense
Restart-NavContainer -containerName $containername
Import-TestToolkitToBCContainer -containerName $containername -ErrorAction SilentlyContinue #Test libraries

Import-NavContainerLicense -containerName $containername -licenseFile $mylicense
Restart-NavContainer -containerName $containername

Full output of scripts
Create new container <mica-co-v16-04W> with image https://bcartifacts.azureedge.net/onprem/16.4.14693.15445/w1 and restore BACPAC C:\temp\dockerinput\ibsccol0_CU4_20200915.bacpac
Bacpac filepath in container <mica-co-v16-04W> is c:\run\my\ibsccol0_CU4_20200915.bacpac
Press enter to confirm or CTRL+C to cancel

NavContainerHelper is version 0.7.0.26
NavContainerHelper is running as administrator
Host is Microsoft Windows 10 Professionnel - 2004
Docker Client Version is 19.03.12
Docker Server Version is 19.03.12
Removing container mica-co-v16-04W
Removing mica-co-v16-04W from host hosts file
Removing C:\ProgramData\NavContainerHelper\Extensions\mica-co-v16-04W
Fetching all docker images
Pulling image mcr.microsoft.com/dynamicsnav:10.0.19041.508-generic
10.0.19041.508-generic: Pulling from dynamicsnav
Digest: sha256:fe59dd46714fa8ec5ed9ca0dbd16fe050f15959c7108ba42f623a5ccbbfd95d3
Status: Image is up to date for mcr.microsoft.com/dynamicsnav:10.0.19041.508-generic
mcr.microsoft.com/dynamicsnav:10.0.19041.508-generic
Using image mcr.microsoft.com/dynamicsnav:10.0.19041.508-generic
Disabling Health Check (always report healthy)
Creating Container mica-co-v16-04W
Version: 16.4.14693.15445-w1
Style: onprem
Platform: 16.0.14648.15420
Generic Tag: 0.1.0.21
Container OS Version: 10.0.19041.508 (2004)
Host OS Version: 10.0.19041.508 (2004)
Using locale en-US
Using HyperV isolation
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file C:\temp\dockerinput\Michelin Colombia_7144912.flf
Additional Parameters:
--env customNavSettings=EnableTaskScheduler=True
Files in C:\ProgramData\NavContainerHelper\Extensions\mica-co-v16-04W\my:
- AdditionalOutput.ps1
- license.flf
- MainLoop.ps1
- SetupNavUsers.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container mica-co-v16-04W from image mcr.microsoft.com/dynamicsnav:10.0.19041.508-generic
31d44d9523a4198248ea60ca5dfccd945b9ccb2e10eb5f0dbc955ddd03d099a1
Waiting for container mica-co-v16-04W to be ready
Using artifactUrl https://bcartifacts.azureedge.net/onprem/16.4.14693.15445/w1
Using installer from C:\Run\150-new
Installing Business Central
Installing from artifacts
Starting Local SQL Server
Starting Internet Information Server
Copying Service Tier Files
Copying PowerShell Scripts
Copying dependencies
Copying ReportBuilder
Importing PowerShell Modules
Determining Database Collation from c:\dl\onprem\16.4.14693.15445\w1\database\Demo Database NAV (16-0).bak
Restoring CRONUS Demo Database
Exporting Application to CRONUS
Removing Application from tenant
Modifying Business Central Service Tier Config File for Docker
Creating Business Central Service Tier
Installing SIP crypto provider: 'C:\Windows\System32\NavSip.dll'
Copying Web Client Files
Copying Client Files
Copying ModernDev Files
Copying additional files
Copying ConfigurationPackages
Copying Test Assemblies
Copying Applications
Starting Business Central Service Tier
Importing license file
Copying Database on localhost\SQLEXPRESS from tenant to default
Taking database tenant offline
Copying database files
Attaching files as new Database default
Putting database tenant back online
Mounting tenant database
Mounting Database for default on server localhost\SQLEXPRESS
Sync'ing Tenant
Tenant is Operational
Stopping Business Central Service Tier
Installation took 187 seconds
Installation complete
Initializing...
Setting host.docker.internal to 10.42.6.15 in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to 10.42.6.15 in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to 127.0.0.1 in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to 172.30.48.1 in container hosts file
Starting Container
Hostname is mica-co-v16-04W
PublicDnsName is mica-co-v16-04W
Using NavUserPassword Authentication
Creating Self Signed Certificate
Self Signed Certificate Thumbprint 8E81B317B08AE7A1CF2CEA3CE6E8F5D00F766EC6
Modifying Service Tier Config File with Instance Specific Settings
Modifying Service Tier Config File with settings from environment variable
Setting EnableTaskScheduler to True
Starting Service Tier
Registering event sources
Creating DotNetCore Web Server Instance
Enabling rewrite rule: Don't rewrite system files
Enabling rewrite rule: Already have tenant specified
Enabling rewrite rule: Hostname (without port) to tenant
Using license file 'c:\run\my\license.flf'
Import License
Dismounting Tenant
Mounting Tenant
Mounting Database for default on server localhost\SQLEXPRESS
Sync'ing Tenant
Tenant is Operational
Creating http download site
Setting SA Password and enabling SA
Creating admin as SQL User and add to sysadmin
Creating SUPER user
Assign Premium plan for ADMIN
Container IP Address: 172.30.63.170
Container Hostname  : mica-co-v16-04W
Container Dns Name  : mica-co-v16-04W
Web Client          : http://mica-co-v16-04W/BC/?tenant=default
Dev. Server         : http://mica-co-v16-04W
Dev. ServerInstance : BC
Dev. Server Tenant  : default
Setting mica-co-v16-04W to 172.30.63.170 in host hosts file

Files:
http://mica-co-v16-04W:8080/ALLanguage.vsix

Initialization took 36 seconds
Ready for connections!
Reading CustomSettings.config from mica-co-v16-04W
Creating Desktop Shortcuts for mica-co-v16-04W
Container mica-co-v16-04W successfully created
Copy C:\temp\dockerinput\*.dll to container mica-co-v16-04W (C:\Program Files\Microsoft Dynamics NAV\BC160\Service\Add-ins\)
Copying license file 'C:\temp\dockerinput\France BC_16 Developer License.flf' to container
Importing License C:\ProgramData\NavContainerHelper\Extensions\mica-co-v16-04W\my\license.flf
mica-co-v16-04W
Waiting for container mica-co-v16-04W to be ready

Initializing...
Setting host.docker.internal to 10.42.6.15 in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to 10.42.6.15 in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to 127.0.0.1 in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to 172.30.48.1 in container hosts file
Restarting Container
PublicDnsName unchanged
Hostname is mica-co-v16-04W
PublicDnsName is mica-co-v16-04W
Using NavUserPassword Authentication
Starting Local SQL Server
Starting Internet Information Server
Cannot find path 'C:\Program Files\Microsoft Dynamics NAV\BC160\Service\CustomSettings.config' because it does not exist.
at <ScriptBlock>, C:\Run\navstart.ps1: line 103
at <ScriptBlock>, C:\Run\start.ps1: line 346
at <ScriptBlock>, <No file>: line 1Error

Initializing...
Setting host.docker.internal to 10.42.6.15 in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to 10.42.6.15 in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to 127.0.0.1 in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to 172.30.48.1 in container hosts file
Restarting Container
PublicDnsName unchanged
Hostname is mica-co-v16-04W
PublicDnsName is mica-co-v16-04W
Using NavUserPassword Authentication
Starting Local SQL Server
Starting Internet Information Server
Cannot find path 'C:\Program Files\Microsoft Dynamics NAV\BC160\Service\CustomSettings.config' because it does not exist.
at <ScriptBlock>, C:\Run\navstart.ps1: line 103
at <ScriptBlock>, C:\Run\start.ps1: line 346
at <ScriptBlock>, <No file>: line 1
Initialization of container mica-co-v16-04W failed
Au caractère C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\0.7.0.26\ContainerHandling\Wait-NavContainerReady.ps1:44 : 17
+ ...             throw "Initialization of container $containerName failed" ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Initialization ...-v16-04W failed:String) [], RuntimeException
    + FullyQualifiedErrorId : Initialization of container mica-co-v16-04W failed

Additional context

does it happen all the time? yes
did it use to work? Do not know

Copy-FileToBcContainer will only copy one file from the host to the container and it needs a full path to the source file and a full path to the destination file (including file name)
If the goal is to share add-ins with the container, you can share the folder using
-additionalparameters @("--volume c:\yourhostpathtoaddinsfolder:c:\run\Add-Ins")

Then the container will copy them in place during startup.

At first time, I did try to copy each file with full local source name / full docker target name but it was the same.
I will let you know.

Hi Freedy, I didn't repro it. Issue closed, thanks.

authors: freddydk xgaronnat

repo: microsoft/navcontainerhelper


text:
The guid number '$(applicationInsightsKey)' does not match the expected pattern:

Describe the issue
Getting this error when running Run-AlPipeline from DevOps-Pipeline.ps1
##[error]c:\sources\MainApp Library\app.json(46,5): error AL1040: The guid number '$(applicationInsightsKey)' does not match the expected pattern: "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$".
I ran with both version 2.0.16 and 2.0.17-dev with the same result.
Scripts used to create container and cause the issue
Used the same scripts and setup from the CICD hands-on lab with different app folders and secrets.
The app that is failing to compile doesn't have the 'applicationInsightsKey' but the 'applicationInsightsConnectionString'
"applicationInsightsConnectionString": "InstrumentationKey=ce0dddb9-0000-0000-0000-6e4291c6b5ef;IngestionEndpoint=https://westus2-0.in.applicationinsights.azure.com/",
Full output of scripts
...
Set appFolders = 'MainApp,MainApp Library'
Set testFolders = 'MainApp TestApp'
Set memoryLimit = '6G'
Set additionalCountries = 'dk,gb'
Set genericImageName = ''
Set vaultNameForLocal = 'CICDBuildVariables'
Set bcContainerHelperVersion = 'dev'
Set installTestRunner = True
Set installTestFramework = False
Set installTestLibraries = False
Set installPerformanceToolkit = False
Set enableCodeCop = False
Set enableAppSourceCop = True
Set enablePerTenantExtensionCop = False
Set enableUICop = True
Set useDefaultAppSourceRuleSet = False
Set doNotSignApps = True
Set doNotRunTests = False
Set cacheImage = False
Set CreateRuntimePackages = False
Downloading https://github.com/microsoft/navcontainerhelper/archive/dev.zip
BcContainerHelper version 2.0.17-dev
Determining artifacts to use
Found https://bcinsider.azureedge.net/sandbox/19.1.31832.0/us
Found https://bcinsider.azureedge.net/sandbox/19.1.31832.0/dk
Found https://bcinsider.azureedge.net/sandbox/19.1.31832.0/gb
.
.
.

Creating container took 216 seconds

   _____                      _ _ _
  / ____|                    (_) (_)
 | |     ___  _ __ ___  _ __  _| |_ _ __   __ _    __ _ _ __  _ __  ___
 | |    / _ \| '_ ` _ \| '_ \| | | | '_ \ / _` |  / _` | '_ \| '_ \/ __|
 | |____ (_) | | | | | | |_) | | | | | | | (_| | | (_| | |_) | |_) \__ \
  \_____\___/|_| |_| |_| .__/|_|_|_|_| |_|\__, |  \__,_| .__/| .__/|___/
                       | |                 __/ |       | |   | |
                       |_|                |___/        |_|   |_|

Using Version 19.0.6964.0
Creating AppSourceCop.json for validation
Using Symbols Folder: C:\temp\notraefik1\_work\18\s\.packages
Downloading symbols: Microsoft_Application_19.1.31832.0.app
Url : http://172.25.158.117:7049/BC/dev/packages?publisher=Microsoft&appName=Application&versionText=19.0.0.0&tenant=default
Adding dependency to System Application from Microsoft
Adding dependency to Base Application from Microsoft
Downloading symbols: Microsoft_System_19.0.29480.31814.app
Url : http://172.25.158.117:7049/BC/dev/packages?publisher=Microsoft&appName=System&versionText=19.0.0.0&tenant=default
Downloading symbols: Microsoft_System Application_19.1.31832.0.app
Url : http://172.25.158.117:7049/BC/dev/packages?publisher=Microsoft&appName=System%20Application&versionText=19.1.0.0&tenant=default
Downloading symbols: Microsoft_Base Application_19.1.31832.0.app
Url : http://172.25.158.117:7049/BC/dev/packages?publisher=Microsoft&appName=Base%20Application&versionText=19.1.0.0&tenant=default
Compiling...
.\alc.exe /project:"c:\sources\MainApp Library" /packagecachepath:"c:\sources\.packages" /out:"c:\sources\.output\PublisherName_MainApp System Library_19.0.6964.0.app" /analyzer:C:\build\vsix\extension\bin\Analyzers\Microsoft.Dynamics.Nav.AppSourceCop.dll /analyzer:C:\build\vsix\extension\bin\Analyzers\Microsoft.Dynamics.Nav.UICop.dll /assemblyprobingpaths:"C:\Program Files (x86)\Microsoft Dynamics NAV\190\RoleTailored Client","C:\Program Files\Microsoft Dynamics NAV\190\Service","C:\Program Files (x86)\Open XML SDK\V2.5\lib","c:\Windows\Microsoft.NET\Assembly","C:\Test Assemblies\Mock Assemblies"
Microsoft (R) AL Compiler version 8.1.8.999
Copyright (C) Microsoft Corporation. All rights reserved

##[warning]c:\sources\MainApp Library\app.json(46,5): warning AL0667: 'applicationInsightsKey' is being deprecated in the versions: '7.2' or greater. This property is being deprecated in favor of 'applicationInsightsConnectionString'. This warning will become an error in a future release.
##[error]c:\sources\MainApp Library\app.json(46,5): error AL1040: The guid number '$(applicationInsightsKey)' does not match the expected pattern: "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$".
App generation failed with exit code 1
Removing container notraefik1-cloudrelease-nextminor
Removing notraefik1-cloudrelease-nextminor from container hosts file
Removing notraefik1-cloudrelease-nextminor-* from container hosts file
Removing C:\ProgramData\BcContainerHelper\Extensions\notraefik1-cloudrelease-nextminor
##[error]App generation failed with exit code 1

Didn't notice the Run-AlPipeline -applicationInsightsKey parameter was not getting any value, I didn't assign the variable $applicationInsightsKey


text:
add support for old devops URL format

Get-BcNugetPackage doesn't support old Azure DevOps URL format. This change adds it.

Btw. Azure Feed has been working great in DevOps for me for a few (two) years now. If you need any guidance or code Samples feel free to message me.

Thanks Kamil

source: gharchive/pull-request

authors: freddydk jonaswre kine


text:
Update LLVM from v10 to v12

While I was investigating llvm-symbolizer issues, I found that we are installing LLVM-10 by default.
Now that we are using the Ubuntu 20.04 image as the default, use the latest LLVM version available for that release. (In addition, v12 is also available on 22.04, whereas v10 is not.)

Codecov Report

Merging #2617 (9f643b9) into main (ff85b80) will decrease coverage by 4.97%.
The diff coverage is 17.94%.

:exclamation: Current head 9f643b9 differs from pull request most recent head b28e09f. Consider uploading reports for the commit b28e09f to get more accurate results

@@            Coverage Diff             @@
##             main    #2617      +/-   ##
==========================================
- Coverage   29.88%   24.91%   -4.98%
==========================================
  Files         290      121     -169
  Lines       35846    12533   -23313
==========================================
- Hits        10714     3122    -7592
+ Misses      25132     9411   -15721

Impacted Files
Coverage Δ

src/ApiService/ApiService/Functions/ReproVmss.cs
0.00% <0.00%> (ø)

src/ApiService/ApiService/Functions/Tasks.cs
22.22% <0.00%> (ø)

src/ApiService/ApiService/UserCredentials.cs
8.82% <8.33%> (+2.26%)
:arrow_up:

...ice/ApiService/onefuzzlib/EndpointAuthorization.cs
22.13% <11.11%> (-0.76%)
:arrow_down:

src/ApiService/ApiService/Functions/Jobs.cs
76.59% <100.00%> (ø)

src/ApiService/ApiService/OneFuzzTypes/Model.cs
72.05% <100.00%> (+0.07%)
:arrow_up:

src/agent/onefuzz-telemetry/src/lib.rs

...rc/agent/input-tester/src/test_result/fast_fail.rs

src/agent/onefuzz-task/src/local/cmd.rs

src/agent/stacktrace-parser/src/lib.rs

... and 165 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Passes check-pr.

authors: Porges codecov-commenter

repo: microsoft/onefuzz


text:
Use correct logger in values.py

Fixes #1211

Thank you for your contribution!

authors: AbhiByte justinchuby

repo: microsoft/onnxscript


text:
[torchlib] [ci] Fix failing external data tests for Windows

Fix failing external data tests for Windows due to file permission errors

Could you add a test to verify that calling numpy() etc. on a released tensor will still work (e.g. we can release and load again at will)? Thanks!

Windows crashes: Windows fatal exception: access violation
https://github.com/microsoft/onnxscript/actions/runs/10693258903/job/29643192895?pr=1834

Windows crashes: Windows fatal exception: access violation
https://github.com/microsoft/onnxscript/actions/runs/10693258903/job/29643192895?pr=1834

Failures seem to be unrelated.


text:
Break apart hcsv2.Host ModifySettings methods

Seperates all hvsv2.Host ModifySettings calls into seperate functions to make
growth easier when adding new entries.
Signed-off-by: Justin Terry (VM) juterry@microsoft.com

@kevpar - No changes just broke it apart.

repo: microsoft/opengcs


text:
[Alert manager] Add firing status to the cert expiration checker alert

Add "status": "firing" to the alert.
So the alert will be shown on the webportal home page.

Coverage remained the same at 33.818% when pulling 3c5e425e42e738df5640552b11b3101c60909d8e on yiyi/fix_alert_from_cert_expiration_checker into ce9b957018dae40418eb82ae375ef6d883501678 on master.

authors: coveralls yiyione

repo: microsoft/pai


text:
"Beta" logo is not clear on high contrast mode

Describe the bug
"Beta" logo on Chrome and Firefox is not complete
Steps to reproduce the behavior

Navigate to https://arcade.makecode.com/beta#editor
Click "More..." -> "High Contrast On" to open high contrast mode
Observe "beta" logo on top-left of the page

Expected behavior
"Beta" logo should be clear on high contrast mode
Actual behavior
"Beta" logo is not clear on high contrast mode

Desktop (please complete the following information)
OS: Windows
Machine build: 17763.1.amd64fre.rs5_release.180914-1434
Additional info
This bug repro on Edge, Chrome, Firefox & IE

fixed by https://github.com/microsoft/pxt/pull/5868

repo: microsoft/pxt-arcade


text:
fix: memory leak in makecode-browser

Right now we're spinning up a new worker on any request that needs a language service. This only takes ~50ms to spin up, but we're also leaving the old one around, increasing memory usage by ~5-10mb per compile
fix https://github.com/microsoft/vscode-makecode/issues/78
(and to confirm, this shouldn't have affected makecode-node at all as that spins up a new node process whenever you call into it from cli, correct?)

yeah, shouldn't affect node!

authors: jwunderl riknoll

repo: microsoft/pxt-mkc


text:
VScode is not completing my code.

 Environment data

Language Server version: 2023.1.20
OS and version: win32 x64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: true
python.analysis.typeCheckingMode: off

 Code Snippet

XXX

 Repro Steps

XXX

 Expected behavior
XXX
 Actual behavior
XXX
 Logs

XXX

Thanks for the report. Unfortunately, this is not enough information for us to investigate this issue.
If this continues to be a problem, would you please reopen the issue and add the information described in the troubleshooting guide?

repo: microsoft/pylance-release


text:
Having a pyproject.toml will break diagnosticSeverityOverrides in settings.json

Diagnostic severity overrides in user settings or workspace settings are ignored if the workspace also contains a pyproject.toml.
Environment data
Pylance v2024.6.101
Repro Steps

open an empty folder in VSCode
create a .vscode/settings.json file with the following contents{
    "python.analysis.diagnosticSeverityOverrides": {
        "reportUnknownParameterType": "warning"
    }
}

create a test.py file with contents:def test(x): ...

create an empty pyproject.toml file

Expected behavior

Actual behavior
No error or warning is reported.

Deleting pyproject.toml will fix the issue.
The same behavior applies to user settings.
This issue is not present in the current release version of pylance (2024.6.1).

thanks for reporting! I can repro in 6.101 & 6.102

This issue has been fixed in prerelease version 2024.6.103, which we've just released. You can find the changelog here: CHANGELOG.md

authors: KacieKK maflAT rchiodo


text:
Downloading Python-Language-Server too slowly in China?

When using the python plugin "ms-python.python" in vscode,Downloading Python-Language-Server too slowly in China?
It takes at least tens of minutes to download it?
Have you considered providing a cdn download address?
Or provide a guide on how to download and install it myself.
Downloading https://pvsc.azureedge.net/python-language-server-stable/Python-Language-Server-win-x64.0.5.30.nupkg...

Downloading https://pvsc.azureedge.net/python-language-server-stable/Python-Language-Server-linux-x64.0.5.30.nupkg...

I have the same problem,i could not download it

After download *.nupkg via Thunder, manually extract it to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30
unzip Python-Language-Server-linux-x64.0.5.30.nupkg -d ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30

Note that the version of Python-Language-Server and the version of ms-python are replaced with the currently used version.

After download *.nupkg via Thunder, manually extract it to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30
unzip Python-Language-Server-linux-x64.0.5.30.nupkg -d ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30

Note that the version of Python-Language-Server and the version of ms-python are replaced with the currently used version.

Unzip to the directory under windows system.
C:\Users\yourusername\.vscode\extensions\ms-python.python-2020.2.64397\languageServer.0.5.30

After download *.nupkg via Thunder, manually extract it to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30
unzip Python-Language-Server-linux-x64.0.5.30.nupkg -d ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30

Note that the version of Python-Language-Server and the version of ms-python are replaced with the currently used version.
Thanks ,i get it

After download *.nupkg via Thunder, manually extract it to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30
unzip Python-Language-Server-linux-x64.0.5.30.nupkg -d ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30

Note that the version of Python-Language-Server and the version of ms-python are replaced with the currently used version.

Unzip to the directory under windows system.
C:\Users\yourusername\.vscode\extensions\ms-python.python-2020.2.64397\languageServer.0.5.30

Thanks for your solution.
I extracted the .nupkg to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30 but vscode says:
[Error - 0:00:00 PM] Starting client failed
Launching server using command /Users/USERNAME/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30/Microsoft.Python.LanguageServer failed.

It's a MacOS Catalina 10.15.3 with vscode 1.14.2, and the file does exist. Is there anything that I missed?
Thanks!

After download *.nupkg via Thunder, manually extract it to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30
unzip Python-Language-Server-linux-x64.0.5.30.nupkg -d ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30

Note that the version of Python-Language-Server and the version of ms-python are replaced with the currently used version.

Unzip to the directory under windows system.
C:\Users\yourusername\.vscode\extensions\ms-python.python-2020.2.64397\languageServer.0.5.30

Thanks for your solution.
I extracted the .nupkg to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30 but vscode says:
[Error - 0:00:00 PM] Starting client failed
Launching server using command /Users/USERNAME/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30/Microsoft.Python.LanguageServer failed.

It's a MacOS Catalina 10.15.3 with vscode 1.14.2, and the file does exist. Is there anything that I missed?
Thanks!

Some problem!

链接: https://pan.baidu.com/s/1JOGlM_3zA4WMJXGpOuoa6A 提取码: fcr7

After download *.nupkg via Thunder, manually extract it to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30
unzip Python-Language-Server-linux-x64.0.5.30.nupkg -d ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30

Note that the version of Python-Language-Server and the version of ms-python are replaced with the currently used version.

Unzip to the directory under windows system.
C:\Users\yourusername\.vscode\extensions\ms-python.python-2020.2.64397\languageServer.0.5.30

Thanks for your solution.
I extracted the .nupkg to ~/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30 but vscode says:
[Error - 0:00:00 PM] Starting client failed
Launching server using command /Users/USERNAME/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30/Microsoft.Python.LanguageServer failed.

It's a MacOS Catalina 10.15.3 with vscode 1.14.2, and the file does exist. Is there anything that I missed?
Thanks!

chmod 777 /home/m/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30/Microsoft.Python.LanguageServer

@masx200 Thanks dude, thanks!
chmod a+x /home/yourusername/.vscode/extensions/ms-python.python-2020.2.64397/languageServer.0.5.30/Microsoft.Python.LanguageServer

did the trick.

I download nupkg file, but i donot know how to unzip it on window or install it

I download nupkg file, but i donot know how to unzip it on window or install it

use 7-zip to extract it

https://github.com/microsoft/vscode-python/issues/9324

microsoft/vscode-python#9324

thank you ！

There are steps in https://github.com/microsoft/python-language-server/blob/master/CONTRIBUTING.md how to set up LS as we do for debugging. Basically

download nuget package
create folder languageServer (does not have to be versioned)
rename .nupkg to .zip and unzip to the folder.
in VS Code set setting python.downloadLanguageServer to false.
in VS Code set setting python.jediEnabled to false.

Closing since CDN is not LS issue. Manual installation steps are above and in https://github.com/microsoft/python-language-server/issues/1698

我整理了一份文档，见 https://blog.csdn.net/feilinyongyuan/article/details/104964275

repo: microsoft/python-language-server


text:
Error standard output about the PermuteQubits function.

Description
As shown in the below testcase, there is an incorrect operation call in line 12. When executing the testcase, it reports an error normally. But the description of the error line in the output message is wrong. The error line should be 12 and 17 instead of 0. Is this a correct behavior of the QDK? Looking forward to your reply. Thank you!
Testcase
namespace NISLNameSpace {
    open Microsoft.Quantum.Intrinsic;
    open Microsoft.Quantum.Convert;
    open Microsoft.Quantum.Math;
    open Microsoft.Quantum.Logical;
    open Microsoft.Quantum.Canon;

    operation NISLOperation () : Unit {
        mutable NISLVariable8 = [0,1,3,2];
        use NISLVariable9 = Qubit[5];
        PermuteQubits(NISLVariable8,NISLVariable9);
    }

    @EntryPoint()
    operation main() : Unit {
        mutable result = NISLOperation();
    }
}

Output
Unhandled exception. Microsoft.Quantum.Simulation.Core.ExecutionFailException: The new ordering has an incorrect number of elements
    Expected:   5
    Actual: 4
 ---> Microsoft.Quantum.Canon.PermuteQubits on /home/nisl1/nisl8121/qx/quantumCompiler/compilerFuzzing/src/Fuzzing/qsharpPattern/D:\a\1\s\submodules\QuantumLibraries\Standard\src\Canon\CommonGates.qs:line 0
   at NISLNameSpace.NISLOperation on /home/nisl1/nisl8121/qx/quantumCompiler/compilerFuzzing/src/Fuzzing/qsharpPattern/Program.qs:line 0
   at NISLNameSpace.main on /home/nisl1/nisl8121/qx/quantumCompiler/compilerFuzzing/src/Fuzzing/qsharpPattern/Program.qs:line 0

Expected Output
Unhandled exception. Microsoft.Quantum.Simulation.Core.ExecutionFailException: The new ordering has an incorrect number of elements
    Expected:   5
    Actual: 4
 ---> Microsoft.Quantum.Canon.PermuteQubits on /home/nisl1/nisl8121/qx/quantumCompiler/compilerFuzzing/src/Fuzzing/qsharpPattern/D:\a\1\s\submodules\QuantumLibraries\Standard\src\Canon\CommonGates.qs:line 0
   at NISLNameSpace.NISLOperation on /home/nisl1/nisl8121/qx/quantumCompiler/compilerFuzzing/src/Fuzzing/qsharpPattern/Program.qs:line 12
   at NISLNameSpace.main on /home/nisl1/nisl8121/qx/quantumCompiler/compilerFuzzing/src/Fuzzing/qsharpPattern/Program.qs:line 17

Environment
Operating system: Windows 10
dotnet version: 3.1.408
QDK: 0.21.2111177148
Command
dotnet run

@QuXing9 With this test case you are hitting a runtime failure, specifically the following assertion fails due to 5 qubits being reordered but only 4 indices given: https://github.com/microsoft/QuantumLibraries/blob/5cb1f4323e8e81196fdd2a6e07867597c62a9ef2/Standard/src/Canon/CommonGates.qs#L305
What you are seeing in the error message is hence the stack trace of this exception, and based on what I see I think you are running this using our C# runtime. This means that the stack trace is generated based on the information in the C# code that the Q# program is translated into for this setup. While the C# generation makes some effort to propagate information about the original source code, in the end what we can do with that setup is somewhat limited and suboptimal. The way to full solve the problem and achieve a good debugging experience is by generating debug symbols. We would hence like to address this (only) as part of switching to a QIR-based stack, where we have indeed started looking at also emitting some amount of debug symbols.  I believe it is a good path to significantly improve cases such as this. However, local execution via QIR right now is not yet officially supported, and the move towards the new infrastructure will only happen gradually. How much of an issue has this been for you with the current setup?

Hello! @bettinaheim Thanks for your timely reply!
It has no effect on my work. I just want to know why this happens.
By the way, you mentioned that the Q# program is translated into C# code and the stack trace is generated based on the C# code. Could you tell me how Q# code is translated into C# code? My previous understanding of Q# program execution is that Q# programs are first compiled to QIR, and then use the C# runtime to support the execution of QIR code. But according to your description, it seems that Q# code isn‘t compiled to QIR but translated into C# code and run. Is that so?
Please forgive me if I misunderstood.

@bettinaheim Thanks! Your reply is very clear. It's very interesting and I will study Q# in depth.

repo: microsoft/qsharp-compiler


text:
Loading IsQscReference package fails if it contains DLLs with external references

When a package reference in a Q# project is tagged with IsQscReference="true", the compiler attempts to load all of the DLLs in the package to look for rewrite steps. This fails if the DLL has dependencies that are not included in the package, and the recommended solution is to redistribute all dependencies in the package itself so they can be loaded at the same time.
The problem is when a package includes DLLs with external dependencies that are not intended to be loaded as rewrite steps along side DLLs that are intended to be loaded. In this case, redistributing dependencies would unnecessarily increase the size of the package, but the compiler will fail to load the rest of the package if it contains any DLL that it cannot load.
See #428 for an example of this problem, which required working around the problem by manually ignoring a specific assembly name in the SDK. It would be nice to support these kinds of packages, maybe by allowing packages to explicitly specify which DLLs they want loaded as rewrite steps.

With PR #472 it is now possible/necessary to list which dlls should be loaded. I believe this is hence taken care of.

authors: bettinaheim samarsha


text:
scroll content with animation

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and microsoft/react-native-macos :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos :thumbsup:
[x] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Summary
This PR fixes the issue where the scrollbar does not move/animate when scrollToOffset/End is called.
Changelog

[macOS] [Fixed] - Fixes the issue where the scrollbar does not move/animate when scrollToOffset/End is called
Test Plan

https://user-images.githubusercontent.com/1132214/107857810-9afad400-6de5-11eb-942a-0fff9dc5b693.mov
Microsoft Reviewers: Open in CodeFlow

Just a heads up this failed the CI with an error that we intermittently hit. Very confident it's unrelated to your change so I kicked off another build that will hopefully succeed and then we can merge this in

Perhaps the magic number used as duration could be moved to the top of the file, but otherwise the change seems good to me 👍
One thing that would worry me slightly is the whitespace changes, which may make it harder to merge in upstream changes in the future, but I’ll defer to @HeyImChris on that.

I agree that it'd be great to move all constants to the top. As for the whitespace... it's definitely a noble change. Maybe we can make the same whitespace fixes upstream too so we don't hit merge problems later? @marty-wang

Perhaps the magic number used as duration could be moved to the top of the file, but otherwise the change seems good to me 👍
One thing that would worry me slightly is the whitespace changes, which may make it harder to merge in upstream changes in the future, but I’ll defer to @HeyImChris on that.

I agree that it'd be great to move all constants to the top. As for the whitespace... it's definitely a noble change. Maybe we can make the same whitespace fixes upstream too so we don't hit merge problems later? @marty-wang

will do

Btw, this fixes #706

Btw, this fixes #706

Thanks- merged!

authors: HeyImChris appden marty-wang

repo: microsoft/react-native-macos


text:
Include general C#/C++ developer documentation, clean up Native UI Components docs

Proposal: Improve the documentation about writing Native modules and Native UI modules

The code on Native UI Components is clearly a bad copy-paste and is broken => this should be fixed
The pages Native Modules and Native UI Components should link to the github sample pages
What each part of the code does should be documented because it is currently not understandable for C# and C++ beginners like I am.

@giregk I made some updates, could you take a look and see if those help? Would love to hear if there are more improvements we can make or what we can clarify.

Somewhat related to #62 in that we could benefit from having some general purpose resource links to guide people new to UWP development.

@asklar I read the whole documentation. It seems much better than the last time I read it. I saw answers to several questions I once had (such as handling asynchronous tasks in C++/winrt with which I struggled a lot). Thank you very much !

Thank you for following up @giregk - please reach out again if you need any more info!

authors: asklar chrisglein giregk stmoy

repo: microsoft/react-native-windows-samples


text:
Enable ARM64.

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and microsoft/react-native :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native :thumbsup:
[ ] I am making a fix / change for the macOS implementation of react-native
[x] I am making a change required for Microsoft usage of react-native

Description of changes
Adds macros to enable ARM64 compilation.
Microsoft Reviewers: Open in CodeFlow

Let's make sure to get this submitted to Facebook/folly too.  I am trying to get rid of the folly fork altogether.

authors: JunielKatarn acoates-ms

repo: microsoft/react-native


text:
dep-check: remove stale dependencies when upgrading react-native

dep-check should remove stale dependencies when upgrading react-native.
For instance, @react-native-community/async-storage was renamed to @react-native-async-storage/async-storage some time ago. When people are upgrading from 0.63 to 0.64, we resolve the storage capability to @react-native-async-storage/async-storage, but do not remove @react-native-community/async-storage.

When doing this, consider making a list of "known deprecated" dependencies that should be removed and storing that per profile. Each profile successively builds on the previous profile's list. That way, if you've left 0.63 and 0.64 behind a long time ago, and you upgrade to 0.68, you still get the cleanup which removes the now-defunct @react-native-community/aync-storage.

@afoxman @tido64 , Is someone already investigating it ? if not , can I take this up and investigate on it.

It's all yours 😄

authors: afoxman rohanprasadofficial tido64

repo: microsoft/rnx-kit


text:
Override canonical links for forked pages

SUMMARY
Insert a new "canonical" link for all pages in the /doc folder.
Technically, this inserts a new request for a link that is passed to the react-helmet plugin, which is smart enough to then override the default canonical link that Docusaurus normally provides.
(It's standard to have a canonical link even to the same page, because this ensures that e.g. /getting_started and /getting_started/ both resolve the same traffic.  In our case, we want this link to lead to the "real" rushstack site, even if the site being crawled is a deployed fork on GitHub Pages.)
Example of the new canonical link in action (use console to view meta tags): https://elliot-nelson.github.io/rushstack-websites/rushstack.io/pages/heft_tutorials/getting_started/

Note: for now, this plugin is relatively simple.  We may need to make it a bit smarter if we add versioning and/or translated pages in the future, but if necessary we can revisit when that time comes.

The PR description doesn't say what problem we are solving.
This is to discourage search indexes from crawling test deployments of the website, right?

authors: elliot-nelson octogonz

repo: microsoft/rushstack-websites


text:
Cloudant

@eddynaka @jameswinkler

            !groups.TryGetNonEmptyValue("host", out string host) ||

we should remove host

Refers to: Src/Plugins/Security/SEC101_015.AkamaiCredentialsValidator.cs:54 in 8da8d8e. [](commit_id = 8da8d8ec668518342b29e7bae0c2ceddf52804c5, deletion_comment = False)

authors: eddynaka michaelcfanning

repo: microsoft/sarif-pattern-matcher


text:
Josh

name: Feature request
about: Suggest an idea for this project

name: Feature request
about: Suggest an idea for this project

repo: microsoft/semantic-kernel


text:
.Net: New Feature: Support ResponseFormat in OllamaPromptExecutionSettings

name: Feature request
about: Suggest an idea for this project

Now as Ollama supports structured outputs, it's OllamaPromptExecutionSettings can support ResponseFormat similar to OpenAIPromptExecutionSettings

For anyone trying to be on the cutting edge with  these structured outputs, just use the OpenAI connector and change the client url to "localhost:xyzport/v1" and apikey "ollama". Then, OpenAI execution settings will still work even though it's making a request to the local instance.


text:
Using PORT as env in workbench app

This PR addresses #167
Update server configuration to use 'localhost' as the host and dynamically assign the port number

Using localhost won't break the app registration. I've tested and the login still works fine...

Using localhost won't break the app registration. I've tested and the login still works fine...

Appreciate the testing and verification of that!  Have you tried it with Codespaces as well?  This is the primary path we've suggested for folks who want to get a quick dev environment to try it out and hack on their own assistants.
We have a hosted version that we use for our team and others that has a different app registration with some customizations that we cannot modify under current Azure portal changes and some other places where we're explicit about using https://127.0.0.1:4000 that is some work to change, beyond what is visible in the repo.  Those are the things I need to check on before committing a change to the default behavior.

authors: bkrabach tommasodotNET

repo: microsoft/semanticworkbench


text:
Use cmake to find backtrace()

On FreeBSD, this notably requires the use of -lexecinfo, as backtrace()
is not available in -lc.  Rather than testing in C, test in cmake.

@schrodingerzhu is this okay with your android prototyping.

tested. it works fine for android.

authors: SchrodingerZhu mjp41 nwf

repo: microsoft/snmalloc


text:
As of latest preview version (1.13.10336.0), homedir alias (~) no longer recognized.

Windows Terminal version
1.13.10336.0
Windows build number
22000.466
Other Software
No response
Steps to reproduce
Open up Terminal Preview, drop down arrow to start a WSL distro session.
Expected Behavior
Session would open normally.
Actual Behavior
[error 2147942667 (0x8007010b) when launching `ubuntu.exe']
Could not access starting directory "~"

This was never supported; the starting directory was simply ignored for profiles like this.
Can you change the commandline from ubuntu.exe to wsl -d Ubuntu (or whatever the name of your Ubuntu distribution is?)

This was never supported; the starting directory was simply ignored for profiles like this.
Can you change the commandline from ubuntu.exe to wsl -d Ubuntu (or whatever the name of your Ubuntu distribution is?)

I didn't specifically set it to that, that I recall. I've only ever messed with those settings to set fonts, and to change the distro name.

AUGH! I think I know what's up. That's not gonna be great.
We changed the base WSL profile, and Ubuntu customizes it to set a different EXE. We try to detect which EXE is being launched, because if it's WSL we want to tell it about the special ~ starting directory.
Hmm. This needs some thought...

Go ahead and close this in favor of the bigger fish to fry. (I saw the localization bug. Thank you for your work on this, man! 🙏🏻)

Aw, thanks. :smile:
I'll keep this one open regardless.. it's gonna bite us, especially since this feature/misfeature is in stable.

@zadjii-msft should we BODGE in our own check that the starting directory is a literal ~ and .... just clear it? These distro launchers are being fragment-customized on top of their WSL profiles ...

Okay so team discussion:
If the startingDirectory is ~, and the commandline isn't wsl.exe, then drop the user in %userprofile%. Do this logic in ConptyConnection.

authors: DHowett akulbe zadjii-msft

repo: microsoft/terminal