StackOverflowException and OutOfMemory Exception

When I run in release mode I get a stackoverflowexception. If I run in debug mode and break I see lots of OutOfMemory exceptions due to trying to allocate an array >2 gb
I ran with the log options and here is the resultant log.
=============================================
Timestamp (UTC): 4/06/2019 3:14:15 AM
ILMerge version <IP_ADDRESS>
Copyright (C) Microsoft Corporation 2004-2006. All rights reserved.
ILMerge company.editor.exe /log /lib:C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated /out:company.exe company.model.dll company.common.dll company.ui.common.dll company.j2534.dll company.external.dll company.api.dll
Set platform to 'v4', using directory 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319' for mscorlib.dll
Running on Microsoft (R) .NET Framework v4.0.30319
mscorlib.dll version = <IP_ADDRESS>
The list of input assemblies is:
        company.editor.exe
        company.model.dll
        company.common.dll
        company.ui.common.dll
        company.j2534.dll
        company.external.dll
        company.api.dll
Trying to read assembly from the file 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\company.editor.exe'.
Can not find PDB file. Debug info will not be available for assembly 'company.editor.exe'.
        Successfully read in assembly.
        There were no errors reported in company.Editor's metadata.
Trying to read assembly from the file 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\company.model.dll'.
Can not find PDB file. Debug info will not be available for assembly 'company.model.dll'.
        Successfully read in assembly.
        There were no errors reported in company.Model's metadata.
Trying to read assembly from the file 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\company.common.dll'.
Can not find PDB file. Debug info will not be available for assembly 'company.common.dll'.
        Successfully read in assembly.
        There were no errors reported in company.Common's metadata.
Trying to read assembly from the file 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\company.ui.common.dll'.
Can not find PDB file. Debug info will not be available for assembly 'company.ui.common.dll'.
        Successfully read in assembly.
        There were no errors reported in company.UI.Common's metadata.
Trying to read assembly from the file 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\company.j2534.dll'.
Can not find PDB file. Debug info will not be available for assembly 'company.j2534.dll'.
        Successfully read in assembly.
        There were no errors reported in company.J2534's metadata.
Trying to read assembly from the file 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\company.external.dll'.
Can not find PDB file. Debug info will not be available for assembly 'company.external.dll'.
        Successfully read in assembly.
        There were no errors reported in company.External's metadata.
Trying to read assembly from the file 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\company.api.dll'.
Can not find PDB file. Debug info will not be available for assembly 'company.api.dll'.
        Successfully read in assembly.
        There were no errors reported in company.Api's metadata.
Checking to see that all of the input assemblies have a compatible PeKind.
        company.Editor.PeKind = ILonly, Requires32bits, Prefers32bits
        company.Model.PeKind = ILonly
        company.Common.PeKind = ILonly
        company.UI.Common.PeKind = ILonly
        company.J2534.PeKind = ILonly
        company.External.PeKind = ILonly
        company.Api.PeKind = ILonly
All input assemblies have a compatible PeKind value.
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'PresentationFramework'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
        AssemblyResolver: Did not find assembly in framework directory.
AssemblyResolver: Unable to resolve reference. (It still might be found, e.g., in the GAC.)
AssemblyResolver: Assembly 'PresentationFramework' is referencing assembly 'WindowsBase'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
        AssemblyResolver: Did not find assembly in framework directory.
AssemblyResolver: Unable to resolve reference. (It still might be found, e.g., in the GAC.)
AssemblyResolver: Assembly 'PresentationFramework' is referencing assembly 'System.Xaml'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Xaml'.
Resolved assembly reference 'System.Xaml' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.Xaml.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'DevExpress.Xpf.Core.v19.1'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.Core.v19.1'.
Resolved assembly reference 'DevExpress.Xpf.Core.v19.1' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.Core.v19.1.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'PresentationFramework' is referencing assembly 'PresentationCore'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
        AssemblyResolver: Did not find assembly in framework directory.
AssemblyResolver: Unable to resolve reference. (It still might be found, e.g., in the GAC.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'DevExpress.Xpf.Grid.v19.1'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.Grid.v19.1'.
Resolved assembly reference 'DevExpress.Xpf.Grid.v19.1' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.Grid.v19.1.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'DevExpress.Xpf.Grid.v19.1' is referencing assembly 'DevExpress.Xpf.Grid.v19.1.Core'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.Grid.v19.1.Core'.
Resolved assembly reference 'DevExpress.Xpf.Grid.v19.1.Core' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.Grid.v19.1.Core.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'DevExpress.Mvvm.v19.1'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Mvvm.v19.1'.
Resolved assembly reference 'DevExpress.Mvvm.v19.1' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Mvvm.v19.1.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'DevExpress.Xpf.Grid.v19.1' is referencing assembly 'DevExpress.Data.v19.1'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Data.v19.1'.
Resolved assembly reference 'DevExpress.Data.v19.1' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Data.v19.1.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'DevExpress.Xpf.Grid.v19.1' is referencing assembly 'DevExpress.Printing.v19.1.Core'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Printing.v19.1.Core'.
Resolved assembly reference 'DevExpress.Printing.v19.1.Core' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Printing.v19.1.Core.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'DevExpress.Xpf.Docking.v19.1'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.Docking.v19.1'.
Resolved assembly reference 'DevExpress.Xpf.Docking.v19.1' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.Docking.v19.1.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'DevExpress.Xpf.Docking.v19.1' is referencing assembly 'DevExpress.Xpf.Layout.v19.1.Core'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.Layout.v19.1.Core'.
Resolved assembly reference 'DevExpress.Xpf.Layout.v19.1.Core' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.Layout.v19.1.Core.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'System.Core'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Core'.
Resolved assembly reference 'System.Core' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.Core.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'DevExpress.Xpf.Controls.v19.1'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.Controls.v19.1'.
Resolved assembly reference 'DevExpress.Xpf.Controls.v19.1' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.Controls.v19.1.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'DevExpress.Xpf.Charts.v19.1'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.Charts.v19.1'.
Resolved assembly reference 'DevExpress.Xpf.Charts.v19.1' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.Charts.v19.1.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'DevExpress.Xpf.Charts.v19.1' is referencing assembly 'DevExpress.Charts.v19.1.Core'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Charts.v19.1.Core'.
Resolved assembly reference 'DevExpress.Charts.v19.1.Core' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Charts.v19.1.Core.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'Arction.WPF.Gauges'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Arction.WPF.Gauges'.
Resolved assembly reference 'Arction.WPF.Gauges' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Arction.WPF.Gauges.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'Arction.Wpf.SemibindableCharting.LightningChartUltimate'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Arction.Wpf.SemibindableCharting.LightningChartUltimate'.
Resolved assembly reference 'Arction.Wpf.SemibindableCharting.LightningChartUltimate' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Arction.Wpf.SemibindableCharting.LightningChartUltimate.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'Nito.AsyncEx'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Nito.AsyncEx'.
Resolved assembly reference 'Nito.AsyncEx' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Nito.AsyncEx.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'Nito.AsyncEx' is referencing assembly 'System.Runtime'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Runtime'.
Resolved assembly reference 'System.Runtime' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.Runtime.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'SharpRaven'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'SharpRaven'.
Resolved assembly reference 'SharpRaven' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\SharpRaven.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Model' is referencing assembly 'protobuf-net'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'protobuf-net'.
Resolved assembly reference 'protobuf-net' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\protobuf-net.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Model' is referencing assembly 'System.ComponentModel.DataAnnotations'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.ComponentModel.DataAnnotations'.
Resolved assembly reference 'System.ComponentModel.DataAnnotations' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.ComponentModel.DataAnnotations.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'company.Model' is referencing assembly 'LiteDB'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'LiteDB'.
Resolved assembly reference 'LiteDB' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\LiteDB.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Model' is referencing assembly 'System.Runtime.Serialization'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Runtime.Serialization'.
Resolved assembly reference 'System.Runtime.Serialization' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.Runtime.Serialization.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'company.Common' is referencing assembly 'Unity.Container'.
        AssemblyResolver: Attempting referencing assembly's directory.
Resolved assembly reference 'Unity.Container' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Unity.Container.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'Unity.Container' is referencing assembly 'Unity.Abstractions'.
        AssemblyResolver: Attempting referencing assembly's directory.
Resolved assembly reference 'Unity.Abstractions' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Unity.Abstractions.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.UI.Common' is referencing assembly 'DevExpress.Xpf.PdfViewer.v19.1'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.PdfViewer.v19.1'.
Resolved assembly reference 'DevExpress.Xpf.PdfViewer.v19.1' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.PdfViewer.v19.1.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'DevExpress.Xpf.PdfViewer.v19.1' is referencing assembly 'DevExpress.Xpf.DocumentViewer.v19.1.Core'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Xpf.DocumentViewer.v19.1.Core'.
Resolved assembly reference 'DevExpress.Xpf.DocumentViewer.v19.1.Core' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Xpf.DocumentViewer.v19.1.Core.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'DevExpress.Xpf.PdfViewer.v19.1' is referencing assembly 'DevExpress.Pdf.v19.1.Core'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'DevExpress.Pdf.v19.1.Core'.
Resolved assembly reference 'DevExpress.Pdf.v19.1.Core' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\DevExpress.Pdf.v19.1.Core.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.UI.Common' is referencing assembly 'Arction.Wpf.BindableCharting.LightningChartUltimate'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Arction.Wpf.BindableCharting.LightningChartUltimate'.
Resolved assembly reference 'Arction.Wpf.BindableCharting.LightningChartUltimate' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Arction.Wpf.BindableCharting.LightningChartUltimate.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Api' is referencing assembly 'HtmlAgilityPack'.
        AssemblyResolver: Attempting referencing assembly's directory.
Resolved assembly reference 'HtmlAgilityPack' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\HtmlAgilityPack.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Api' is referencing assembly 'System.Net.Http'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Net.Http'.
Resolved assembly reference 'System.Net.Http' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\System.Net.Http.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Api' is referencing assembly 'SendGrid'.
        AssemblyResolver: Attempting referencing assembly's directory.
Resolved assembly reference 'SendGrid' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\SendGrid.dll'. (Used referencing Module's directory.)
Using assembly 'company.Editor' for assembly-level attributes for the target assembly.
Merging assembly 'company.Editor' into target assembly.
Merging assembly 'company.Model' into target assembly.
Duplicate type name: modifying name of the type '<>F{00000008}`5' (from assembly 'company.Model') to 'company.Model.<>F{00000008}`5'
Duplicate type name: modifying name of the type '<PrivateImplementationDetails>' (from assembly 'company.Model') to 'company.Model.<PrivateImplementationDetails>'
Merging assembly 'company.Common' into target assembly.
Duplicate type name: modifying name of the type '<PrivateImplementationDetails>' (from assembly 'company.Common') to 'company.Common.<PrivateImplementationDetails>'
Merging assembly 'company.UI.Common' into target assembly.
Merging assembly 'company.J2534' into target assembly.
Duplicate type name: modifying name of the type '<PrivateImplementationDetails>' (from assembly 'company.J2534') to 'company.J2534.<PrivateImplementationDetails>'
Merging assembly 'company.External' into target assembly.
Duplicate type name: modifying name of the type '<PrivateImplementationDetails>' (from assembly 'company.External') to 'company.External.<PrivateImplementationDetails>'
Merging assembly 'company.Api' into target assembly.
Copying 9 Win32 Resources from assembly 'company.Editor' into target assembly.
Transferring entry point 'company.Editor.App.Main' from assembly 'company.Editor' to assembly 'company'.
        There were no errors reported in the target assembly's metadata.
ILMerge: Writing target assembly 'company.exe'.
AssemblyResolver: Assembly 'PresentationCore' is referencing assembly 'UIAutomationTypes'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
        AssemblyResolver: Did not find assembly in framework directory.
AssemblyResolver: Unable to resolve reference. (It still might be found, e.g., in the GAC.)
AssemblyResolver: Assembly 'Arction.Wpf.SemibindableCharting.LightningChartUltimate' is referencing assembly 'Arction.RenderingDefinitions'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Arction.RenderingDefinitions'.
Resolved assembly reference 'Arction.RenderingDefinitions' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Arction.RenderingDefinitions.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'Arction.Wpf.SemibindableCharting.LightningChartUltimate' is referencing assembly 'Arction.Licensing'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Arction.Licensing'.
Resolved assembly reference 'Arction.Licensing' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Arction.Licensing.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'Arction.Wpf.SemibindableCharting.LightningChartUltimate' is referencing assembly 'Arction.RenderingEngine'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Arction.RenderingEngine'.
Resolved assembly reference 'Arction.RenderingEngine' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Arction.RenderingEngine.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'Arction.Wpf.SemibindableCharting.LightningChartUltimate' is referencing assembly 'Arction.DirectX'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Arction.DirectX'.
Resolved assembly reference 'Arction.DirectX' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Arction.DirectX.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'System.Configuration'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Configuration'.
Resolved assembly reference 'System.Configuration' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.Configuration.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'DevExpress.Xpf.Grid.v19.1.Core' is referencing assembly 'System.Printing'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
        AssemblyResolver: Did not find assembly in framework directory.
AssemblyResolver: Unable to resolve reference. (It still might be found, e.g., in the GAC.)
AssemblyResolver: Assembly 'DevExpress.Xpf.Grid.v19.1.Core' is referencing assembly 'UIAutomationProvider'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
        AssemblyResolver: Did not find assembly in framework directory.
AssemblyResolver: Unable to resolve reference. (It still might be found, e.g., in the GAC.)
AssemblyResolver: Assembly 'company.Editor' is referencing assembly 'Microsoft.CSharp'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'Microsoft.CSharp'.
Resolved assembly reference 'Microsoft.CSharp' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\Microsoft.CSharp.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'Nito.AsyncEx' is referencing assembly 'System.Threading.Tasks'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Threading.Tasks'.
Resolved assembly reference 'System.Threading.Tasks' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.Threading.Tasks.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'Nito.AsyncEx' is referencing assembly 'System.Diagnostics.Debug'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Diagnostics.Debug'.
Resolved assembly reference 'System.Diagnostics.Debug' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.Diagnostics.Debug.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'SharpRaven' is referencing assembly 'Newtonsoft.Json'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Newtonsoft.Json'.
Resolved assembly reference 'Newtonsoft.Json' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Newtonsoft.Json.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Model' is referencing assembly 'CoreTechs.Common'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'CoreTechs.Common'.
Resolved assembly reference 'CoreTechs.Common' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\CoreTechs.Common.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Model' is referencing assembly 'MoreLinq'.
        AssemblyResolver: Attempting referencing assembly's directory.
Resolved assembly reference 'MoreLinq' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\MoreLinq.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'MoreLinq' is referencing assembly 'System.ValueTuple'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'System.ValueTuple'.
Resolved assembly reference 'System.ValueTuple' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\System.ValueTuple.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Common' is referencing assembly 'ICSharpCode.SharpZipLib'.
        AssemblyResolver: Attempting referencing assembly's directory.
Resolved assembly reference 'ICSharpCode.SharpZipLib' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\ICSharpCode.SharpZipLib.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Api' is referencing assembly 'System.Net.Http.WebRequest'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Net.Http.WebRequest'.
Resolved assembly reference 'System.Net.Http.WebRequest' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.Net.Http.WebRequest.dll'. (Used framework directory.)
AssemblyResolver: Assembly 'System.Net.Http.WebRequest' is referencing assembly 'System.Net.Http'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Net.Http'.
Resolved assembly reference 'System.Net.Http' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Net.Http.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Api' is referencing assembly 'GoogleAnalyticsTracker.Simple'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'GoogleAnalyticsTracker.Simple'.
Resolved assembly reference 'GoogleAnalyticsTracker.Simple' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\GoogleAnalyticsTracker.Simple.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'GoogleAnalyticsTracker.Simple' is referencing assembly 'GoogleAnalyticsTracker.Core'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'GoogleAnalyticsTracker.Core'.
Resolved assembly reference 'GoogleAnalyticsTracker.Core' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\GoogleAnalyticsTracker.Core.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Api' is referencing assembly 'WebApiContrib.Formatting.ProtoBuf'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'WebApiContrib.Formatting.ProtoBuf'.
Resolved assembly reference 'WebApiContrib.Formatting.ProtoBuf' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\WebApiContrib.Formatting.ProtoBuf.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'WebApiContrib.Formatting.ProtoBuf' is referencing assembly 'System.Net.Http.Formatting'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Net.Http.Formatting'.
Resolved assembly reference 'System.Net.Http.Formatting' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\System.Net.Http.Formatting.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'WebApiContrib.Formatting.ProtoBuf' is referencing assembly 'System.Net.Http'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'System.Net.Http'.
Resolved assembly reference 'System.Net.Http' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\System.Net.Http.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'WebApiContrib.Formatting.ProtoBuf' is referencing assembly 'protobuf-net'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'protobuf-net'.
Resolved assembly reference 'protobuf-net' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\protobuf-net.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'System.Net.Http.Formatting' is referencing assembly 'Newtonsoft.Json'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Newtonsoft.Json'.
Resolved assembly reference 'Newtonsoft.Json' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Newtonsoft.Json.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'SendGrid' is referencing assembly 'Newtonsoft.Json'.
        AssemblyResolver: Attempting referencing assembly's directory.
Can not find PDB file. Debug info will not be available for assembly 'Newtonsoft.Json'.
Resolved assembly reference 'Newtonsoft.Json' to 'C:\Temp\company\UI\company.Editor\bin\Debug - Editor - Obfuscated\Newtonsoft.Json.dll'. (Used referencing Module's directory.)
AssemblyResolver: Assembly 'company.Api' is referencing assembly 'System.DirectoryServices.AccountManagement'.
        AssemblyResolver: Attempting referencing assembly's directory.
        AssemblyResolver: Did not find assembly in referencing assembly's directory.
        AssemblyResolver: Attempting input directory.
        AssemblyResolver: Did not find assembly in input directory.
        AssemblyResolver: Attempting user-supplied directories.
        AssemblyResolver: Did not find assembly in user-supplied directories.
        AssemblyResolver: Attempting framework directory.
Can not find PDB file. Debug info will not be available for assembly 'System.DirectoryServices.AccountManagement'.
Resolved assembly reference 'System.DirectoryServices.AccountManagement' to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\..\v4.0.30319\System.DirectoryServices.AccountManagement.dll'. (Used framework directory.)

Process is terminated due to StackOverflowException.

@rolandh , I can see that you use some obfuscated assemblies as ILMerge input.
Are those assemblies verifiable? You can check that with the help of PEVerify.exe tool from .NET Framework SDK.
If they are not verifiable then ILMerge or any other .NET tool cannot guarantee the consistent behavior. This can be the root cause of stack overflow you get.
Another thing to check is to temporarily exclude obfuscation from the pipeline. Does stack overflow persist?


feat: markdown upload image button

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3904   👈

This comment was auto-generated by Graphite.


[BUG]: .default() does not work on boolean pg types

What version of drizzle-orm are you using?
0.31.2
What version of drizzle-kit are you using?
0.22.7
Describe the Bug
When I set .default(sql'FALSE').notNull() or .default(false).notNull(), manually entering a row does not result in FALSE by default.
Check the snapshot:

The CHECK() constraint, using sql magic operator also doesn't work. I am aware the drizzle did not implement this yet.
Please check the code snippet below for understanding what I am trying to achieve:
export const trackers = createTable(
  "tracker",
  {
    id: uuid("id").primaryKey(),
    createdAt: timestamp("created_at", {
      mode: "date",
      withTimezone: true,
    }).default(sql`CURRENT_TIMESTAMP`).notNull(),
    hashedId: varchar("hashed_id", { length: 255 }).notNull(),
    country: varchar("country", { length: 2 }).notNull(),
    isMalicious: boolean("is_malicious").default(sql`FALSE`).notNull(),
    canBypassProtection: boolean("can_bypass_protection").default(sql`FALSE`).notNull(),
  },
  (tracker) => ({
    hashedIdIdx: index("tacker_hashedId_idx").on(tracker.hashedId),
    canBypassProtectionCstr:
      sql`CHECK (can_bypass_protection = FALSE OR (can_bypass_protection = TRUE AND is_malicious = TRUE))`, // <-- DOESN'T WORK
  })
);

Expected behavior
It should be FALSE by default.
Environment & setup
No response

same here! been driving me crazy

What is the createTable function? It would be awesome if you could send a full repro example, so I can add it to the test cases and fix it if needed

@codesfromshad Is this issue specific to Drizzle Studio or are you encountering this issue while running a query with the ORM?

Same thing here.
export const blogs = createTable(
  "blogs",
  {
    id: serial("id").primaryKey(),
    author: varchar("author")
      .notNull()
      .references(() => userTable.username),
    title: varchar("title", { length: 255 }).notNull(),
    active: boolean("active").notNull().default(false),
    createdAt: timestamp("created_at")
      .default(sql`CURRENT_TIMESTAMP`)
      .notNull(),
    updatedAt: timestamp("updated_at").$onUpdate(() => new Date()),
    deletedAt: timestamp("deleted_at"),
  },
  (table) => ({
    blogTitleUniqueIdx: uniqueIndex("blog_title_uniqueIdx").on(table.title),
    /* Only force uniqueness on author's "current" blog (don't include deleted ones) */
    authorBlogUniqueIdx: uniqueIndex("author_blog_uniqueIdx")
      .on(table.author)
      .where(sql`"deleted_at" IS NULL`),
  })
);

.default(false) does not apply - therefore when "active" boolean isn't explicitly supplied, the entry isn't created due to the notNull() constraint.
I could explicitly include active: false on every DB insert, but you'd at least expect stuff to work? Or not take months of being swept under the rug? Isn't this a pretty huge deal?

.default(false) does not apply

@MGSimard What do you mean by that? That the default value statement isn't being generated in migrations or that inside an insert query the default value isn't being applied?
I tried both anyways and both behave as expected in the latest version of ORM and Kit (v0.33.0 and v0.24.2 respectively). If it's an issue with an insert statement, I'm curious to know what driver you're using and how you've defined the query that's causing the issue.

.default(false) does not apply

@MGSimard What do you mean by that? That the default value statement isn't being generated in migrations or that inside an insert query the default value isn't being applied?
I tried both anyways and both behave as expected in the latest version of ORM and Kit (v0.33.0 and v0.24.2 respectively). If it's an issue with an insert statement, I'm curious to know what driver you're using and how you've defined the query that's causing the issue.

I mean it's intrinsically both isn't it? When you db:push this table schema, the default(false) constraint doesn't actually get applied to the column, which inherently means that whether you run an insert query or attempt to create a row manually in drizzle studio, the "active" column will default to null rather than false, which will obviously throw an error because of notNull(). You're being forced to supply an explicit true/false boolean on every insert or update, because default(false) isn't actually being applied on table creation, so any insert will not default to false. The exact context supplied by both the issue's OP and myself. Neither default(false) or default(sqlFALSE) work. This is on latest.
This behaviour can be observed simply by adding a row in drizzlthis upon attempting to add a row through db:studio simply by the untouched column saying "NULL" instead of "DEFAULT". This is on the exact table described by the above schema.

I haven't tested on a non multi-project schema yet, but considering that if your testing of boolean .default() does indeed work on your end, and the fact that OP is using syntax indicating they're also doing multi-project schema -- could this possibly be yet another bug introduced by the use of multi-project schema, somehow? Same as this other issue introduced a few months ago?
This is the multi-project schema documentation: https://orm.drizzle.team/kit-docs/conf#multi-project-schema

@codesfromshad @raydelvecchio @MGSimard Hey! This should be fixed.


Name Collision

Instead of overwriting files, append .num to the file name. Ex:
naked.lunch.1991.en.srt => naked.lunch.1991.en.1.srt &  naked.lunch.1991.en.2.srt. (also, check if there are already numbered subs.)
This works with mpv and vlc with srt files. I have not tested other formats and video players.
Also, could you, please, add the repo link to the description of the script and some sort of versioning (in the README as well)? the script name is widely used.
Is there a way to make the script's output less verbose in the terminal? (not shut it entirely.)

I don't really see why it would be useful to keep multiple subtitles of the same language? Either the subtitle is ok and you keep it, or it isn't, and you delete or overwrite it. But if the overwriting bothers you, you can turn it off by setting the force bool in the script to false.
To make the script's output less verbose in the terminal, turn debugging off by setting the debug bool to false.
I've added the repo link in the readme title.


compile error on macosx

fontstash.h
on macosx should include <sys/malloc.h>

It's already included from compat directory...
https://github.com/bkaradzic/bx/blob/master/include/compat/osx/malloc.h


Provide an option to turn off host load indicator

Since it causes network traffic which may be costing $$$

https://github.com/Microsoft/RTVS/commit/8cec036b69fd0d5af1b31516b88d6d4bfa62476f


pre-trained models

Hi, I found that the loss did not drop during training, so I would like to ask if you can make the pre-trained model publicly available? Thank you very much!

Thanks for asking.  Unfortunately, many pretrianed models that are reported in our paper are lost.
But I trained a VRCNet (2048pts) recently, which achieves better results than our report.
Here is the link:
https://www.dropbox.com/sh/8uixt8dbqfoh1bn/AADbmET-i73hzMEvsYVYhT_Za?dl=0
and you can give it a try~

Thanks a lot!

Is there any chance you could provide a model pretrained for 4096 points?


Rename primary development branch to main

Would be nice if the primary development branch was named main rather than the somewhat outdated/potentially insensitive master :innocent:

Sure I can move it over after all theses PRs go through.

Done.


[DOC]: Update model cards and example readme with dataset info

How would you describe the priority of this documentation request
Medium
Please provide a link or source to the relevant docs
https://github.com/nv-morpheus/Morpheus/blob/branch-22.11/models/README.md
Describe the problems in the documentation
Does not include detailed information about datasets
(Optional) Propose a correction
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I have searched the open documentation issues and have found no duplicates for this bug report

closed by https://github.com/nv-morpheus/Morpheus/pull/612


Operators after precommands are wrongly displayed as error

For example, in env | grep PATH the operator | is displayed in red color.
Other examples are || in sudo || xxx, ; in nohup; xxx... Of course these are not very meaningful commands but still legal zsh syntax.

That's mostly intentional. For most precommands running them without a command is an error even if legal syntax (; ; is highlighted as unknown-token for the same reason.) The unknown-token style is a bit overloaded (cf. #695) and is used for a syntax-error and for linting type warnings.
In the case of env, it's reasonable to run without a command. Since #695 is for unknown-token being overloaded, I think it's reasonable to restrict this issue to precommands that are reasonable to run without a command (e.g. env).

+1
@cuihaoleo Interested in writing a patch to have the env case highlighted correctly?  Or in starting work on #695?  In the latter case, note that @johnsonjh has an unknown-token-related patch in the offing over on #794, which would cover one case of #695.

@johnsonjh Thanks. Looking forward to it.


[Windows]: Initialize on window creation event

Do all initialize on WM_CREATE instead of the context where the window gets created.
Avoids issues in case of more than WM_CREATE gets issued on window creation (e.g WM_SIZE) with other window styles. This results in a panic as not everything is initialized at that time.
Noticed while trying to implement https://github.com/xi-editor/druid/issues/427.

Quick response: I see the point of this and want to incorporate the logic, but there's an internal layering of the low level window creation and the actual wndproc handling, and this breaks it. Is there any possibility this could be done in WM_CREATE in MyWndProc instead of the C window procedure?
The internal layering is not enforced, but the win_win branch would move this out to a separate crate. We don't have consensus to make that an explicit dependency, but I would like to preserve the layering (and also fix the soundness issue, for which I've been meaning to do a separate PR, which would conflict with this one).
Thanks for digging into this, I know it's tricky.

sure, new try (:

@msiglreith this collided with #419, want to rebase or merge and then we'll get it in?

Seems to build \o/


Cursor Animation Tweak

Allowed the animation from circle <-> dot to be interrupted, making the cursor feel more responsive.

What does "m_InterruptionSource: 2" correspond to in the editor?

CursorSomple.controller->Both Ring_Idle to Dot_Idle transitions ->Settings->Interruption Source.
You need to select either of the linse with the arrows between the states to see the inspector window.
Changed Interruption Source from None 0 to Next State 2.
This enables the Ring animation to be interrupted by the dot animation instead of finishing it's animation to the end. Makes the cursor feel a bit more responsive when recognizing input sources.

Looks good to me!


Implemented (Python) Logistic Regression

🛠 Issue (Number)

Issue no #350
👨💻 Changes proposed

Added implementation for logistic regression in Python
Added demo datasets
Added README file with screenshots to demonstrate usage

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots
Code:

Output:

@Kumar-laxmi @072arushi @Arun9739 @Rancho2002
Requesting a review. Thank you.

@Kumar-laxmi I was under the impression that this was an advanced issue, not an intermediate one. Could you please check and confirm?


Here is how I got around client cert authentication, hope it helps others.  Basically just intercept the request, then fire the request off yourself using your favorite httpclient lib, and repond to the intercepted request with the response info.

This post is asked how to successfully enter the digital certificate on a particular site that requires such authentication. I tried to do the @dapriett process with a slight modification which is changing the .crt and .key to the .pfx according to what @camjackson suggested but always gives the error below:

{ Error: unable to get local issuer certificate
at TLSSocket.onConnectSecure (_tls_wrap.js:1058:34)
at TLSSocket.emit (events.js:198:13)
at TLSSocket._finishInit (_tls_wrap.js:636:8) code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY' }
my code looks like this:
'use strict';

const puppeteer = require('puppeteer')
const fs = require('fs')
const request = require('request');

(async() => {
    const browser = await puppeteer.launch()

    let page = await browser.newPage()

    await page.setViewport({ width:0, height:0 })

    await page.goto('http://nfe.sefaz.go.gov.br/nfeweb/sites/nfe/consulta-publica/principal')

    await page.setRequestInterception(true);

    const pfx = fs.readFileSync('C:/temp/agf_cert.pfx');
    const password = 'password'

    await page.waitFor(3000)

    page.on('request', interceptedRequest => {
        // Intercept Request, pull out request options, add in client cert
        const options = {
            uri: interceptedRequest.url(),
            method: interceptedRequest.method(),
            headers: interceptedRequest.headers(),
            body: interceptedRequest.postData(),
            pfx: pfx,
            passphrase: password,
        };

        // Fire off the request manually (example is using using 'request' lib)
        request(options, function(err, resp, body) {
            // Abort interceptedRequest on error
            if (err) {
                console.error(`Unable to call ${options.uri}`, err);
                return interceptedRequest.abort('connectionrefused');
            }

            // Return retrieved response to interceptedRequest
            interceptedRequest.get({
                status: resp.statusCode,
                contentType: resp.headers['content-type'],
                headers: resp.headers,
                body: body
            });
        });

    });

    await page.click("a[href*='nfe/consulta-publica'] button")

    await page.waitFor(2000)

    browser.close()
})()

Has anyone been able to log in with the certificate of agreement mentioned above without error? Or does anyone know how to resolve the error I mentioned above?

@ElderVivot try with these options:
    const options = {
      uri: interceptedRequest.url(),
      method: interceptedRequest.method(),
      headers: interceptedRequest.headers(),
      body: interceptedRequest.postData(),
      gzip: true,
      agentOptions: {
          pfx: pfx,
          passphrase: password,
          securityOptions: 'SSL_OP_NO_SSLv3'
      }
    };

It should fix your autentication problem... in my case however, for another website, I'm not able to dowload some resources (js, css files) after it

@carbuz2
Hi, I tried the code you provided, but the following error occurs:
"Uncaught TypeError: Cannot read properties of undefined (reading 'toString')
Process exited with code 1"
Has anyone managed to log in using certificate?

In the end I was not able to do it using puppeteer...
I used casperjs instead (phantomjs worked as well if I remember correctly).
The terminal  command is:
casperjs --ssl-client-certificate-file=${pathCertPem}   --ssl-client-key-file=${pathKeyPem}  --ssl-client-key-passphrase=${passphrase}  --ignore-ssl-errors=true     ${yourCasperFile}

My workaroud is use headfull puppeter running in docker without GUI using xvfb:
Docker

Install Google Chrome & xvfb

RUN wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \    && echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list
RUN apt-get update
RUN apt-get install -yq gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget x11vnc x11-xkb-utils xfonts-100dpi xfonts-75dpi xfonts-scalable xfonts-cyrillic x11-apps
RUN apt-get install -yq xvfb google-chrome-stable

Add SSL certificate to Google Chrome

RUN apt-get install -yq libnss3-tools
RUN mkdir -p $HOME/.pki/nssdb
RUN pk12util -d sql:$HOME/.pki/nssdb -i /tmp/cert.pfx -w /tmp/cert.pfx.pass

Set up autoselecting added SSL certificate in Google Chrome

{ "AutoSelectCertificateForUrls": ["{\"pattern\":\"*\",\"filter\":{\"ISSUER\":{\"CN\":\"XY name\"}}}"]}

mkdir -p /etc/opt/chrome/policies/managed
cp policy.json /etc/opt/chrome/policies/managed

Run nodejs part with rendering redirected to xvfb

CMD xvfb-run --setver-args='-screen 0 1024x768x24" node index.js

Nodejs

Install npm Puppeteer package

npm install puppeteer

Run Puppeteer

const browser = await puppeteer.launch({ executablePath: '/usr/bin/google-chrome-stable', headless: false, args: [' - no-sandbox',' - disable-setuid-sandbox'] });

Tested on render.com.
Example project


Process command is truncated on Windows

Describe the bug
Process command is truncated on Windows after upgrading from 5.6.22 to 5.12.4.
To Reproduce
See https://github.com/jonas-ah/systeminformation-process-command-bug.
This example lists the current process, which is started with a long command line, using the processes function.
Current Output
Using 5.12.4:
"C:\\Program Files\\nodejs\\node.exe" .\\src\\ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz01234567
Expected behavior
Using 5.6.22:
"C:\\Program Files\\nodejs\\node.exe" .\\src\\ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789\\index.mjs
Environment (please complete the following information):

systeminformation package version: 5.12.4
OS: Windows 10

@jonas-ah need to make some investigation here … will hopefully come up with a solution as soon as possible.

@jonas-ah still unsure why this happens ... can you provide the output of
Get-WmiObject Win32_Process | select ProcessId,ParentProcessId,ExecutionState,Caption,CommandLine,ExecutablePath,UserModeTime,KernelModeTime,WorkingSetSize,Priority,PageFileUsage,CreationDate | fl

@jonas-ah ... well I guess I have an idea. Will provide a fix today in the evening.

@jonas-ah ... version 5.12.8 just released. Can you check it?

It's working. Thanks! 😃

@jonas-ah … thank you for your fast feedback and once again sorry for having not responding so long …


[sparkle] Refactor IconButton

Description

Close #8243

Risk
Deploy Plan

Publish a new release candidate for sparkle.

Let's not bump sparkle here as the changes are only refactoring, could you rollback the package.json changes?


Use file API to bundle the ZK circuits

Replace getting circuit from ipfs or any cloud with the manifest files section and snap_getFile method

@lukachi reflect the changes in the changelog, including the updated MM libraries


How to message volunteers - User Doc

Breakout from #1362
We should add a documentation page describing how to message volunteers from allReady

Would the documentation be put in the wiki?

@wmay1991 I think best option is to build Markdown pages to sit under allready/docs/user_documentation

I think documentation is suuuper interesting so I've started to try and write some for this project.
I'd love to receive feedback including if I'm doing something completely wrong 😋

@stevejgordon What more work is required on this before you can consider this issue closed? 🙂

I'd say that your documentation covers this requirement for now. Thanks!


Edited user and workspace tab to only display the name for accessibility #184530

Fix #184530
When you hover the mouse over user or workspace in settings it will only show again user or workspace instead of the path to the settings.
This allows for accessibility features such as NVDA for windows and macOS VoiceOver to not be as verbose and confuse the user.
To Test: Go to settings and hover the mouse over user and workspace in the tab section for scope switching.

Also, the build failed. Please try running yarn && yarn watch locally and then fixing the build errors.

@microsoft-github-policy-service agree


Gantt Chart Layout

Adds a Gantt Chart Layout to Directus.
Notes:

Uses a bundled version of the latest Frappe Gantt-library, as their npm action is broken and hasn't published the latest version. It also contains a minor fix to an issue that made it difficult to drag and drop items on some browsers (fixed by changing offsetX/Y to clientX/Y).
Should work in both regular layouts and with selectMode, and I've tested running filters. This is my first layout extension so if you see something that I missed to test let me know!

Fixed
The library used isn't very responsive in this way as it's rendering svgs on the fly, but I found a configuration to extend the "padding" used, so it looks better on most common screen sizes
3-5. Added error handling now, opted to use the notification store to display any date interval errors so the view can still be used without it crashing.
Fixed
Should be fixed, seemed to be a CSS issue

Any update on 5, 6, and 7 @Arood ?

@phazonoverload oh, didn't notice that Github ruined my formatting, they are all done

Feedback

Upon re-review the time still changes when I change days, same for other units (changing month also changes days etc).
https://github.com/user-attachments/assets/f4d841ea-ebe9-41cf-aaf6-6488b856b070
The notice now displays on any change, we should maybe only display it on initial navigation/page load?

@ComfortablyCoding I noticed when testing that the issue might appear when using a Datetime-type, but it works as intended with Timestamp. Which seems to make sense as Datetime doesn't contain any timezone information, so I need to handle that. Does that description match your collection setup when testing?

@ComfortablyCoding I noticed when testing that the issue might appear when using a Datetime-type, but it works as intended with Timestamp. Which seems to make sense as Datetime doesn't contain any timezone information, so I need to handle that. Does that description match your collection setup when testing?

Yes, that does seem to be the case.

What's left to get this finished? It's running a bit behind.

What's left to get this finished? It's running a bit behind.

The issues outlined in https://github.com/directus-labs/extensions/pull/45#issuecomment-2325232688

Oh, I was just looking at this and sent a new update :)
I believe I figured out how to fix the date issue, thanks for confirming the issue @ComfortablyCoding
Regarding the errors I adjusted so the error shows once per set of items that errored (stored in sessionStorage so it resets for each session).

Oh, I was just looking at this and sent a new update :)
I believe I figured out how to fix the date issue, thanks for confirming the issue @ComfortablyCoding
Regarding the errors I adjusted so the error shows once per set of items that errored (stored in sessionStorage so it resets for each session).

Sounds good, should issue #3 regarding the app crashing be addressed as well in the last update?

@ComfortablyCoding Ah sorry, I missed that one. Should be easy enough to add a check there though, I'll fix it in a few mins

@ComfortablyCoding there we go! Added another error popup, handled the same way as the invalid date interval

I'm sure you got this, but we held this back to release in October's set. :)


Performance improvements in the library

Description
Currently, the library doesn't perform well with a huge address history and messages. Some operations (address generation, syncing, read operations) become extremely slow and is not convenient for users such as exchanges. We should investigate the pain points in the library and should improve the implementation so that there are no performance issues regardless of the size of db.
Motivation
The wallet library should not have a poor performance with a big database.
Requirements

[ ]  Decouple addresses from account object — One of the pain points @Thoralf-M found was the writing of new addresses to the account object. For instance, if you have 500k addresses and you try to generate a new address, the address generation process will be extremely slow;
[x] Decouple messages from account object — Similar to the previous issue, messages should also be decoupled from the account object so that there are no performance overheads when new messages are added;
[x] All the changes should also be reflected in nodejs, java and python bindings;
[ ] The documentation for library and its bindings should be updated.

Open questions (optional)

Do we need to implement paging for reading addresses & messages? If yes, how would the API look like?
After decoupling the addresses & messages from the account object, how should the users read addresses & messages?
What kind of stress tests can we perform to see if there are more pain points in the library (performance wise) ?

Are you planning to do it yourself in a pull request?
No.

Messages are already separated from the account object

Decouple addresses from account object
Would require changing the logic to rely only on a part of the addresses (stop getting data from old addresses or something like that)
If one accounts gets slow because too many addresses are used one can just move to a new account to get the same result and then no breaking changes are required


Implement RDM style cell checking

Implement RDM-style cell checking where golbat will notice if forts removed.
Ensure there is a pokestop / gym webhook sent to indicate a fort is removed

#44 implements

Second point not yet. We need a webhook format for that. But I would prefer another PR for that?!

#48 follow up ticket


Added ground symbol

Issue #171

issue #171

Hey @seveibar @Timer00 @imrishabh18 please review this

@imrishabh18 Done

The lock file and the diff png file is still there.

@imrishabh18 i have deleted the two files

Looks great! Resolving the merge conflicts will be good to merge

how to resolve conflict @imrishabh18

rebase your branch with the main branch

@imrishabh18 Done


feat: Button to Redirect Users to Mapped Videos on harkirat.classx

PR Fixes:

Added a button to redirect users to mapped videos on harkirat.classx.
Integrated video ID mapping between app.100xdevs and harkirat.classx.

Resolves #1590
Checklist before requesting a review:

[x] I have performed a self-review of my code.
[x] I assure there is no similar/duplicate pull request regarding the same issue.

Note: Needs to be tested in the Production environment.

Thinking about it. It's not possible. We can't assume someone has purchased certain course.


Request to move ar_archive_writer to the rust-lang repo

https://github.com/bjorn3/ar_archive_writer is extracted from and will be used by https://github.com/rust-lang/rust/pull/97485. It is currently a rewrite of LLVM's archive writer in Rust, allowing it to be used by any backend.
I think access should be given to the compiler team and everyone working on codegen backends (as of right now that did be me and @antoyo).
Previously discussed in https://rust-lang.zulipchat.com/#narrow/stream/231349-t-core.2Flicensing/topic/cg_clif.20ar

I can handle this - can you transfer the repo to me or make me an owner of it? (Not sure the latter is possible with human and not org owned repos).

I initiated a transfer to you.

@bjorn3
Any reasons not to contribute this to object-rs instead?
They already have archive format structures and an archive reader, and archive writer also seems like an acceptably large piece of code to add to that crate.

This crate is Apache-2.0 WITH LLVM-exception licensed as it is derived from LLVM. Object is Apache-2.0 OR MIT licensed. Apache-2.0 WITH LLVM-exception is not an acceptable license for the standard library, but object is a standard library dependency.

Finished the transfer.

Thanks!

By the way for the crates.io package I have to add rust-lang-owner as owner, right?

Yes, please do so. We don't yet have that automation in place for publishing, but hopefully soon.

Invited rust-lang-owner. What is an expected time before it invites the invitation?

"Human time" -- currently a manual process. Just accepted.


Default Flask Web Role template does not work in Azure

Visual Studio 2015 Update 2
Python Tools 2.2.3 for VS 2015
To repro, in Visual Studio 2015:

New Project -> Python -> Azure Cloud Service -> Flask Web Role
Install into Virtual Environment, Python 2.7 64-bit
Publish to Azure

Web page returns with 500 Internal Server Error, diagnostics logs shows: Failed to load role assembly: Microsoft.PythonTools.WebRole, Version=<IP_ADDRESS>5, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
The entire project including the virtual environment is attached, but this should be easily reproducible from scratch.
AzureCloudService1.zip

This seems to be true for Visual Studio 2013 with Python Tools 2.2 as well.

Hi!  Please try with Python 2.7 32-bit:
https://github.com/Microsoft/PTVS/wiki/Cloud-Project#webpi-references

Is this problem solved? I still got this error even though I installed 32bit.

Have a look at https://azure.microsoft.com/en-us/documentation/articles/cloud-services-python-ptvs/ especially the updated instructions on how to install Python on a cloud service.
Basically, WebPI turned out to not be as useful as we thought, so we're revising our instructions. It means more work for you, but you'll also get much more control and insight into what's going on.

Got it. it's working fine but this error message is still recorded in WebRole log. Maybe internal Startup process invokes this module.

Failed to load role assembly: Microsoft.PythonTools.WebRole, Version=<IP_ADDRESS>5, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

So we used to be forced to deploy that because everything had to be .NET. Are you able to look on the web role and see if it's there (or in the .cspack file - it's just a ZIP)? Maybe we aren't deploying it for some reason...


New Jersey blocks future dated opinions

I checked a bunch of errors in New Jersey and it appears that future dated opinions
ie tomorrow are not available.  Looks like they mean it when they set a published date.

Can you share the errors? I'm confused who is blocking here. Us? NJ?

No one is blocking us.
New Jersey provides a big JSON
https://www.njcourts.gov/attorneys/assets/js/objects/opinions/op2017.json
that the scraper users for the Supremes, Appeals Published Unpublished etc.
Looks like this
{
        "OpinionID": "A-78-20",
        "ID": "085608",
        "DocumentURL": "/attorneys/assets/opinions/supreme/a_78_20.pdf",
        "PublishDate": "05/02/2022",
        "Summary": "
Because a detective here repeatedly contradicted and minimized the significance of the Miranda warnings -- starting at the outset of the interrogation and continuing throughout -- the State cannot shoulder its heavy burden of proving defendantâ€™s waiver was voluntary. The Appellate Division majority correctly concluded defendantâ€™s statement had to be suppressed.
",
        "Title": "State v. O.D.A.-C. (085608) (Bergen County & Statewide)"
    }

but it also provides stuff like
{
            "OpinionID": "A-2726-20",
            "DocumentURL": "/attorneys/assets/opinions/appellate/unpublished/a2726-20.pdf",
            "PublishDate": "05/27/2022",
            "Title": "MICHELLE SABATINI VS. LOUIS SABATINI (FM-01-0772-15, ATLANTIC COUNTY AND STATEWIDE)"
        },
        {
            "OpinionID": "A-0475-19",
            "DocumentURL": "/attorneys/assets/opinions/appellate/unpublished/a0475-19.pdf",
            "PublishDate": "05/26/2022",
            "Title": "STATE OF NEW JERSEY VS. ANTHONY BAINES (17-02-0155, UNION COUNTY AND STATEWIDE)"
        },

The top one throws a 404 and the bottom one doesn't.  It appears to me that they've set the published date in the JSON for tomorrow.  Even though we know the URL and scrape it, we can't access the document until tomorrow.  I was just going to ignore opinions with Published Dates in the future and move on.

~Courts~ Humans are so weird. Nice find and fix!

Well... I still stand by my belief, but I'm still waiting for validation as to when these PDFs become available.
Sample for May 27th
Is not yet available

Timing: Document became available at 9:59 AM


defusedxml is only required when using the OpenNebula provider

defusedxml is only required for ON.

@gwarf Is this a good idea? Having dependencies for various available providers as suggested? Even though choosing a provider is only a configuration choice?

@arax in fact it was already like this, just continuing in the same way as it was done for the novaclient package.
For the time being the RPM and deb do not include all the required dependencies for ON and OS (for ON you have to install at least defusedxml and for ON you have to install at least python-novaclient).
For the requirements.txt for pip we can follow what @enolfc proposed but I'm not sure what to do for RPM and debs. What is sure is that forcing people to install and enable a repo for a package that they don't need is not appropriate (specifc to RHEL with EPEL here).
What do you think is the most appropriate?
Ideally as we will have two repo that will be specific to two CMF I would prefer to have all packages including all the required dependencies, but it will be more work and we will have to duplicate the build files...

@gwarf So python-novaclient is in standard repositories on both platforms and only python-defusedxml requires EPEL?

I don't think that python-novaclient is in standard repo on both platforms, but it was just already there in the debian/control file...
You  have to configure some OS release-specific repo to install python-novaclient it on RHEL.
So both should be handled in the same way as they are boh present in default Xenial repo and both absent of default CentOS 7 repos...
We just need to agree and follow a policy for this, everything is just a matter of policy it seems ;)

@gwarf Oh, yes, everything is just a matter of policy :-)
If we don't want to force CentOS 7 users to enable both repositories regardless of the CMF they are using, we would have to create two separate RPMs. One for OpenStack (with dependency on novaclient, without files supporting ON provider) and one for OpenNebula (with dependency on defusedxml, without files supporting OS provider). I don't like the idea of installing software that doesn't work in certain configurations because of missing dependencies ... but that might be just my personal preference. I understand that it would double the packaging workload for you.

@gwarf  That was a nice monologue :)
I also think separate meta-packages for ON and OS could provide a solution to the problem.
E.

OK, so it seems there is a consensus and as we have in CMD CMF-specific repo it seems appropriate to look at implementing CMF-specific packages.
The problem will be with the AppDB, all the packages versions goes to the same repository (like http://repository.egi.eu/community/software/cloud.info.provider/0.x/releases/ubuntu/dists/xenial/main/binary-amd64/ ) so we cannot have two packages with the same name but different dependencies, @enolfc what was your idea with the "meta-pacakges" ? Creating some kind of CMF specific meta-pacakge (like cloud-info-provider-openebula and cloud-info-provider-openstack ?) including the cloud-info-provider package and other CMF-specific packages as dependencies?

@gwarf Yes: two different packages with different naming to avoid conflicts that depend on cloud-info-provider + the specific ones.

hi all. We're close on 10 months after this, and #62 is still open, and this pull request discussion is still open.
since the code is merged, I would suggest closing and locking the issues, and moving the discussion to the discussion forum


When will this code be available?

I look forward to seeing your work. When will this code be available?

+1


Added test for AAS with extension

Added  a test for deserialization of AAS with Extension - which leads currently to an AasEnv with an empty Submodel.

Fixed by #136


MicroMasters data migration command and model

Pre-Flight checklist

[x] Migrations

[x] Migration is backwards-compatible with current production code

[x] Testing

[x] Changes have been manually tested

What are the relevant tickets?
Fixes #721
What's this PR do?

Adds data models for mapping course and program ids
Adds a management command that runs SQL files in alphanumeric order by filename.

How should this be manually tested?

You should be able to go to django-admin and add new records for CourseId and ProgramId
You should be able to run the ./manage.py import_micromasters_data command

@rachellougee Addressed your feedback, I'm not sure exactly how the postgres driver determines the row count, but that property is what the documentation indicates should do the job.

@rachellougee addressed your feedback, also noticed that ProgramId had an FK to Course, so I fixed that and redid the migration. You should run ./manage.py migrate micromasters_import zero locally before pulling my latest changes otherwise you'll end up in a weird db state.


Schema Compare diff editor windows don't have horizontal scrollbar

Azure Data Studio Version: master

Steps to Reproduce:

Run Schema Compare and checkout the diffs

Expected: If SQL content overflows visible editor window size then a scrollbar is visible in order to see all content.
Actual: No horizontal scrollbar in the diff editor windows.

Note there is no horizontal scrollbar in the below screenshot even though text overflows.

@kisantia is already investigating

@udeeshagautam Can I take this issue, please? I would like to help to investigate and fix this. Thanks.

The bug can be worked around by using "Shift + Mouse Scroll" to scroll horizontally.

Given that there already exists a bottom horizontal scrollbar for Schema Compare tab, adding another horizontal scrollbar for each view in the diff viewer might be a bit confusing.
It could be possible that this bottom scrollbar is unwanted in this case.
The vertical scrollbar also has some issues for screen with large heights, it does not reach the bottom bar.

My suggestion for this issue:
Must: Show the scrollbar for each view in diff viewer
Should:

Sync the scrollbar in both diff view when one view is scrolled (like the current behavior of vertical scrollbar)
Fix the vertical scrollbar max height issue
Hide the bottom scrollbar when not needed


How many Snps used in the PCA ?

Hi Brent, I am using Peddy to get ancestry from VCF files from RNA-seq samples which have 5-15 million uniquely mapped reads, so the quality is not great. My question is, how do I know how many snps were used in the PCA ? This is quite important in my analysis.
Thanks.
Yusuph.

you can look at het_check.csv and look at the sampled_sites column to know how many sites were used in the PCA.


electron forge + multiple renders

Is it possible to use this plugin if I have an electron application with multiple renders?
I have 3 renderers with node target and one with nodeIntegration=false, this cannnot change.
Please advise! Thank you.

Hello @iamisti! Yes, you can use this plugin in electron main and/or renderers separately. Since each is a separate webpack configuration, you'd need to enable it in each. Our current understanding is that it is currently not possible to use in renderers with nodeIntegration=false, as the implementation needs access to node to decode the bytecode.


⚠ WSINGRESOS - GENERICO has degraded performance

In 2ddbaed, WSINGRESOS - GENERICO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/servicios/wsGenericoPagosWeb.r) experienced degraded performance:

HTTP code: 200
Response time: 2192 ms

Resolved: WSINGRESOS - GENERICO performance has improved in 150e110 after 21 minutes.


lib.platform.loongnix: init

Description of changes
Adding the support of loongarch64 platform
but current the platform couldn't work, the detail information could be seemed in the commit messages.
Sorry, I haven't enough time to fix this problem since the middle of May, thus I have to make a kind of PR right now, and see if anyone is willing to help here.
Things done
Adding the support of loongarch64
adding a kind of mapping in linux-header from loongarch64 into loongarch
adding code in pkgs/development/tools/misc/binutils/default.nix to avoid to using gold linker in the compile of loongarch64 arch.

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

The platform seems facing a situation that it hasn't been supported by newlib and the glibc under the version 2.361, thus maybe it's need to update the version of glibc

@ofborg build pkgsCross.loongarch64.hello

@wegank  Looks like the generated hello program could successfully run in loongarch64 machine. But Nix still failure.
The running linux kernel is still 4.19
[root@bogon bin]# pwd
/nix/store/zzsh8cmdcdhzx0mpznifb33bnxffhm6b-nix-loongarch64-unknown-linux-gnu-2.13.3/bin
[root@bogon zzsh8cmdcdhzx0mpznifb33bnxffhm6b-nix-loongarch64-unknown-linux-gnu-2.13.3]# ls
bin  etc  lib  libexec  share
[root@bogon zzsh8cmdcdhzx0mpznifb33bnxffhm6b-nix-loongarch64-unknown-linux-gnu-2.13.3]# cd bin/
[root@bogon bin]# ls
nix  nix-build  nix-channel  nix-collect-garbage  nix-copy-closure  nix-daemon  nix-env  nix-hash  nix-instantiate  nix-prefetch-url  nix-shell  nix-store
[root@bogon bin]# ./nix
error: querying signal mask: Invalid argument
[root@bogon bin]# file nix
nix: ELF 64-bit LSB pie executable, LoongArch, version 1 (SYSV), dynamically linked, interpreter /nix/store/k8l0drxnsjdrlvy2paaqrahpkq73qhnm-glibc-loongarch64-unknown-linux-gnu-2.37-8/lib/ld-linux-loongarch-lp64d.so.1, BuildID[sha1]=081ddaf4ee84797b1875b64cc39db093c6ab7518, for GNU/Linux 5.19.0, not stripped

by the ways, is it anyway to rebuild the program when the nixpkgs has changed ?

The running linux kernel is still 4.19

The binary compatibility with the old world is indeed not guaranteed.

By the ways, is it anyway to rebuild the program when the nixpkgs has changed?

It is not possible to avoid rebuilding the world if stdenv is affected. You will experience this from time to time if you continue to bootstrap a native loongarch64-linux stdenv.


Fix a memory leak with command modules

This commit fixes a memory leak that can happen with Linker::module
when the provided module is a command. This function creates a closure
but the closure closed over a strong reference to Store (and
transitively through any imports provided). Unfortunately a Store
keeps everything alive, including Func, so this meant that Store was
inserted into a cycle which caused the leak.
The cycle here is manually broken by closing over the raw value of each
external value rather than the external value itself (which has a
strong reference to Store).

@sunfishcode mind taking another look at this?


Wrong constant name

Wrong constant name in
android-architecture/todoapp/app/src/main/java/com/example/android/architecture/blueprints/todoapp/data/source/local/TasksDbHelper.java
public class TasksDbHelper extends SQLiteOpenHelper {

    //...

    private static final String BOOLEAN_TYPE = " INTEGER";

    //...

There is no boolean type in SQLite and you store booleans in Integer columns as 0 or 1.


Compound Database Search

Basic information
MZmine 3.3.0
What happened
The adduct search option is not saved after the first change. Reset negative, enabling the possible adducts, ok. After opening the setup again or running the batch mode different adducts are enabled.  (Short notice: The negative mode has the M+Na+ adduct as an option.)

I think I fixed this in #1195

I get this issue frequently.


Diff parsing fails when filenames contain unicode characters

Subject of the issue
Unicode characters in filenames breaks diffing
Your environment

git version 2.20.1
git (1.5.0)
ruby 2.6.4p104 (2019-08-28 revision 67798) [x86_64-linux]

Steps to reproduce
$ mkdir -p /tmp/test && cd /tmp/test
$ git init
$ printf '\xE2\x98\xA0' # print a skull and crossbones symbol
$ touch 'some_file'
$ git add .
$ git commit -m"init"
$ touch 'my_other_file_\xE2\x98\xA0'
$ git add .
$ git commit -m"commit"

git = Git.init '/tmp/test'
git.diff('@^').each { |x| ... }

Expected behaviour
The diff to be produced as usual
Actual behaviour
NoMethodError: undefined method `[]' for nil:NilClass
The first line of a diff is usually something like git --diff a/somefile b/somefile, but when the filename contains a unicode character, the filenames are escaped, (e.g. diff --git "a/my_other_file_\\xE2\\x98\\xA0" "b/my_other_file_\\xE2\\x98\\xA0") and this regex fails to detect the line.

I believe this issue was addressed with #504


LLvm rebase

merge llvm-rebase to main branch

add support for linkage-attribute
add convertPtoint

Please integrate the changes from: https://github.com/intel/intel-xpu-backend-for-triton/tree/chengjun/alternative_llvm_package

Up to now, there are two ways to use intel llvm.

export TRITON_INTEL_LLVM, it will download intel_llvm to ~/.triton/intel_llvm, if already exists, will not download
export TRITON_INTEL_LLVM_DIR as user provide llvm path

export TRITON_INTEL_LLVM, it will download intel_llvm to ~/.triton/intel_llvm, if already exists, will not download

For this one, can we merge this var into TRITON_CODEGEN_INTEL_XPU_BACKEND=1. @leizhenyuan

export TRITON_INTEL_LLVM, it will download intel_llvm to ~/.triton/intel_llvm, if already exists, will not download

For this one, can we merge this var into TRITON_CODEGEN_INTEL_XPU_BACKEND=1? That means, if user want to build triton with xpu backend, it will download intel_llvm to ~/.triton/intel_llvm by default, if already exists, will not download. @leizhenyuan

ok

@chuanqi129 , you can mail @leizhenyuan in case @leizhenyuan misses the GitHub message.


Adding useMeta hook

@stevenpersia this can be Added ?

Can you give this a try please @webbertakken

There is multiple issues in your last commit : content from merge conflict system.
Sorry, I can't merge your PR.


revert: snow

Reverts open-amt-cloud-toolkit/sample-web-ui#1584

:tada: This PR is included in version 3.5.2 :tada:
The release is available on:

GitHub release
v3.5.2

Your semantic-release bot :package::rocket:


Update automated-backup.md

Docs Build status updates of commit 7f745af:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-sql/virtual-machines/windows/automated-backup.md
:bulb:Suggestion

Details

azure-sql/virtual-machines/windows/automated-backup.md

Line 49, Column 25: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/sql/database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option?view=sql-server-ver16' will be broken in isolated environments. Replace with a relative link.
Line 49, Column 25: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: https://docs.microsoft.com/sql/database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option?view=sql-server-ver16

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@MashaMSFT can you help to merge changes please?

Docs Build status updates of commit 6b09237:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5b3eb83:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

azure-sql/virtual-machines/windows/automated-backup.md
:bulb:Suggestion

Details

azure-sql/virtual-machines/windows/automated-backup.md

Line 45, Column 240: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/sql/database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option?view=sql-server-ver16' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 240: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: https://docs.microsoft.com/sql/database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option?view=sql-server-ver16

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#sign-off


Enable 3d dot

This pull request enable 3d dot.
With this change, we can pass 161 test_core.py::test_dot3d unit test cases.

Does the test in test_core.py work now ?

It can take the 3D tensor input and lowering to the end, but the result is incorrect.
It should be the indices calculation issue, I'm working on figuring them out.

This issue is still WIP. Current status for dot3d UT is that it have 85 passes over 161 cases.
Most of the remaining failures are caused by these 2 reasons:

FMA Dot do not support 3d yet. I'm checking why these cases go through FMA Dot, then decide should we apply 3d dot changes to FMA. This would need to change some upstream common file.
Batch dim offset calculation seems not correct.

Latest run shows:
language: passed: 10859, failed: 0, skipped: 170, xfailed: 1017, total: 12046, fixme: 0, pass rate (w/o xfailed): 98.46%

The skipped are too many. Can you update the skil lists please ?

Latest run shows:
language: passed: 10859, failed: 0, skipped: 170, xfailed: 1017, total: 12046, fixme: 0, pass rate (w/o xfailed): 98.46%

The skipped are too many. @LiyangLingIntel can you update all the skip lists please ?

Removed 3d dot cases from the default and xe2 config skip lists.

language: passed: 11020, failed: 0, skipped: 9, xfailed: 1017, total: 12046, fixme: 0, pass rate (w/o xfailed): 99.92%


Timing issue

Issue has been resolved.
Main question now: How can I obtain the WhatsApp version?

Since 2 weeks, messages sent using WA-js chat.sendTextMessage are no longer sent. They are marked with a 'clock' icon, indicaton network issues. When trying a second time I get a DuplicateMessageError.
No code was changed, behavior is the same on WA-js v2.24.1 and 2.24.2 and older versions.
Manually sent messages work fine, so there is no 'real' network issue so it appears that WA-js is triggering this behavior since the latest WA update.

Does this resonate with someone?
Is there a solution?
Where can I get the WhatsApp version?
How to reproduce:
Open console (or code) and enter:
<EMAIL_ADDRESS>'test', {
createChat: true
});
Issue: message is marked as 'not sent'

Using the latest version of wa-js can resolve the issue.

Fixed by https://github.com/wppconnect-team/wa-js/commit/d95b140164e688c2603487602283039114a9e9b0 ?


Small Typo Update

Allow "delegating" fresh credentials with NTLM-only server authentication
Instead of
Allow fresh credentials with NTLM-only server authentication
Thank You!

Thank you :).


unique model map regions

fixes #48

looks good to me, but wouldn't it make more sense to give meaningful name to the tests, rather than the issue number?


app not executing on Python 3.x

README.md shows that :

Dependencies

Python 2.x or Python 3.x
Node.js
Pip
Flask
BeautifulSoup4

But dependencies using pip could not be installed for python3.x .
Quoting the error message :

File "/tmp/pip-build-s4ac1_v3/librabbitmq/setup.py", line 191
except Exception, exc:

This is because librabbitmq is not supported in Python3.x version.
Please change the README.md .

The librabbitmq code on GitHub has this problem fixed but that fix is not in the current librabbitmq release.

@cclauss Although it has been fixed but it is still not in the release, so the current version README.md should conform to latest release version of librabbitmq . Please correct me if I am mistaken.

Hi @pratik0509 You are correct...  I was writing too fast and did not express myself clearly.  As you can see above, I have commented on an issue in upstream.  However, that issue has been for a year and a half...

The dependency mechanize is also not Python 3 compatible...
https://github.com/fossasia/query-server/blob/master/requirements.txt#L12

@pratik0509 Can you close this issue, given the latest Python3 port PR (#152).

Our Travis tests fail on Python 3:
https://github.com/fossasia/query-server/pull/168/files
https://travis-ci.org/fossasia/query-server/builds/278811497
This issue should be reopend and should remain open until our Travis tests pass on Python 3.

Sorry. Failed to notice that.

Did #177 close this issue or is there another problem?

Hi @cclauss can you please elaborate on the point? I am unable to comprehend your statement.

I think we can close this issue.


Upgrade dependencies to latest

Codecov Report

Merging #1100 into master will decrease coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1100      +/-   ##
==========================================
- Coverage   94.07%   93.68%   -0.39%
==========================================
  Files          39       39
  Lines        4269     4339      +70
  Branches      468      740     +272
==========================================
+ Hits         4016     4065      +49
- Misses        253      254       +1
- Partials        0       20      +20

Impacted Files
Coverage Δ

browser/model/devstudio-autoinstall.js
97.29% <0%> (-2.71%)
:arrow_down:

browser/model/helpers/hash.js
85.29% <0%> (-2.59%)
:arrow_down:

browser/pages/install/controller.js
79.85% <0%> (-1.73%)
:arrow_down:

browser/model/helpers/downloader.js
96.13% <0%> (-1.66%)
:arrow_down:

browser/pages/account/controller.js
82.11% <0%> (-1.33%)
:arrow_down:

browser/model/jbossfusekaraf.js
95.09% <0%> (-0.83%)
:arrow_down:

browser/services/data.js
91.5% <0%> (-0.79%)
:arrow_down:

browser/pages/confirm/controller.js
87.59% <0%> (-0.78%)
:arrow_down:

browser/model/cdk.js
99.24% <0%> (-0.76%)
:arrow_down:

browser/model/installable-item.js
93.47% <0%> (-0.71%)
:arrow_down:

... and 16 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 509fdd1...aa0979b. Read the comment docs.


<EMAIL_ADDRESS>annotation is necessary.

Describe the bug
vue version used this problem
      src/tooltipContent.ts(76,14): error TS2742: The inferred type of 'OkuTooltipContent' cannot be named without a reference to '.pnpm/@floating-ui+utils@0.1.1/node_modules/@floating-ui/utils'. This is likely not portable. A type annotation is necessary.

Screenshots

i used pnpm node 18.
It looks like it has an external problem.

I don't understand this issue as you haven't given much context. It looks like a pnpm installation issue and possible version mismatches. Can you try uninstalling all Floating UI packages, and then re-installing them correctly?

import { defineConfig } from 'tsup'
import pkg from './package.json'

const external = [
  ...Object.keys(pkg.dependencies || {}),
  ...Object.keys(pkg.peerDependencies || {}),
  '@floating-ui/vue',
]

export default defineConfig((options) => {
  return [
    {
      ...options,
      entryPoints: ['src/index.ts'],
      external,
      dts: true,
      clean: true,
      target: 'node16',
      format: ['esm'],
      outExtension: () => ({ js: '.mjs' }),
    },
  ]
})

Actually, the problem occurs when I'm building a library and using what I've done elsewhere.

pnpm i node_modules in problem this library

I guess this happens on workspace pnpm domains. I solved it this way. https://github.com/oku-ui/primitives/pull/335.
Thank you back.


Document Search Template API usage

Currently NEST has support for the Search Template API (see tests here but doesn't have any documentation for them.  Would be useful to document this API given the the current deprecation of the Template Query in Elasticsearch (the spiritual predecessor of Search Template).

@joshuar agreed! we have an open ticket to automatically generate documentation from all *ApiTests.cs and *CrudTests.cs files. Everything is in place for it we just need to manually verify the output before adding 100+ new documentation pages 😄
Closing this in favour of the other ticket #2248

Added a check box to #2248 for this one; I think it's a good candidate for a more detailed page demonstrating serializing request and adding as template

Agreed although the CrudTest should/would provide such a walkthrough.