Containers start issue since a few weeks

Describe the issue
Hello,
Since a few weeks, I have some containers which are non longer restarting.
We're deploying our containers in a N tiers format with external database hosted on a dedicated MSSQL Server.
Every day, servers are automatically shutdown and started the next day at fixed times.
I have setup a scheduled task on that server which will restart all containers 15 min after its startup.
This situation seems to be tied to certain docker image - but I'm not sure.
We have curent multiple containers hosted by the server - using differents versions :

image
encounter issue

mcr.microsoft.com/businesscentral:10.0.17763.2928
yes

mcr.microsoft.com/businesscentral:10.0.17763.2803
no

mcr.microsoft.com/businesscentral:10.0.17763.2686
no

mcr.microsoft.com/businesscentral:10.0.17763.2565
no

mcr.microsoft.com/businesscentral:10.0.17763.2114
no

mcr.microsoft.com/businesscentral:10.0.17763.1817
no

Output of crashed containers is the following :
Creating DotNetCore Web Server Instance
Using application pool name: container_name
Using default container name: NavWebApplicationContainer
Remove C:\inetpub\wwwroot\container_name
Access to the path 'clrjit.dll' is denied.
at New-NavWebSite, C:\run\my\NAVWebClientManagement.psm1: line 562
at New-NAVWebServerInstance, C:\run\my\NAVWebClientManagement.psm1: line 501
at <ScriptBlock>, C:\Run\SetupWebClient.ps1: line 50
at <ScriptBlock>, C:\Run\navstart.ps1: line 189
at <ScriptBlock>, C:\Run\start.ps1: line 377
at <ScriptBlock>, <No file>: line 1

2e434ac9fd43    mcr.microsoft.com/businesscentral:10.0.17763.2928       running         Up 4 hours (unhealthy)
66a58b3e6d5c    mcr.microsoft.com/businesscentral:10.0.17763.2928       running         Up 4 hours (unhealthy)
ec6fd69a0ace    mcr.microsoft.com/businesscentral:10.0.17763.2928       running         Up 2 hours (unhealthy)
c0f6de830d04    mcr.microsoft.com/businesscentral:10.0.17763.2928       running         Up 4 hours (unhealthy)
3974bcef0a06    mcr.microsoft.com/businesscentral:10.0.17763.2686       running         Up 4 hours (healthy)
4b1afbb29c9f    mcr.microsoft.com/businesscentral:10.0.17763.2686       running         Up 4 hours (healthy)
e3c96d2cd0af    mcr.microsoft.com/businesscentral:10.0.17763.2565       running         Up 4 hours (healthy)
38265df6a3dc    mcr.microsoft.com/businesscentral:10.0.17763.2565       running         Up 4 hours (healthy)
afcdce41fb1e    mcr.microsoft.com/businesscentral:10.0.17763.2565       running         Up 4 hours (healthy)
e48c1c1ba933    mcr.microsoft.com/businesscentral:10.0.17763.2114       running         Up 4 hours (healthy)
6bc94b032eb5    mcr.microsoft.com/businesscentral:10.0.17763.2114       running         Up 4 hours (healthy)
89de291d4148    mcr.microsoft.com/businesscentral:10.0.17763.2114       running         Up 4 hours (healthy)
17663b96ebfe    mcr.microsoft.com/businesscentral:10.0.17763.2114       running         Up 4 hours (healthy)
f403d1decfd4    mcr.microsoft.com/businesscentral:10.0.17763.1817       running         Up 4 hours (healthy)
c379242900c3    traefik:v1.7-windowsservercore-1809                     running         Up 4 hours

Scripts used to create container and cause the issue
# Load MSSQL functions
Import-Module SqlServer
Import-Module BcContainerHelper

# init MSSQL Server node
$sqlServer = $env:SqlServer # SQL Server
$sqlInstance = $env:SqlInstance # SQL Instance
$sqlDataDirectory = $env:SqlDataDirectory # SQL Database DATA Directory
$sqlLogsDirectory = $env:SqlLogsDirectory # SQL Database LOGS Directory

# init docker node FQDN (for SSL and routing)
$node_fqdn = $env:DockerNode

# init template (bak filename - without Docker Prefix and Template Suffix)
$template = $env:TemplateName;

# init containers list
$containers = $env:Containers

# Load references containers setup
$matrixFile = "c:\Scripts\images.json"

# Business Central
$navUser = "username"
$navPassword = "P@$sW03d"

Write-Host ""
Write-Host "-----------------------------------------"
Write-Host "Checking Microsoft SQL Server Settings"
Write-Host "-----------------------------------------"
Write-Host ""

if (-Not ($sqlServer))
{
    Throw "Required SQL Server is missing !"
}

if (-Not ($sqlInstance))
{
    Throw "Required SQL Instance is missing !"
}

if (-Not ($sqlDataDirectory))
{
    Throw "Required database DATA directory is missing !"
}

if (-Not ($sqlLogsDirectory))
{
    Throw "Required database LOGS directory is missing !"
}

Write-Host "Check pass" -ForegroundColor Green

Write-Host ""
Write-Host "-----------------------------------------"
Write-Host "Checking Docker Settings"
Write-Host "-----------------------------------------"
Write-Host ""

if (-Not ($node_fqdn))
{
    Throw "Required Docker public name (FQDN) is missing !"
}

if (-Not ($template))
{
    Throw "Required template name is missing !"
}

if (-Not ($containers))
{
    Throw "Required container list is missing !"
}

if (-Not (Test-Path $matrixFile))
{
    Throw "Required referencial is missing !"
}

Write-Host "Check pass" -ForegroundColor Green

# retrieve image metadata
# Name | DatabaseBackup | TargetVersion | ServerDirectory | StagingEnvironmentName
Write-Host ""
Write-Host "Looking for container setup using ${template}..."
$image = (Get-Content $matrixFile | `
        Out-String | `
        ConvertFrom-Json) | `
        Where-Object { $_.Name -eq $template } | `
        Select-Object -First 1

if ($null -eq $image)
{
    Throw "Unable to determine suitable setup. Template ${template} is not found !"
}

# get Business Central package and license
$artifactUrl = Get-BCArtifactUrl -type OnPrem -Country FR -version ${image}.TargetVersion
$licenseFile = "c:\Licences\DEV_BC$(${image}.ServerDirectory).flf"

if (-Not (Test-Path $licenseFile))
{
    Throw "Required license file for Business Central $(${image}.TargetVersion) is missing !"
}

# Explode containers list
$containers = $containers.Split(',')

Write-Host ""
Write-Host "-----------------------------------------"
Write-Host "Bootstrap $($containers.Length) container(s)"
Write-Host "-----------------------------------------"

# bootstrap containers
# $containers | ForEach-Object -Parallel # when powershell 7.0 compliant
foreach ($container in $containers)
{
    $container = $container.Trim()

    # drop existing container
    Write-Host ""
    Write-Host "Drop existing container $container"
    Remove-BcContainer -containerName $container

    # bootstrap database
    Write-Host ""
    Write-Host "Bootstrap database... as $container"
    Restore-SqlDatabase -ServerInstance "${sqlServer}\${sqlInstance}" `
        -Database "docker-$container" `
        -ReplaceDatabase `
        -BackupFile ${image}.DatabaseBackup `
        -RelocateFile ((New-Object Microsoft.SqlServer.Management.Smo.RelocateFile("Template_Data", "${sqlDataDirectory}\docker-$($container)_Data.mdf")), (New-Object Microsoft.SqlServer.Management.Smo.RelocateFile("Template Data Filegroup 1", "${sqlDataDirectory}\docker-$($container)_Data Filegroup 1.ndf")), (New-Object Microsoft.SqlServer.Management.Smo.RelocateFile("Template_Log", "${sqlLogsDirectory}\docker-$($container)_Log.ldf")))

    # spawn container
    Write-Host ""
    Write-Host "Spawning Container $($container)..."
    New-BcContainer `
        -accept_eula `
        -containerName $container `
        -artifactUrl ${artifactUrl} `
        -enableTaskScheduler `
        -licenseFile ${licenseFile} `
        -databaseServer "${sqlServer}\${sqlInstance}" `
        -databasePrefix "docker-" `
        -databaseName $container `
        -useTraefik `
        -PublicDnsName ${node_fqdn} `
        -auth "NavUserPassword" `
        -shortcuts None `
        -Credential (New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList ${navUser}, (ConvertTo-SecureString -String ${navPassword} -AsPlainText -Force))

    # to be run during boot stage
    Invoke-ScriptInBcContainer -containerName $container -ScriptBlock { param($LoadTestToolkit, $image)
        Write-Host ""
        Write-Host "Importing Add-Ins..."
        Copy-Item -Path "c:\programdata\bccontainerhelper\AddIns\BC$($image.ServerDirectory)\" "C:\Program Files\Microsoft Dynamics NAV\$($image.ServerDirectory)\Service\Add-Ins\" -Recurse

        # publish test toolkit
        if ($LoadTestToolkit)
        {
            Write-Host ""
            Write-Host "Importing Test Toolkit..."

            Import-Module "c:\Program Files\Microsoft Dynamics NAV\$($image.ServerDirectory)\Service\NavAdminTool.ps1"

            # Random data management
            Publish-NAVApp -ServerInstance BC -Path "C:\Applications\TestFramework\TestLibraries\Any\Microsoft_Any.app"

            # Assert Library
            Publish-NAVApp -ServerInstance BC -Path "C:\Applications\TestFramework\TestLibraries\Assert\Microsoft_Library Assert.app"

            # Tests runner
            Publish-NAVApp -ServerInstance BC -Path "C:\Applications\TestFramework\TestRunner\Microsoft_Test Runner.app"

            Sync-NAVApp -ServerInstance BC -AppPublisher "Microsoft" -AppName "Any"
            Sync-NAVApp -ServerInstance BC -AppPublisher "Microsoft" -AppName "Library Assert"
            Sync-NAVApp -ServerInstance BC -AppPublisher "Microsoft" -AppName "Test Runner"

            Install-NAVApp -ServerInstance BC -AppPublisher "Microsoft" -AppName "Any"
            Install-NAVApp -ServerInstance BC -AppPublisher "Microsoft" -AppName "Library Assert"
            Install-NAVApp -ServerInstance BC -AppPublisher "Microsoft" -AppName "Test Runner"
        }
    } -ArgumentList ($container -ne $image.StagingEnvironmentName), $image

    # reboot container to load added assemblies
    Restart-NavContainer -containerName $container
}

Full output of scripts
2022-06-09T07:12:23.5245712Z ##[section]Starting: New Container
2022-06-09T07:12:23.5797398Z ==============================================================================
2022-06-09T07:12:23.5798013Z Task         : PowerShell
2022-06-09T07:12:23.5798439Z Description  : Run a PowerShell script on Linux, macOS, or Windows
2022-06-09T07:12:23.5798641Z Version      : 2.200.0
2022-06-09T07:12:23.5798926Z Author       : Microsoft Corporation
2022-06-09T07:12:23.5799264Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2022-06-09T07:12:23.5799552Z ==============================================================================
2022-06-09T07:12:24.7708941Z Generating script.
2022-06-09T07:12:24.7735442Z Formatted command: . 'C:\Scripts\NewContainer.ps1'
2022-06-09T07:12:24.8068921Z ========================== Starting Command Output ===========================
2022-06-09T07:12:24.8282996Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'E:\Agents\agent_1\_work\_temp\06bdeb94-604d-4162-8deb-5964673208db.ps1'"
2022-06-09T07:12:25.8758700Z BcContainerHelper version 3.0.10
2022-06-09T07:12:25.9459593Z Setting hostHelperFolder = e:\BcContainerHelper
2022-06-09T07:12:25.9502300Z Setting bcartifactsCacheFolder = e:\bcartifacts.cache
2022-06-09T07:12:26.1406986Z BcContainerHelper emits usage statistics telemetry to Microsoft
2022-06-09T07:12:28.5924532Z WARNING: The names of some imported commands from the module 'BcContainerHelper' include unapproved verbs that might
2022-06-09T07:12:28.5926372Z make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the
2022-06-09T07:12:28.5927511Z Verbose parameter. For a list of approved verbs, type Get-Verb.
2022-06-09T07:12:28.6379792Z
2022-06-09T07:12:28.6384896Z -----------------------------------------
2022-06-09T07:12:28.6389993Z Checking Microsoft SQL Server Settings
2022-06-09T07:12:28.6395335Z -----------------------------------------
2022-06-09T07:12:28.6398067Z
2022-06-09T07:12:28.6412940Z Check pass
2022-06-09T07:12:28.6415675Z
2022-06-09T07:12:28.6421247Z -----------------------------------------
2022-06-09T07:12:28.6426841Z Checking Docker Settings
2022-06-09T07:12:28.6431932Z -----------------------------------------
2022-06-09T07:12:28.6434642Z
2022-06-09T07:12:28.6444431Z Check pass
2022-06-09T07:12:28.6446723Z
2022-06-09T07:12:28.6452426Z Looking for container setup using TEMPLATE...
2022-06-09T07:12:30.0134408Z
2022-06-09T07:12:30.0140530Z -----------------------------------------
2022-06-09T07:12:30.0167558Z Bootstrap 1 container(s)
2022-06-09T07:12:30.0172890Z -----------------------------------------
2022-06-09T07:12:30.0188083Z
2022-06-09T07:12:30.0194088Z Drop existing container container_name
2022-06-09T07:12:31.3055797Z Removing Session container_name
2022-06-09T07:12:31.7234838Z Removing container container_name
2022-06-09T07:12:32.3435678Z Removing Desktop shortcuts
2022-06-09T07:12:32.3901836Z Removing e:\BcContainerHelper\Extensions\container_name
2022-06-09T07:12:32.8032374Z
2022-06-09T07:12:32.8040007Z Bootstrap database... as container_name
2022-06-09T07:13:10.2030718Z
2022-06-09T07:13:10.2037312Z Granting Docker access...
2022-06-09T07:13:10.3180919Z
2022-06-09T07:13:10.3188166Z Spawning Container container_name...
2022-06-09T07:13:12.0132645Z BcContainerHelper is version 3.0.10
2022-06-09T07:13:12.0138675Z BcContainerHelper is running as administrator
2022-06-09T07:13:13.3309440Z Hyper-V is Disabled
2022-06-09T07:13:13.3333540Z UsePsSession is True
2022-06-09T07:13:13.3355637Z Host is Microsoft Windows Server 2019 Datacenter - ltsc2019
2022-06-09T07:13:13.7822466Z Docker Client Version is 20.10.0
2022-06-09T07:13:13.7851528Z Docker Server Version is 20.10.0
2022-06-09T07:13:14.7702490Z Removing Desktop shortcuts
2022-06-09T07:13:15.2311219Z Fetching all docker images
2022-06-09T07:13:15.5611236Z Fetching all docker volumes
2022-06-09T07:13:15.8976711Z Enabling SSL as otherwise all clients will see mixed HTTP / HTTPS request, which will cause problems e.g. on the mobile and modern windows clients
2022-06-09T07:13:16.7027360Z Using image mcr.microsoft.com/businesscentral:10.0.17763.2928
2022-06-09T07:13:16.9988890Z PublicDnsName is mydomain.tld
2022-06-09T07:13:17.4044550Z Creating Container container_name
2022-06-09T07:13:17.4052036Z Style: onprem
2022-06-09T07:13:17.4059280Z Multitenant: No
2022-06-09T07:13:17.4074027Z Version: 19.1.31886.32186
2022-06-09T07:13:17.4081013Z Platform: 19.0.31889.32155
2022-06-09T07:13:17.4090867Z Generic Tag: <IP_ADDRESS>
2022-06-09T07:13:17.4118171Z Container OS Version: 10.0.17763.2928 (ltsc2019)
2022-06-09T07:13:17.4125882Z Host OS Version: 10.0.17763.2928 (ltsc2019)
2022-06-09T07:13:17.4207629Z Using process isolation
2022-06-09T07:13:17.4248280Z Using locale fr-FR
2022-06-09T07:13:17.4288053Z Adding special CheckHealth.ps1 to enable Traefik support
2022-06-09T07:13:17.4310729Z Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
2022-06-09T07:13:17.4624417Z Using license file c:\Licences\DEV_BC190.flf
2022-06-09T07:13:17.5315574Z Additional Parameters:
2022-06-09T07:13:17.5432423Z -e webserverinstance=container_name
2022-06-09T07:13:17.5439650Z -e publicdnsname=mydomain.tld
2022-06-09T07:13:17.5446159Z -l "traefik.protocol=https"
2022-06-09T07:13:17.5453029Z -l "traefik.web.frontend.rule=PathPrefix:/container_name"
2022-06-09T07:13:17.5458863Z -l "traefik.web.port=443"
2022-06-09T07:13:17.5466374Z -l "traefik.soap.frontend.rule=PathPrefix:/container_namesoap;ReplacePathRegex: ^/container_namesoap(.*) /BC$1"
2022-06-09T07:13:17.5473150Z -l "traefik.soap.port=7047"
2022-06-09T07:13:17.5479560Z -l "traefik.rest.frontend.rule=PathPrefix:/container_namerest;ReplacePathRegex: ^/container_namerest(.*) /BC$1"
2022-06-09T07:13:17.5486058Z -l "traefik.rest.port=7048"
2022-06-09T07:13:17.5492698Z -l "traefik.dev.frontend.rule=PathPrefix:/container_namedev;ReplacePathRegex: ^/container_namedev(.*) /BC$1"
2022-06-09T07:13:17.5498396Z -l "traefik.dev.port=7049"
2022-06-09T07:13:17.5504836Z -l "traefik.snap.frontend.rule=PathPrefix:/container_namesnap;ReplacePathRegex: ^/container_namesnap(.*) /BC$1"
2022-06-09T07:13:17.5510783Z -l "traefik.snap.port=7083"
2022-06-09T07:13:17.5517132Z -l "traefik.dl.frontend.rule=PathPrefixStrip:/container_namedl"
2022-06-09T07:13:17.5523264Z -l "traefik.dl.port=8080"
2022-06-09T07:13:17.5529384Z -l "traefik.dl.protocol=http"
2022-06-09T07:13:17.5536481Z -l "traefik.enable=true"
2022-06-09T07:13:17.5543896Z -l "traefik.frontend.entryPoints=https"
2022-06-09T07:13:17.5552455Z --env customNavSettings=EnableTaskScheduler=True,PublicODataBaseUrl=https://mydomain.tld/container_namerest/odata,PublicSOAPBaseUrl=https://mydomain.tld/container_namesoap/ws,PublicWebBaseUrl=https://mydomain.tld/container_name
2022-06-09T07:13:17.5558473Z Files in e:\BcContainerHelper\Extensions\container_name\my:
2022-06-09T07:13:17.5702207Z - AdditionalOutput.ps1
2022-06-09T07:13:17.5711647Z - CheckHealth.ps1
2022-06-09T07:13:17.5720213Z - license.flf
2022-06-09T07:13:17.5727937Z - MainLoop.ps1
2022-06-09T07:13:17.5735428Z - SetupVariables.ps1
2022-06-09T07:13:17.5743679Z - updatecontainerhosts.ps1
2022-06-09T07:13:17.5751235Z Creating container container_name from image mcr.microsoft.com/businesscentral:10.0.17763.2928
2022-06-09T07:13:17.6203332Z Using Shared Encryption Key file
2022-06-09T07:13:17.9965003Z 2e434ac9fd43db75a582dc6d6d665adc2ca954881f56425252ce053fbd7a8dc4
2022-06-09T07:13:20.3293838Z Waiting for container container_name to be ready
2022-06-09T07:13:28.6081813Z Using artifactUrl https://bcartifacts.azureedge.net/onprem/19.1.31886.32186/fr
2022-06-09T07:13:28.6082281Z Using installer from C:\Run\150-new
2022-06-09T07:13:28.6082563Z Installing Business Central
2022-06-09T07:13:28.6083565Z Installing from artifacts
2022-06-09T07:13:32.6136217Z Starting Local SQL Server
2022-06-09T07:13:32.6136841Z Starting Internet Information Server
2022-06-09T07:13:32.6137245Z Copying Service Tier Files
2022-06-09T07:13:33.9721651Z c:\dl\onprem\19.1.31886.32186\platform\ServiceTier\Program Files
2022-06-09T07:13:33.9722302Z c:\dl\onprem\19.1.31886.32186\platform\ServiceTier\System64Folder
2022-06-09T07:13:33.9722697Z Copying PowerShell Scripts
2022-06-09T07:13:33.9723017Z c:\dl\onprem\19.1.31886.32186\platform\WindowsPowerShellScripts\Cloud\NAVAdministration
2022-06-09T07:13:33.9723390Z c:\dl\onprem\19.1.31886.32186\platform\WindowsPowerShellScripts\WebSearch
2022-06-09T07:13:33.9723665Z Copying Web Client Files
2022-06-09T07:13:35.2988450Z c:\dl\onprem\19.1.31886.32186\platform\WebClient\Microsoft Dynamics NAV
2022-06-09T07:13:35.2989144Z Copying Client Files
2022-06-09T07:13:35.2989596Z c:\dl\onprem\19.1.31886.32186\platform\LegacyDlls\program files\Microsoft Dynamics NAV
2022-06-09T07:13:35.2990157Z c:\dl\onprem\19.1.31886.32186\platform\LegacyDlls\program files\Microsoft Dynamics NAV
2022-06-09T07:13:35.2990681Z c:\dl\onprem\19.1.31886.32186\platform\LegacyDlls\systemFolder
2022-06-09T07:13:35.2991053Z Copying ModernDev Files
2022-06-09T07:13:35.2991377Z c:\dl\onprem\19.1.31886.32186\platform
2022-06-09T07:13:36.6161326Z c:\dl\onprem\19.1.31886.32186\platform\ModernDev\program files\Microsoft Dynamics NAV
2022-06-09T07:13:36.6161825Z Copying additional files
2022-06-09T07:13:36.6162075Z Copying ConfigurationPackages
2022-06-09T07:13:36.6162343Z C:\dl\onprem\19.1.31886.32186\platform\ConfigurationPackages
2022-06-09T07:13:36.6162641Z Copying Test Assemblies
2022-06-09T07:13:36.6162961Z C:\dl\onprem\19.1.31886.32186\platform\Test Assemblies
2022-06-09T07:13:36.6163203Z Copying Applications
2022-06-09T07:13:36.6163461Z C:\dl\onprem\19.1.31886.32186\fr\Applications
2022-06-09T07:13:36.6163689Z Copying dependencies
2022-06-09T07:13:53.1684996Z Copying ReportBuilder
2022-06-09T07:13:53.1685446Z Importing PowerShell Modules
2022-06-09T07:13:53.1685747Z Skipping restore of Cronus database
2022-06-09T07:13:53.1686190Z Modifying Business Central Service Tier Config File for Docker
2022-06-09T07:13:54.5001590Z Creating Business Central Service Tier
2022-06-09T07:13:54.5002030Z Installing SIP crypto provider: 'C:\Windows\System32\NavSip.dll'
2022-06-09T07:13:54.5002338Z Installation took 26 seconds
2022-06-09T07:13:54.5002609Z Installation complete
2022-06-09T07:13:54.5002800Z Initializing...
2022-06-09T07:13:54.5003085Z Setting host.containerhelper.internal to <IP_ADDRESS> in container hosts file
2022-06-09T07:13:54.5003353Z Starting Container
2022-06-09T07:13:54.5003564Z Hostname is container_name
2022-06-09T07:13:54.5003827Z PublicDnsName is mydomain.tld
2022-06-09T07:13:55.8355970Z Using NavUserPassword Authentication
2022-06-09T07:14:01.0976652Z Import Encryption Key
2022-06-09T07:14:02.4181676Z Stopping local SQL Server
2022-06-09T07:14:02.4182166Z Creating Self Signed Certificate
2022-06-09T07:14:02.4182560Z Self Signed Certificate Thumbprint 4306F0D1825954121C1250360207BACEA2C81541
2022-06-09T07:14:02.4183026Z DNS identity mydomain.tld
2022-06-09T07:14:02.4183857Z Modifying Service Tier Config File with Instance Specific Settings
2022-06-09T07:14:03.7370783Z Modifying Service Tier Config File with settings from environment variable
2022-06-09T07:14:03.7371322Z Setting EnableTaskScheduler to True
2022-06-09T07:14:03.7371780Z Setting PublicODataBaseUrl to https://mydomain.tld/container_namerest/odata
2022-06-09T07:14:03.7372434Z Setting PublicSOAPBaseUrl to https://mydomain.tld/container_namesoap/ws
2022-06-09T07:14:03.7372880Z Setting PublicWebBaseUrl to https://mydomain.tld/container_name
2022-06-09T07:16:27.2700102Z Starting Service Tier
2022-06-09T07:16:27.2700754Z CertificateThumprint 4306F0D1825954121C1250360207BACEA2C81541
2022-06-09T07:16:27.2701792Z Registering event sources
2022-06-09T07:16:27.2702181Z Creating DotNetCore Web Server Instance
2022-06-09T07:16:27.2702676Z Using application pool name: container_name
2022-06-09T07:16:27.2703138Z Using default container name: NavWebApplicationContainer
2022-06-09T07:16:30.0622726Z Copy files to WWW root C:\inetpub\wwwroot\container_name
2022-06-09T07:16:31.3836950Z Create the application pool container_name
2022-06-09T07:16:32.7052718Z Create website: NavWebApplicationContainer with SSL
2022-06-09T07:16:32.7053238Z Update configuration: navsettings.json
2022-06-09T07:16:32.7053481Z Done Configuring Web Client
2022-06-09T07:16:32.7053714Z Using license file 'c:\run\my\license.flf'
2022-06-09T07:16:32.7053943Z Import License
2022-06-09T07:16:34.0300552Z Creating http download site
2022-06-09T07:16:34.0300919Z Container IP Address: <IP_ADDRESS>
2022-06-09T07:16:34.0301203Z Container Hostname  : container_name
2022-06-09T07:16:34.0301590Z Container Dns Name  : mydomain.tld
2022-06-09T07:16:34.0301956Z Web Client          : https://mydomain.tld/container_name/
2022-06-09T07:16:34.0302426Z Dev. Server         : https://mydomain.tld
2022-06-09T07:16:34.0302709Z Dev. ServerInstance : BC
2022-06-09T07:16:34.0302808Z
2022-06-09T07:16:34.0302949Z Files:
2022-06-09T07:16:34.0303667Z http://mydomain.tld:8080/ALLanguage.vsix
2022-06-09T07:16:34.0304098Z http://mydomain.tld:8080/certificate.cer
2022-06-09T07:16:34.0304303Z
2022-06-09T07:16:34.0304517Z Container Total Physical Memory is 128.0Gb
2022-06-09T07:16:34.0304769Z Container Free Physical Memory is 68.9Gb
2022-06-09T07:16:34.0304889Z
2022-06-09T07:16:34.0305067Z Initialization took 160 seconds
2022-06-09T07:16:34.0305884Z Ready for connections!
2022-06-09T07:16:34.6723902Z Reading CustomSettings.config from container_name
2022-06-09T07:16:35.4312324Z Container container_name successfully created
2022-06-09T07:16:35.4318706Z Because of Traefik, the following URLs need to be used when accessing the container from outside your Docker host:
2022-06-09T07:16:35.4325272Z Web Client:        https://mydomain.tld/container_name
2022-06-09T07:16:35.4331588Z SOAP WebServices:  https://mydomain.tld/container_namesoap
2022-06-09T07:16:35.4337776Z OData WebServices: https://mydomain.tld/container_namerest
2022-06-09T07:16:35.4344148Z Dev Service:       https://mydomain.tld/container_namedev
2022-06-09T07:16:35.4350454Z Snapshot Service:  https://mydomain.tld/container_namesnap
2022-06-09T07:16:35.4356521Z File downloads:    https://mydomain.tld/container_namedl
2022-06-09T07:16:35.4359528Z
2022-06-09T07:16:35.4365229Z Use:
2022-06-09T07:16:35.4376839Z Get-BcContainerEventLog -containerName container_name to retrieve a snapshot of the event log from the container
2022-06-09T07:16:35.4388318Z Get-BcContainerDebugInfo -containerName container_name to get debug information about the container
2022-06-09T07:16:35.4400009Z Enter-BcContainer -containerName container_name to open a PowerShell prompt inside the container
2022-06-09T07:16:35.4412778Z Remove-BcContainer -containerName container_name to remove the container again
2022-06-09T07:16:35.4424943Z docker logs container_name to retrieve information about URL's again
2022-06-09T07:16:36.2994082Z
2022-06-09T07:16:36.2996193Z Importing Add-Ins...
2022-06-09T07:16:46.0722424Z container_name
2022-06-09T07:16:46.4209102Z Waiting for container container_name to be ready
2022-06-09T07:16:47.7821968Z
2022-06-09T07:16:47.7822749Z Initializing...
2022-06-09T07:16:47.7823186Z Setting host.containerhelper.internal to <IP_ADDRESS> in container hosts file
2022-06-09T07:16:47.7823468Z Restarting Container
2022-06-09T07:16:47.7824030Z PublicDnsName unchanged
2022-06-09T07:16:47.7824324Z Hostname is container_name
2022-06-09T07:16:47.7824584Z PublicDnsName is mydomain.tld
2022-06-09T07:16:47.7824907Z Using NavUserPassword Authentication
2022-06-09T07:16:49.1416009Z Starting Internet Information Server
2022-06-09T07:18:06.4433309Z Starting Service Tier
2022-06-09T07:18:06.4433678Z Container IP Address: <IP_ADDRESS>
2022-06-09T07:18:06.4434534Z Container Hostname  : container_name
2022-06-09T07:18:06.4434946Z Container Dns Name  : mydomain.tld
2022-06-09T07:18:06.4435439Z Web Client          : https://mydomain.tld/container_name
2022-06-09T07:18:06.4435872Z Dev. Server         : https://mydomain.tld
2022-06-09T07:18:06.4436170Z Dev. ServerInstance : BC
2022-06-09T07:18:06.4436267Z
2022-06-09T07:18:06.4436426Z Files:
2022-06-09T07:18:06.4436874Z http://mydomain.tld:8080/ALLanguage.vsix
2022-06-09T07:18:06.4437401Z http://mydomain.tld:8080/certificate.cer
2022-06-09T07:18:07.7748436Z
2022-06-09T07:18:07.7749308Z Container Total Physical Memory is 128.0Gb
2022-06-09T07:18:07.7749697Z Container Free Physical Memory is 72.6Gb
2022-06-09T07:18:07.7749882Z
2022-06-09T07:18:07.7750072Z Initialization took 79 seconds
2022-06-09T07:18:07.7754820Z Ready for connections!
2022-06-09T07:18:09.8413423Z ##[section]Finishing: New Container

Additional context

does it happen all the time? as said, it occures always after server restart - and on all containers using image mcr.microsoft.com/businesscentral:10.0.17763.2928
did it use to work? yes, until few weeks

Just updated scripts using your first option, redeploy containers which was using image mcr.microsoft.com/businesscentral:10.0.17763.2928 ans reboot the server manualy.
It appears to works, but will confirm you the state of things on monday.

I think this bug is related to another bug (#2536 and #2535), which I just suggested a fix in the generic image for.
Could you try to add this to your New-BcContainer (instead of the special generic image):
-myscripts @("https://raw.githubusercontent.com/microsoft/nav-docker/master/generic/Run/navstart.ps1")

Hello @freddydk,
I confirm you that since I've force image 10.0.17763.2928 I have non longer issue with previous containers.
I've just updated deployment script with your last change and renew two containers - I'll give you the state of things tomorrow after daily server start.

@freddydk confirm it still working using the provided custom scripts instruction.
However, I just figure it might be tied to another thing since in my initial diag, I had spot that we were encountering issue only on containers using latest image... which is build 2928.
But I've created last 5 containers using that specific image.

First attempt, using usegenericimage
Second attempt, using myscripts

I've rollback changes and will make new check tomorrow - let's see how it's going.

State of thing, with changes rollback, lastly deployed container are again experiencing issue after VM reboot - except one which is using new build 3046 (assume it's containing upper changes ?).
As a result, I've added back the following instruction to deployment script and redeploy last containers.
-myscripts @("https://raw.githubusercontent.com/microsoft/nav-docker/master/generic/Run/navstart.ps1")

hi, I confirm I have non longer issue since 10.0.17763.3046 has been released.
thank you very much :)


Time issue book a desk-> bookings

Describe the bug
The booking time displayed in bookings lies 1h before the time selected in book a desk. This does not happen when using the edit bookings function. This happens when using the production server.
To Reproduce
Steps to reproduce the behavior:

Go to book a desk
Book a desk, remember the time
Look at the booking in Bookings
See error

Expected behavior
The times should be the same
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

THis is a display error in the My Bookings Overview, i will fix that this sprint.


Prove a minimum spending condition for proposals

If a valid transaction does not remove any deposits, it should be true that coin (consumed pparams utxoSt txb) ≥ length (txprop txb) * govActionDeposit.
A more general version of this would be to drop the condition that no deposits are removed and subtract the refunded deposits. It may or may not be easier to prove the above from this more general version, but going via this route is optional and only worth it if it's easier.

This should be proven with respect to the utxo rule in this PR, it should be lifted to the top level later in a separate issue.

Task complete!  PR #375 now ready for review.  🚀


How i can put  to postTweet?

How i can put  to postTweet?

You can use "\n" for newline.
Example:
$status = "First line. \nSecond line. \nThird line";


Setting initial collapsed state of nodes

Are you reporting a bug, or opening a feature request?
Question or Feature Request
What is the behavior/output you expect?
How do you set the initial collapsed/expanded state of any particular set of nodes in the Tree data?
In v1, we were able to do this via the _collapsed attribute - but setting the __rd3t.collapsed attribute does not have the same effect.
What version of react-d3-tree are you using?
3.3

If anyone knows of any workarounds to this, e.g. via an imperative API call, please do let me know. 💜

Copying across the example I posted of what I am trying to achieve;
I would like to load the tree with a specific path expanded (everything else collapsed).
For example, given the following tree;
             A
           /   \
          /     \
         B       E
        / \
       /   \
      C     D

I would like to be able to set the path of A -> B -> D to be be visible/expanded when the tree initially loads;
             A
           /
          /
         B
          \
           \
            D

hey,  @sockthedev. Is there any chance that you resolved the issue? I'd highly appreciate if you reply. Ciao

Hey @hikmert, in the end I rendered the entire tree, but then updated the style for the active path so that it was "brighter" than the rest of the nodes. I would have preferred the above, but for now this is working. I'll see how the solution scales though.

Hey, @sockthedev. Were you able to resolve the issue?
I basically had search kind of thing built on this. So, Stuck with using v1.

Something like this patch can work:
https://gist.github.com/danielbeeke/ca8e4c6a95928d11cc9b8df0f7c18628

Exactly that,
with this you can control if a node should be opened on load.

I guess my question is, how do I use it? I just see a patch to the source code of the library, but how do i use it from my application?

This might help: https://www.npmjs.com/package/patch-package

that does help with patching the library. But how do i control these states in my app? Thanks

Figured out more or less how i can control the collapsed state from my app, using the patch from @danielbeeke  I will post my solution here eventually (after my vacation)


Expose message generation framework

Original report (archived issue) by Anonymous.

Summary
I'm trying to add custom messages to my ignition project. Since ign-msgs doesn't seem to expose this functionality, I had to copy the cmake macro ign_msgs_protoc from ign-msgs/src/CMakeLists.txt into my own project, along with the generator source files: ign-msgs/src/Generator.cc, ign-msgs/src/Generator.hh, ign-msgs/src/generator_main.cc. Although this works, it's not a clean solution. Are there any plans to export the message generation framework so it can be used by other projects?

This was completed in #339, tutorial added in: https://github.com/gazebosim/gz-msgs/pull/386


Fix keyboard navigation in dropdown

The previous change assumed jQuery was in use (angular.element uses jQuery Lite by default which does NOT support class names with .find() -  https://docs.angularjs.org/api/ng/function/angular.element).  This change works without wrapping angular.element() around the selectors but I did it to keep it AngularJS-ish (don't really know if there are benefits to making it into a jqLite or jQuery object again).

https://github.com/Morgul/ui-bootstrap4/issues/67

That seems like a reasonable fix.
I'll try to remind myself how to do a release this weekend. (Haven't even looked at this project in years. 😅)


Return 200 status code on API requests to '/' urls

Fixes #1064

Codecov Report

Merging #1074 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master    #1074   +/-   ##
=========================================
  Coverage     99.39%   99.39%
- Complexity     2254     2257    +3
=========================================
  Files           341      342    +1
  Lines          6151     6155    +4
  Branches        358      358
=========================================
+ Hits           6114     6118    +4
  Misses            5        5
  Partials         32       32

Flag
Coverage Δ
Complexity Δ

#unittests
?
?

Impacted Files
Coverage Δ
Complexity Δ

...com/quorum/tessera/app/TesseraRestApplication.java
100.00% <ø> (ø)
3.00 <0.00> (ø)

...va/com/quorum/tessera/api/common/BaseResource.java
100.00% <100.00%> (ø)
3.00 <3.00> (?)

Continue to review full report at Codecov.

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


[1.7.10] Logistical Sorter 'default' route is counter-intuitive

It seems that the default route is used as a fallback for everything.
What I would like to do is define say 5 filter rules to send specific items one direction and all others a different direction. So I set up a default route. However, of the destination for one of the 5 filter rules is full (for example, a ore processing setup, which isn't fast enough to keep up), it will not hold on to the items until space is available but send them the default route instead.
I'd like this behaviour to be at least configurable, where 'default' can either mean, 'if you can't send it any other way, send it here', or 'if you there isn't a filter matching this item, send it here'.

+1 Would be nice if we can configure the Sorter in a way that it won't sent items if the target color is full (like a strict color filter or something).

Added an "Allow Default" option to transporter filters.


Syntax highlighting issue

I'm having unusual syntax highlighting using zed 0.151.1 on Ubuntu  and bitbake extension 0.0.2

@MikeBergmann, I see
Somehow, line 149 breaks the syntax highlight

What happens is that bitbake and bash syntax overlap each other. I need to add a bash tree-sitter and figure out how to make it work only for bitbake functions.
Any suggestions are appreciated.

That's what I thought to do. Also, We may need a tree-sitter for Python, as bitbake recipes can have Python functions and anonymous Python functions.
The problem is that config.toml allows configuring tree-sitter usage by file name/extension pattern (.bb, .bbappend). I don't see the possibility of configuring it by some text pattern inside the file.

@MikeBergmann Fix was merged into the extensions repo.

@MikeBergmann Did you try an update?

@anikinmd Yes, thanks a lot. It's looking much better now.


Changed Dockerfile to Node:18-slim (Fixing #1865)

I changed to node:18-slim in the Dockerfile for all the stages.
This fixes the issue #1865
This does increase image size around ~ 100 MB but fixes the problem until https://github.com/prisma/prisma/issues/18510 is fixed from the prisma team
@mikecao

I can't get this PR to properly build on my Portainer instance. Do you have to do anything particular in order to get it to work? It returns nothing in my container logs and does not seem to be assigned to the correct container image, though I am unsure what to do in this case.

@busybox11 Hmm.. not anything specific. The only change is just the base image.  Maybe there is some caching issues?

I try to build the image and run it like the dockerhub one but it doesn't run anything - just an empty shell. It could very well be an issue on my end but tbh I'm not quite sure what to do - it works with the original image. Could this be related to ARM64?

I just build the Dockerfile and it works for me. The only thing that I missed was to specify DATABASE_TYPE in --build-arg when building the image. I also build on ARM64
@busybox11: it sounds like your build succeeds but you just get an empty shell? Can you post your build logs?


Email2

email+priority

Why are you flooding the UniTime project with pull requests that have no description, contain changes that make no sense (like adding PDF fragments to the project's root folder), or would not even compile? Please stop that!
We are open to pull requests; however, they must make sense and provide added value. Also, please test your changes first!


fixed swift 4 warnings

Closing as this actually fails when using swift 3.1.1 but does not feel like checking swift version in every case worths it.


toThrow should return the error

🚀 Feature Proposal
.toThrow and .rejects.toThrow should return the error thrown.
Motivation
When working with a project that uses ava I noticed their .throws and .throwsAsync return the original error. It is very convenient.
This would make it possible to never need the expect.hasAssertions() + try / catch syntax.
Example
function throwSyncError() {
	const syncError = new Error('sync error');
	syncError.code = 'SYNC';
	throw syncError;
}

async function throwAsyncError() {
	const asyncError = new Error('sync error');
	asyncError.code = 'ASYNC';
	throw asyncError;
}

test('can get error message', async () => {
	const syncError = expect(() => throwSyncError()).toThrow('sync error');
	expect(syncError.code).toEqual('SYNC');

	const asyncError = await expect(throwAsyncError()).rejects.toThrow('sync error');
	expect(asyncError.code).toEqual('ASYNC');
});

Pitch
Because using .toThrow and .rejects.toThrow over try/catch it prevents tests that don't fail because they no longer reject. https://github.com/facebook/jest/issues/3917

Sounds like a good idea to me. @SimenB @thymikee @pedrottimark wdyt?

While I agree the idea is sound, I'm not sure we should do this. All matchers today return void (or Promise<void> in the case of resolves and rejects) - changing that is a pretty big change. I'd definitely like @cpojer's and/or @scotthovestadt's thoughts on this before we do much work on it (sorry about not responding sooner, @chrisblossom!).
Note that this change will also break things like https://github.com/mattphillips/jest-chain (/cc @mattphillips who might have thoughts on this 🙂)

As for my own opinion - I think this is better solved by a custom matcher that takes predicate rather than returning the error.

Personally I disagree. But I also think that 90% of the matchers should be removed and should just be expressed as plain javascript with toEqual. Less too learn, less to document.
I'd prefer to use the existing matcher if anything:
test('example', () => {
	let errorThrown;
	expect(() => {
		throw new Error('boom');
	}).toThrow((error) => {
		errorThrown = error;

		// boolean return (true passes, false fails)
		return error.message === 'boom';
	});

	expect(errorThrown.code).toEqual('MODULE_NOT_FOUND');
});

But I think the PR as is feels a lot more natural / expected. Also I think it is best to provide the tools to never need try/catch considering how easy it is to shoot yourself in the foot with it.

All matchers today return void (or Promise in the case of resolves and rejects) - changing that is a pretty big change.

Just curious, why is this considered a big change?

Note that you can do this today:
test('example', () => {
  expect(() => {
    throw new Error('boom');
  }).toThrow(expect.objectContaining({ message: 'boom' }));
});

Another big use case for this is dealing with aggregate errors. Examples: tc39/proposal-promise-any and aggregate-error. Seems very difficult to deal with with the current matching api. With this PR you could set the error and run your own expects.

The type declarations say that matchers return the actual value.  Is that intended to be the case, or is it a mistake?
https://github.com/facebook/jest/blob/master/packages/expect/src/types.ts#L118-L122
I'm hitting the same issue where it's annoying to assert against thrown values.  I already know how to use expect(valueGoesHere).<matchers that I already understand how to use>()  It seems unnecessarily convenient that I have to use a different style of matching for thrown values.

expect(promise).rejects.<matcher here>() can be used to extract the rejection of a promise and match against it.  Can there be a sync variant?  expect(fn).throws.toMatchObject({code: 'ENOENT'})?
It's still not ideal because multiple assertions means multiple function invocations, which is not the case with the promise.  The assertion library should be giving the developer a straightforward way to assert that something throws and get a reference to the thrown value.

@SimenB  Is there any progress to this proposal? I really like it and would be greatly ease testing async functions.

Upvoting this feature as well. 🍌 that it's been sitting for a year without action while other test suites support this.

Note that you can do this today:
test('example', () => {
  expect(() => {
    throw new Error('boom');
  }).toThrow(expect.objectContaining({ message: 'boom' }));
});

For message you can just add the string as .toThrow('boom'), but the asymmetric expect.objectContaining allows you to check any field (at any depth). And you can create your own custom asymmetric matchers if you want as well

@SimenB Is this doced anywhere? I canot find.

Note that you can do this today:
test('example', () => {
  expect(() => {
    throw new Error('boom');
  }).toThrow(expect.objectContaining({ message: 'boom' }));
});

For message you can just add the string as .toThrow('boom'), but the asymmetric expect.objectContaining allows you to check any field (at any depth). And you can create your own custom asymmetric matchers if you want as well

This is great, but I'd like to be able to use expect(thing()).rejects.toBeInstanceOf(SomeErrorClass) and additionally check that the thrown error has the correct data added to it (ie constructed with the right message or value).

This is great, but I'd like to be able to use expect(thing()).rejects.toBeInstanceOf(SomeErrorClass) and additionally check that the thrown error has the correct data added to it (ie constructed with the right message or value).

Currently I do
const promise = thing()
await expect(promise).rejects.toThrow(MyErrorClass)
await expect(promise).rejects.toThrow('Error message')
await expect(promise).rejects.toThrow(expect.objectContaining({ code: 'MY_CODE' }));

But it only kind of works for async code if you want thing() to be evaluated only once. It's a bit clunky.

As for my own opinion - I think this is better solved by a custom matcher that takes predicate rather than returning the error.
expect(() => { throw new Error('boom'); }).toThrowWithField(err => err.code === 'MODULE_NOT_FOUND');

or something like that. Such a matcher may or may not make sense to have in core, but that's a separate discussion

For the sake of keeping Jest consistent, I'm actually fine with this approach. However, I think it would be useful for toThrow to accept a callback.
expect(() => { throw new Error('boom'); }).toThrow((err: any): void => {
  expect(err.code).toBe('MODULE_NOT_FOUND');
});

It's basically just a callback that enables the user to perform their own assertions on the thrown error.

And you can create your own custom asymmetric matchers if you want as well

Ideally, users should be able to avoid making custom matchers. That's probably its own barrier to entry. I've been using Jest for years, and I've never had to make custom matchers. I imagine this is why A) jest has so many matchers out of the box to begin with and B) popular libraries often provide matchers that prevent their users from worrying about this. This is great. But for a typical user, it also makes the idea of creating matchers intimidating. I imagine such an approach is avoided for the average person.
Resorting to "Make a custom matcher" kind of defeats the point and raises a number of problems. Moreover, as chrisblossom, said, leaving the try/catch in the user's hands increases the chance of making mistakes.
The current toThrow doesn't seem to expect a function. So it could easily be overloaded and given a if (typeof input === 'function') portion, I would presume. (I haven't read the code yet.) Thoughts? @SimenB @chrisblossom And/or @cpojer and @scotthovestadt? since it seems Simen really wanted your opinions too.

Welp. For anyone who's interested, I had the (bad) idea of trying out matchers for the first time. I'm not sure whether or not people will find it useful, but I'm leaving it behind as an artifact just in case... while people are waiting to hear back from the Jest devs.
My solution should solve both sync and async use cases. @Janpot could you let me know if you find this useful? You still have to write a bit of code with my solution, but hopefully the approach looks less hackish to you.
const promise = thing() // `thing` is an async function

await expect(promise).rejects.toThrowWithError((error: MyErrorClass) => {
  expect(error).toBeInstanceOf(MyErrorClass);
  expect(error.message).toBe("Error message");
  expect(error.code).toBe("MY_CODE");
});

Jest Code (TypeScript)
Note that I tested my code locally, and it works in all of the anticipated use cases. So if you use my code and it doesn't work, then either A) You have an outdated version of jest or typescript (or some other environment problem), or B) I copy-pasta'd wrong... in which case you should ping me. :slightly_smiling_face:
Extend jest wherever you want -- in your test file, or in a file that you import:
expect.extend({
  toThrowWithError(received, expected) {
    // Constants
    const passErrorToUser = (err: unknown): jest.CustomMatcherResult => {
      expected(err);
      return { pass: true, message: () => "" };
    };

    /* -------------------- Handle Promise Modifiers -------------------- */
    if (this.promise === "resolves")
      return {
        pass: false,
        message: () =>
          this.utils.matcherErrorMessage(
            this.utils.matcherHint("toThrowWithError", undefined, undefined, {
              promise: this.promise,
            }),
            `'${this.promise}' is an invalid modifier for 'toThrowWithError'`,
            ""
          ),
      };

    // Jest already takes care of validating `rejects`. We just need to pass the error along.
    if (this.promise === "rejects") return passErrorToUser(received);

    /* -------------------- Argument Validation -------------------- */
    if (typeof received !== "function")
      return {
        pass: false,
        message: () =>
          this.utils.matcherErrorMessage(
            this.utils.matcherHint("toThrowWithError"),
            `${this.utils.RECEIVED_COLOR("received")} value must be a function`,
            `Received has value: ${this.utils.RECEIVED_COLOR(typeof received)}`
          ),
      };

    if (typeof expected !== "function")
      return {
        pass: false,
        message: () =>
          this.utils.matcherErrorMessage(
            this.utils.matcherHint("toThrowWithError"),
            `${this.utils.EXPECTED_COLOR("expected")} value must be a function`,
            `Expected has value: ${this.utils.EXPECTED_COLOR(typeof expected)}`
          ),
      };

    /* -------------------- Matcher Logic -------------------- */
    try {
      received();
      const errorMessage = "Received function did not throw" as const; // copied from Jest's `toThrow` matcher.

      return {
        pass: false,
        message: () =>
          `${this.utils.matcherHint("toThrowWithError", undefined, undefined)}\n\n${errorMessage}`,
      };
    } catch (err) {
      return passErrorToUser(err);
    }
  }
});

For TS users, you'll still have to update the types for Jest. In a type declaration file of your choosing, apply the following:
// Add custom jest matchers
declare global {
  namespace jest {
    interface Matchers<R> {
      /**
       * Used to test that a function throws when it is called. Allows
       * assertions to be performed on the error that is generated.
       */
      // eslint-disable-next-line @typescript-eslint/no-explicit-any
      toThrowWithError(expected: (error: any) => void): R extends Promise<void> ? R : void;
    }
  }
}

(Note that I use TS ESLint's recommended settings. So I have a comment for disabling a linter warning.)
I would still love to hear from the Jest devs about updating their toThrow matcher.

Being able to analyze the error in the usual jest funcional style feels like it should be part of the standard api, especially with the discouragement of try{} catch{}

My workaround, usage:
it("checks an error", async () => {
  let error = await getError(doAsyncStuff(arg1, arg2));

  // wrap in `async` function if you want to use a sync function or `await` keyword
  // let error = await getError(async () => {...})

  // typeguards for typescript to be happy, since `error` will be `unknown` just like in a `catch` clause
  // if (!expectedErrorGuard(error)) throw error;
  // for example:
  // if (!(error instanceof Error)) throw error;

  expect(error.message).toContain("my error message")
  expect(error.exitCode).toBe(1)
})

Implementation:
class NoErrorThrownError extends Error {}
const getError = async (
  erroring: Promise<unknown> | (() => Promise<unknown>)
) => {
  try {
    let promise = typeof erroring === "function" ? erroring() : erroring;
    await promise;
    throw new NoErrorThrownError();
  } catch (error: unknown) {
    if (error instanceof NoErrorThrownError) throw error;
    return error;
  }
};

I wanted to add that implementing this (or the proposal to make toThrow accept a callback) would also make it easier to to deal with dynamic error messages. For example, if the error message was something like Error: This part of the error message is static but then there is ${someValueThatIDoNotWantJestToCareAbout}, I would want my test to check whether the error message contained just the static part of the error.
The only ways to do that I'm currently aware of are by using a try/catch block (which I don't want to do because it is discouraged for reasons that seem valid), or writing a custom matcher (which I don't want to do either because I would rather not have to learn how to just to accomplish something that seems like it ought to be fairly simple).
I'll probably dig into writing a custom matcher, but FWIW I think the usability of Jest would be significantly improved if it was easier to make assertions about errors other than the message exactly matching a particular string.

This still seems like a legit issue to me (correct me if I'm wrong), so just commenting to keep the bot from killing it as stale (I couldn't remove the stale label)

It's been 5 years, with various suggestions.
Can we please have a expect(myFunction).toThrowWith(expect.objectContaining({/* ... */ }), this becomes similar to toBeCalledWith and generally should assert that the invocation threw an error that supports asymmetric matchers.
The earlier comments that toThrow supports expect.objectContaining seem to be false (perhaps it changed since then) on Jest v29.7.0


vibration/rumble didn't work with bluetooth but work with usb

Discussed in https://github.com/ViGEm/DsHidMini/discussions/265

Originally posted by inibintang November 19, 2022
BthPS3 Bluetooth Drivers v2.6.174
DsHidMini Driver v2.2.282
ps3 sixaxis CECHZC2E B1
HID : xinput

Why do you open an issue when there already exists a discussion? Some crave to get banned for spam...


net: samples: dumb_http_server: Add netusb and zeroconf configurations

Add netusb and zeroconf configuration and fix LLMNR responder for IPv4.

This looks good, though would be nice to have an explicit comment whether that was tested with a real hardware, and what it was.

This should be working on any board with supported USB controller.


Cannot apply default configuration in Debian 9

Cookbook version: 2.6.5
Chef-client version: 14.8.12
Platform Details: Debian 9
Scenario: Use iptables instead of ufw
Steps to Reproduce: Create a recipe that uses firewall 'default' with attribute:
default['firewall']['ubuntu_iptables'] = true

Expected Result: iptables is configured with options 'default'
Actual Result:
I, [2018-12-17T14:55:12.425141 #7031]  INFO -- default-debian-9: [2018-12-17T22:55:10+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: firewall[default] (machete.kvm::default line 25) had an error: Mixlib::ShellOut::ShellCommandFailed: service[iptables-persistent] (/tmp/kitchen/cache/cookbooks/firewall/libraries/provider_firewall_iptables_ubuntu1404.rb line 177) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
I, [2018-12-17T14:55:12.425210 #7031]  INFO -- default-debian-9: ---- Begin output of /bin/systemctl --system enable iptables-persistent ----
I, [2018-12-17T14:55:12.425248 #7031]  INFO -- default-debian-9: STDOUT:
I, [2018-12-17T14:55:12.425279 #7031]  INFO -- default-debian-9: STDERR: Failed to enable unit: File iptables-persistent.service: No such file or directory
I, [2018-12-17T14:55:12.425309 #7031]  INFO -- default-debian-9: ---- End output of /bin/systemctl --system enable iptables-persistent ----
I, [2018-12-17T14:55:12.425338 #7031]  INFO -- default-debian-9: Ran /bin/systemctl --system enable iptables-persistent returned 1
E, [2018-12-17T14:55:12.444482 #7031] ERROR -- default-debian-9: Converge failed on instance <default-debian-9>.

This may be related to #193 but I can't tell because they didn't provide a stack trace. On that note, there is a netfilter-persistent provider in the libraries but for some reason it is using the wrong one.

I think what's happening is that it's calling the wrong provider because I'm using Debian; I believe it thinks I'm using an OS < 14.04:
https://github.com/chef-cookbooks/firewall/blob/master/libraries/provider_firewall_iptables_ubuntu.rb#L26

(I have forked and think I might have a fix)


Include Exit Code -3 on site crash detector

Moving this to ready.
for few sites, I did a check on existing site crash detector and with the new query to include exit code -3. Couldnt find differences in data.
So we can decide if we need to get the new logic to calculate crash:
where (EventId == 15013) and ExitCode != -3


Add Dockerfile

This seems to work.
Build: docker build -t ctop .
Run: docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock ctop
I'd rather use alpine for a smaller image, but it didn't run. Might be musl vs glibc differences. I'm not sure.

Looks good; thanks! I've been looking at the issue running on alpine as well, and hope to have a workaround soon.

Would be good if you add it to docker hub so you can just have people run docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock bcicen/ctop

or you could use minideb - http://www.skippbox.com/minideb-an-ultra-slim-debian-based-docker-image/

with minideb, I get these file sizes

IMAGE               CREATED             CREATED BY                                      SIZE                COMMENT
1a92f20486cf        7 minutes ago       /bin/sh -c #(nop)  CMD ["ctop"]                 0 B
2bec2051645c        7 minutes ago       /bin/sh -c AUTO_ADDED_PACKAGES=`apt-mark s...   1.34 MB
04560cca2d7c        7 minutes ago       /bin/sh -c wget $(curl -s https://api.gith...   4.88 MB
baa82a541575        7 minutes ago       /bin/sh -c BUILD_PACKAGES="curl wget" &&  ...   56.9 MB
75715f037248        17 hours ago                                                        51.1 MB             from Bitnami with love

official alpine-based image build has been pushed and added to README in the latest release:
REPOSITORY                                                  TAG                 IMAGE ID            CREATED             SIZE
quay.io/vektorlab/ctop                                      latest              239e55cd219f        7 minutes ago       28.2 MB


[BUG] PineconeClient: Error getting project name: SyntaxError... after first input in chat

Describe the bug
PDF->Pinecone->Conversational Retrieval QA Chain (see attachement)
pdf is not loaded and this error occures:
[ErrorWithoutStackTrace: PineconeClient: Error getting project name: SyntaxError: Unexpected token A in JSON at position 0]
To Reproduce
Load Chatflow
Choose a pdf
start chat
ask something
Expected behavior
loading the pdf into pinecone and answer
Screenshots
oas-cash-pdf Chatflow.json.txt
Setup

OS: Windows
Browser chrome
<EMAIL_ADDRESS>
tried with several pdfs, has worked with older version

can you try deleting the node, drag n drop a new one to canvas and see if that works?

when deleting and redrop the Pinecone Upsert Document Node, there is an input field Pinecone namespace instead of Additional Params.
Filling it with my namespace (or leaving it blank) results in the same old error (ErrorWithoutStackTrace: PineconeClient: Error getting project name: SyntaxError: Unexpected token A in JSON at position 0)
I put it to railway, but still same error
Found this in the deploy logs, maby it helps:
Starting Flowise...
TypeError: Cannot read properties of undefined (reading 'startsWith')
at Pdf_DocumentLoaders.init (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/documentloaders/Pdf/Pdf.js:81:27)
at buildLangchain (/usr/local/lib/node_modules/flowise/dist/utils/index.js:208:72)
at async App.processPrediction (/usr/local/lib/node_modules/flowise/dist/index.js:539:44)
at async /usr/local/lib/node_modules/flowise/dist/index.js:294:13
[ErrorWithoutStackTrace: PineconeClient: Error getting project name: SyntaxError: Unexpected token A in JSON at position 0]
[ErrorWithoutStackTrace: PineconeClient: Error getting project name: SyntaxError: Unexpected token A in JSON at position 0]

Same with the "Metadata Filter Load" template from the marktplace, no change after delete and redrop the node

are you installing flowise via docker or npx flowise start or yarn start ?
if using npx can you reinstall npm install -g flowise and npx flowise start?
if using yarn start:
git clone https://github.com/FlowiseAI/Flowise.git
cd Flowise
yarn install
yarn build-force
yarn start

This flow works for me:
example Chatflow.txt

I have solved it.
Reinstalling with yarn did not bring any changes. I then deleted the index and created a new one. Now it works. Not understandable, but obviously not a problem on Flowise's part.
Thanks a lot for helping me troubleshoot this.
Flowise is such a great project with fantastic developers.
Thanks again Henry!


V1.5 View schedules

Coverage decreased (-0.07%) to 92.167% when pulling d3534bc0a1c133e2d048653826ac9cb0f14e3228 on v1.5ViewSchedule into 7967bfca4d360a89ddc57b809e0061dc70eccff6 on master.

Coverage decreased (-0.07%) to 92.167% when pulling a8cfa39be642d426ae84c3a81cbe62b3fa4daca4 on v1.5ViewSchedule into 758de183889ca701b03016328d75ee604588b232 on master.

Coverage increased (+0.02%) to 92.255% when pulling 49501e0b46dfe4536203ffd28ee29935326bee0d on v1.5ViewSchedule into 758de183889ca701b03016328d75ee604588b232 on master.


Closed meetings: Account detail view needs info about closed meetings

Current behavior
All meetings in which a user is participating are listed in the account detail view. There is currently no indication if the meeting is closed or not.
Example - Last meeting is closed without any indicator.

Wanted behavior
A lock icon should be added in front of the name of a meeting to make closed meetings recognizable. The size of the symbol should be based on the font size of the meeting name. The lock icon should be similar to the one used in the calendar.

The link should additionally have the same colour as the groups if the admin cannot enter the meeting

The icon should be in front of the meeting name the icon should be black

Added an additional behavior


ak.wwise.core.object.copy returns WwiseObjectInfo with an invalid path and type

	def copy(self, obj: GUID | tuple[EObjectType, Name] | ProjectPath,
	         parent: GUID | tuple[EObjectType, Name] | ProjectPath,
	         name_conflict_strategy: ENameConflictStrategy = ENameConflictStrategy.FAIL,
	         version_control_auto_checkout: bool = True,
	         version_control_auto_add: bool = True) -> WwiseObjectInfo | None:
		"""
		https://www.audiokinetic.com/en/library/edge/?source=SDK&id=ak_wwise_core_object_copy.html
		Copies an object to the given parent. Note that if a Work Unit is copied, the operation cannot be
		undone and the project will be saved.
		:param obj: The GUID, type and name, or project path of the object to copy.
		:param parent: The GUID, type and name, or project path of the new object's parent.
		:param name_conflict_strategy: The strategy to use in case of a name conflict.
		:param version_control_auto_checkout: Determines if Wwise automatically performs a Checkout source control
											  operation for affected work units and for the project.
		:param version_control_auto_add: Determines if Wwise automatically performs an Add source control operation for
										 affected work units.
		:return: The new object as a WwiseObjectInfo, or None if the operation failed. **Note**: path and type are not
				 available at the time of creation, so the returned WwiseObjectInfo will have an invalid path and an invalid
		"""
		args = {"object": f"{obj[0].get_type_name()}:{obj[1]}" if isinstance(obj, tuple) else obj,
		        "parent": f"{parent[0].get_type_name()}:{parent[1]}" if isinstance(parent, tuple) else parent,
		        "onNameConflict": name_conflict_strategy,
		        "autoCheckOutToSourceControl": version_control_auto_checkout,
		        "autoAddToSourceControl": version_control_auto_add}
		options = {"return": EReturnOptions.get_defaults()}  # AK docs say this should work, but it doesn't
		results = self._client.call("ak.wwise.core.object.copy", args, options=options)  # missing options
		return WwiseObjectInfo.from_dict(results["object"])  # path and type are invalid here

See comments in code. The results dict (returned from ak.wwise.core.object.copy) only has id and name. It seems to be ignoring the return options (options).

I might have a solution for this one. Not optimal, but calling ak.wwise.core.object.get to fetch the missing data might do the trick.

I might have a solution for this one. Not optimal, but calling ak.wwise.core.object.get to fetch the missing data might do the trick.

Yup, that worked! Would be ideal to avoid chaining API calls like that - but, well, it works!


[Feature] inject Python agent automatically in SWCK

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Since https://github.com/apache/skywalking-python/pull/159 is merged, we have Docker image for SkyWalking Python agent and non-intrusive way to install the agent, it would be perfect if we can also enhance SWCK to make it possible to inject the Python agent automatically when Kubernetes annotation is specified.
Use case
When users label a Kubernetes Pod with a special annotation, for example, swck-java-agent-injected=true, SWCK can automatically inject the Python agent to the application Pod, hence the users don't even need to modify their Docker image.
Related issues
Java agent injector: https://github.com/apache/skywalking-swck/pull/30
https://github.com/apache/skywalking-python/pull/159
https://github.com/apache/skywalking/issues/7461
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Superskyyy FYI 😉

Do I wait the Java PR to be ready first? In case something can be reused. Looks like a very big feature there base on the LOC.

@hanahmily Please confirm tye statue of that PR.

@Superskyyy FYI https://github.com/apache/skywalking-swck/pull/30 is merged

@Superskyyy FYI apache/skywalking-swck#30 is merged

Okay, my turn then.

@Superskyyy Could you try to finish this? I hope we could move forward 1.0 soon.

@Superskyyy Could you try to finish this? I hope we could move forward 1.0 soon.

@wu-sheng I would try my best to proceed soon, so that hopefully we could go to 1.0.0 in early March. Sorry for the delays, I had to focus on my graduate research on service mesh recently.

Service Mesh is good to learn :)

Hi @Superskyyy , @fgksgf is interested in this issue and he has enough available time recently so I just suggested him to take a look at this. Please comment here if you've already started, in case.

Hello! Actually, I already started implementing this one last week, I was planning to finish it this month and go for the 1.0.0 milestone. Can we see if there's another work that is suitable for @fgksgf?

Hi @Superskyyy , @fgksgf is interested in this issue and he has enough available time recently so I just suggested him to take a look at this. Please comment here if you've already started, in case.

Hello! Actually, I already started implementing this one last week, I was planning to finish it this month and go for the 1.0.0 milestone. Can we see if there's another work that is suitable for @fgksgf?

Ok, good luck :)

@Superskyyy @dashanji Is anyone planning to do this? It is stable for years.

@Superskyyy @dashanji Is anyone planning to do this? It is stable for years.

@rabajaj0509 is interested in this and may work on this after he finishes the GSoC program

@Superskyyy @dashanji Is anyone planning to do this? It is stable for years.

@rabajaj0509 is interested in this and may work on this after he finishes the GSoC program

Lets hand it to Rahul :), things are out of hand for me currently.

Yes, I will start working on this next week.

Yes, I will start working on this next week.

Thanks man!

Looking into this one now.

Looking into this one now.

Hi @rabajaj0509, thanks for the interest. FYI, https://github.com/apache/skywalking-swck/blob/master/docs/how-to-add-new-crd-and-controller.md


Can't upload large files

I'm not able to upload large files. Ddrive works very good with low file sizes but when i try to upload files more than 250 mb i'm facing an error:

I tried increasing the timeout.
I tried uploading different files.
My network speed:

It seems because of your upload speed, What timeout time have you tested?

I have the same problem, can't upload 1GB+ files. I set all available timeout values, but it has no effect.

I have had success uploading 5gb+ files, but my upload speed is also gigabit.

Issue solved. My NodeJS was v18 so i uninstalled it and installed v16 now its working with every file size.

It seems because of your upload speed, What timeout time have you tested?

anybody know how to change the timeout value? tried setting an env variable with no luck. I see the API usage in the readme but no idea where that code goes


when i function deploy in visual code Service Unavailable

Repro steps:1.2.Action: azureFunctions.deployError type: 503Error Message: Service UnavailableVersion: 0.16.0OS: win32VS Code Version: 1.33.1Call Stack```module.exports.s.pipeline (C:/Users/Kevit dist/extension.bundle.js:333:833828)s (C:/Users/Kevit dist/extension.bundle.js:277:110820)s (C:/Users/Kevit dist/extension.bundle.js:165:25754)C:/Users/Kevit dist/extension.bundle.js:165:26994o (C:/Users/Kevit dist/extension.bundle.js:223:7055)C:/Users/Kevit dist/extension.bundle.js:165:24675$.module.exports.t.requestLibrarySink.t.headersOnly.t.streamedResponse.t.body.function.t.body.pipe.a [as _callback] (C:/Users/Kevit dist/extension.bundle.js:1:579051)$.module.exports.$.init.t._callback.t.callback.t.callback (C:/Users/Kevit dist/extension.bundle.js:253:5461)$.emit (events.js:182:13)$. (C:/Users/Kevit dist/extension.bundle.js:253:18274)$.emit (events.js:187:15)IncomingMessage. (C:/Users/Kevit dist/extension.bundle.js:253:17116)Object.onceWrapper (events.js:273:13)IncomingMessage.emit (events.js:187:15)endReadableNT (_stream_readable.js:1090:12)process._tickCallback (internal/process/next_tick.js:63:19)```

@piyushkacha7 can you add some detailed repro steps to this issue? Also - "Service Unavailable" will sometimes happen and there's not much we can do about it in the VS Code extension. If it's persistent definitely let us know, but otherwise try deploying again and hopefully that will resolve the issue.

@EricJizbaMSFT I created my resource group from the Azure portal also created an azure function application form portal because of VS code don't support to change the default hosting plan.
so first I create an app in the portal and try to deploy from VS code then give me this kind of error
and currently I don't see my Streaming log in VC code.

What type of function app did you create in the portal?

What runtime?
What region?
What kind of app service plan (Consumption vs. Dedicated)?

Do you have full permissions to that function app?

I'm using Following:
Runtime: Linux
Region: Central US
App service plan: Dedicated
Also, I'm not able to connect to log streaming service and see the logs that I've done using context.log() function. Also, not able to connect to the log streaming service using VS Code.

Okay I can't repro "Service Unavailable", but I can repro the fact that streaming logs doesn't work for a linux dedicated plan. Updating title to reflect that.
As a workaround, you should be able to stream logs here:
https://<insert site name>.scm.azurewebsites.net/api/logstream
In general, this site just lets you view a lot more logs and advanced tools:
https://<insert site name>.scm.azurewebsites.net

Hello Mr.Eric Jizba, I want to know how much time for this issue slove? because we need to see all the log of our azure function as soon as possible.

@piyushkacha7 did you try going to the site I mentioned? You should be able to see log stream either in that site or in the portal. I don't have an estimate for when we fix this is VS Code, but I'm hoping you're not blocked since you should be able to see the logs there.

@EricJizbaMSFT
yes, I can see log https://.scm.azurewebsites.net/api/logstream but in this only log like info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2] 2019-06-12T05:21:13.800889850Z: [INFO]        Request finished in 357.8865ms 200 application/json; charset=utf-8 request success or request failed.
we are a developer so need see log if any request failed then failed log error need to see.
any proper way for I can see my full logs? in the above site only display logs like success or failure. but I need to see debug logs. before stopping the VS Code stream its display fully logs so it's easy to debug application error.
 context.log('HTTP trigger function processed a request.');  context.log.error(Exception);  context.log.error(error);
I need to see these logs live tracking. it's easy to debug me.
So any other way to see my fully debug and error logs?

@piyushkacha7 the best I can do from VS Code is replicate the experience you see in that site. That's my plan to fix this issue.
If you want to see your console logs you would have to file an issue directly with the Azure Functions team. See here for more info: https://github.com/Azure/azure-functions#questions--help


Use (loaded) event with *ngFor

From @EricRobertBrewer on January 20, 2017 0:13
Did you verify this is a real problem by searching Stack Overflow and the other open issues in this repo?
Yes
Tell us about the problem
Given a UI element with an *ngFor directive, can we use the properties of each *ngFor iteration in the (loaded) event of that element, or one of its child elements? Like this:
<DockLayout *ngFor="let item of currentItems">

</DockLayout>

with this:
onItemLabelLoaded(event, id: number) {
    console.log("Loaded item: "+id);
    // call a function here using 'id'
}

Currently, I get an error which tells me that properties of the item cannot be used as the point where onItemLabelLoaded() is called.
JavaScript error:
file:///app/tns_modules/rxjs/Subscriber.js:227:22: JS ERROR Error: Error in app.component.html:6:8 caused by: null is not an object (evaluating 'self.context.$implicit.id')

Which platform(s) does your issue occur on?
Both
Please provide the following version numbers that your issue occurs with:

CLI: 2.4.2
Cross-platform modules: "tns-core-modules": 2.4.4
Runtime(s): tns-android: 2.4.1, tns-ios: 2.4.0

Please tell us how to recreate the issue in as much detail as possible.
Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
app.component.html:
<ActionBar>
    <ActionItem text="Mix" (tap)="onMixTapped($event)" ios.position="right" android.position="actionBarIfRoom">
    </ActionItem>
</ActionBar>
<StackLayout>
    <DockLayout *ngFor="let item of currentItems">

    </DockLayout>
</StackLayout>

app.component.ts:
import { Component, OnInit } from "@angular/core";

@Component({
    selector: "my-app",
    templateUrl: "app.component.html",
})
export class AppComponent implements OnInit {

    allItems: Array<Item>;
    currentItems: Array<Item> = [];

    ngOnInit() {
        this.allItems = [];
        for (let i = 0; i < 8; i++) {
            let item = { id: i };
            this.allItems.push(item);
        }
    }

    /** Make a random subset of `allItems` */
    onMixTapped(event) {
        this.currentItems = [];
        for (let i = 0; i < this.allItems.length; i++) {
            let random = AppComponent.nextInt(2) + 1;
            if (random === 1) {
                this.currentItems.push(this.allItems[i]);
            }
        }
    }

    onItemLabelLoaded(event, id: number) {
        console.log("Loaded item: "+id);
        // call a function here using 'id'
    }

    static nextInt(range: number): number {
        return Math.floor(Math.random() * range);
    }
}

class Item {
    id: number;
}

Copied from original issue: NativeScript/NativeScript#3508

Hi @EricRobertBrewer,
It is possible to use loaded event with angular *ngFor directive. In your case you could use element get method, which will help you to get the id of the component. For your convenience I am attaching sample code, where this scenario has been shown.
HTML
<ScrollView sdkExampleTitle sdkToggleNavButton>
    <StackLayout class="list-group">

        <StackLayout *ngFor="let fruit of fruitList" class="list-group-item">

        </StackLayout>

    </StackLayout>
</ScrollView>

TypeScript
import { Component } from "@angular/core";

// >> ngfor-bind-items-code
@Component({
    moduleId: module.id,
    templateUrl: "./ngfor-directive.component.html",
})
export class NgForComponent {
    public fruitList: Array<any> = [];

    constructor() {
    }
    ngOnInit(){
        this.fruitList= [
            {name:"Apple", id:1},
            {name:"Apricot", id:2},
            {name:"Avocado", id:3},
            {name:"Banana", id:4},
            {name:"Bilberry", id:5},
            {name:"Blackberry", id:6}
        ];
    }

    public labelLoaded(args){
        console.log("is label");
        console.log(args.object.get("id"));
    }
}

For further help you could also review the samples here.
Regards,
@tsonevn

I made the following changes to my app:

and
public onItemLabelLoaded(event) {
    console.log("Loaded item: "+event.object.get("id"));
    // call a function here using 'id'
}

I still get the following result on iOS and Android:
JS: Loaded item: undefined
JS: Loaded item: undefined
JS: Loaded item: undefined

The strange thing is that when I change my function to the following:
public onItemLabelLoaded(event) {
    console.log("Loaded item: "+event.object.get("id"));
    setTimeout(() => {
        console.log("Loaded item after 10 ms:"+event.object.get("id"));
    }, 10);
    // call a function here using 'id'
}

I get this:
JS: Loaded item: undefined
JS: Loaded item: undefined
JS: Loaded item: undefined
JS: Loaded item after 10 ms:5
JS: Loaded item after 10 ms:6
JS: Loaded item after 10 ms:7

Is there any way to use the (loaded) function WITHOUT using setTimeout?

Repository is here.

@EricRobertBrewer handling items from ngFor is not a trivial job and indeed the loaded event in your case would work after all elements are loaded which might not be what you need.
You can use eventEmitter - more about it here and here.


False positive breaking-changes when moving a param from endpoint to path level

Describe the bug
Comparing two specs with a parameter moved from endpoint level to path level produces wrong errors.
See also https://github.com/Tufin/oasdiff/pull/376#discussion_r1327364537
To Reproduce
Steps to reproduce the behavior:

Run oasdiff changelog base.yaml revision.yaml
With specs below
Receive:

2 changes: 1 error, 1 warning, 0 info
error	[new-required-request-default-parameter-to-existing-path] at data/request_params/required-request-params.yaml
	in API GET /api/test5
		added the new required 'query' request parameter 'emptyPath2' to all path's operations

warning	[request-parameter-removed] at data/request_params/required-request-params.yaml
	in API GET /api/test5
		deleted the 'query' request parameter 'emptyPath2'

Expected behavior
No errors
Base spec:
openapi: 3.0.1
info:
  title: Test API
  version: v1
paths:
  /api/test:
    get:
      operationId: getTest
      parameters:
        - in: query
          name: emptyPath2
          required: true
          schema:
            type: string

Revised spec:
openapi: 3.0.1
info:
  title: Test API
  version: v1
paths:
  /api/test:
    parameters:
      - in: query
        name: emptyPath2
        required: true
        schema:
          type: string
    get:
      operationId: getTest

Fixed by https://github.com/Tufin/oasdiff/pull/479


Decomposed relative position embedding in attention layer of ImageEncoder

I am looking for more information on why this is added in the attention layer of the image encoder, I understand it acts as a residual connection to the original positional embeddings but I can't find mentions of it in the paper, has any ablation been conducted of its effect on VITs? Has in been studied in another publication?

Up

I am looking for more information on why this is added in the attention layer of the image encoder, I understand it acts as a residual connection to the original positional embeddings but I can't find mentions of it in the paper, has any ablation been conducted of its effect on VITs? Has in been studied in another publication?

From the code comments, the relative positional embedding is proposed in paper 'MViTv2: Improved Multiscale Vision Transformers for Classification and Detection'


feat(RHTAPWATCH-777): add snapshotgc to image

Modify the dockerfile so that snapshotgc is built and included inside the container image
Maintainers will complete the following section

[ ] Commit messages are descriptive enough (hints)
[ ] Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
[ ] Controllers diagrams are updated when PR changes controllers code  (if applicable)

@MartinBasti This one changes the dockerfile to have the image contain the gc code. Please take a look.


Optimize slow path

Currently if neither AES or FoldedMultiply is available the slow path involves 5 multiplies for short inputs. It should be theoretically possible to reduce this to 3. An alternative update function is needed. Ideally a quality sacrifice should not be needed and smhasher should still pass.

Fixed in https://github.com/tkaitchuck/aHash/commit/a8267e3d8215ca15752c13a58f004dad9f8d992e


The PHP-8.0.0 does not have the version info

Output
module folder

httpd.conf

Expected Result
The binary should named with version libphp8.0.0.so
Command
phpbrew --debug install --jobs "$(nproc)" 8.0.0 +default +dbs +dba +apxs2 +ftp +soap +gettext +exif +iconv +intl +bz2 +zlib

Platform
OS:
macOS 10.15.7

Running PHP:
PHP-7.4.12

Installing PHP:
PHP-8.0.0

===> Checking patches...
Checking patch for replace apache php module name with custom version name
0 changes patched.

Likely because of there's no patch for that.

I think it can rename the libphp.so to libphp8.0.0.so manually and it can make them identified with manual way.

It better managed by phpbrew as it used to be.

You're right. It seems that the patch parser for Apache2 module should be updated for parsing PHP 8.x patches.

After digging the configure file that generated by buildconf from PHP source, the PHP-7.4 configure file is different from PHP-8.
Here the steps I use to notice above situation:

Prepare the Ubuntu 20.04 or other distributions that can run the autoconf command.
Install the autoconf command. Running the sudo apt-get install autoconf in Ubuntu 20.04.
Running the cd ~/ to change directory to the user home directory.
Download the PHP-7.4 source archive file with wget https://www.php.net/distributions/php-7.4.29.tar.gz.
Running the tar -xzf php-7.4.29.tar.gz to extract the archived gzip file.
Download the PHP-8.0.19 source archive file with wget https://www.php.net/distributions/php-8.0.19.tar.gz.
Running the tar -xzf php-8.0.19.tar.gz to extract the archived gzip file.
Running the cd php-7.4.29 then running the ./buildconf --force to regenerate the configure file.
Running the cd php-8.0.19 then running the ./buildconf --force to regenerate the configure file.

We can see that related libphp.so variable defined in the line 6270, 6271 and 6272 of ~/php-7.4.29/configure:
......
 SAPI_SHARED=libs/libphp$PHP_MAJOR_VERSION.$SHLIB_DL_SUFFIX_NAME
 SAPI_STATIC=libs/libphp$PHP_MAJOR_VERSION.a
 SAPI_LIBTOOL=libphp$PHP_MAJOR_VERSION.la
......

We can see that related libphp.so variable defined in the line 6256, 6257 and 6258 of ~/php-8.0.19/configure:
.....
SAPI_SHARED=libs/libphp.$SHLIB_DL_SUFFIX_NAME
SAPI_STATIC=libs/libphp.a
SAPI_LIBTOOL=libphp.la
......

I also see that the PHP_MAJOR_VERSION pattern is not found in ~/php-8.0.19/build/Makefile.global file.
That's the reason why the patch parser for Apache2 will not find any version info for the PHP-8.x because the file contents are changed.
@markwu, do have find any version info about libphp.so in PHP-8.x version?

I've created the PR #1265 to fix this issue :).

This issue is resolved by PR #1265.


.get() attempting to grab from home dir (Linux)

OS: Debian GNU/Linux 11 (bullseye) aarch64
Bug: .get() (specifically when using robotx.txt) trys to grab /home/xxxxx/microwavebot-webrobots.txt (I presume due to the folder name)
Code snippet:
app.get("/robots.txt", function (req, res) {
  res.sendFile(__dirname + "robots.txt");
});

Expected result: It grabs robots.txt from the current directory
Actual result: it attemps to grab from the home directory of the user
Note: I am entirely unsure if this is due to something I did that I don't remember or my OS or maybe even an actual bug

__dirname does not have trailing slash, so your problem is the string concatenation.
You can use path.join, which will build a path from segments by inserting platform-specific directory separator between segments.
// const path = require("node:path");
app.get("/robots.txt", function (req, res) {
    res.sendFile(path.join(__dirname, "robots.txt"));
});

Yep, its a path construction issue.


Provide separate LICENSE file

Hello,
Is it possible to include a separate file with the license text? It makes redistributing amber easier for some projects (like in distros).
Thank you!

Just added, thanks.


Instagram "Null" Ripper?

Ripme version: 1.7.95 E621 Fix
Java version: openjdk version "1.8.0-262"
Operating system: Microsoft Windows [Version 10.0.19043.1348]
Exact URL you were trying to rip when the problem occurred: instagram.com/instagram (whatever)

Expected Behavior
Should download instagram images normally.
Actual Behavior
Was shouting out a "Null" Error.
See; https://sketchys.de/s/i2bSSjAxKTGoi3J

Getting this same issue on Mac: 1.7.95, java 1.8.0_302, Monterey 12.1. Any VSCO URL returns error: null.

Please provide example link


Typo in documentation

Just to declare a small typo in the documentation, in the "Usage" section there is a hyphen missing in the property name
"quarkus.ngrok.authtoken" -> "quarkus.ngrok.auth-token".
However, a message informs us that the application can't find the property, which puts us on the right track.
And above all, thank you for your contributions

Why not!
I'll have a look at the contribution guide

Thanks for the fix!

@all-contributors add @zakhdar for docs


For calibrate_model, by default use random initial guess?

Would it make sense to, for calibrate_model, if an initial parameter guess (p0) is not provided, simply randomly select one from within the bounds (and priors) of the parameters? It feels like this will typically be a random value, in which case providing functionality for it might be good.

Hmm, I am against this, as I would like calibrate_model to mimic most available optimizers that all require a start-guess to be generated.
But it would be nice to to have functionality for start-guesses, so maybe a good solution would be to export the generate_startguesses function, and make it return a vector in case the user only wants 1 start-guess?

Consistency is probably best here, and a generate_startguesses should serve the same purpose as well.


Corrected Grammar in Found a Bug Section

Changed 'have confirmed that someone else facing the same issue' in the Found a Bug section to 'have confirmed that someone else is facing the same issue'.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@Scriptle Congratulations on your first merged pull request to this project. Thanks for catching this typo and fixing it!


Update travis to add OOI Credentials

Overview
This PR adds OOI_USERNAME and OOI_TOKEN variables.

Pull Request Test Coverage Report for Build 188

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

Totals

Change from base Build 187:
0.0%

Covered Lines:
366

Relevant Lines:
874

💛  - Coveralls


Migrate to GitHub Actions

Migrate current CircleCI Workflows to GitHub Actions.
Quip Documentation: https://alteryx.quip.com/3k39OY4VPQGu/GitHub-Actions

Before we close this, let's make sure we've updated release.md to link to github actions instead of circleci.

Notes from discussion about codecov with @ParthivNaresh :

Always upload codecov, even if any of the linux unit tests fail.
Verify that if there is a coverage decrease, the "coverage" github check on the PR fails.
Always run both of the linux 3.8 jobs (with/without core deps flag), because our coverage needs both. Otherwise, if even one test fails, one of the two jobs will not run, and coverage will look much worse than it really is. Fine to file this separately.

@ParthivNaresh what work is left in order to close this epic? This was what I remembered:

build_conda_pkg tracked by #1824
codecov -- if there is still work needed for this, and there isn't already a PR in flight, please file an issue and attach it to this epic so we can track.

@dsherry I had filed #1911 previously, added it to the Epic now!

@ParthivNaresh I believe we are all set here! You wanna close this epic? 😁


Add message about just kicked user

For some reason, the built-in message is not shown in the VLDC chat

This message already writes into "admin actions" tab in the Chat settings


Set up test scenarios for basic unauthenticated LDP

In https://github.com/RubenVerborgh/Solid-World-September-2020/blob/master/scenario/steps.sh


Using require for Token preconditions

Using require at the beginning of the function to check preconditions.

Thank you @phiferd! 😄


fix #11 closing bracket conditional for c++

fix ble_hs_pvcy.h c++ closing  bracket.

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

@marcogmaia Thank you for fix. LGTM

Hi @marcogmaia Could you please also add header guards at the start of the file ?
#ifndef H_BLE_HS_PVCY_
#define H_BLE_HS_PVCY_

Of course, corresponding #endif at the end as well ?

sure, when I get home I'll do it

@prasad-alatkar All done. :)

LGTM. @dhrishi PTAL

@marcogmaia Thanks for the PR. This looks good!

sry for closing/reopenning, I clicked "close" in the app thinking it would close the dialog


Update powered_by.yml

Updated directly in https://github.com/facebook/infer/commit/cb257aa3b31e9874b4795c38a7a475b376980cb7 for simplicity


fix: dependencies that require contextvars being broken by BaseHTTPMiddleware

…ddleware

Codecov Report

Merging #72 (a51fed0) into main (8bd2473) will decrease coverage by 0.09%.
The diff coverage is 93.90%.

@@            Coverage Diff             @@
##             main      #72      +/-   ##
==========================================
- Coverage   98.06%   97.97%   -0.10%
==========================================
  Files         139      140       +1
  Lines        4440     4484      +44
  Branches      718      726       +8
==========================================
+ Hits         4354     4393      +39
- Misses         43       46       +3
- Partials       43       45       +2

Impacted Files
Coverage Δ

xpresso/routing/websockets.py
85.71% <75.00%> (-5.96%)
:arrow_down:

xpresso/routing/operation.py
96.87% <85.71%> (-3.13%)
:arrow_down:

xpresso/applications.py
96.09% <92.30%> (-0.79%)
:arrow_down:

tests/test_dependency_contextvars.py
100.00% <100.00%> (ø)

xpresso/_utils/asgi.py
100.00% <100.00%> (ø)

xpresso/middleware/exceptions.py
83.87% <100.00%> (+8.00%)
:arrow_up:

xpresso/responses.py
100.00% <100.00%> (ø)

tests/test_docs/advanced/test_websockets.py
92.00% <0.00%> (-8.00%)
:arrow_down:


Make JcePublicKeyDataDecryptorFactoryBuilder support Non-NIST Curves

Hi,
I just tried to decrypt PGP content with a brainpool curve (btw encryption works fine) and got an NullPointer in JcePublicKeyDataDecryptorFactoryBuilder.decryptSessionData. Problem is that decryptSessionData assumes that the presented curve is a NISTNamedCurves (line 140):
X9ECParameters x9Params = NISTNamedCurves.getByOID(ecKey.getCurveOID());
therefore in line 153 a NullPointer is thrown since x9Params is null
ECPoint publicPoint = x9Params.getCurve().decodePoint(pEnc);
I fixed this by changing the the decryptSessionData method to
PublicKeyPacket pubKeyData = privKey.getPublicKeyPacket();
ECDHPublicBCPGKey ecKey = (ECDHPublicBCPGKey) pubKeyData.getKey();
ECCurve curve = null;
String name = ECNamedCurveTable.getName(ecKey.getCurveOID());
if (name != null) {
ECNamedCurveParameterSpec spec = ECNamedCurveTable.getParameterSpec(name);
if (spec != null) curve = spec.getCurve();
}
if (curve == null) {
	throw new PGPException("Unknown ECC Curve with OID " + ecKey.getCurveOID());
}
byte[] enc = secKeyData[0];
int pLen = ((((enc[0] & 0xff) << 8) + (enc[1] & 0xff)) + 7) / 8;
byte[] pEnc = new byte[pLen];
System.arraycopy(enc, 2, pEnc, 0, pLen);
byte[] keyEnc = new byte[enc[pLen + 2]];
System.arraycopy(enc, 2 + pLen + 1, keyEnc, 0, keyEnc.length);
ECPoint publicPoint = curve.decodePoint(pEnc);
could you please consider such a fix for one of the next releases?
regards
stefan

Resolved as part of #369


feat: allow extensions

Closes #41
Allows to provide extensions to the code mirror instance via props. One use case is to add line numbers.
Example from the popup editor spike (https://github.com/bpmn-io/form-js/pull/708)
import { lineNumbers } from '@codemirror/view';

const editor = new FeelEditor({
  container: inputRef.current,
  /* ... */
  extensions: [
    lineNumbers()
  ]
});

Sorry for that; I forgot to push the test case.


Cannot delete a field with relation to scalar (simple type) array.

@tomitrescak commented on Wed Jul 11 2018
Hi, asked this question as well in the forum, but to me this seems as a bug.
I have a type with a string array field
type Notification {
  id: ID
  params: [String!]!
}

Prisma generates the Notification_params table.
I have an issue deleting notification as I am receiving server error:
DELETE FROM "default$default"."Notification" as "Alias" WHERE TRUE
update or delete on table "Notification" violates foreign key constraint "Notification_params_nodeId_fkey" on table "Notification_params"
Now, there is no exposed function to delete something from Notification_params table
Nor, I can use Cascading delete relation.

Shouldn't these array fields be deleted automatically? Any help is greatly appreciated. If you answer here I will lint the answer in forum to this post.

Thanks for bringing this up, @tomitrescak.
Can you share additional information according to the bug report template?
In particular, your Prisma server version, as well as the mutation that results in that error.
Thanks!

Describe the bug
Description above
To Reproduce
Steps to reproduce the behavior:

Insert a new notification in the system with some parameters
Try to delete the notification
Error appears in the Postgre database

**Expected behavior**
The related array would be deleted automatically.

**Versions (please complete the following information):**
 - OS X High Sierra
 - prisma/1.10.2
 - Prisma Server: Running in docker from latest image with PostgreSql
 - Using graphql-yoga: 1.14.12

Sorry and the code that deletes this is: db.mutation.deleteNotification({ where: { id } }) and id is part of the Mutation resolvers args.

It is definietly a bug in the Progres server ... I just used MySQL version and all works as expected.

Hey @tomitrescak, I am not able to reproduce this issue.
I used this datamodel:
type Notification {
  id: ID! @unique
  params: [String!]!
}

I used this JavaScript file:
const { Prisma } = require("prisma-binding");

const prisma = new Prisma({
  typeDefs: "./prisma.graphql",
  endpoint: "http://localhost:4466/r-2756/dev"
});

const id = 'cjjqsgtsd001z0980qcffws1x'
prisma.mutation.deleteNotification({ where: { id } })

The Notification node and Notification_params was correctly deleted.
I used Postgres and Prisma 1.12.
Did you use the verbatim datamodel you shared in the initial issue? The error message refers to a FK on nodeId which does not exist in this datamode.

Hi, my model is a bit more complex then that, I thought this minimal example would help.
#import BpmnProcessInstance from './bpmn_process_instance.graphql'
#import User from './user.graphql'

enum NotificationCode {
  ServiceStarted
  ServiceStopped
}

type BpmnProcessInstance {
  id: ID! @unique
}

type Notification {
  id: ID! @unique
  processInstance: BpmnProcessInstance
  code: NotificationCode
  text: Localisation
  params: [String!]!
  visible: Boolean
}

I'll investigate a bit more on a clean repo and post back.

It's not clear if the GraphQL file you shared is the datamodel, or the application schema.
The datamodel does not support import statements (see #1913).
Thanks for looking into a detailed repo 🙏

Hi, let me investigate, as after I switched to MySQL I did not go back to. Progress.

Interesting. I just had the same issue.
My docker-compose:
 ...
 prisma:
    image: prismagraphql/prisma:1.8
    depends_on:
      - postgres
    restart: always
    ports:
      - "4466:4466"
    environment:
      PRISMA_CONFIG: |
        port: 4466
        databases:
          default:
            connector: postgres
            host: postgres
            port: 5432
            user: ***
            password: ***
            migrations: true
  postgres:
    image: postgres
    restart: always
    ports:
      - 5432:5432
    environment:
      POSTGRES_USER: ***
      POSTGRES_PASSWORD: ***

But it is weird as I have other tables where scalar arrays are deleted just fine. As a workaround I update the entity just before delation. So something like this:
const where = { id }
// This sets the array to [], which I assume does the deletion of the linked table
await ctx.db.mutation.updateEntity({
      where,
      data: { problematicField: { set: [] } },
    })
// This deletes the main table and because of the previous step there is no fk constraint issue
await ctx.db.mutation.deleteEntity({ where })