Im unable to generate .dll while building the .net framework application. Please help on below error.

Description
Build started 12/15/2022 3:17:26 PM.
1>Project "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer.sln" on node 1 (default targets).
1>ValidateSolutionConfiguration:
Building solution configuration "Debug|x64".
1>Project "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer.sln" (1) is building "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj" (2) on node 1 (default targets).
2>PrepareForBuild:
Creating directory "bin\x64\Debug".
Creating directory "obj\x64\Debug".
1>Project "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer.sln" (1) is building "D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj" (3) on node 2 (default targets).
3>PrepareForBuild:
Creating directory "bin\x64\Debug".
Creating directory "obj\x64\Debug".
ResolveAssemblyReferences:
Primary reference "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL".
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2203,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj]
For SearchPath "{HintPathFromItem}".
Considered "D:\a\FDT\FDT\FastDataTransfer\packages\log4net.2.0.8\lib\net45-full\log4net.dll", but it didn't exist.
For SearchPath "{TargetFrameworkDirectory}".
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Facades\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Facades\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Facades\log4net.exe", but it didn't exist.
For SearchPath "{AssemblyFoldersFromConfig:C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\AssemblyFolders.config,v4.5.2}".
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.exe", but it didn't exist.
For SearchPath "{Registry:Software\Microsoft.NETFramework,v4.5.2,AssemblyFoldersEx}".
Considered AssemblyFoldersEx locations.
For SearchPath "{AssemblyFolders}".
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\log4net.exe", but it didn't exist.
Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\log4net.winmd", but it didn't exist.
Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\log4net.dll", but it didn't exist.
Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\log4net.exe", but it didn't exist.
Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\log4net.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\log4net.dll", but it didn't exist.
Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\log4net.exe", but it didn't exist.
For SearchPath "{GAC}".
Considered "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL", which was not found in the GAC.
For SearchPath "{RawFileName}".
Considered treating "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL" as a file name, but it didn't exist.
For SearchPath "bin\x64\Debug".
Considered "bin\x64\Debug\log4net.winmd", but it didn't exist.
Considered "bin\x64\Debug\log4net.dll", but it didn't exist.
Considered "bin\x64\Debug\log4net.exe", but it didn't exist.
Primary reference "Topshelf, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b800c4cfcdeea87b, processorArchitecture=MSIL".
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2203,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Topshelf, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b800c4cfcdeea87b, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj]
For SearchPath "{HintPathFromItem}".
Considered "D:\a\FDT\FDT\FastDataTransfer\packages\Topshelf.4.2.1\lib\net452\Topshelf.dll", but it didn't exist.
For SearchPath "{TargetFrameworkDirectory}".
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Facades\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Facades\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Facades\Topshelf.exe", but it didn't exist.
For SearchPath "{AssemblyFoldersFromConfig:C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\AssemblyFolders.config,v4.5.2}".
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\Topshelf.exe", but it didn't exist.
For SearchPath "{Registry:Software\Microsoft.NETFramework,v4.5.2,AssemblyFoldersEx}".
Considered AssemblyFoldersEx locations.
For SearchPath "{AssemblyFolders}".
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\Topshelf.exe", but it didn't exist.
Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\Topshelf.winmd", but it didn't exist.
Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\Topshelf.dll", but it didn't exist.
Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\Topshelf.exe", but it didn't exist.
For SearchPath "{GAC}".
Considered "Topshelf, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b800c4cfcdeea87b, processorArchitecture=MSIL", which was not found in the GAC.
For SearchPath "{RawFileName}".
Considered treating "Topshelf, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b800c4cfcdeea87b, processorArchitecture=MSIL" as a file name, but it didn't exist.
For SearchPath "bin\x64\Debug".
Considered "bin\x64\Debug\Topshelf.winmd", but it didn't exist.
Considered "bin\x64\Debug\Topshelf.dll", but it didn't exist.
Considered "bin\x64\Debug\Topshelf.exe", but it didn't exist.
AssemblyFoldersEx location: "{Registry:Software\Microsoft.NETFramework,v4.5.2,AssemblyFoldersEx}"
C:\Program Files\Microsoft SDKs\Azure.NET SDK\v2.9\ref
C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies
C:\Program Files\Reference Assemblies\Microsoft\Workflow Manager\1.0\
             C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.9\bin\plugins\Diagnostics\
             C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.9\ref\Caching\
             C:\Program Files (x86)\Microsoft Visual Studio\Shared\Visual Studio Tools for Office\PIA\Office15\
             C:\Program Files (x86)\Microsoft Visual Studio\Shared\Visual Studio Tools for Office\PIA\Office14\
             C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Tasks
             C:\Program Files (x86)\Microsoft SQL Server\[12](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:13)0\DTS\Tasks
             C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Tasks
             C:\Program Files (x86)\Microsoft SQL Server\[13](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:14)0\DTS\PipelineComponents\
             C:\Program Files (x86)\Microsoft SQL Server\120\DTS\PipelineComponents\
             C:\Program Files (x86)\Microsoft SQL Server\110\DTS\PipelineComponents\
             C:\Program Files (x86)\Microsoft SQL Server\130\DTS\ForEachEnumerators
             C:\Program Files (x86)\Microsoft SQL Server\120\DTS\ForEachEnumerators
             C:\Program Files (x86)\Microsoft SQL Server\110\DTS\ForEachEnumerators
             C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Connections\
             C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Connections\
             C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Connections\
             C:\Program Files (x86)\Open XML SDK\V2.5\lib
             C:\Program Files (x86)\WiX Toolset v3.11\SDK\
             C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\\PublicAssemblies
             C:\Program Files (x86)\Microsoft Chart Controls\Assemblies
   CoreCompile:
     C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Roslyn\csc.exe /noconfig /nowarn:1701,1702 /fullpaths /nostdlib+ /platform:x64 /errorreport:prompt /define:DEBUG;TRACE /highentropyva+ /reference:D:\a\FDT\FDT\Lib\Measures\ExxonMobil.MeasuresApiLogger.dll /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\Microsoft.CSharp.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\mscorlib.dll" /reference:D:\a\FDT\FDT\Lib\Measures\MsrCommon.dll /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Configuration.Install.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Core.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Data.DataSetExtensions.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Data.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.ServiceProcess.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Xml.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Xml.Linq.dll" /debug+ /debug:full /filealign:512 /out:"obj\x64\Debug\FDT Listener Service.exe" /ruleset:"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Team Tools\Static Analysis Tools\\Rule Sets\MinimumRecommendedRules.ruleset" /subsystemversion:6.00 /target:exe /utf8output /win32icon:FDT_Icon.ico /langversion:7.3 FDTListener.cs Program.cs Properties\AssemblyInfo.cs "obj\x64\Debug\.NETFramework,Version=v4.5.2.AssemblyAttributes.cs"
 2>ResolveAssemblyReferences:
     Primary reference "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL".
 2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2203,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
             For SearchPath "{HintPathFromItem}".
             Considered "D:\a\FDT\FDT\FastDataTransfer\packages\log4net.2.0.8\lib\net45-full\log4net.dll", but it didn't exist.
             For SearchPath "{TargetFrameworkDirectory}".
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\Facades\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\Facades\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\Facades\log4net.exe", but it didn't exist.
             For SearchPath "{AssemblyFoldersFromConfig:C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\AssemblyFolders.config,v4.5}".
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\SqlDb\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v4.0\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.5\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v4.0\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VSSDK\VisualStudioIntegration\Common\Assemblies\v2.0\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\v2.0\log4net.exe", but it didn't exist.
             For SearchPath "{Registry:Software\Microsoft\.NETFramework,v4.5,AssemblyFoldersEx}".
             Considered AssemblyFoldersEx locations.
             For SearchPath "{AssemblyFolders}".
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\log4net.exe", but it didn't exist.
             Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\log4net.dll", but it didn't exist.
             Considered "C:\Program Files\IIS\Microsoft Web Deploy V3\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies\log4net.exe", but it didn't exist.
             Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\log4net.winmd", but it didn't exist.
             Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\log4net.dll", but it didn't exist.
             Considered "C:\Program Files (x86)\WiX Toolset v3.11\SDK\log4net.exe", but it didn't exist.
             For SearchPath "{GAC}".
             Considered "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL", which was not found in the GAC.
             For SearchPath "{RawFileName}".
             Considered treating "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL" as a file name, but it didn't exist.
             For SearchPath "bin\x64\Debug\".
             Considered "bin\x64\Debug\log4net.winmd", but it didn't exist.
             Considered "bin\x64\Debug\log4net.dll", but it didn't exist.
             Considered "bin\x64\Debug\log4net.exe", but it didn't exist.
     AssemblyFoldersEx location: "{Registry:Software\Microsoft\.NETFramework,v4.5,AssemblyFoldersEx}"
             C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.9\ref
             C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies\
             C:\Program Files\Reference Assemblies\Microsoft\Workflow Manager\1.0\

             C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.9\bin\plugins\Diagnostics\
             C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.9\ref\Caching\
             C:\Program Files (x86)\Microsoft Visual Studio\Shared\Visual Studio Tools for Office\PIA\Office15\
             C:\Program Files (x86)\Microsoft Visual Studio\Shared\Visual Studio Tools for Office\PIA\Office[14](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:15)\
             C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Tasks
             C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Tasks
             C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Tasks
             C:\Program Files (x86)\Microsoft SQL Server\130\DTS\PipelineComponents\
             C:\Program Files (x86)\Microsoft SQL Server\120\DTS\PipelineComponents\
             C:\Program Files (x86)\Microsoft SQL Server\110\DTS\PipelineComponents\
             C:\Program Files (x86)\Microsoft SQL Server\130\DTS\ForEachEnumerators
             C:\Program Files (x86)\Microsoft SQL Server\120\DTS\ForEachEnumerators
             C:\Program Files (x86)\Microsoft SQL Server\110\DTS\ForEachEnumerators
             C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Connections\
             C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Connections\
             C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Connections\
             C:\Program Files (x86)\Open XML SDK\V2.5\lib
             C:\Program Files (x86)\WiX Toolset v3.11\SDK\
             C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\\PublicAssemblies
             C:\Program Files (x86)\Microsoft Chart Controls\Assemblies
 3>D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\Program.cs(1,7): error CS0246: The type or namespace name 'Topshelf' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj]
     CompilerServer: server - server processed compilation - 3238971c-5308-4c30-bf03-76e46ab4c74c
 3>Done Building Project "D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj" (default targets) -- FAILED.
 2>CoreResGen:
     "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\resgen.exe" /useSourcePath /r:D:\a\FDT\FDT\Lib\Measures\ExxonMobil.MeasuresApiLogger.dll /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\Microsoft.CSharp.dll" /r:"C:\Program Files (x86)\Microsoft Visual Studio\Shared\Visual Studio Tools for Office\PIA\Office[15](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:16)\Microsoft.Office.Interop.Outlook.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\mscorlib.dll" /r:C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Newtonsoft.Json\v4.0_<IP_ADDRESS>__30ad4fe6b2a6aeed\Newtonsoft.Json.dll /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\PresentationCore.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\PresentationFramework.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Configuration.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Core.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Data.DataSetExtensions.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Data.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Deployment.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.DirectoryServices.AccountManagement.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Drawing.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.EnterpriseServices.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Net.Http.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Runtime.Serialization.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.ServiceModel.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Web.Extensions.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Web.Services.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Xaml.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Xml.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Xml.Linq.dll" /r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\WindowsBase.dll" /r:D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\obj\x64\Debug\Interop.IWshRuntimeLibrary.dll /compile Properties\Resources.resx,obj\x64\Debug\FastDataTransfer.Properties.Resources.resources
     Processing resource file "Properties\Resources.resx" into "obj\x64\Debug\FastDataTransfer.Properties.Resources.resources".
   CoreCompile:
     C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Roslyn\csc.exe /noconfig /nowarn:[17](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:18)01,1702 /fullpaths /nostdlib+ /platform:x64 /errorreport:prompt /warn:4 /define:DEBUG;TRACE /highentropyva+ /reference:D:\a\FDT\FDT\Lib\Measures\ExxonMobil.MeasuresApiLogger.dll /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\Microsoft.CSharp.dll" /link:"C:\Program Files (x86)\Microsoft Visual Studio\Shared\Visual Studio Tools for Office\PIA\Office15\Microsoft.Office.Interop.Outlook.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\mscorlib.dll" /reference:C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Newtonsoft.Json\v4.0_<IP_ADDRESS>__30ad4fe6b2a6aeed\Newtonsoft.Json.dll /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\PresentationCore.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\PresentationFramework.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Configuration.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Core.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Data.DataSetExtensions.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Data.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Deployment.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.DirectoryServices.AccountManagement.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Drawing.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.EnterpriseServices.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Net.Http.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Runtime.Serialization.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.ServiceModel.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Web.Extensions.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Web.Services.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Xaml.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Xml.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\System.Xml.Linq.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\WindowsBase.dll" /link:D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\obj\x64\Debug\Interop.IWshRuntimeLibrary.dll /debug+ /debug:full /filealign:512 /nowin32manifest /optimize- /out:obj\x64\Debug\FastDataTransfer.exe /ruleset:"C:\Program Files (x86)\Microsoft Visual Studio\20[19](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:20)\Enterprise\Team Tools\Static Analysis Tools\\Rule Sets\MinimumRecommendedRules.ruleset" /subsystemversion:6.00 /resource:obj\x64\Debug\FastDataTransfer.g.resources /resource:obj\x64\Debug\FastDataTransfer.Properties.Resources.resources /target:winexe /utf8output /win32icon:FDT_Icon_V2.ico /langversion:7.3 "Helper Classes\ImageSourceFromFilePath.cs" "Helper Classes\MeasuresLogging.cs" "Helper Classes\ObservableObject.cs" "Helper Classes\RecentActivitiesHelper.cs" "Helper Classes\RelayCommand.cs" "Helper Classes\WaitCursor.cs" Models\FileTransferBase.cs Models\LocalFileTransferModel.cs Models\RecipientSelectModel.cs Objects\Recipient.cs Objects\TransferFile.cs ViewModels\MainViewModel.cs ViewModels\RecipientSelectViewModel.cs ViewModels\TransferCompleteViewModel.cs ViewModels\TransferFileViewModel.cs Views\HelpWindow.xaml.cs Views\RecipientSelectView.xaml.cs Views\TransferCompleteView.xaml.cs App.xaml.cs Views\MainWindow.xaml.cs Properties\AssemblyInfo.cs Properties\Resources.Designer.cs Properties\Settings.Designer.cs D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\obj\x64\Debug\Views\HelpWindow.g.cs D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\obj\x64\Debug\Views\MainWindow.g.cs D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\obj\x64\Debug\Views\RecipientSelectView.g.cs D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\obj\x64\Debug\Views\TransferCompleteView.g.cs D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\obj\x64\Debug\App.g.cs D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\obj\x64\Debug\FastDataTransfer_Content.g.cs "obj\x64\Debug\.NETFramework,Version=v4.5.AssemblyAttributes.cs"
 2>D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\Properties\AssemblyInfo.cs(58,12): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
 2>D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\Helper Classes\MeasuresLogging.cs(12,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
 2>D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\Views\TransferCompleteView.xaml.cs(13,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
 2>D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\Models\LocalFileTransferModel.cs(15,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
 2>D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\ViewModels\TransferFileViewModel.cs(13,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
 2>D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\ViewModels\MainViewModel.cs(38,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
 2>D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\ViewModels\RecipientSelectViewModel.cs(22,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
     CompilerServer: server - server processed compilation - a4f15308-e1d0-44ed-80ff-6a545404073f
 2>Done Building Project "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj" (default targets) -- FAILED.
 1>Done Building Project "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer.sln" (default targets) -- FAILED.

Build FAILED.
   "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer.sln" (default target) (1) ->
   "D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj" (default target) (3) ->
   (ResolveAssemblyReferences target) ->
     C:\Program Files (x86)\Microsoft Visual Studio\[20](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:21)19\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2203,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj]
     C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2203,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Topshelf, Version=4.2.1.[21](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:22)5, Culture=neutral, PublicKeyToken=b800c4cfcdeea87b, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj]

   "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer.sln" (default target) (1) ->
   "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj" (default target) (2) ->
     C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets([22](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:23)03,5): warning MSB3[24](https://github.com/ExxonMobil/FDT/actions/runs/3705277776/jobs/6278982658#step:14:25)5: Could not resolve this reference. Could not locate the assembly "log4net, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]

   "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer.sln" (default target) (1) ->
   "D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj" (default target) (3) ->
   (CoreCompile target) ->
     D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\Program.cs(1,7): error CS0246: The type or namespace name 'Topshelf' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FDT Listener Service\FDTListenerService.csproj]

   "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer.sln" (default target) (1) ->
   "D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj" (default target) (2) ->
     D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\Properties\AssemblyInfo.cs(58,12): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
     D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\Helper Classes\MeasuresLogging.cs(12,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
     D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\Views\TransferCompleteView.xaml.cs(13,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
     D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\Models\LocalFileTransferModel.cs(15,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
     D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\ViewModels\TransferFileViewModel.cs(13,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
     D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\ViewModels\MainViewModel.cs(38,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]
     D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\ViewModels\RecipientSelectViewModel.cs(22,33): error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) [D:\a\FDT\FDT\FastDataTransfer\FastDataTransfer\FastDataTransfer.csproj]

3 Warning(s)
8 Error(s)

Time Elapsed 00:00:26.08
Error: Process completed with exit code 1.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] Windows Server 2019
[X] Windows Server 2022

Image version and build link
For GitHub Actions, under "Set up job" -> "Runner Image" -> "Version".
Is it regression?
build:    runs-on: [windows-2019]    s
Expected behavior
My build needs to done successfully and publish the artifacts.
Actual behavior
Unable to build the solution
Repro steps
Step 1

Hi @Nivedga we will take look, please provide minimal repro steps. I suppose you are using windows-2019?

Yes
runs-on: [windows-2019]

@Nivedga Hello!
Please provide fully reproducible steps (yaml/workflows/repos) so we could reproduce the issue. It is currently unclear of what's going on in your installation. Feel free to reach us again once all the information we ask is prepared, for now I am going to close the issue due to lack of information.


fix: make title optional

What does it do?
Make the title property of the Alert component optional
Why is it needed?
Because on the Strapi codebase is already being used without specifying the title. And during the migration from JS to TS the errors are starting to appear
How to test it?
Use the Alert component and check that no title is required

Can you add a changeset please


Import sorting within indented block uses Black-incompatible line length

Within an indented block, Ruff excludes the indentation from its line length calculation when sorting imports, thereby fighting with Black.
Ruff:
from line_with_88 import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
from line_with_89 import (
    aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
)

if indented:
    from line_with_88 import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    from line_with_89 import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    from line_with_90 import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    from line_with_91 import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    from line_with_92 import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    from line_with_93 import (
        aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
    )

Black:
from line_with_88 import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
from line_with_89 import (
    aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
)

if indented:
    from line_with_88 import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    from line_with_89 import (
        aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
    )
    from line_with_90 import (
        aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
    )
    from line_with_91 import (
        aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
    )
    from line_with_92 import (
        aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
    )
    from line_with_93 import (
        aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
    )

Ugh, I actually designed this to work, but forgot to add the offset from the indentation. Should be a trivial fix, one sec.

Confirmed that https://github.com/charliermarsh/ruff/pull/693 gives that output.

(I added this to the test case.)


Add flag to TextureLoader for sRGB textures, load some textures as linear

Fixes #332.
Currently, all textures in Unity are loaded as if they're sRGB textures. This isn't correct for things like normal maps, where treating them as sRGB will mess up the direction of the normals. This change adds a flag to TextureLoader::loadTexture to allow specifying which textures are sRGB, and specifies the flag for each texture loaded based on the Unreal implementation.

Looks great! Please just merge in main. It's another painful conflict, unfortunately.

@kring Merged with main! It feels a little bit like I did something wrong in the merge but the changes look right to me, so 🤷♀

Thanks @azrogers !


 The call to IEgressOperation.ExecuteAsync will return a failed ExecutionResult instead of throwing an exception when the operation fails.
To fix this, I've added an Exception property to the ExecutionResult class which is populated when creating a failure result and updated the actions to throw a CollectionRuleActoinException that wraps the exception from the ExecutionResult.

/backport to release/6.x


Consistent usage of Result over Option

Make the switch where it makes sense. The goal is the let users use ? instead of .unwrap() in more places.

Actually now I'm leaning the other direction.
As per this post, I'm realizing I'm not really following the expected standard and style.

Option is for functions that may or may not return a value (say, a string search may find something or may not find something). So, both return values are valid and expected in your program.
Result, as is is shown by the Err enum, is for functions that are expected to succeed (thus, Ok()), but may fail and this has to be catched. Example: Opening a connection to some other server would generally be expected to work but of course can fail.

For that reason I'm going to take some time to switch over a lot Result returns for Option returns.

Another realization: I've been returning errors in places when I really just want to return data. For example, if there are no leds within 0.2 units of the center_point, then sled.set_within_dist(0.2, color) wouldn't do anything. That isn't erroneous behavior, but it would still be nice to know from this call if it did anything.
So for methods like this, I've opted to return true or false depending on whether or not a change was made by the mutating method.

closed by #77


Met Office - value needs to have a number

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
1.0.5
Last working release (if known):
N/A
Browser and Operating System:
Windows 10, Firefox 113.0.2

Occurs on all OS, configuration issue with card.
Description of problem:
When trying to configure the weather forecast max/min temperatures, error below is returned.
'entity_forecast_min_1=sensor.met_office_REDACTED_temperature_daily' value needs to have a number

Numerical value is provided by Met Office API, should be displayed as normal. Have tested this with other elements which do display the number correctly, this only appears to be an issue with the min/max on the forecast section.
I have tried to use other readings such as Met Office Daily but this returns a different error 'entity_forecast_min_1 attribute forecast[1].templow not found, though this one does arguably make sense if that specific reading is not sent by the API in that way.
It would be good if I can either disable the temperatures entirely (when the API doesn't provide the specific information it's looking for) or if there is a possible fix for this.

Thought I would try creating a dummy sensor with a numerical value to see what it was looking for, still returns the same error. I assume I am just missing something, I tried casting it to a string and declaring it as an integer too but still the same, not sure what data it's expecting.

OK so it seems to be down to the fact that the Met Office readings do not include templow, so it's unable to display it correctly. Having the option to display just the temperature instead of high/low would be ideal, but in the meantime I will try to figure out a way to inject templow with an arbitrary reading from the normal temperature reading.
I suppose this is a feature request then rather than a bug, sorry!

as a suggestion, use something like statistics integration (or the custom average component) to generate the high/low and point the entity in the card to that. Of course this is not a bug with the card but a deficiency in the weather integration you are using. The card can point to ANY entity you want it to BTW.

as a suggestion, use something like statistics integration (or the custom average component) to generate the high/low and point the entity in the card to that. Of course this is not a bug with the card but a deficiency in the weather integration you are using. The card can point to ANY entity you want it to BTW.

Thanks, I am trying to work out (with my limited skills) how I can just pass the temperature readings I do have through a separate entity. It's expecting an index with templow and temperature rather than just anything, otherwise it still fails with a different error entity_forecast_min_1 attribute forecast[1].templow not found.

Can you post a screenshot of the states for the weather entities here please. Is it a weather integration you are using or individual sensors? Also post the yaml code for the card config.

Thanks for getting back to me. I am using the Met Office integration, from the UK. I hope you don't mind, I have redacted my location for privacy. I use the Met Office one as it seems to be the most accurate.
As you can see below, the states summary only includes temperature, not templow and temperature. I have tested, and if I inject a templow: 0 to the state then I can add it to the card successfully. I'm not knowledgeable enough to know how to do this through the configuration, I'd be happy with that or just a new entity that I can create with the right temperature and templow readings created from this existing state.
I can of course access the reading(s) with:
{{ state_attr('weather.met_office_REDACTED_daily', 'forecast')[0]['temperature'] }}
I just don't know how to translate that into a new entity or inject templow to the existing state.
STATES
temperature: 16
temperature_unit: °C
humidity: 76
pressure_unit: hPa
wind_bearing: NE
wind_speed: 28.97
wind_speed_unit: km/h
visibility_unit: km
precipitation_unit: mm
forecast:
  - datetime: '2023-06-07T12:00:00+00:00'
    condition: sunny
    precipitation_probability: 4
    wind_bearing: ENE
    temperature: 18
    wind_speed: 28.97
  - datetime: '2023-06-08T12:00:00+00:00'
    condition: cloudy
    precipitation_probability: 4
    wind_bearing: ENE
    temperature: 17
    wind_speed: 28.97
  - datetime: '2023-06-09T12:00:00+00:00'
    condition: cloudy
    precipitation_probability: 12
    wind_bearing: ENE
    temperature: 18
    wind_speed: 25.75
  - datetime: '2023-06-10T12:00:00+00:00'
    condition: cloudy
    precipitation_probability: 34
    wind_bearing: NNE
    temperature: 19
    wind_speed: 14.48
attribution: Data provided by the Met Office
friendly_name: Met Office REDACTED Daily

CARD YAML
card_config_version: 8
custom1_icon: mdi:radar
custom1_value: sensor.met_office_REDACTED_weather_3_hourly
daily_forecast_days: 4
entity_apparent_temp: sensor.met_office_REDACTED_feels_like_temperature_3_hourly
entity_forecast_icon: weather.met_office_REDACTED_3_hourly
entity_forecast_icon_1: weather.met_office_REDACTED_daily
entity_forecast_max: weather.met_office_REDACTED_daily
entity_humidity: weather.met_office_REDACTED_3_hourly
entity_pop: sensor.met_office_REDACTED_probability_of_precipitation_3_hourly
entity_pop_1: weather.met_office_REDACTED_daily
entity_pos: sensor.met_office_REDACTED_probability_of_precipitation_3_hourly
entity_pressure: weather.met_office_REDACTED_daily
entity_summary_1: weather.met_office_REDACTED_daily
entity_sun: sun.sun
entity_temperature: sensor.met_office_REDACTED_temperature_3_hourly
entity_uv_alert_summary: sensor.met_office_REDACTED_uv_index_3_hourly
entity_wind_bearing: weather.met_office_REDACTED_3_hourly
entity_wind_speed: sensor.met_office_REDACTED_wind_speed_3_hourly
option_locale: GB
section_order:
  - overview
  - extended
  - slots
  - daily_forecast
show_section_daily_forecast: true
slot_l1: forecast_max
slot_l2: custom1
slot_l3: wind
slot_l4: remove
slot_l5: sun_next
slot_l6: remove
slot_l7: remove
slot_l8: remove
slot_r1: popforecast
slot_r2: humidity
slot_r3: uv_summary
slot_r4: remove
slot_r5: sun_following
slot_r6: remove
slot_r7: remove
slot_r8: remove
type: custom:platinum-weather-card

I have done some testing, and was able to get the following attributes by using the below:
        tempfix:
            friendly_name: "tempfix"
            value_template: "sunny"
            attribute_templates:
                forecast: "{{ state_attr('weather.met_office_REDACTED_daily', 'forecast')[0]['temperature'], state_attr('weather.met_office_REDACTED_daily', 'forecast')[1]['temperature'], state_attr('weather.met_office_REDACTED_daily', 'forecast')[2]['temperature'], state_attr('weather.met_office_REDACTED_daily', 'forecast')[3]['temperature'] }}"

forecast:
  - 18
  - 17
  - 18
  - 19
friendly_name: tempfix

But even if I add in templow like my original API call, I still get the value needs to have a number error. I don't get this error however if I add in templow to the API output. What data is it expecting? I can't see any difference between them?
forecast:
  - templow: 18
  - templow: 17
  - templow: 18
  - templow: 19
friendly_name: tempfix

forecast:
  - datetime: '2023-06-07T12:00:00+00:00'
    condition: sunny
    precipitation_probability: 4
    wind_bearing: ENE
    temperature: 18
    templow: 18
    wind_speed: 28.97
  - datetime: '2023-06-08T12:00:00+00:00'
    condition: cloudy
    precipitation_probability: 4
    wind_bearing: ENE
    temperature: 17
    templow: 17
    wind_speed: 28.97
  - datetime: '2023-06-09T12:00:00+00:00'
    condition: cloudy
    precipitation_probability: 12
    wind_bearing: ENE
    temperature: 18
    templow: 18
    wind_speed: 25.75


Settings don't save

Settings don't save and are reset upon restarting the game.


Handle the maximize button change when maximizing the window

Just another small improvement. After this PR, the maximized button would change accordingly
Normal:

Maximized:

THanks!


Fix typo introduced by #167

Correct double named find_all to find_all and filter introduced by 382340966b7b065fe463680c73cb56ab4b0ab878.

Good catch! Can you update the source doc  to pass the CI?
https://github.com/rubocop-hq/rubocop-performance/blob/v1.8.1/lib/rubocop/cop/performance/detect.rb#L7

Thanks for hint, I'm new to CircleCi and its message was a bit confusing me, so I didn't know how to fix ist. Now I updated the sources and force-pushed the patch branch. All checks have passed :-)

Perfect! Thank you for your taking time!


[Nami Wallet Chrome Extension] Wallet can't finish loading assets (in both testnet and mainnet)

Platform: Linux
Browser: Chrome
Screenshot:

Hey, so it's stuck at loading? Do you have a few more details maybe?

I can see why it was stuck. I just saw chrome extension got updated.
Now it is working fine.

Mine just does this


[NEW ICON] OpenShift

Skill Name
OpenShift
Why?
Popular enterprise-ready Kubernetes container platform
Reference Image
in attachment

Added in 1bfaa272b1632ec9c26a6e4a1d2cb01fce981516, thank you!


Attribute Error: Can't pickle local object when sending multiple circuits in job

Information

Qiskit IBMQ Provider version:  0.11.1
Python version:  3.9.1
Operating system: Catalina 10.15.7

What is the current behavior?
I have a list of 74 circuits. When I submit them all as a single job, I get the titular error. But if I submit any one of the circuits from the job individually, I do not get the titular error.
Steps to reproduce the problem
First, I try to submit all my circuits into a single job. Note that "backend" is a backend object of my own custom class and "submit_job" is a method that does the obvious thing. I have included the source code for this at the bottom for clarity.
# job_list is list of 74 circuits
backend.submit_job(job_list, 'test')

This gives the a long error, but I've clipped the bottom with the Attribute Error here:

If I submit each circuit in job_list individually, I get no such error. I can even check on ibmq status that my jobs were submitted correctly
for j, circ in enumerate(job_list):
    print(j)
    backend.submit_job(circ, 'test')
    backend.backend.active_jobs()[0].cancel()

What is the expected behavior?
The job should submit when given a list of circuits if each individual circuit doesn't throw an error.
Suggested solutions
I don't know enough about what's going wrong now to suggest anything.
Source code for submit_job
def submit_job(self, experiments, qobj_id, num_shots='max',
               shuffle=False):
    """
    Submit [experiments] to [backend] and run [num_shots] for each of
    the [experiments]. Results get a qobj_id tag labelled with [qobj_id].
    If [shuffle] is True, randomly shuffles input data before sending to
    prevent biasing data with time.
    """
    # set runs to max runs allowed by hardware if set to do so
    max_runs = self.get_max_runs()
    if str(num_shots).lower() == 'max':
        num_shots = max_runs['max_shots']

    if not isinstance(experiments, list):
        experiments = [experiments]

    # parse experiments a bit before passing to assemble
    parsed_experiments = []
    for exp in experiments:
        if isinstance(exp, IBMQDdSchedule):
            parsed_experiments.append(exp.sched)
        else:
            parsed_experiments.append(exp)

    # shuffle data if desired
    if shuffle is True:
        random.shuffle(parsed_experiments)

    # submit the job in the background and output status information
    program = assemble(parsed_experiments, backend=self.backend,
                       shots=num_shots, qobj_id=qobj_id)
    job = self.backend.run(program)
    return job

@taalexander @lcapelluto Have you seen this before? I transferred this issue to terra because I think it's related to the actual pulse used and not the pulse library.

The problem appears to be with my custom class wrapper over QuantumCircuit and how it interacts with assemble. To this end, I found two band-aide solutions (although, they are pretty good). Just a reminder "armonk" is an object of my own custom Backend as well, but armonk.backend gives me the usual think obtained via provider.get_backend('ibmq_armonk').
1. Create QuantumCircuit and extend with my custom circuit
circ = IBMQDdCircuit(1, 1, ibmq_backend=armonk)
circ.x(0)
# Note: This throws the titular error
program = assemble([circ, circ], backend=armonk.backend)

qc = QuantumCircuit(1, 1)
qc.extend(circ)
# Note: This doe NOT given error
program = assemble([qc, qc], backend=armonk.backend)

2. Cast as Schedule
This works same way as above, but instead of turning into a QuantumCircuit, I use build_schedule to turn into a schedule.
3. Define custom schedules using circuit "gates"
sched = IBMQDdSchedule(armonk, 'c_basis')
# add x adds the "pulse" implementation of circuit X
sched.add_x(0)
# Note: This works as well
program = assemble([sched, sched], backend=backend.backend)

The problem appears to be with my custom class wrapper over QuantumCircuit and how it interacts with assemble. To this end, I found two band-aide solutions (although, they are pretty good). Just a reminder "armonk" is an object of my own custom Backend as well, but armonk.backend gives me the usual think obtained via provider.get_backend('ibmq_armonk').
1. Create QuantumCircuit and extend with my custom circuit
circ = IBMQDdCircuit(1, 1, ibmq_backend=armonk)
circ.add_x(0)
# Note: This throws the titular error
program = assemble([circ, circ], backend=armonk.backend)

qc = QuantumCircuit(1, 1)
qc.extend(circ)
# Note: This doe NOT given error
program = assemble([qc, qc], backend=armonk.backend)

2. Cast as Schedule
This works same way as above, but instead of turning into a QuantumCircuit, I use build_schedule to turn into a schedule.
3. Define custom schedules using circuit "gates"
sched = IBMQDdSchedule(armonk, 'c_basis')
# add x adds the "pulse" implementation of circuit X
sched.add_x(0)
# Note: This works as well
program = assemble([sched, sched], backend=backend.backend)

By the way, add_x is my own custom way to add the X gate as well. It gives the following circuit:

I do this because it's important to maintain certain phase relationships, etc...
But what's extremely peculiar is the following. Suppose I start a fresh Jupyter notebook up (no instances of assemble have been called yet). Then the following code works. Note that I am adding the "standard x" that comes with QuantumCircuit API and not my custom add_x method.
# This works on fresh instance of Jupyter notebook (no assemble functions run yet)
circ = IBMQDdCircuit(1, 1, ibmq_backend=backend)
circ.x(0)
program = assemble([circ, circ], backend=backend.backend)
# I can run it again no problem
circ = IBMQDdCircuit(1, 1, ibmq_backend=backend)
circ.x(0)
program = assemble([circ, circ], backend=backend.backend)

If I start a fresh instance, as I've reported above, the following breaks with titular error
# Breaks with titular error even on fresh cache (no calls to assemble yet)
circ = IBMQDdCircuit(1, 1, ibmq_backend=backend)
circ.add_x(0)
program = assemble([circ, circ], backend=backend.backend)

But then, if I run the following, I get an error:
# works fine on first call
circ = IBMQDdCircuit(1, 1, ibmq_backend=backend)
circ.x(0)
program = assemble([circ, circ], backend=backend.backend)
# works fine on 2nd call
circ = IBMQDdCircuit(1, 1, ibmq_backend=backend)
circ.x(0)
program = assemble([circ, circ], backend=backend.backend)

# breaks as usual
circ = IBMQDdCircuit(1, 1, ibmq_backend=backend)
circ.add_x(0)
program = assemble([circ, circ], backend=backend.backend)

# breaks now that add_x has been called?
circ = IBMQDdCircuit(1, 1, ibmq_backend=backend)
circ.x(0)
program = assemble([circ, circ], backend=backend.backend)

So it seems the problem is partially with my custom definition of x--but then once assemble breaks once, the issue persists even for circuits that would normally not throw an error until I clear my cache (i.e. restart Python). This is very weird.


Add pickle support for Keras model

https://github.com/keras-team/keras/issues/19554
Implements some basic unit tests for pickling on top of one of the existing parameterized tests.  I think this gets pretty good coverage across cases.
There might be some weird edge cases where reloading fails, but I think this is fine in that pickling isn't really useful as  a long term storage solution - just a short term way to transfer some info between workers.
Open to ideas about better approaches here - this is just the best I could come up with.

Codecov Report
Attention: Patch coverage is 55.55556% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 55.21%.  Consider uploading reports for the commit 9ae1a60 to get more accurate results

Files
Patch %
Lines

keras/src/models/model.py
55.55%
4 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #19555       +/-   ##
===========================================
- Coverage   76.32%   55.21%   -21.11%
===========================================
  Files         496      496
  Lines       44245    44254        +9
  Branches     8208     8208
===========================================
- Hits        33768    24436     -9332
- Misses       8766    18232     +9466
+ Partials     1711     1586      -125

Flag
Coverage Δ

keras
55.21% <55.55%> (-20.96%)
:arrow_down:

keras-jax
?

keras-numpy
55.21% <55.55%> (+<0.01%)
:arrow_up:

keras-tensorflow
?

keras-torch
?

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

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

LGTM, thanks!

awesome - thanks for the help!  Very happy with keras-3!


Update applyAsMentor method with new fields

Purpose
The purpose of this PR is to fix #228
Goals
Mentors should be able to update all fields using applyAsMentor endpoint
Approach
Update the src/main/java/org/sefglobal/scholarx/service/ProgramService.java:applyAsMentor method to set the following fields.

category
expertise
institution
position
bio
slots

Screenshots
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Related PRs
Test environment
Learning

You're welcome @Piumal1999


Memory error at server

works fine on local machine (Mac), but getting memory issues after deploy to server (digitalocean)
server:
4vcpu
8GB RAM
Django==2.1.3
profanity-check==1.0.2
uWSGI==<IP_ADDRESS>
scikit-learn==0.20.2
scipy==1.2.1
numpy==1.16.2
unable to load configuration from from multiprocessing.semaphore_tracker import main;main(14)
File "/usr/local/lib/python3.6/dist-packages/profanity_check/__init__.py", line 1, in <module>
  File "/usr/local/lib/python3.6/dist-packages/profanity_check/profanity_check.py", line 5, in <module>
  File "/usr/local/lib/python3.6/dist-packages/sklearn/externals/joblib/numpy_pickle.py", line 598, in load
  File "/usr/local/lib/python3.6/dist-packages/sklearn/externals/joblib/numpy_pickle.py", line 526, in _unpickle
  File "/usr/lib/python3.6/pickle.py", line 1050, in load
  File "/usr/lib/python3.6/pickle.py", line 1338, in load_global
  File "/usr/lib/python3.6/pickle.py", line 1388, in find_class
  File "/usr/local/lib/python3.6/dist-packages/sklearn/feature_extraction/__init__.py", line 10, in <module>

server uwsgi log:
https://gist.github.com/ishafizan/a8cfbc9c266a4d2ba736331190c8d545
simple code test:
pred = predict_profanity("scum")
def predict_profanity(strmsg):
    pred = predict_prob([strmsg])
    return pred

I don't know exactly what's going on but it seems like it's a memory error. How much RAM is free on your server? Maybe try provisioning some more swap space - you might not have that enabled.

Closing because inactive + seems unrelated to the actual library.


Documentation HTML invalid

The sourcery documentation has been broken for a couple of days now. It looks, like there is an additional </div> generated after </body>, which makes at least my browser (Chrome on macOS) show me the source code instead of rendering the HTML page.
e.g<EMAIL_ADDRESS>

fixed

This issue seems to be back<EMAIL_ADDRESS>

the documentation is now hosted here

Ah, thanks. Google sent me to this page https://github.com/krzysztofzablocki/Sourcery/blob/master/guides/Writing templates.md which contains an outdated link to the Types documentation. Will update my bookmark.


problem in the file extract_vein_by_region_grow.py

Traceback (most recent call last):
File "E:\research\LeafVeinExtraction-master\main.py", line 93, in
extract_vein_by_region_grow.extract_vein_by_region_grow(edges_canny[i], images[i], 150, (15, 15))
File "E:\research\LeafVeinExtraction-master\extract_vein_by_region_grow.py", line 164, in extract_vein_by_region_grow
cv2.findContours(vein[:, round(w/2)-20:round(w/2)+20], cv2.RETR_TREE, cv2.CHAIN_APPROX_SIMPLE)
ValueError: not enough values to unpack (expected 3, got 2)
How to fix this? opencv-python <IP_ADDRESS>

https://stackoverflow.com/questions/54164630/want-to-find-contours-valueerror-not-enough-values-to-unpack-expected-3-go

Thanks for your answer. To be frank, I'm a bit confused... The number of parameters returned by findContours turns from 2(opencv2.x) --> 3(opencv3.x) --> 2(opencv4.x), maybe there was a protracted controversy in the comunity, haha.


Create heartbeat function

Create heartbeat function
revert main
clippy
clippy+fmt

Current dependencies on/for this PR:

main

PR #6

PR #7

PR #8   👈

This stack of pull requests is managed by Graphite.

Merge activity

Nov 27, 3:45 PM: @kafonek started a stack merge that includes this pull request via Graphite.


if possible please add all functionality of api like rust version

i wanna build n music app but when i follow your documentation s i found search is not working in ts version if possible please add all functionality of rust version

Hey @ViSurya ,
Thanks for reaching out.
The TS version actually has more features than the Rust version. I apologize for the incomplete documentation; I'll be updating it whenever I get the time. In the meantime, you can check out this. I've used the TS version of the API in one of my projects, and you can review the routes and implementation there.
Thanks!

Thanks you so much now just an last question before closing this issue
When I use this api and api hit so much call so it can possible that jiosaavn can block ip or you are using any proxies because I am php dev so it's difficult for me to understand the framework that you use btw thanks for wonderful work

Im not entirely sure about that, and no, I am not using any proxies. However, I did stress test JioSaavn's original API using Oha, and my IP wasnt banned.
In most cases, I dont make direct requests to the API. The project Im using makes requests to a wrapper I wrote, which then makes the requests to the original API.
And thank you for the appreciation! I created this wrapper for my personal project, but since you find it useful, Ill try to write the documentation as soon as possible.

bhai ye music player aapne kitne dino me bnaya hai me apna bnane ki try kar rha hu but per mera itna accha nhi hai


Reversing message order / upside down widget

Hi, I've found myself in the boat where it is much better for me to do the widget upside down, so that the messages are written at the top of the screen in a full screen mode. I've got that done by editing the css; but I don't know how to go about getting the message order to reverse so new messages appear at top of the screen rather than the bottom of the screen. Do you have any ideas that don't involve editing the source code?

Started to answer my own question, just need to get widgets supplied with messages below the messages now:
.react-chatbot-kit-chat-message-container {
padding: 0 17.5px 10px 17.5px;
overflow: auto;
position: relative;
display: flex;
flex-direction: column-reverse;
background-color: #f8f3f0;
min-height: 100%;
height: 100%;
width: 100%;
}

Actually it's not as good an answer as hoped as widgets that normally come with messages are displayed above messages, any ideas?

Removing the last fix and changing the actual message order has done it, emergency over
addMessageToState = (message) => {
    this.setState((prevState) => ({
        ...prevState,
        messages: [...prevState.messages, message].reverse(),
    }));
};


Option to Disable Event Time Display

Please add the option to disable the display of event time in the "month" view of the calendar. Currently, the event field accommodates a limited number of characters, and it is sometimes necessary to save space.

@IvanBarvinok Thank you for openning Feature Request. We will add it in the upcoming version.


Revert to previous vagrant-up deployment

A Vagrantfile is created from prod/dev template and gets deleted on cleanup
Removed .sh suffixes
Edited README to reflect changes

Coverage increased (+0.03%) to 76.448% when pulling 7a996e8357cc6acb042f17253f9e53f65de77264 on brecode:vagrant into 00fef15fd2cffcbb8e551469e649ef39724c7d6e on contiv:master.


Failure & coredump check-environment.sh using blosc filter

On my local system, after installing conda & building the environment as per the README. Running deployment/check-environment.sh failed here:
https://github.com/OpenDataCubePipelines/ard-pipeline/blob/ea84164ab0cd4fb13188984bfd4332d7eb6b59e1/deployment/check-environment.sh#L55
The output:
# ... other tests passing

Attempting hdf5 blosc compression...python3: /home/conda/feedstock_root/build_artifacts/libnetcdf_1702228817425/work/plugins/H5Zblosc.c:160: blosc_set_local: Assertion `nelements == 7' failed.
./ard-pipeline/deployment/check-environment.sh: line 63: 121505 Aborted                 (core dumped) python3 <<EOF

# rest of embedded python code printed to terminal

Modifying check-environment.sh's embedded python to use hdf5plugin directly solves the core dump:
# The previous import of wagl should have initialised the filters.
print("Attempting hdf5 blosc compression...", end='', flush=True)
import h5py
import hdf5plugin  # for filter plugins
import tempfile
f = h5py.File(tempfile.mktemp('-test.h5'),'w')

# FIX: change compression from int to a plugin
dset = f.create_dataset("myData", (100, 100), compression=hdf5plugin.Blosc())

@uchchwhash @jeremyh are you aware of any reasons against using hdf5plugins for the compression arg?

hdf5plugin is what we use already — the comment higher up mentions it indirectly: # The previous import of wagl should have initialised the filters.
In wagl we import it here: https://github.com/OpenDataCubePipelines/ard-pipeline/blob/e841eb271a1bf5050394ca6365abb4302ecb8cc8/wagl/init.py#L3
So somehow it is no longer being included implictly by the wagl import?

Ah, I see — it's the number that's the problem, not the import itself. Perhaps something has changed in a library upgrade and that hardcoded number is not a sensible choice?

So somehow it is no longer being included implictly by the wagl import?

I'm not sure of the specifics - it's buried somewhere & I haven't delved into it.

Ah, I see — it's the number that's the problem, not the import itself.

Removing the int code & compression arg allowed the test to pass. Also, using hdf5plugin for the compression arg brought in more error handling. Deliberately breaking the code with compression=hdf5plugin & compression=hdf5plugin.Blosc (no func call) was raised exceptions, so better than a core dump (some failures crashed the conda env).

.... but if a raw number doesn't work, does wagl itself work? I can see the blosc int used here:
https://github.com/OpenDataCubePipelines/ard-pipeline/blob/b53ca81476f3cf4e96769a462fce95b3d5bd5383/wagl/hdf5/compression.py#L258

I haven't run wagl yet to find out definitively.
In the meantime, I'll experiment with changing compression=<plugin> across the codebase to run that through the GitHub actions.

.... but if a raw number doesn't work, does wagl itself work? I can see the blosc int used here:
https://github.com/OpenDataCubePipelines/ard-pipeline/blob/b53ca81476f3cf4e96769a462fce95b3d5bd5383/wagl/hdf5/compression.py#L258

... I'll experiment with changing compression=<plugin> across the codebase ...

With some grep work, I can't find any evidence in the code that the blosc filter is being used. Compression mostly defaults to LZF filters.
Is blosc compression used in any production runs?
If not, is there any issue with modifying check-environment script to use the default LZF?

Is blosc compression used in any production runs?

No.

If not, is there any issue with modifying check-environment script to use the default LZF?

No.

Is blosc compression used in any production runs?

No.

If not, is there any issue with modifying check-environment script to use the default LZF?

No.

Ok, I'll create a change on a new branch & ask @sixy6e to try the check-environment script for a sanity check.

The issue is actually to do with the fact that the compression_opts argument is empty, and for blosc it's expecting a tuple/list containing 7 elements; hence your error on the assertion nelements == 7.
Here's a snippet of how you should be setting it up:
from wagl import hdf5
comp = hdf5.compression.H5CompressionFilter.BLOSC_ZSTANDARD
config = comp.config(chunks=(200, 300), aggression=9)
kwargs = config.dataset_compression_kwargs()
# print(kwargs)  to actually see what it comes back as
# {'chunks': (200, 300), 'shuffle': False, 'compression': 32001, 'compression_opts': (0, 0, 0, 0, 9, 1, 5)}

The hdf5plugin.Blosc() is a similar wrapper to what we have, and sets up the required params eg:
>>> dict(hdf5plugin.Blosc())
{'compression': 32001, 'compression_opts': (0, 0, 0, 0, 5, 1, 1)}


X-Shopify-Webhook-Id is not provided to the webhook callback

It doesn't seem like there's any way for the webhook callback to access the value of the X-Shopify-Webhook-Id header. This means it's not possible to easily detect if a webhook has already been processed.
According to Shopify:

The webhooks API provides "at least once" delivery of webhook events. This means that an endpoint might receive the same webhook event more than once. You can detect duplicate webhook events by comparing the X-Shopify-Webhook-Id header to previous events.

https://shopify.dev/apps/webhooks#limitations

This is a good idea.  It might be a bit of refactoring in here https://github.com/pixelunion-apps/elixir-shopifyapi/blob/main/lib/shopify_api/plugs/webhook.ex#L105 to make it work. I'd be open to looking at it when I have a couple or going over a PR if you are inclined to take a go at it.
NOTE: We did just cut a new release which included a new plug for webhook handling, this new plug is not backwards compatible.


New version - 3.0.0

I've pushed a prerelease version of 3.0.0 to NuGet, based on the vnext branch.
Includes:
https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/238
https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/240
https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/241
I've rewritten some of the stuff, so let me know below if something is broken.

Do you can add the support to open player packs pls?

What happened with client.RequestFactories.CookieContainer?

I see that it was removed here: https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/238/files#diff-12cb7e6a147c95d0cbf87b9bb653e38fL93.
I guess there are no reason to remove it, so i'll add it again. Thanks for the feedback @mtdx.

@tringler any reason you removed it? Is there another method? https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/238/files#diff-12cb7e6a147c95d0cbf87b9bb653e38fL93.

No, obviously my fault

@tringler I get {"error":"invalid_grant","error_description":"code is invalid"} when I try to connect via companion app, but I did checked, the emails codes are good and the web app login works fine with emails codes, any ideas?

after which call?

GET /p/mobile/fifa/companion/code?code=QUORADljvCxnYZFJlwfMNOyK.......
then
POST /connect/token HTTP/1.1
{"error":"invalid_grant","error_description":"code is invalid"}
I write to the console the call to the ITwoFactorCodeProvider and I see beeing called and that the returned code is right.

You know that these codes have nothing to do with the TwoFactor codes right? Normally LoginMobileRequest.cs should send your code GET /p/mobile/fifa/companion/code?code=QUORADljvCxnYZFJlwfMNOyK....... into the GetAuthTokenAsync method.

Looks to me that it gets blocked at the TwoFactor email code, I keep getting EA codes on email, I didn't do nothing custom, is the vnext branch as it is. Where is the issue?
http://prntscr.com/al9z48

Can you post your code where you test the vnext branch?

ITwoFactorCodeProvider provider = new ImapTwoFactorCodeProvider(Gmail, Gpassword);
LoginDetails loginDetails = new LoginDetails(Email, Password, FutSecurityAnswer, Platform.Ps3, AppVersion.CompanionApp);
LoginResponse loginResponse = await _utClient.LoginAsync(loginDetails, provider);
CookieContainer cookiecontainer = _utClient.RequestFactories.CookieContainer;
....
I doesn't get past Login, Get this exception
UltimateTeam.Toolkit.Exceptions.FutException: Unable to login to WebApp ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at UltimateTeam.Toolkit.Requests.FutRequestBase.d__41`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UltimateTeam.Toolkit.Requests.LoginRequestMobile.d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at UltimateTeam.Toolkit.Requests.LoginRequestMobile.d__15.MoveNext()
--- End of inner exception stack trace ---
at UltimateTeam.Toolkit.Requests.LoginRequestMobile.d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UltimateTeam.Toolkit.FutClient.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
...

You should debug it and check which code used here: var authToken = await GetAuthTokenAsync(**_code**);
It should be the code you get here: GET /p/mobile/fifa/companion/code?code=QUORADljvCxnYZFJlwfMNOyK.......

@mtdx: I've pushed a new prerelease to NuGet, which has the CookieContainer getter.

Thanks @trydis ,
@tringler I see in the POST https://accounts.ea.com/connect/token HTTP/1.1
grant_type=authorization_code&code=&client_id=FIFA-16-MOBILE-COMPANION....
Code is empty, but why? do you have any ideas?

After the sending your TwoFactorCode you should get code here:
        private async Task SetTwoFactorCodeAsync(HttpResponseMessage loginResponse)
        {
            var tfCode = await _twoFactorCodeProvider.GetTwoFactorCodeAsync();

            var responseContent = await loginResponse.Content.ReadAsStringAsync();

            AddReferrerHeader(loginResponse.RequestMessage.RequestUri.ToString());

            var codeResponseMessage = await HttpClient.PostAsync(loginResponse.RequestMessage.RequestUri, new FormUrlEncodedContent(
                        new[]
                            {
                            new KeyValuePair<string, string>(responseContent.Contains("twofactorCode") ? "twofactorCode" : "twoFactorCode", tfCode),
                            new KeyValuePair<string, string>("_eventId", "submit"),
                            new KeyValuePair<string, string>("_trustThisDevice", "on"),
                            new KeyValuePair<string, string>("trustThisDevice", "on")
                            }));

            codeResponseMessage.EnsureSuccessStatusCode();

            var contentData = await codeResponseMessage.Content.ReadAsStringAsync();

            if (contentData.Contains("Incorrect code entered"))
                throw new FutException("Incorrect TwoFactorCode entered.");

            if (contentData.Contains("Tired of waiting for your code?"))
                await SkipAuthenticatorAdvertise(codeResponseMessage);

            //TO DO: How to verify, that content is a companion code
            else if (contentData.Length <= 64)
            {
                _code = contentData;
            }
        }

Yoh should check what you get as contentData.

I get the code as content QUORADljCByGxEjIcsydFmp..... but is 40 length, code so because of the contentData.Length <= 64 it doesn't get assigned?

for sure it should be assigned, because it's lower than 64 - Pls verify why it doesn't get assigned by debugging

OK, it goes into SkipAuthenticatorAdvertiseAsync which doesn't assigned _code but gets the right content but _code never gets assigned when SkipAuthenticatorAdvertiseAsync returns since is an else if
 var contentData = await authenticatorResponseMessage.Content.ReadAsStringAsync(); in SkipAuthenticatorAdvertiseAsync remain unused.

Other than the login issue above everything seems to be working but I think we need better exception handling on mobile, which seems to be lacking with just "Response code doesn't indicate success" also getting the gifts list is not implemented.

also getting the gifts list is not implemented.
Yes, because I don't know if gifts even implemented in the CompanionApp and if yes, I need the requests/responses for it - That's the reason why it's not implemented. It's the same like for captcha handling, but this I will implement as soon as the vnext brach got merged. See https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/issues/246

I know the bug, which you described, but this should be fixed with that commit:
https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/238/commits/7539363ee6565e58edc1512488a962a3bd48dda2?diff=unified
I'm also OK with this fix, but then https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/238/commits/7539363ee6565e58edc1512488a962a3bd48dda2?diff=unified should be reverted, because I'm doing exactly the same here:
                 await SetTwoFactorCodeAsync(loginResponseMessage);
 +
 +            //TO DO: How to verify, that content is a companion code
 +            else if (contentData.Length <= 64)
 +            {
 +                _code = contentData;
 +            }

Don't know what to say about how to fix the bug, I just added that "if" in SkipAuthenticatorAdvertise and worked fine after.

I assume you don't apply the commit https://github.com/trydis/FIFA-Ultimate-Team-Toolkit/pull/238/commits/7539363ee6565e58edc1512488a962a3bd48dda2 - You added this inside the call SkipAuthenticatorAdvertise here:
             else if (contentData.Length <= 64)
              {
                  _code = contentData;
              }

and I added it outside the call here:
             await SkipAuthenticatorAdvertise(codeResponseMessage);

             //TO DO: How to verify, that content is a companion code
             else
             else if (contentData.Length <= 64)
              {
                  _code = contentData;
              }

I have the vnext with all its commits, but here in SetTwoFactorCodeAsync
            if (contentData.Contains("Tired of waiting for your code?"))
                await SkipAuthenticatorAdvertise(codeResponseMessage);

            //TO DO: How to verify, that content is a companion code
            else if (contentData.Length <= 64)
            {
                _code = contentData;
            }

you can see that it goes into SkipAuthenticatorAdvertise which doesn't do   _code = contentData; and when it returns due to the else it just exits the function.
The file you mention doesn't have that double else else you're pasting, also a double else else would not work in that context. I think we already confused @trydis, we may need to do a pull request on this.
https://github.com/tringler/FIFA-Ultimate-Team-Toolkit/blob/7539363ee6565e58edc1512488a962a3bd48dda2/UltimateTeam.Toolkit/Requests/LoginMobileRequest.cs

I'm also confused, but I think I got it now! :D
@trydis: Can you apply @mtdx proposal? I just realized I never ran into the SkipAuthenticatorMethod, since I have activated the Google Authenticator.

@Extremeg Pls remove this post from this thread.

@trydis - I pushed a PR which contains the both bugfixes @mtdx mentioned. Accidently pushed into master branch, but it should not be a problem to apply it to vnext branch as far as I know.

Thanks @tringler, I'll take a look tomorrow :+1:

I've pushed another prerelease package, which includes #251: https://www.nuget.org/packages/UltimateTeam.Toolkit/3.0.0-rc3

Just tested the new prerelease fixes and are working fine.

Thanks for the feedback @mtdx. I'll leave this open a few days just in case something's discovered on certain platforms etc.

When it will be merged as main branch?

As soon as we have we enough positive test feedbacks - Feel free to test it and give feedback ;)

Relased