Any chance to get a tutorial how to apply it to MFC app ?

How apply it to MFC app ?
There is a similar tutorial at:
https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands-cpp
But that was UWP so some details are not applicable here.

Truthfully, it isn't that different to doing this with UWP Xaml with WinUI 2.
The issue is that DesktopWindowXamlSource and WindowsXamlManager are experimental features that are only available in the experimental versions of WinUI 3.
As an example, if you run winmdidl on the 1.2 experimental 2 version of Microsoft.UI.Xaml.winmd, you can get:
[composable(Microsoft.UI.Xaml.Hosting.IDesktopWindowXamlSourceFactory, public, Microsoft.UI.Xaml.Hosting.HostingContract, 1.0)]
[contract(Microsoft.UI.Xaml.Hosting.HostingContract, 1.0)]
[experimental]
[marshaling_behavior(agile)]
[threading(both)]
runtimeclass DesktopWindowXamlSource
{
    [default] [experimental] interface Microsoft.UI.Xaml.Hosting.IDesktopWindowXamlSource;
    [contract(Microsoft.UI.Xaml.Hosting.HostingContract, 1.0)] [experimental] interface Windows.Foundation.IClosable;
}

and
[contract(Microsoft.UI.Xaml.Hosting.HostingContract, 1.0)]
[experimental]
[marshaling_behavior(agile)]
[static(Microsoft.UI.Xaml.Hosting.IWindowsXamlManagerStatics, Microsoft.UI.Xaml.Hosting.HostingContract, 1.0)]
[threading(both)]
runtimeclass WindowsXamlManager
{
    [default] [experimental] interface Microsoft.UI.Xaml.Hosting.IWindowsXamlManager;
    [contract(Microsoft.UI.Xaml.Hosting.HostingContract, 1.0)] [experimental] interface Windows.Foundation.IClosable;
}

These are the interfaces needed to host Xaml content in MFC, but notice how they have the experimental attribute? The WinUI 3 Xaml islands are not classed as ready for general usage right now.
If you have no issues with experimenting with experimental features, it takes a little more work, but it is still easy to get it to work. The biggest thing you need in addition is a class that derives from Microsoft.UI.Xaml.Application and implements IMetadataProvider. Although the metadata provider can be much simpler than a full Xaml application. It only needs to provide metadata for existing components, meaning you can just pass the metadata provider through.
If you want an example, I have no issues providing a fairly minimal Windows API example. It is easy enough to adapt that when you have all of the pieces.

Hello,
Thank for for hints.
Unfortunately with my current knowledge I'm not able to make it work.
I wanted to start with a simple setup. I followed that tutorial, trying to rework it with WinUI.
https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands-cpp
I forked repo
https://github.com/tomaszkot/WindowsAppSDK-Samples
New sln in in Samples\CustomControlsMFC\WinUIComponentCsToMFC.sln

created project MyUWPApp - Experimental Win3UI (c++)
created project MFCApplication1

Note: Currently app must be switched to x86 before compilation.
Currently there are such issues:

MFCApplication1 give compilation error :

cppwinrt : error Type 'Microsoft.UI.Xaml.Markup.IXamlMetadataProvider' could not be found
1>D:\Repos\WindowsAppSDK-Samples\Samples\CustomControlsMFC\packages\Microsoft.Windows.CppWinRT.2.0.220929.3\build\native\Microsoft.Windows.CppWinRT.targets(741,9): error MSB3073: The command ""D:\Repos\WindowsAppSDK-Samples\Samples\CustomControlsMFC\packages\Microsoft.Windows.CppWinRT.2.0.220929.3\build\native....\bin"cppwinrt @"D:\Repos\WindowsAppSDK-Samples\Samples\CustomControlsMFC\obj\x64\Debug\MFCApplication1\MFCApplication1.vcxproj.cppwinrt_ref.rsp"" exited with code 1.

If I temporarily remove MyUWPApp from a dependency list of MFCApplication1, previous  one is gone, but I get other one :
Severity	Code	Description	Project	File	Line	Suppression State
Error	C2039	'DesktopWindowXamlSource': is not a member of 'winrt::Windows::UI::Xaml::Hosting'	MFCApplication1	D:\Repos\WindowsAppSDK-Samples\Samples\CustomControlsMFC\MFCApplication1\MFCApplication1View.cpp	28

Summing up, hard way to start without a decent tutorial.

Okay. This sample uses a Windows API window.
It creates a window and loads a Xaml control from an embedded resource.
XamlIslandTest3.zip
It should be fairly easy to transfer the required parts into an MFC application. The important parts are the IslandApplication component and some method for getting the DesktopWindowXamlSource to filter any messages.

Thank you for this one.
When I try to build it I get:
Severity	Code	Description	Project	File	Line	Suppression State
Error	MIDL2072	[msg]inapplicable attribute [context]: Windows.Foundation.Metadata.ExperimentalAttribute [ RuntimeClass 'Microsoft.UI.Xaml.Application' ( RuntimeClass 'XamlIslandTest3.IslandApplication' ) ]	XamlIslandTest3	D:\tmp\XamlIslandTest3\XamlIslandTest3\XamlIslandTest3\IslandApplication.idl	9
I installed the stuff from beneath link and have experimental projects available when trying to add a new Project, but obviously I miss something.
https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/experimental-channel#version-12-experimental-120-experimental2

Thank you for further help.
I've machine with win10, was wondering it I can install SDK 10.0.22621.0 on it, tried and installation was fine,.
Then it compiled.
At the startup I got:
'This application requires the Windows App Runtime
Version 1.2-experimental2
(MSIX package version >= <IP_ADDRESS>)
Do you want to install a compatible Windows App Runtime now?'
So I installed it.
Now it's crashing at startup:
D:\a_work\1\s\dev\DynamicDependency\API\WinRTInprocModule.h(55)\Microsoft.WindowsAppRuntime.dll!7950A005: (caller: 79509AEE) Exception(1) tid(1eb8) 80004002 No such interface supported
Msg:[Error 0x80004002 in ifactory->QueryInterface(Microsoft.UI.Xaml.Media.AcrylicBrush)]
Exception thrown at 0x7555CC12 in XamlIslandTest3.exe: Microsoft C++ exception: wil::ResultException at memory location 0x009DC050.
Exception thrown at 0x7555CC12 in XamlIslandTest3.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
D:\a_work\1\s\dev\DynamicDependency\API\MddWinRT.cpp(54)\Microsoft.WindowsAppRuntime.dll!79504C50: (caller: 7950BBD9) ReturnHr(2) tid(1eb8) 80004002 No such interface supported
Msg:[D:\a_work\1\s\dev\DynamicDependency\API\WinRTInprocModule.h(55)\Microsoft.WindowsAppRuntime.dll!7950A005: (caller: 79509AEE) Exception(1) tid(1eb8) 80004002 No such interface supported
Msg:[Error 0x80004002 in ifactory->QueryInterface(Microsoft.UI.Xaml.Media.AcrylicBrush)]
So I suppose maybe win10  is not capable of running it.

The output for these projects is problematic since the Windows App SDK doesn't hesitate to use exceptions internally.
On a Windows 11 system, I get.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Users\Darran\source\repos\XamlIslandTest3\ARM64\Debug\XamlIslandTest3.exe'. Symbols loaded.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\gdi32full.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\ole32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\combase.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\dwmapi.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\oleaut32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140d.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\msvcp140d.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbased.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbased.dll'.
'XamlIslandTest3.exe' (Win32): Unloaded 'C:\Windows\System32\ucrtbased.dll'
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbased.dll'.
'XamlIslandTest3.exe' (Win32): Unloaded 'C:\Windows\System32\ucrtbased.dll'
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Users\Darran\source\repos\XamlIslandTest3\ARM64\Debug\Microsoft.WindowsAppRuntime.Bootstrap.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\shell32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\bcryptprimitives.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\uxtheme.dll'.
D:\a\_work\1\s\BuildOutput\Release\ARM64\WindowsAppRuntime_DLL\WindowsAppRuntimeInsights.h(53)\Microsoft.WindowsAppRuntime.Bootstrap.dll!00007FFFA5791CEC: (caller: 00007FFFA57919D0) LogHr(1) tid(9b8) 8007007E The specified module could not be found.
    Msg:[Unable to load resource dll. Microsoft.WindowsAppRuntime.Insights.Resource.dll]
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\clbcatq.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\AppXDeploymentClient.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Windows.ApplicationModel.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\WinTypes.dll'.
D:\a\_work\1\s\dev\WindowsAppRuntime_BootstrapDLL\MddBootstrap.cpp(814)\Microsoft.WindowsAppRuntime.Bootstrap.dll!00007FFFA578A9BC: (caller: 00007FFFA5789404) LogHr(2) tid(9b8) 80040010 Object is not in any of the inplace active states
    Msg:[Bootstrap.Intitialize: Scanning packages for Major.Minor=1.2, Tag=experimental2, MinVersion=<IP_ADDRESS>] CallContext:[\Initialize]
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Windows.StateRepositoryCore.dll'.
D:\a\_work\1\s\dev\WindowsAppRuntime_BootstrapDLL\MddBootstrap.cpp(923)\Microsoft.WindowsAppRuntime.Bootstrap.dll!00007FFFA578B188: (caller: 00007FFFA5789404) LogHr(3) tid(9b8) 80040012 Not able to perform the operation because object is not given storage yet
    Msg:[Bootstrap.Intitialize: Microsoft.WinAppRuntime.DDLM.2000.616.1852.0-a6-e2_2000.616.1852.0_arm64__8wekyb3d8bbwe is applicable (Major.Minor=1.2, Tag=experimental2, MinVersion=<IP_ADDRESS>)] CallContext:[\Initialize]
D:\a\_work\1\s\dev\WindowsAppRuntime_BootstrapDLL\MddBootstrap.cpp(914)\Microsoft.WindowsAppRuntime.Bootstrap.dll!00007FFFA578B104: (caller: 00007FFFA5789404) LogHr(4) tid(9b8) 80040011 Not able to convert object
    Msg:[Bootstrap.Intitialize: Microsoft.WinAppRuntime.DDLM.2000.616.1852.0-x6-e2_2000.616.1852.0_x64__8wekyb3d8bbwe not applicable. Architecture doesn't match current architecture arm64 (Major.Minor=1.2, Tag=experimental2, MinVersion=<IP_ADDRESS>)] CallContext:[\Initialize]
D:\a\_work\1\s\dev\WindowsAppRuntime_BootstrapDLL\MddBootstrap.cpp(914)\Microsoft.WindowsAppRuntime.Bootstrap.dll!00007FFFA578B104: (caller: 00007FFFA5789404) LogHr(5) tid(9b8) 80040011 Not able to convert object
    Msg:[Bootstrap.Intitialize: Microsoft.WinAppRuntime.DDLM.2000.616.1852.0-x8-e2_2000.616.1852.0_x86__8wekyb3d8bbwe not applicable. Architecture doesn't match current architecture arm64 (Major.Minor=1.2, Tag=experimental2, MinVersion=<IP_ADDRESS>)] CallContext:[\Initialize]
D:\a\_work\1\s\dev\WindowsAppRuntime_BootstrapDLL\MddBootstrap.cpp(946)\Microsoft.WindowsAppRuntime.Bootstrap.dll!00007FFFA578B560: (caller: 00007FFFA5789404) LogHr(6) tid(9b8) 80040013     Msg:[Bootstrap.Intitialize: Microsoft.WinAppRuntime.DDLM.2000.616.1852.0-a6-e2_2000.616.1852.0_arm64__8wekyb3d8bbwe best matches the criteria (Major.Minor=1.2, Tag=experimental2, MinVersion=<IP_ADDRESS>) of 95 packages scanned] CallContext:[\Initialize]
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\twinui.appcore.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\windows.storage.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\OneCoreUAPCommonProxyStub.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\SHCore.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\daxexec.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\userenv.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\container.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\usermgrcli.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Windows.StateRepositoryClient.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Windows.StateRepositoryPS.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\LicenseManagerApi.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\capauthz.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\ntmarta.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\shlwapi.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\propsys.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Windows.FileExplorer.Common.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\windowsudk.shellcommon.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\xmllite.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\OneCoreCommonProxyStub.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\vaultcli.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\profapi.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\cfgmgr32.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\edputil.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\urlmon.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\iertutil.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\netutils.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\srvcli.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\cldapi.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\sspicli.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\AppResolver.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\BCP47Langs.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\mpr.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\execmodelproxy.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.WindowsAppRuntime.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\rometadata.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\powrprof.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\powrprof.dll'.
'XamlIslandTest3.exe' (Win32): Unloaded 'C:\Windows\System32\powrprof.dll'
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\romd_arm64.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\umpdc.dll'.
onecore\base\appmodel\runtime\src\lookup.cpp(218)\kernelbase.dll!00007FF837385DE0: (caller: 00007FF8373E2A10) ReturnHr(1) tid(9b8) 8007007A The data area passed to a system call is too small.
onecore\base\appmodel\runtime\src\lookup.cpp(218)\kernelbase.dll!00007FF837385DE0: (caller: 00007FF8373E2A10) ReturnHr(2) tid(9b8) 8007007A The data area passed to a system call is too small.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.UI.Xaml.Controls.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\d2d1.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.ui.xaml.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\DWrite.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\d3d11.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\dxgi.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.Internal.FrameworkUdk.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\CoreMessaging.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\dcomp.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Microsoft.Internal.FrameworkUdk.System.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\twinapi.appcore.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\CoreMessagingXP.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Windows.UI.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\DXCore.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\ResourcePolicyClient.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Windows.UI.Immersive.dll'.
'XamlIslandTest3.exe' (Win32): Unloaded 'C:\Windows\System32\ResourcePolicyClient.dll'
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\directxdatabasehelper.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.Windows.ApplicationModel.Resources.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\MRM.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\qcdx8180.inf_arm64_df5df23ee5cd0b80\qcdx11arm64xum8180.dll'.
onecoreuap\windows\frameworkudk\mrtcore.cpp(388)\Microsoft.Internal.FrameworkUdk.System.dll!00007FFFDA46E80C: (caller: 00007FFF977A64F0) ReturnHr(1) tid(9b8) 80073D54 The process has no package identity.
D:\a\_work\1\s\dev\DynamicDependency\API\PackageGraphManager.cpp(219)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA58E8: (caller: 00007FFF98D9BDD4) ReturnHr(1) tid(9b8) 8007007A The data area passed to a system call is too small.
D:\a\_work\1\s\dev\DynamicDependency\API\WinRTInprocModule.h(55)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA6ED8: (caller: 00007FFF98DA6A54) Exception(1) tid(9b8) 80004002 No such interface supported
    Msg:[Error 0x80004002 in ifactory->QueryInterface(Microsoft.UI.Xaml.Media.AcrylicBrush)]
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.WindowsAppRuntime.Insights.Resource.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\qcdx8180.inf_arm64_df5df23ee5cd0b80\qcdxarm64xcompiler8180.DLL'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\cryptbase.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\D3DSCache.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\TextShaping.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\BCP47mrm.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\Windows.Globalization.dll'.
The thread 0x2754 has exited with code 0 (0x0).
Exception thrown at 0x00007FF8373C8D44 in XamlIslandTest3.exe: Microsoft C++ exception: wil::ResultException at memory location 0x00000099190F9790.
Exception thrown at 0x00007FF8373C8D44 in XamlIslandTest3.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
D:\a\_work\1\s\dev\DynamicDependency\API\MddWinRT.cpp(54)\Microsoft.WindowsAppRuntime.dll!00007FFF98DDF558: (caller: 00007FFF98DA9960) ReturnHr(2) tid(9b8) 80004002 No such interface supported
    Msg:[D:\a\_work\1\s\dev\DynamicDependency\API\WinRTInprocModule.h(55)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA6ED8: (caller: 00007FFF98DA6A54) Exception(1) tid(9b8) 80004002 No such interface supported
    Msg:[Error 0x80004002 in ifactory->QueryInterface(Microsoft.UI.Xaml.Media.AcrylicBrush)]
]
D:\a\_work\1\s\dev\UndockedRegFreeWinRT\catalog.cpp(348)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA9984: (caller: 00007FFF98DACF08) ReturnHr(3) tid(9b8) 80004002 No such interface supported
D:\a\_work\1\s\dev\UndockedRegFreeWinRT\catalog.cpp(334)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA999C: (caller: 00007FFF98DACF08) ReturnHr(4) tid(9b8) 80004002 No such interface supported
D:\a\_work\1\s\dev\UndockedRegFreeWinRT\urfw.cpp(244)\Microsoft.WindowsAppRuntime.dll!00007FFF98DACEE8: (caller: 00007FFF97E3A39C) ReturnHr(5) tid(9b8) 80004002 No such interface supported
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.UI.Windowing.Core.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\msctf.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\dcompi.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\marshal.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.UI.Composition.OSSupport.dll'.
'XamlIslandTest3.exe' (Win32): Unloaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.UI.Composition.OSSupport.dll'
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.UI.Composition.OSSupport.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\dwmcorei.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.InputStateManager.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\D3DCompiler_47.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\cryptsp.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.UI.Input.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\DataExchange.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\TextInputFramework.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Windows\System32\oleacc.dll'.
'XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_arm64__8wekyb3d8bbwe\Microsoft.DirectManipulation.dll'.
onecoreuap\windows\frameworkudk\dxprivatescommon.cpp(53)\Microsoft.Internal.FrameworkUdk.System.dll!00007FFFDA4623CC: (caller: 00007FFF977A6590) ReturnHr(2) tid(9b8) 80004002 No such interface supported
onecoreuap\windows\frameworkudk\dxprivatescommon.cpp(53)\Microsoft.Internal.FrameworkUdk.System.dll!00007FFFDA4623CC: (caller: 00007FFF977A6590) ReturnHr(3) tid(9b8) 80004002 No such interface supported
D:\a\_work\1\s\dev\DynamicDependency\API\WinRTInprocModule.h(55)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA6ED8: (caller: 00007FFF98DA6A54) Exception(2) tid(9b8) 80004002 No such interface supported
    Msg:[Error 0x80004002 in ifactory->QueryInterface(Microsoft.UI.Xaml.Controls.AnimatedIcon)]
Exception thrown at 0x00007FF8373C8D44 in XamlIslandTest3.exe: Microsoft C++ exception: wil::ResultException at memory location 0x00000099190F7AD0.
Exception thrown at 0x00007FF8373C8D44 in XamlIslandTest3.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
D:\a\_work\1\s\dev\DynamicDependency\API\MddWinRT.cpp(54)\Microsoft.WindowsAppRuntime.dll!00007FFF98DDF558: (caller: 00007FFF98DA9960) ReturnHr(6) tid(9b8) 80004002 No such interface supported
    Msg:[D:\a\_work\1\s\dev\DynamicDependency\API\WinRTInprocModule.h(55)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA6ED8: (caller: 00007FFF98DA6A54) Exception(2) tid(9b8) 80004002 No such interface supported
    Msg:[Error 0x80004002 in ifactory->QueryInterface(Microsoft.UI.Xaml.Controls.AnimatedIcon)]
]
D:\a\_work\1\s\dev\UndockedRegFreeWinRT\catalog.cpp(348)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA9984: (caller: 00007FFF98DACF08) ReturnHr(7) tid(9b8) 80004002 No such interface supported
D:\a\_work\1\s\dev\UndockedRegFreeWinRT\catalog.cpp(334)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA999C: (caller: 00007FFF98DACF08) ReturnHr(8) tid(9b8) 80004002 No such interface supported
D:\a\_work\1\s\dev\UndockedRegFreeWinRT\urfw.cpp(244)\Microsoft.WindowsAppRuntime.dll!00007FFF98DACEE8: (caller: 00007FFF97E3A39C) ReturnHr(9) tid(9b8) 80004002 No such interface supported
D:\a\_work\1\s\dev\DynamicDependency\API\WinRTInprocModule.h(55)\Microsoft.WindowsAppRuntime.dll!00007FFF98DA6ED8: (caller: 00007FFF98DA6A54) Exception(3) tid(9b8) 80004002 No such interface supported
    Msg:[Error 0x80004002 in ifactory->QueryInterface(Microsoft.UI.Xaml.Controls.CommandBarFlyout)]
Exception thrown at 0x00007FF8373C8D44 in XamlIslandTest3.exe: Microsoft C++ exception: wil::ResultException at memory location 0x00000099190F6C50.
Exception thrown at 0x00007FF8373C8D44 in XamlIslandTest3.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.

The thread 0x3798 has exited with code 0 (0x0).
The thread 0xc3c has exited with code 0 (0x0).
The thread 0x22d4 has exited with code 0 (0x0).
The thread 0x3720 has exited with code 0 (0x0).
The thread 0x250 has exited with code 0 (0x0).
The thread 0xee4 has exited with code 0 (0x0).
The thread 0x1474 has exited with code 0 (0x0).
The thread 0x1b04 has exited with code 0 (0x0).
The thread 0x1f98 has exited with code 0 (0x0).
The thread 0x387c has exited with code 0 (0x0).
The thread 0xf30 has exited with code 0 (0x0).
The thread 0x1a00 has exited with code 0 (0x0).
The thread 0x2c4c has exited with code 0 (0x0).
The thread 0x1ab8 has exited with code 0 (0x0).
The thread 0x1294 has exited with code 0 (0x0).
The thread 0x1778 has exited with code 0 (0x0).
The program '[13088] XamlIslandTest3.exe' has exited with code 0 (0x0).

For a successful run. I have the AcrylicBrush exception as well as two others (AnimatedIcon and CommandBarFlyout). So that isn't the issue. But after looking through the code again, I did find the issue. I did originally use it to test a couple of extra things, but I stripped them out. I missed one.
If you open mainwindow.cpp and check lines 87 and 88, you should find:
BOOL host_backdrop = TRUE;
THROW_IF_FAILED(DwmSetWindowAttribute(get_handle(), DWMWA_USE_HOSTBACKDROPBRUSH, &host_backdrop, sizeof(BOOL)));

This attribute is only available on Windows 11 21H2 and newer. For Windows 10, it would fail. It doesn't do anything for the application. My apologies about this.

Thank you, now it compiles and runs.
Now I grabbed the idl code you provided above  for DesktopWindowXamlSource put it into idl file in the project.
When trying to compile, lots of errors occured.
Added a reference to the C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.22621.0\Windows.winmd
Now it compiles for a while and gives:
...
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.22621.0\windows.web.http.diagnostics.httpdiagnosticscontract\<IP_ADDRESS>\windows.web.http.diagnostics.httpdiagnosticscontract.winmd
1>
1>midl : error MIDL9008: internal compiler problem - See documentation for suggestions on how to find a workaround.
1>midl: Assertion failed: node == nullptr, file com\rpc\midl\midlrt\metaread\metadataparser.cxx, line 216
1>Done building project "XamlIslandTest3.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

That is why, if you check the sample project that I gave, there is no extra reference to the Windows metadata.
I would have to double check, but I think it is C++/WinRT adding the metadata reference automatically. This means that there ends up being multiply defined symbols, and midlrt just gets really crashy in these cases.

Without adding that reference when trying to compile idl files I get:
Severity	Code	Description	Project	File	Line	Suppression State
Error	MIDL2025	[msg]syntax error [context]: expecting . near "("	XamlIslandTest3	D:\tmp\XamlIslandTest3\XamlIslandTest3\XamlIslandTest3\DesktopWindowXamlSource.idl	1
Error	MIDL2009	[msg]undefined symbol [context]: composable.Microsoft.UI.Xaml.Hosting.IDesktopWindowXamlSourceFactory	XamlIslandTest3	D:\tmp\XamlIslandTest3\XamlIslandTest3\XamlIslandTest3\DesktopWindowXamlSource.idl	1
Error	MIDL2009	[msg]undefined symbol [context]: Microsoft.UI.Xaml.Hosting.HostingContract	XamlIslandTest3	D:\tmp\XamlIslandTest3\XamlIslandTest3\XamlIslandTest3\DesktopWindowXamlSource.idl	1
Error	MIDL2025	[msg]syntax error [context]: expecting ] or , near "1.0"	XamlIslandTest3	D:\tmp\XamlIslandTest3\XamlIslandTest3\XamlIslandTest3\DesktopWindowXamlSource.idl	1
Error	MIDL2025	[msg]syntax error [context]: expecting . near "]"	XamlIslandTest3	D:\tmp\XamlIslandTest3\XamlIslandTest3\XamlIslandTest3\DesktopWindowXamlSource.idl	3
Error	MIDL2026	[msg]cannot recover from earlier syntax errors; aborting compilation	XamlIslandTest3	D:\tmp\XamlIslandTest3\XamlIslandTest3\XamlIslandTest3\DesktopWindowXamlSource.idl	4

Ok, in wanting to solve the midl error, I didn't read your post fully.
You don't have to use the IDL for DesktopWindowXamlSource or WindowsXamlManager. Just by referencing the Windows App SDK Nuget package, Visual Studio will reference all of the .winmd files in the Windows App SDK. The hosting classes, which DesktopWindowXamlSource and WindowsXamlManager are part of, are in Microsoft.UI.Xaml.winmd.
This is verifiable. If you set the Visual Studio build log to diagnostic, you can find the midl command line.

The command line contains the name of the response (.rsp) file.

This is the path on my system. It is relative to where the file is stored. This response file contains all of the references that midl uses. For my system, this file starts off as:
/reference "C:\Users\Darran\source\repos\XamlIslandTest3\packages\Microsoft.WindowsAppSDK.1.2.220909.2-experimental2\lib\uap10.0.18362\Microsoft.Foundation.winmd"
/reference "C:\Users\Darran\source\repos\XamlIslandTest3\packages\Microsoft.WindowsAppSDK.1.2.220909.2-experimental2\lib\uap10.0.18362\Microsoft.Graphics.winmd"
/reference "C:\Users\Darran\source\repos\XamlIslandTest3\packages\Microsoft.WindowsAppSDK.1.2.220909.2-experimental2\lib\uap10.0\Microsoft.UI.Text.winmd"
/reference "C:\Users\Darran\source\repos\XamlIslandTest3\packages\Microsoft.WindowsAppSDK.1.2.220909.2-experimental2\lib\uap10.0.18362\Microsoft.UI.winmd"
/reference "C:\Users\Darran\source\repos\XamlIslandTest3\packages\Microsoft.WindowsAppSDK.1.2.220909.2-experimental2\lib\uap10.0\Microsoft.UI.Xaml.winmd"

Where Microsoft.UI.Xaml.winmd is quite high up. The response file is used because of the Windows command line limit, so it is better to use a response file to pass in lots of command line options if the executable looks out for it. But it is equivalent to passing all of these options on the command line. I showed the runtime class definitions above to illustrate their presence, but it would be rare to want to use the in idl form. The idl definitions were extracted from the generated files, so they were incomplete.
C++/WinRT is the expected way to use WinRT these days, and midl references the metadata directly, so you don't need to have separate idl files to use the Xaml Island classes and interfaces in your own components. As an example, if the IslandApplication runtime class is modified as follows:
[default_interface]
runtimeclass IslandApplication : Microsoft.UI.Xaml.Application, IXamlMetadataContainer, Windows.Foundation.IClosable
{
	IslandApplication(Windows.Foundation.Collections.IVector<Microsoft.UI.Xaml.Markup.IXamlMetadataProvider> providers);
	protected IslandApplication();
	protected void Initialize();

	//note, this is now WindowsXamlManager
	Microsoft.UI.Xaml.Hosting.WindowsXamlManager WindowsXamlManager{ get; };
	Boolean IsDisposed{ get; };
};

then this idl file will compile with a warning. The warning is that since you are using an experimental type in a runtime class, the runtime class itself must be marked as experimental.
//add the experimental attribute to the runtime class
[experimental]
[default_interface]
runtimeclass IslandApplication : Microsoft.UI.Xaml.Application, IXamlMetadataContainer, Windows.Foundation.IClosable
{
	IslandApplication(Windows.Foundation.Collections.IVector<Microsoft.UI.Xaml.Markup.IXamlMetadataProvider> providers);
	protected IslandApplication();
	protected void Initialize();

	//note, this is now WindowsXamlManager
	Microsoft.UI.Xaml.Hosting.WindowsXamlManager WindowsXamlManager{ get; };
	Boolean IsDisposed{ get; };
};

That was actually the reason why I used IClosable there. The only useful operation on WindowsXamlManager is Close, InitializeForCurrentThread is a static and is used to create the instance. This means that the runtime class can reference IClosable and not require the experimental attribute. Obviously, doing this will require modifications to the IslandApplication.h and IslandApplication.cpp files.
C++/WinRT picks these classes up too. If you look at the Microsoft.UI.Xaml.Hosting.h file that C++/WinRT generates (it is under (project root)(platform)(configuration)\Generated Files, where project root is the directory where the .vcxproj is, you will find that C++/WinRT has generated wrappers for the runtime classes and interfaces there. The sample uses these particular classes directly. IslandApplication.h has a variable named m_xamlmanager of type winrt::Microsoft::UI::Xaml::Hosting::WindowsXamlManager. Using these types with C++/WinRT and the Windows App SDK packages doesn't require much else.
If you were trying to use the idl definitions because it wasn't clear that you didn't need to use them, then you don't need to use them. As mentioned, Visual Studio will reference the correct .winmd file automatically meaning midl and C++/WinRT will just automatically use them.
If you were trying to use the definitions because you cannot use C++/WinRT in your application, then that will require a completely different tutorial on how to generate the ABI headers for the Windows App SDK.

Thank you.
I then included the IslandApplication.idl file to my MFC project.
I made sure Windows SDK is 1.2.220930.4-preview2 tried to compile a got:

Then I reviewed properties of MFC project against XamlIslandTest3, did  a few changes, but the error still remains.
I updated repo with my recent changes, the project file is also attached here:
MFCApplication1.vcxproj.txt

As I said previously, Xaml Islands are currently an experimental feature. This means that they are only in experimental versions of the Windows App SDK. For 1.2, this means 1.2.220727.1-experimental1 and 1.2.220909.2-experimental2 only.
Also, are those just intellisense errors? Does the compile itself fail? The Visual C++ intellisense can be slow to pick up generated code.
If it is just intellisense errors, then just force Visual Studio to rescan the solution.

Selecting Rescan Solution will cause Visual Studio to dump all intellisense information and then rebuild it from the solution.

As I said previously, Xaml Islands are currently an experimental feature. This means that they are only in experimental versions of the Windows App SDK. For 1.2, this means 1.2.220727.1-experimental1 and 1.2.220909.2-experimental2 only.

Yes, I noticed that but did not update the post. I changed it to be  1.2.220909.2-experimental2, but still not helped.

Also, are those just intellisense errors? Does the compile itself fail? The Visual C++ intellisense can be slow to pick up generated code. If it is just intellisense errors, then just force Visual Studio to rescan the solution.

Sorry I did not provided exact error, no it's not intellisense , it's a compiler error:

Here is the solution you provided with that MFC project added:
XamlIslandTest3WithMFC.zip

Well, for the entire MFC thing. I didn't have a clue.
I installed the MFC libraries for Visual Studio, tried the project and it failed. I looked at the source around what was being shown, and I eventually noticed something:

Notice the colouring on TRY there? That means it is a definition of some kind, and in this case, it is a macro defined by MFC. So, I disabled precompiled headers for the MFC project, moved the C++/WinRT headers out of pch.h and into a separate header, then I included that into IslandApplication.cpp, replacing pch.h in that file. It compiled fine.
This is a simple case of the macros defined by MFC interfering with the C++/WinRT headers.
For the second case, try looking at this.

Thank you for a MFC hint, it really helped. Macros are evil.
But creation of instance of User Control still crashes.
I'm not sure what exactly was to be applied from the link you provided.
I already had an entry in manifest

Adding this was quite obvious as error was:
\XamlIslandTest3\Debug\Generated Files\winrt\base.h(6126)\XamlIslandTest3.exe!00F96D9A: LogHr(1) tid(a4c) 80040154 Class not registered
[get_activation_factory]
While the error I'm facing is:
XamlIslandTest3\Debug\Generated Files\winrt\base.h(6126)\XamlIslandTest3.exe!00636D9A: LogHr(1) tid(5fd4) 8007007F The specified procedure could not be found.
[get_activation_factory]
I added Microsoft.VCRTForwarders.140, but it did not helped.

Well, after having a little look at various pieces of documentation and inferring from there, it wasn't that hard to get it working.
If you look at the page that you linked for the component, you should have noticed how the C# component was registered:
<!--In order to host the C# component from C++, you must add the following Extension group and list the activatable classes-->
<Extensions>
    <Extension Category="windows.activatableClass.inProcessServer">
        <InProcessServer>
            <Path>WinRT.Host.dll</Path>
            <ActivatableClass ActivatableClassId="WinUIComponentCs.NameReporter" ThreadingModel="both" />
            <ActivatableClass ActivatableClassId="WinUIComponentCs.WinUIComponentCs_XamlTypeInfo.XamlMetaDataProvider" ThreadingModel="both" />
        </InProcessServer>
    </Extension>
</Extensions>

more specifically, the file name.
Using:
  <file name="WinRT.Host.dll">
    <activatableClass name="WinUIComponentCs.NameReporter" threadingModel="both" xmlns="urn:schemas-microsoft-com:winrt.v1"></activatableClass>
    <activatableClass name="WinUIComponentCs.NameReporterModel" threadingModel="both" xmlns="urn:schemas-microsoft-com:winrt.v1"></activatableClass>
    <activatableClass name="WinUIComponentCs.WinUIComponentCs_XamlTypeInfo.XamlMetaDataProvider" threadingModel="both" xmlns="urn:schemas-microsoft-com:winrt.v1"></activatableClass>
  </file>

as the registration free WinRT registration allows the component to load successfully. There is still a couple of things that I need to do to get things working again properly, but that is what normally happens when you have to reinstall Windows.

Thank you, that's exactly what I suspected is lacking

Tried it, changed settings.manifest into XamlIslandTest3.exe.manifest to workaround linker error, and it's crashing :/

That is curious.
Well, this is also one of the annoyances of working with code that you didn't write, also the sample was only ever written to show the initialisation of Xaml Islands.
Anyway, getting things in the right place is key. If you don't do that, and especially don't clean things up properly after you then it does get rather crashy. I guess this is still one of the reasons why Xaml Islands is considered  experimental.

Thx again I think we are close to resolve it.
I took the XamlIslandTest3.zip you posted 8 days ago and somehow the button created in the main_window::on_create is not visible in the main window.

I have the impression it due to the fact I'm using Win10.

So it's there but somehow not visible.
Weird...

So after forcing manually styles inside the C# control I was able to see it:

Yet, events are not arriving (can not focus textbox, can not click a button). There is a lot of low level stuff of there (window_base.cpp, main_window.cpp). I suppose some it it is not working.

Well, without knowing what you have and have not done then it is tough to say.
Since I am technically on holiday now, I'll give you a bit of a run through about how bad the entire situation is in general.
There is no really good source of information for Xaml Islands in general. The UWP Xaml Islands samples, which was the starting point of this work, are terrible.
The samples only provide enough to get UWP Xaml working, and the code itself is uncommented and doesn't work right anyway. When I started my great adventure into these uncharted waters, it was mostly as a hobby and a huge amount of time went into figuring the code out.
Anyway, as I stated, this sample isn't enough to get WinUI working. This is true of WinUI 3, and it was true for WinUI 2. So, work had to go into figuring out how to load WinUI 2.
After a bit of looking around, I found reference to the XamlApplication class in the Microsoft Community Toolkit. This is what IslandApplication is based upon. But this was one of the requirements to get WinUI loaded. Interestingly, this class also had its own problems. When I was originally figuring things out, I was working with composition in the same application. The XamlApplication class was actually using the presence of a DispatcherQueue to determine if the application was a desktop or UWP application.
The WinUI 3 work ended up being figuring out any differences between WinUI 2 and WinUI 3 and then changing the namespaces. There were some requirement differences. WinUI 2 needed to be loaded using the Dynamic Dependency API, the resources needed to be merged into the main resources.pri and there was also an interface difference. But this actually made working with WinUI 3 a bit easier.
While I was at it, I also ended up running into a few bugs too. For example, the Dynamic Dependency API included with the Windows App SDK has an issue where if you try to use the registry or a file to control the lifetime of the dependency, it throws an exception. This works fine with the Windows 11 built in API though. So obviously I had to report this.
Another bug that I ended up running into is in DesktopWindowXamlSource itself. There is an event named GotFocus which is documented to fire when the source receives focus. This never fires.
Anyway, I finally managed to get the time to update the project and upload it to GitHub. The repository is here. But be warned, I ran across another bug, this time it is in the WinUI 3  DesktopWindowXamlHost. The TakeFocusRequested event isn't firing, so this won't allow you to navigate out of a xaml source. This was part of the reason why I took so long to reply, I was also getting the original WinUI 2 sample into a form that could be used to show that the bug exists.

At my pc that middle  button is not visible:

After forcing styles it's working a bit - sometimes is visible , sometimes disappears (if I click it).
Most likely win10 related issue - maybe someone having win10 could confirm that.
I'm going to wait for  a official release from Microsoft, currently there is too much effort needed, and to much low level windows messaging related code involved.
Talking about examples quality that repo (subfolder XamlIslands-master\1903_Samples\CppWinRT_Win32_App) has a code that tries to create a User Control with a different approach - it's created inside Windows Runtime Component.
Code in win32 app is like:
 m_managedControl = winrt::SampleLibraryCS::CustomUserControl();         m_managedControl.Height(ButtonHeight / dpi);         m_managedControl.Width(ButtonWidth / dpi);         m_hWndXamlButton1 = wil::unique_hwnd(CreateDesktopWindowsXamlSource(WS_TABSTOP, m_managedControl));
Yet, app is crashing at the startup.
It seemed to me a trick mentioned there (adding
true to the proj) would help , but it is still not working.

As a proof if that is a win10/11 issue I tried to compile it on win11 machine but got:
Joanna, 14:19
Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB4062	The "Microsoft.Build.Packaging.Pri.Tasks.ExpandPriContent" task could not be loaded from the assembly C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.Build.Packaging.Pri.Tasks.dll. Could not load file or assembly 'file:///C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.Build.Packaging.Pri.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the  declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.	XamlIslandTest3	C:\Users\Joanna Karnas\Desktop\testTomekKot\XamlIslandTest3\XamlIslandTest3\packages\Microsoft.WindowsAppSDK.1.2.220909.2-experimental2\build\MrtCore.PriGen.targets	911
Also tried a hint from https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/experimental-channel

Using dotnet build with a WinAppSDK C# class library project may see a build error "Microsoft.Build.Packaging.Pri.Tasks.ExpandPriContent task could not be loaded". To resolve this issue set true in your project file.

but it's still not compiling.

From the XamlIslandTest3 build output with the log file set to Diagnostic on Windows 11:
1>Target "AddPriPayloadFilesToCopyToOutputDirectoryItems" in file "C:\Users\Darran\source\repos\XamlIslandTest3\packages\Microsoft.WindowsAppSDK.1.2.220909.2-experimental2\build\MrtCore.PriGen.targets":
1>  Using "ExpandPriContent" task from assembly "D:\Programs64\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\\Microsoft.Build.Packaging.Pri.Tasks.dll".
1>  Task "ExpandPriContent"
1>    Task Parameter:MakePriExeFullPath=C:\Users\Darran\source\repos\XamlIslandTest3\packages\Microsoft.Windows.SDK.BuildTools.10.0.22621.1\bin\10.0.22621.0\x64\makepri.exe
1>    Task Parameter:IntermediateDirectory=x64\Debug\
1>    Task Parameter:ExcludeXamlFromLibraryLayoutsWhenXbfIsPresent=True
1>    Task execution duration: 287 ms.
1>  Done executing task "ExpandPriContent".
1>Done building target "AddPriPayloadFilesToCopyToOutputDirectoryItems" in project "XamlIslandTest3.vcxproj".

There is a few more using that library, but it is loading and using the pri tasks library without issue. So, are you sure this is a Windows problem?
Both versions of Windows 11 (initial release and 22H2) have no issue building here at all. I also don't have a particularly complex Visual Studio install either.

So, are you sure this is a Windows problem?

I might not described problems precisely. So there are two separate problems:

The application is not working on  win10 machines. I tested it on two machines and on both that User Control is not rendered (without forcing styles).

There are some 'No such interface supported' messages in the output, maybe they are saying it's basically not meant to be run on win10.

XamlIslandTest3.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.2-experimental2_2000.616.1852.0_x64__8wekyb3d8bbwe\MRM.dll'.
onecoreuap\windows\frameworkudk\mrtcore.cpp(388)\Microsoft.Internal.FrameworkUdk.dll!00007FFF5F7656D8: (caller: 00007FFF5F79F08D) ReturnHr(1) tid(6448) 80073D54 The process has no package identity.
D:\a_work\1\s\dev\DynamicDependency\API\PackageGraphManager.cpp(219)\Microsoft.WindowsAppRuntime.dll!00007FFF60C7B41E: (caller: 00007FFF60C71C59) ReturnHr(1) tid(6448) 8007007A The data area passed to a system call is too small.
D:\a_work\1\s\dev\DynamicDependency\API\WinRTInprocModule.h(55)\Microsoft.WindowsAppRuntime.dll!00007FFF60C7CCEC: (caller: 00007FFF60C7C38A) Exception(1) tid(6448) 80004002 No such interface supported
Msg:[Error 0x80004002 in ifactory->QueryInterface(Microsoft.UI.Xaml.Media.AcrylicBrush)]
D:\a_work\1\s\dev\DynamicDependency\API\MddWinRT.cpp(54)\Microsoft.WindowsAppRuntime.dll!00007FFF60CADD55: (caller: 00007FFF60C7EC1F) ReturnHr(2) tid(6448) 80004002 No such interface supported
Msg:

Compilation problem on win11 - I have limited access to this machine, but I'd try to get more info soon.

I finally got it working on Win11. Initially I did not have that Experimental  Windows App SDK.
Summing up (to get idea without reading the whole thread):

It works on Win11
Requires Experimental  Windows App SDK
Requires quite a lot of custom code that you had to figure out and provided in the XamlIslandTest3 project

Tried again with [Windows App SDK, looks like it could work but there is strange exception, code at: https://github.com/microsoft/WindowsAppSDK-Samples/issues/328


Sometimes subtitles are stacked on LG SmartTVs

Have you read the FAQ and checked for duplicate open issues?
Yes.
What version of Shaka Player are you using?
Latest.
Can you reproduce the issue with our latest release version?
Yes.
Can you reproduce the issue with the latest code from master?
Yes.
Are you using the demo app or your own custom app?
Own app.
If custom app, can you reproduce the issue using our demo app?
Not tried.
What browser and OS are you using?
SmartTV
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
LG SmartTV
What are the manifest and license server URIs?

What did you do?

Playback a stream with active subtitles

What did you expect to happen?

Subtitles are properly shown.

What actually happened?
Subtitles are shown stacked. Sometimes one subtitle is shown without removing the previous one.

JFYI, Chrome, Edge, and Safari all get this wrong in their native cue rendering.  FF & IE/legacy Edge get it right.
I filed these issues with the browser vendors to make the same/similar fix in the browser for native cue display:

https://bugs.chromium.org/p/chromium/issues/detail?id=1178026
https://bugs.webkit.org/show_bug.cgi?id=221854


Faster-whisper fails due to CUDA compatibility with CTranslate2

https://github.com/SYSTRAN/faster-whisper/issues/1086
Apparently adding
!pip install ctranslate2==4.4.0 fixes this, but I wanted to ask if this should be something added to stable-ts or if everyone using stable-ts should just wait for an upstream fix from here or from faster-whisper.
Thanks!

As mentioned here: https://github.com/SYSTRAN/faster-whisper/pull/1082#issuecomment-2437214073
It will be best to wait for an upstream fix. I'll pin this issue for now.
Thanks for bringing this up.


Fix README example for server function

Closing, docs seem still WIP, fixes like this can be annoying


Added option to run a Dangerfile from a branch and/or path when using a remote repo

Problem
Having a centralized Dangerfile for several projects inside an organization. As the branch and path where hardcoded to master and Dangerfile respectively, achieving this goal demanded too many repositories to be created, making it hard to mantain and a hassle hard to test changes on Dangerfiles without needing to create new repositories or risking breaking all builds.
Solution
import_dangerfile_from_github receives the repo slug to create the download URL, so 2 new optional parameters were added for the branch and path be set, keeping master and Dangerfile as the default values.

          1 Message

  :book:
  @felipesabino is not a contributor yet, would you like to join the Danger org?

  Generated by :no_entry_sign: danger

@felipesabino want to be in the org?

@felipesabino want to be in the org?

@orta sure, this would awesome

invited, and merging


Helm Chart Volume Configuration "ReadWriteOnce" Doesn't Work with Multiple Pods

My actions before raising this issue

[X] Read/searched the docs
[X] Searched past issues

When using the Helm Chart, the storage.yml ReadWriteOnce option under the backend folder structure doesn't work in my K8s environment. If you have deployments across multiple nodes, ReadWriteOnce will form a race condition causing only one backend pod to start successfully. ReadWriteOnce by definition only allows one node to mount - so how is this supposed to work?
Steps to Reproduce (for bugs)

Attempt to deploy the helm chart to Kubernetes with the default storage

Expected Behaviour

The defaults for the helm chart should be able to launch CVAT in K8s with the minimal amount of modification.

Current Behaviour

Possible Solution

Changing storage.yml to ReadWriteMany
Put all backend deployments into the same node (maybe there's a reason this isn't designed this way though)

Do we actually need these pods to all share storage? Or can they each be granted individual PVCs for each instance of the server/utils/workers pods? Sharing a cache a la volumes seems like a poor design choice so I question if this is just an assumption made in the docker-compose configuration and just found it's way into the helm chart.

I'm unsure why it is needed that all share the same claim. Maybe someone more familiar with the chart knows? It might have some unintended consequences if we remove it.


Code coverage with coveralls failing

Coveralls is not working in appveyor and gives me a failed build.
An opencoverCoverage.xml is generated successfully.
However, the problem is that appveyor will not even run .\tools\csmacnz.Coveralls.exe --help.
Response:
Usage:
  csmacnz.Coveralls (--opencover | --dynamiccodecoverage | --monocov | --exportcodecoverage | --chutzpah | --lcov | --ncover | --reportgenerator | --multiple) -i ./opencovertests.xml (--repoToken <repoToken> | [--repoTokenVariable <repoTokenVariable>]) [-o ./opencovertests.json] [--dryrun] [--useRelativePaths [--basePath <path>] ] [--commitId <commitId> --commitBranch <commitBranch> [--commitAuthor <commitAuthor> --commitEmail <commitEmail> --commitMessage <commitMessage>] ] [--jobId <jobId>] [--serviceName <Name>] [--serviceNumber <Number>] [--pullRequest <pullRequestId>] [--treatUploadErrorsAsWarnings] [--parallel]
  csmacnz.Coveralls --version
  csmacnz.Coveralls --help
Command exited with code 1

I have tried using:
(in the test_script in appveyor.yml)
.\tools\csmacnz.Coveralls --help (Error message above)
.\tools\csmacnz.coveralls --help (Error message above)
.\tools\csmacnz.Coveralls.exe --help (Error message above)
.\tools\csmacnz.coveralls.exe --help (Error message above)
Same thing with this:
$coveralls = ".\tools\csmacnz.coveralls.exe"
& $coveralls --help

csmacnz.Coveralls --help (The term 'csmacnz.Coveralls' is not recognized)
All of these work fine when tested locally in PowerShell.

This issue was solved by using codecov instead of coveralls.


Remove the extra position added to undo list while using Shift key

An extra position was added to the undo list when text was entered using Shift key.
This PR will fix #8259

Maintainer merge checklist

[x] Title is descriptive/clear for inclusion in release notes.
[x] Applied a Component: xxx label.
[x] Applied the api-deprecation or api-break label.
[x] Applied the release-highlight label to be highlighted in release notes.
[x] Added to the milestone version it was merged into.
[ ] Unittests are included in PR.
[ ] Properly documented, including versionadded, versionchanged as needed.

@atharva-satpute thanks 👍

Please someone explain me how to use Kivy after that change? Is enough to download textinput.py and replace in directory or I have to reinstal whole Kivy?
Thanks.

https://github.com/RadoslawGlebicki if you need support raise a discussion


Error running devbox

Following #164 I wanted to give ruby a try but can't make it work (although does not seem to be related to ruby at all).
No idea what to check so pasting everything I did. Any idea?
devbox.json
{
  "packages": [
    "ruby_3_1"
  ],
  "shell": {
    "init_hook": null
  }
}

then running devbox returns
devbox shell
Installing nix packages. This may take a while...
Starting a devbox shell...
bash: command substitution: line 46: syntax error near unexpected token `newline'
bash: command substitution: line 46: `			$NIX_STORE/*'

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
(devbox) bash-3.2$ ruby -v
bash: ruby: command not found

hmm, that's odd (and does seem unrelated to ruby).
my guess is the shell is trying to load some .bash_profile script or something like that, and failing.
but i'm also curious if some other planner is affecting things. what's the output of devbox plan?

$ devbox plan
{
  "dev_packages": [
    "ruby_3_1"
  ],
  "runtime_packages": [
    "ruby_3_1"
  ],
  "install_stage": {
    "command": ""
  },
  "build_stage": {
    "command": ""
  },
  "start_stage": {
    "command": ""
  }
}

Hmm ok that's as expected.
Does the problem still happen before trying it with ruby?
What's your OS? do you have any profile scripts, and if so, does the problem persist if you disable them? does the problem happen with different shells? looks like bash 3.2 is kinda old (from 2006... latest is 5.2)--is there any reason why you're using such an old shell?

same error with python example, so I guess related to my shell.

is there any reason why you're using such an old shell?

haha. am using what Mac OS provides on my good old trusty iMac. I'll try again on most recent laptop if not supported.


feat(fis): Adding the admin.installations() API for deleting Firebase installation IDs

Added the new admin.installations() API.
Deprecated the existing admin.instanceId() API. The implementation of this API now just invokes the installations API under the hood.
The admin.instanceId() retains backward compatibility by converting the FirebaseInstallationsError raised by the new implementation to the old FirebaseInstanceIdError type. Error codes are the same, but the error message may defer.

go/firebase-admin-fis

Thanks @egilmorez. I've responded to your comments. PTAL.


Type hints and type stubs

120 symbols line

Pull Request Test Coverage Report for Build 325

30 of 30 (100.0%) changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 324:
0.0%

Covered Lines:
360

Relevant Lines:
360

💛  - Coveralls

Pull Request Test Coverage Report for Build 325

30 of 30 (100.0%) changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 324:
0.0%

Covered Lines:
360

Relevant Lines:
360

💛  - Coveralls

Pull Request Test Coverage Report for Build 325

30 of 30 (100.0%) changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 324:
0.0%

Covered Lines:
360

Relevant Lines:
360

💛  - Coveralls

Pull Request Test Coverage Report for Build 325

30 of 30 (100.0%) changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 324:
0.0%

Covered Lines:
360

Relevant Lines:
360

💛  - Coveralls

Pull Request Test Coverage Report for Build 325

30 of 30 (100.0%) changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 324:
0.0%

Covered Lines:
360

Relevant Lines:
360

💛  - Coveralls

Pull Request Test Coverage Report for Build 325

30 of 30 (100.0%) changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 324:
0.0%

Covered Lines:
360

Relevant Lines:
360

💛  - Coveralls


Payouts Pallet

What's keeping this PR as a draft?

Now it's not a Draft, the PR is ready for review


Latvia's Magnitsky Law Sanctions List

The first working version of the Latvia's Magnitsky Law Sanctions List.

Very nice work! Thank you.


Pipeline changes

Changes include:

Repo list is based on the current user, not the project owner that enables project pipeline.
Branch selection(both UI/yaml) is to determine where the pipeline file locates, and is different from the branch conditions in pipeline files.
Add missing event trigger configuration for a repository.
Secrets can be in the pipeline namespace so that the distribution scope is smaller.
A manual run is done by UI, the Git CLI way is included in the webhook triggered runs.
Change the word admin permission to more generic webhook management permission, since admin is specific to Github.

LGTM


In README, correct mentioned GHC version

It's not anymore true that GHC 7.8 is the default for developers.

Excellent, thanks!


website redesign

The site badly needs a redesign, the current one isn't very professional

At least two sections should be added in a new design:

FAQ
About (the project)

There is also an idea to refactor current sections and make a "Community" section. Any ideas are welcome!


Does CompressAI support direct compression of [y] instead of [y-mean]?

As stated, how can we use CompressAI to compress [y] instead of [y-mean]. Furthermore, how can we understand the advantages of compressing [y-mean]? Thank you very much for your answer!!!

round(y-means) == round(y) if means = 0.  (Or means == None works too.)
For example, just set means=None when using the desired entropy model:
        y_hat, y_likelihoods = self.gaussian_conditional(y, scales_hat, means=means_hat)

In terms of advantages, that depends on the situation. If the source y has its most-likely-value occurring exactly at the mean, then [y - mean] will probably produce less reconstruction error since we can then reconstruct the most-likely-value with exact precision. On the other hand, if the actual values occur at locations other than the mean, then both methods will produce similar results. So... it depends.

Somewhat related concept: the deadzone quantizer used by JPEG allows near-zero DCT-transformed-and-rescaled coefficients to be rounded to zero, which helps reduce the rate since the most-likely-symbols are near zero, and reconstructing them as zero is worth the R-D tradeoff.

Great answer! Thanks a lot! In general, compressing [y-mean] achieves better R-D tradeoff. However, in some cases, we have to compress [y] whose mean is not none. For example, in Checkerboard Context Model, we should compress [y] for one-pass encoding, and compressing [y-mean] leads to two-pass encoding. Can you make some suggestions for AE/AD of [y] using CompressAI?Thank you very much for your answer!!!

As stated, how can we use CompressAI to compress [y] instead of [y-mean]. Furthermore, how can we understand the advantages of compressing [y-mean]? Thank you very much for your answer!!!

Hello, I would like to ask you a question about the installation of compressai “Successfully installed compressai-1.2.4.dev0” . I successfully installed cmpressai, but I got the following error when importing:

import compressai
Traceback (most recent call last):
File "", line 1, in
File "F:\compressai\compressai_init_.py", line 30, in
from compressai import (
File "F:\compressai\compressai\latent_codecs_init_.py", line 38, in
from .rasterscan import RasterScanLatentCodec
File "F:\compressai\compressai\latent_codecs\rasterscan.py", line 38, in
from compressai.ans import BufferedRansEncoder, RansDecoder
ImportError: DLL load failed while importing ans: 找不到指定的程序。


pkg/security/OWNERS: add auth team

This updates the auth team to be owners of the security package which mostly includes ldap helpers.
/cc @sttts

/lgtm
/approve


Re-enable use our app experiment

Task/Issue URL: https://app.asana.com/0/1125189844152671/1200123506690912
Tech Design URL:
CC:
Description:
This PR re-adds the code removed in https://github.com/duckduckgo/Android/pull/924 to re-enable the use our app experiment.
Before testing
In AppUserStageStore lines 83 and 84 change the code to:
val days = TimeUnit.MILLISECONDS.toSeconds(System.currentTimeMillis() - appInstallStore.installTimestamp)
if (days >= 30) {

You will be now moved out of the onboarding stage after 30 seconds from install whenever you resume the app.
In AndroidNotificationScheduler lines 77 and 89 change the code to be 40 and TimeUnit.SECONDS. Also change the line 58 to be:
scheduleNotification(OneTimeWorkRequestBuilder<PrivacyNotificationWorker>(), 40, TimeUnit.SECONDS, UNUSED_APP_WORK_REQUEST_TAG)

The notifications will be now triggered after 40 seconds.
Go to CtaViewModel lines 259 & 260 and change them to:
val days = TimeUnit.MILLISECONDS.toMinutes(System.currentTimeMillis() - timestampKey.timestamp)
return (days >= 1)

This will now trigger the second CTA after 1 minute rather than 2 days.
Steps to test this PR:
Variant mc - In App usage flow
Hardcode the variant to use mc
Normal flow

Install and launch the app.
Go to SERP.
You should see the SERP CTA, press Phew.
Stay in that screen for at least 40 seconds.
The new in-app usage notification should show up.
Pixel mnot_s_uoa should be sent (notification seen)
Tap the notification.
Pixel mnot_l_uoa should be sent (notification launched)
Home screen should show, the keyboard should be hidden and a the new cta should shown.
Tap on "Add Facebook Shortcut".
Pixel m_uoa_d_ok should be sent (use our app ok button pressed)
Pixel m_uoa_van should be sent (use our app site visited after notification seen)
Add the shortcut
Pixel m_uoa_s_a should be sent. (use our app shortcut added)
A toast message saying the shortcut was added should show (message can vary depending on the device).
Sign in to Facebook
The fireproof dialog should be shown
Close the facebook tab and navigate to facebook again.
Pixel m_uoa_vas should be sent (use our app site visited after adding shortcut).
After a minute (or whatever time you set in CtaViewModel the next time you navigate to Facebook (page has to load) you should see a new Cta.
Pixel m_uoa_dd should be sent (use our app delete dialog seen)
Close the facebook tab and open facebook again in a new tab.
Pixel m_uoa_vad should be sent (use our app site visited after delete cta).

Clicking the notification moves you out of the onboarding

Install and launch the app.
Go to SERP.
You should see the SERP CTA, press Phew.
Stay in that screen for at least 40 seconds.
The new in-app usage notification should show up.
Notice the day 1 privacy notification does not show up.
Click on the notification, you should be taken to a new tab showing the hombre screen with the new CTA.
Ignore the CTA (click Not now) and go to instagram.com.
You should not see any onboarding CTAs since you are not in the onboarding stage anymore.

After X time you are moved out of the onboarding

Install and launch the app.
Go to SERP.
You should see the SERP CTA, press Phew.
Stay in that screen for at least 30 seconds (if you see the in app usage notification do not interact with it or change the timing to a higher value so you don't see it).
Send the app to the background or kill the app.
Relaunch the app
Go to instagram.com
You should not see any onboarding CTAs since you are not in the onboarding stage anymore.

Hiding tips does not show the notification

Install and launch the app.
Go to SERP.
You should see the SERP CTA, click hide tips and hide them forever.
Stay in that screen for at least 40 seconds
You should not see any notifications.

Variant mb - Removes onboarding and day1/3 notifications
Hardcode the variant to use mb
After X time you are moved out of the onboarding and no notifications are scheduled

Install and launch the app.
Go to SERP.
You should see the SERP CTA, press Phew.
Stay in that screen for at least 40 seconds.
No notifications should be shown.
Send the app to the background or kill the app.
Relaunch the app
Go to instagram.com
You should not see any onboarding CTAs since you are not in the onboarding stage anymore.

Pixels and tabs

Launch the app .
Go to facebook.com
Pixel m_uoa_v should be sent.
In the menu click Add to Home.
The Add to Home Screen dialog should show with a high-res icon.
Click in Add.
Pixel m_uoa_s_a should be sent
Login to facebook.
The fireproof dialog should be shown or not depending on your settings.
On Facebook, navigate to your notifications.
Kill the app.
Open the shortcut you just created.
Pixels m_sho_uoa_o and m_uoa_v should be sent.
The notifications tab you had opened before should be opened instead of a new tab.
Close the tab and send the app to the background.
Open the shortcut.
A new tab should be created pointing to facebook.com

Variant ma - Control
Hardcode the variant to use ma
Notification and onboarding

Install and launch the app.
Go to SERP.
You should see the SERP CTA, press Phew.
Stay in that screen for at least 40 seconds.
The privacy notification should be shown.
Send the app to the background or kill the app.
Relaunch the app
Go to instagram.com
You should see a CTA.

Pixels and tabs

Launch the app .
Go to facebook.com
Pixel m_uoa_v should be sent.
In the menu click Add to Home.
The Add to Home Screen dialog should show with a high-res icon.
Click in Add.
Pixel m_uoa_s_a should be sent
Login to facebook.
The fireproof dialog should be shown or not depending on your settings.
On Facebook, navigate to your notifications.
Kill the app.
Open the shortcut you just created.
Pixels m_sho_uoa_o and m_uoa_v should be sent.
The notifications tab you had opened before should be opened instead of a new tab.
Close the tab and send the app to the background.
Open the shortcut.
A new tab should be created pointing to facebook.com

Internal references:
Software Engineering Expectations
Technical Design Template

Hey @cmonfortep this is ready to re-review. We decided to remove the shown pixel for the fist CTA because it was causing too many issues. For the second CTA I noticed we were triggering the pixel way too early, should be fine now.


Remove incorrect statement about TextureButton normal texture

The documentation currently states that TextureButtons must have a texture for their "normal" state in texture_normal, but I found this didn't seem to be the case in practice, as noted here: https://github.com/godotengine/godot-docs/issues/9763
This PR simply removes that line about needing the texture from the TextureButton documentation page.
Bugsquad edit: fixes https://github.com/godotengine/godot-docs/issues/9763

This depends I'd say what is meant, I think it should instead explain what happens without this texture and suggest using it unless you know what you're doing

That makes sense; how does something like this sound?

It is recommended to at least set a texture for the "normal" state ([member texture_normal]). Otherwise, the TextureButton will still receive input events and be clickable, but the user will not be able to see it.

I suppose I should test adding textures for texture_disabled, texture_focused, texture_hover, and texture_pressed to confirm how they interact with texture_normal (or a lack thereof) - from the docs it sounds like these textures may show up once the user performs the relevant interaction, and as such should factor into the description.

I would suggest you update the PR to add the note you wrote (or similar) at the bottom the leading description.
There's nothing explicitly preventing TextureButton from existing without texture_normal. But texture_normal is what the other button states fall back to if no corresponding texture exists. So, in a way, it is essential.
The vague statement being removed sucks, anyway. It leaves you with your own thoughts assuming the worst.

Thanks for the reminder! I've updated the PR with a version of what I'd written above. I wasn't entirely sure how to succinctly phrase the idea that the other states fall back to the "normal" state; hopefully the current wording is okay, but if anyone has suggestions for improving it, please feel free to add them in a review!

I wasn't entirely sure how to succinctly phrase the idea that the other states fall back to the "normal" state

Honestly I feel like that's something that each state texture property's description could be more explicit about, instead of summarising it in the leading description.

I pushed a few changes to elaborate more on how the texture-swapping works, both in the note at the beginning and the descriptions for the texture properties.

I created a small test project to verify these behaviors before I added the notes to the documentation - a little later today I can post a set of short videos demonstrating them in action

Is this ready as-is, or do these adjustments still need to be integrated?

Looks like I need to commit those suggestions and squash, and then it should be ready to go. I'll try to get that done within the next hour or two :)

Updates are pushed and history is squashed!

Thanks!


Typescript refactoring stopped working: "Server Error (3.8.3) Debug Failure"

i've been using TS refactoring for a year or so. something broke in the current version where i get this error when trying to refactor parts of React.ReactNode type elements in render method.
i.e.
return (

foo

)

i am still able to press cmd+. to get the refactor context, when i select "extract method" it gives me the below exception. (this happens on both the  line, and entire return () line.
i tried disabling other plugins.
<semantic> TypeScript Server Error (3.8.3) Debug Failure.
    False expression. Error: Debug Failure.
    False expression. at getPos (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:123278:22)
      at assignPositionsToNode (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:124064:27)
     at visitNode (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:72887:23)
    at Object.visitEachChild (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:73104:117)
   at assignPositionsToNode (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:124061:30) at visitNode (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:72887:23) at Object...

Version: 1.45.1
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:33:47.663Z (2 wks ago)
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 18.7.0

@squarewave24 does this continue to happen if you use the latest TypeScript version, 3.9.3?

@squarewave24 does this continue to happen if you use the latest TypeScript version, 3.9.3?

hmm. i upgraded to 3.9.3 both in local project and global. but vs code still only shows 3.8.3 as options. i tried restarting VS

@squarewave24 See https://code.visualstudio.com/docs/typescript/typescript-compiling#_using-newer-typescript-versions
Or try using VS Code insiders which includes TS 3.9.3


Allow Type Overrides

This PR is to allow a developer to define the following in their ide-helper.php configuration:
    /*
    |--------------------------------------------------------------------------
    | Property Casts
    |--------------------------------------------------------------------------
    |
    | Cast the given "real type" to the given "type".
    |
    */
   'type_overrides' => array(
       'integer' => 'int',
       'boolean' => 'bool',
   ),

This will replace @property integer with @property int when running ide-helper:models. This will satisfy the phpdoc_scalar fixer when using the Laravel preset on StyleCI.
This is also the scalar convention for Laravel and I would actually honestly consider changing integer to int and boolean to bool in the following locations:

https://github.com/barryvdh/laravel-ide-helper/blob/master/src/Console/ModelsCommand.php#L260
https://github.com/barryvdh/laravel-ide-helper/blob/master/src/Console/ModelsCommand.php#L332
https://github.com/barryvdh/laravel-ide-helper/blob/master/src/Console/ModelsCommand.php#L245
https://github.com/barryvdh/laravel-ide-helper/blob/master/src/Console/ModelsCommand.php#L339

+1+1+1
Would relieve a lot of my headachest

Do we need this a a config? Why not just always change them?

That's why I have the recommendation for the change spots in the OP. Giving the author the option on which one they want to use.
Sent from my iPhone

On Aug 21, 2016, at 12:45 PM, Barry vd. Heuvel<EMAIL_ADDRESS>wrote:
Do we need this a a config? Why not just always change them?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Can you set them by default so that they make sense with setting the config?

Uncommented the defaults as requested.

Thanks!


Add openssf scorecard badge

Fill out openssf scorecard best practices form
Add badge to main page (like is shown at https://github.com/ebpf-for-windows)

We need an admin to go to https://bestpractices.coreinfrastructure.org/en/projects to submit l3af-project/l3afd
(Also there are score github actions: https://github.com/ossf/scorecard which we should also look at)

PR #63 added the best practices badge


SWODLR-SDS Issues

Issues which have been observed on the SWODLR HySDS instance:

Jobs failing upon retry due to noclobber setting
Odd API behavior where jobs report as completed during intermediate step and change to failed later
Job timeouts being too low
ElasticSearch failures lead to unpredictable/difficult to diagnose API issues

Current plan for corrective action:

SDS: handle noclobber issue
SWODLR: Investigated and found to be false issue
SWODLR: Timeouts to be lowered to 10 hours instead of increased (TODO)
SDS: implement automated monitoring of ElasticSearch on instance

HySDS ticket launched: https://hysds-core.atlassian.net/browse/HC-516

SWOT aware of noclobber behavior and ticket launched

SWODLR fixes deployed

3/25/24: The update of "SDS: handle noclobber issue" was developed in v5.1 and will be deployed on the week of 4/8/24.  v5.1 is currently in SDR and should be wrapped up on the week of 4/1/14.


⚠ PrivateHD has degraded performance

In c4aa9a9, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2313 ms

Resolved: PrivateHD performance has improved in 6ddd593.


Question about TOI solver in dyn4j

While working with box2d's continuous detection code it was easy to spot some differences with the one in dyn4j, so here I am curious about how the design came to be.
After finding the minimum TOI box2d builds an island with the bodies, uses the position solver for those bodies and then updates the affected contacts (more or less).
On the other hand dyn4j will just interpolate the bodies to the TOI so they're solved in the next frame with no extra corrections on the SolveTOI code (correct me if I'm wrong).
In some recent tests I found out box2d's approach to be unstable. While it works ok for few sparse bullet bodies it freaks out when multiple bullets collide.
Bodies and joints start glitching, producing very weird optical artifacts, effectively destroying the simulation.
On the other hand dyn4j is pretty smooth, I have not seen strange behavior/movement of bodies with (the default) CCD.ALL which makes me think it's approach is simpler and superior.
Any comments on the implementation and differences, William? I would like to find out more details about this. Thanks

I can't really speak to what box2d is doing unfortunately.  I remember looking at the code but then quickly pivoting to my own implementation of the solution described in Continuous Collision Detection and Physics.  The implementation is in ConservativeAdvancement.java.
dyn4j's implementation is far from perfect.  I opted to not track closest points between objects like Brian Mirtich.  Instead, it's implemented as a post detection/resolution step that has to check every dynamic (ALL) or bullet (BULLETS_ONLY) body against every other non-bullet body in the world.  I use the pre- and post-detection/resolution transforms and root find to see if there's a missed collision.  If I detect there's a collision, I interpolate the collision position for both bodies so they can be detected by static collision detection and resolved by the impulse solver in the next frame (as you mentioned).  The solveTOI() and solveTOI(Body) methods are what control what bodies are tested and there are a number of conditions being used to lower the number of detections that must be made.
This results in the following behavior:

Performance - It's not a problem in worlds with a small number of bodies, but large worlds would struggle.  This is because we don't know what pairs we need to check so we end up having to check most of them.  On top of that, root finding is not a particularly performant task.  On the flip side, the process typically exits quickly when there's no missed collision, but doing no work is always better than doing a little bit of work.
Time loss - Because the bodies are advanced, then backtracked when a collision is found, the motion can appear to stutter when there's a lot of these collisions in sequence.  The reason it appears this way is because we move the bodies back to the collision and don't try to catch them up to the current world time.
Potential for missed collisions - In dyn4j's implementation, once a body has participated in a TOI, it can no longer participate in others in that same step.  This could have the effect of missed collisions when dealing with a lot of fast/small moving objects.  I haven't seen this in my testing, but my testing hasn't been very extensive of this scenario.

Alright thanks for all the helpful info and the links! I think this approach produces better result anyway so it’s good you made your own implementation.
About performance by the way, I know that solveTOI scales very bad with body count but this can be fixed to a great extend. I actually propose we implement this for v4. One can use the broadphase to find candidate overlapping swept AABB pairs instead of a double loop. I have tried this in the past as an experimental implementation and the results were very good. The only thing missing is a clean way to handle this different use of the broadphase and the API (see #63)
I think box2d tries to solve your point 3 in a way (by solving the collision and then allowing the body to participate again in another TOI) but this eventually makes the result even worse, mostly when multiple bullets collide.
Thanks


Update grpc

Disallow cached versions of gRPC.
Related: https://github.com/GoogleCloudPlatform/google-cloud-node/issues/2699

I don't have the ability to land PRs here. @lukesneeringer @alexander-fenster


im on FW 10.7.0-32U which one should i use?

no browser or browser? im confused as hell sorry
if its no browser im fucked i dont have any of the games listed

this is not a support forum.
that being said, start with "Homebrew Launcher (Browser)" then go to "9.2.0 Downgrade".

sorry how cani delete this


Update Hstream

Checklist:
Fixes #3195 #3178

[x] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[x] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[x] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[x] Have removed web_hi_res_512.png when adding a new extension

How does this fix #3178 ?

How does this fix #3178 ?

I accidentally added it, sorry.


How to use it properly

Imagine in my example repo that I were to:

generate another feature, say 'feature-b' also with an overview, 'b-overview' mounted on the root route
mount 'feature-b' in my app on path 'b'
and I would generate the routes again using the schematic nx g @routerkit/core:parse --project app
and I then want to point the user from 'a-overview' to 'b-overview' using a routerlink and the generated routes
and then do the same the other way around, adding a routerlink on 'b-overview' pointing to 'a-overview' using the generated routes

I would then stumble upon two circular dependency issues, as the libs 'feature-a' and 'feature-b' cannot depend on the project 'app' so I cannot use the typings. Even if you would generate the typings for the feature libs and expose them from the lib itself, you would have a circular dependency between libs 'feature-a' and 'feature-b' as they need to reference the generated typings from each other. When not using the generated typings, this pictured scenario is perfectly possible because they are loosely coupled using some 'magic' strings. How will I still be able to use the typings in this setup (monorepo nx style)?

Without using the typings there are no issues:

When using the typings, there are circular dependencies (red arrows):

oh, it's weird
because types file should be a separate unit which only imports 1 thing file from node_modules/@routerkit/core and always exports the type...
can you add a commit to reproduce circular dependencies in your example repo?

@retarsis Sure, it's this commit. When you open up a-overview.component.ts in VSCode, the nx linting rule will tell you about the circular dependency.
The problem in detail
In a monorepo setup like nx, features (libs) can be reused in multiple apps and don't know anything about the app they're used in. So storing the generated typings on app level is not going to work in my depicted scenario: if you want to use a route path of a feature in another feature and vice versa.
On the other hand, storing the routes in the feature lib itself also won't work as this can introduce circular dependencies as I explained in the example above. So I don't see any other solution than storing the route typings in a separate lib with no reference to the feature lib (to keep it loosely coupled). So the feature lib and all other features/apps can use the generated routes without introducing circular dependencies. This introduces a small problem: the generated routes typings can get out of sync with its source.
In the project I'm working on right now, we just have a separate lib with all routes/magic strings and use this lib in both the components (for routerLinks) and in modules for the routing declaration. This has also the downside of this lib sometimes not being used and the lib with the routes being out of sync with the reality.
Sidetrack
While preparing this comment, I also came across a bug regarding lazy loaded modules and empty paths. The types are not correct for those. They are called 'root' while they're just an empty string. When you use those with the routerLink directive they obviously won't work because there is no route with a 'root' path. The correct route path is an empty string.

@JoepKockelkorn i'll answer for sidetracks
That is a design for empty paths to be root.
I didn't think it's unclear for new users, but ok, I'll think more about it
    location: {
        root: TypedRoute<[
            '/',
            'location'
        ]>;
  }

as you can see, location has a property root but the final tuple hasn't root path
sorry for this, I'll take some time to brainstorm this, otherwise I'll add additional documentation about this
does it makes sense? did my answer help?

I think I then stumbled upon a bug in the getRoutes function because I can see that 'root' is in the actual rendered href and the routing in my minimal example repo therefore doesn't work. The href of the link on the a-overview is http://localhost:4200/b/root where it should be http://localhost:4200/b. The typing is correct though.
Btw, I get the way you intended it now. The idea is quite okay 😄 but it might clash when the dev actually has a route named 'root'. It might be more dev friendly if routes.b would also have the asString, asArray and toString methods instead of having to do .root, but I don't know the consequences of that.

root inside href is a bug

2)now I am actively thinking about the options for renaming the root. Current options: ROOT and EMPTY.
Not quite satisfied yet, I will make a decision in the near future

we apply root only if particular route has siblings

Good
{
    location: {
        root: TypedRoute<[
            '/',
            'location'
        ]>;

       map: TypedRoute<[
            '/',
            'location',
            'map'
        ]>;
    }
}

Bad
{
    location: {
        root: TypedRoute<[
            '/',
            'location'
        ]>;

       map: TypedRoute<[
            '/',
            'location',
            'map'
        ]>;
    }
}

If route has no siblings, then it will be structured in that way:
```javascript
{
    location: TypedRoute<[ '/', 'location']>;
}

@retarsis Yes it's available in my repo. Just navigate to localhost:4200/a after yarn ng serve and the link to b-overview has 'root' in it.

@JoepKockelkorn thanks a lot, again 😅
I will come back to this issue tomorrow as there is a lot of other work to be done.

So, both issues are identified and I started working on it.

@JoepKockelkorn I have news
The fix is in master branch for both issues but I didn't release it because we have few issues to fix with parser. I think we will release this in a few days.
sorry for keeping you waiting
but there is more good news
I added you as a contributor to the project because I appreciate what you have done for the project

@retarsis Nice, thanks! Regarding the waiting, no problem as I don't use it yet. I have to figure out how in a nx setup.

@JoepKockelkorn about nx repo issue I decided to just generate routes type file in the rootDir because "circular dependency" isn't real (project compiles and only custom lint rule complains). It's just a custom lint rule from nx team when you import anything in the not appropriate way (from app to feature and from feature to app).

about nx repo issue I decided to just generate routes type file in the rootDir because "circular dependency" isn't real (project compiles and only custom lint rule complains)

How is the circular dependency not real? Even though they're just typings, it's definitely a reference in both ways.

and starting from the next release you generated files will be located in the rootDir which means you won't have circular dependencies anymore

So what happens if you have two apps and you generate the typings for both of them?

How is the circular dependency not real? Even though they're just typings, it's definitely a reference in both ways.

if I'm not mistaken typescript destroys types on compilation
by the way, routes type file doesn't import anything except TypedRoute from node_modules that's why you won't have circularity anyway. Custom lint rule from nx is just a semantic thing to warn.

So what happens if you have two apps and you generate the typings for both of them?

Each generated routes type file has unique project name (you can't have 2 different apps with the same project name)
Let's suppose you have 2 apps with the following names: app1 and app2.
The output of routerkit will be app1.routes.d.ts. and app2.routes.d.ts in the root folder.

@JoepKockelkorn just released 0.8.0, check it out
https://github.com/retarsis/routerkit/releases/tag/0.8.0

@retarsis Looking good, nice to see my comments being taken seriously. However, I'm not convinced of the rootDir approach. Referencing the typed routes of a feature module though the generated routes of an app feels dirty, even though it's just typings and will not be bundled in the resulting deployable bundles.
If this package would have the following features then the devs can decide for themselves how to use it properly:

Besides generating routes of an app, the tool allows to generate typed routes of a lazy loaded feature module separately
Be able to pass a param/config path where to write the generated typings

If this tool would have these options I would use it as following in a nx repo:

Generate separate sibling libs for all my lazy loaded feature libs where all of the typed routings are going to live
Generate the typings using this tool into the generated libs so it can be used (imported) it other features while keeping the loosely coupled characteristic

Generating the typed routings of a feature module is currently not possible as it throws this error:
Can't find tsconfig inside angular.json for feature-a project. An appropriate config name should include 'tsconfig' and '.json'. I don't know if it even is possible, haven't investigated.

@JoepKockelkorn I do appreciate your efforts, therefore we try to help in response
You say interesting ideas, but meanwhile, they are not quite included in the project plans for the 1.0.0 release, and I want to spend time improving the parser and other basic features that are necessary for the 1.0.0 release.
What you propose sounds interesting, and it really makes sense, since I already had experience with workspaces.
But the problem is that we will have to rewrite many things and this will take a significant amount of time.
Therefore, in order not to miss anything, and to separate the problem from the request, I propose to proceed as follows:

close this issue as we have resolved several issues related to the original issue
create RFC through a new issue item, and describe exactly what is not ok and how it should work
attach a link with this issue to the newly created

@JoepKockelkorn does that suit you?

@retarsis Yeah of course! My priority is not yours, I understand that completely 🙂

Closing this issue, created an RFC #73


FormRequest always returns JSON for AJAX requests

I know it is something pretty hard to get right, but i disagree with the way FormRequest checks if it should return JSON.
The code says:
if ($this->ajax() || $this->wantsJson()) {
         return new JsonResponse($errors, 422);
}

So when the request is AJAX, it won't even check if i want JSON.

What if I explicitly said that I want HTML (XML or anything else) in my AJAX request?
Is it a convention that is used elsewhere in Laravel?

It seems to me that being a AJAX request and wanting (or accepting) JSON are two different things.

@jp7carlos You can just overwrite the method checking for this :)

I've brought this up before, and we looked into change it, but we ended up deciding this implementation is an OK default.


user/response count histogram with too many response counts

If more than 40 or so different response counts exist for a given campaign, this histogram might look really funny.

old, closing


Use real AppScale Cloud Storage when configured

By default, the dispatcher for non-Java runtimes uses the blobstore backend for GCS operations. This change allows users to use a real GCS service instead.

@jeanleonov I agree. Good call.

https://ocd.appscale.com:8080/job/Daily Build/5459/

I'm going to close this for now since there are some problems with it (I didn't sufficiently test it before submitting it) and it's not a high priority.


please add some install instructions

It would be nice if there where some install instruction on top of the readme file. I would like to link the project from a howto-guide and don't wont to explain it there.

See: #24

thx

#24 has been merged and I cut a new release, 1.2.1 which should be available from PyPi shortly.


Heatmap does not show axis.

Demo :
https://stackblitz.com/edit/react-dfrhfs?file=Hello.js
which config is an exact copy of official demo:
https://jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/master/samples/highcharts/demo/heatmap/

Having the same issue, I follow this thread but I had no luck https://github.com/kirjs/react-highcharts/issues/300 need to solved this ASAP!! :(

It's a very important problem!
Not display:

title
categories


Add support for Zepto.js

Add support for Zepto.js

Good work! We dropped jQuery as a dependency so I don't think Zepto support is feasible. Try the modern vanilla vex!


Js install readme steps

@paetling these are currently the install steps (for any user).  For gc users, should the script go in gcsystems (it could do this + other gc-specific stuff)?

this looks good.  what are the pros and cons of doing it in gcsystems vs gcconfig?  Not really sure what gcconfig is supposed to be used for

Either way, I don't really know what either is for

just put it in gcsystems.  you can move it later if needed


Added section about React

For a private project i needed this awesome little tool to work with react.
Turns out, it does right out of the box like shown in this section.
Didn't do extensive testing so there might be some problems in some cases (maybe stateful components?), but this might be helpful.

We'll merge this and hopefully we can do a new release soon.
So much thanks for your contribution!