<EMAIL_ADDRESS>decompress error

Logs
7-Zip 22.01 (x64) : Copyright (c) 1999-2022 Igor Pavlov : 2022-07-15

Scanning the drive for archives:
1 file, 362964741 bytes (347 MiB)

Extracting archive: C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable.7z
--
Path = C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable.7z
Type = 7z
Physical Size = 362964741
Headers Size = 17649
Method = LZMA:26
Solid = +
Blocks = 1

Sub items Errors: 187

Archives with Errors: 1

Sub items Errors: 187
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.compiler\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.datatransfer\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.desktop\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.instrument\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.logging\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.management.rmi\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.management\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.naming\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.net.http\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.prefs\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.rmi\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.scripting\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.security.jgss\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.security.sasl\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.smartcardio\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.sql.rowset\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.sql\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.transaction.xa\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.xml.crypto\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.xml\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.accessibility\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.attach\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.charsets\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.compiler\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.crypto.cryptoki\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.crypto.ec\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.dynalink\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.editpad\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.httpserver\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.incubator.foreign\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.incubator.jpackage\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.ed\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.jvmstat\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.le\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.opt\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.vm.compiler.management\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jartool\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.javadoc\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jconsole\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdeps\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdi\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdwp.agent\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jfr\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jlink\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jshell\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jsobject\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jstatd\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.localedata\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management.agent\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management.jfr\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.naming.dns\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.naming.rmi\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.net\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.nio.mapmode\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.sctp\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.security.auth\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.security.jgss\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.unsupported.desktop\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.unsupported\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.xml.dom\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.zipfs\ADDITIONAL_LICENSE_INFO
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.compiler\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.datatransfer\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.desktop\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.instrument\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.logging\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.management.rmi\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.management\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.naming\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.net.http\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.prefs\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.rmi\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.scripting\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.security.jgss\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.security.sasl\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.smartcardio\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.sql.rowset\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.sql\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.transaction.xa\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.xml.crypto\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.xml\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.accessibility\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.attach\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.charsets\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.compiler\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.crypto.cryptoki\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.crypto.ec\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.dynalink\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.editpad\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.httpserver\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.incubator.foreign\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.incubator.jpackage\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.ed\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.jvmstat\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.le\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.opt\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.vm.compiler.management\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jartool\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.javadoc\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jconsole\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdeps\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdi\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdwp.agent\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jfr\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jlink\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jshell\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jsobject\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jstatd\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.localedata\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management.agent\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management.jfr\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.naming.dns\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.naming.rmi\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.net\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.nio.mapmode\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.sctp\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.security.auth\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.security.jgss\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.unsupported.desktop\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.unsupported\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.xml.dom\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.zipfs\ASSEMBLY_EXCEPTION
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.compiler\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.datatransfer\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.desktop\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.instrument\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.logging\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.management.rmi\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.management\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.naming\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.net.http\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.prefs\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.rmi\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.scripting\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.security.jgss\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.security.sasl\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.smartcardio\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.sql.rowset\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.sql\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.transaction.xa\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.xml.crypto\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\java.xml\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.accessibility\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.attach\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.charsets\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.compiler\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.crypto.cryptoki\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.crypto.ec\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.dynalink\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.editpad\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.httpserver\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.incubator.foreign\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.incubator.jpackage\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.ed\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.jvmstat\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.le\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.opt\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.internal.vm.compiler.management\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jartool\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.javadoc\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jconsole\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdeps\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdi\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jdwp.agent\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jfr\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jlink\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jshell\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jsobject\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.jstatd\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.localedata\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management.agent\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management.jfr\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.management\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.naming.dns\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.naming.rmi\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.net\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.nio.mapmode\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.sctp\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.security.auth\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.security.jgss\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.unsupported.desktop\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.unsupported\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.xml.dom\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.zipfs\LICENSE
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : C:\Users\myuser\scoop\apps\sweethome3d\7.1\SweetHome3D-7.1-portable\SweetHome3D-macosx.app\Contents\runtime\Contents\Home\legal\jdk.localedata\cldr.md

Try enabling developer mode.
Windows 10:
Settings => Update & Security => For Developers => Developer Mode
Windows 11:
Settings => Privacy & Security => For Developers => Developer Mode
❯ scoop install sweethome3d
Installing 'sweethome3d' (7.1) [64bit] from extras bucket
Loading SweetHome3D-7.1-portable.7z from cache
Checking hash of SweetHome3D-7.1-portable.7z ... ok.
Extracting SweetHome3D-7.1-portable.7z ... done.
Running pre_install script...
Linking ~\scoop\apps\sweethome3d\current => ~\scoop\apps\sweethome3d\7.1
Creating shim for 'SweetHome3D'.
Creating shortcut for Sweet Home 3D (SweetHome3D-windows-x64.exe)
Persisting data\preferences.xml
Persisting data\plugins
Persisting data\furniture
Persisting data\textures
'sweethome3d' (7.1) was installed successfully!


Patch 1

add GeometryCollection class

Thank you for your pull request. Geometry collection type can be a useful enhancement.
Please, check the getType method. Geometry Collection isn't a multi-polygon,
Your pull-request comes without tests. Feel free to complete it.


Geofence send without moving

When I leave my smartphone on a table,
Occasionally, outputs and zone entry is sent,
Before sending the log, should vérrifier if there is indeed information to send,
I propose to ask the exact location system (GPS) just before send to URL,
It happens every 30/40 minutes, the betterie should not be affected,
Thank you,
Merci,

Are you seeing entries without exists?
Have you tried making the geofence larger?
In fact this is all handled by Google play Location services on Android, we could however let the user tweak the parameters:
https://developer.android.com/training/location/geofencing.html

I think this is the mode "doze" from Android 6.0,
I deleted Locative of battery optimization,
And it seems to work better,
Thank you for your reply, I close the ticket


order & color ouput header fields by their categories.

As per rfc2616 section 4.2:

The order in which header fields with differing field names are received is not significant. However, it is “good practice” to send general-header fields first, followed by request-header or response-header fields, and ending with the entity-header fields.

Can httpie provide a switch to order & color the header fields by their categories. I think it would be a little feature for those HTTP protocol learners to distinguish different kind of headers at a glance.

@jkbrzt Can I work on this?


Setup core for unified pipelines.

This PR sets up the core services directory for unified pipelines. Do we just need to ship the azure-core package from this pipeline or do we need to support shipping others?

Can one of the admins verify this patch?

/azp run python - core - ci


Merge remote-tracking branch 'refs/remotes/OfficeDev/master'

Hi @baisao, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Seems to be an accidental submission, so closing.


FFmpeg is trying to connect to HDHomeRun on Port 443

Describe the bug
FFmpeg is trying to connect to HDHomeRun on Port 443
Server (please complete the following information):
Linux Docker
Threadfin Version: 1.1(14)
Threadfin Branch: Main
Threadfin is behind an Nginx Reverse Proxy over https on port 443. Not sure if this is related.
Xteve does work but, since Xteve didn't really support https the Nginx proxy worked by just redirecting http to https
To Reproduce
Steps to reproduce the behavior:
Set Buffer to FFmpeg and then try to start a stream. You will see these logs:
2024-06-02 10:49:24 [Threadfin] Streaming Status:       Channel: XXXX(Clients: 0)
2024-06-02 10:58:53 [Threadfin] Buffer:                 true [ffmpeg]
2024-06-02 10:58:53 [Threadfin] Buffer Size:            1024 KB
2024-06-02 10:58:53 [Threadfin] Channel Name:           XXXX
2024-06-02 10:58:53 [Threadfin] Client User-Agent:      VLC/3.0.20 LibVLC/3.0.20
2024-06-02 10:58:53 [Threadfin] Streaming Status:       Playlist: HDHomeRun - Tuner: 1 / 1
2024-06-02 10:58:53 [Threadfin] FFMPEG path:            /usr/bin/ffmpeg
2024-06-02 10:58:53 [Threadfin] Streaming URL:          https://192.168.x.xxx:443/auto/v4
2024-06-02 10:58:53 [Threadfin] FFMPEG:                 Processing data
2024-06-02 10:58:53 [Threadfin] Streaming Status:       Receive data from FFMPEG
2024-06-02 10:58:53 [Threadfin] FFMPEG log:             [tcp @ 0x55ee1d6d7440] Connection to tcp://192.168.x.xxx:443 failed: Connection refused
Expected behavior
Should be connecting to HDHomeRun over HTTP
Desktop (please complete the following information):
Windows - VLC

If you choose to use https then the whole end to end has to be https. Not a bug. This is by design

What a nonsensical design as HDHomeRun doesn't support https. Even if it did it wouldn't be on port 443 or 80 as even the standard http one is on port 5004. It is also not tcp:// but http://
Here is a log from xteve for example:
2024-06-02 11:46:48 [xTeVe] Streaming URL:          http://192.168.x.xxx:5004/auto/v3


Proposal: add setCookie & refreshCookie

This PR would revert the changes made to relog to a state where they worked (though they log the user out of all sessions)
It:

Deprecates cookieLogin
Adds function setCookie
Adds function refreshCookie
Reverts relog.js

setCookie
All setCookie does is store the provided cookie, and verify it (this is customisable through the novalidate argument)
It does not refresh the cookie.
refreshCookie
Refreshes either a given cookie or the interally stored cookie, stores the newly generated cookie and returns it. This then places the responsibility for storing the cookie on it's user.
This information will need to be put in docs & readme, of course.
Why?
See #114
cookieLogin was intended as a temporary fix and it's been in use since March 2018.
I would say it's bad because libraries having unintended effects like this (and of course the creation of a file) makes them more difficult to use and it wreaks havoc with services like Glitch or Heroku. This PR means that these services are supported, provided the user creates their own storage mechanism for the refreshed cookie.
Another improvement about this is that we don't know when cookies expire, so the user can decide that themselves. I've personally had a lot of problems because the cookie file is stored relative to the file that runs it, not the library itself - and the cookie file creates an inherent security issue with many users unwittingly uploading their cookie file.

Also closes #41 and #48  though they won't autoclose now


Fix init-deploy to use cert manager as issuer

Test name
Status

storage
passed

big-data
passed

haproxy
passed

scaling
passed

recreate
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

limits
failed

self-healing-advanced
passed

demand-backup
passed

operator-self-healing
failed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
failed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed


Change Get-ChildItem to list the content of a link to a directory on Unix. (#1958)

Fix #1958
Brings Get-ChildItem in line with ls command on Unix and with the PowerShell behavior on Windows when the link is a directory symbolic link.

@jeffbi Thanks for the fix! 👍


Drop JSON Schema draft-04 support

[x] exclusiveMaximum/Minimum as boolean
[x] id
[x] draft-04 meta-schema

in v7-alpha


deps: upgrade root devDependencies

Once https://github.com/FuelLabs/fuels-ts/issues/2035 is completed we will need to upgrade all the dependencies.

Blocked by https://github.com/FuelLabs/fuels-ts/pull/2158

I'll address #2195 first due to linting issues that will happen during the upgrade

This PR was a bit ambiguous in it's goal, I've changed it to just upgrading turbo for now


NDRS-913: Push whole block to the event stream.

https://casperlabs.atlassian.net/browse/NDRS-913
https://github.com/CasperLabs/casper-node/pull/892 moved deploy_hashes, transfer_hashes and proposer from the BlockHeader structure to the new BlockBody. Up until now, we've been pushing only BlockHeader to the event stream, which means that since #892 got merged those three were missing from the event stream events. This PR changes what gets pushed to the event stream – we're now pushing the whole Block.
The main differences are in the structure of the event. Instead of block_header field containing BlockHeader structure, there's now a block field with Block struct. Structure of the Block can be found here.

bors merge


PIXI.Bounds is missing

It looks like the export for PIXI.Bounds is missing. I'm getting a PIXI.Bounds is not a constructor error when I try to create one.
Using v4.2.2

@OSUblake thanks for pointing this out. Looks like when we reorganized some of the code in 4.1, we neglected to expose Bounds again. I submitted a PR to fix.


Windows Version

Ack, I'll add that - it will require configuration in the service configuration file for the service name and such and will only work with command line programs.


Create LICENSE

The project was missing a license information, I have created a license file with Apache License (the safe and reasonable default)

What about going with Public Domain licence ? http://choosealicense.com/licenses/unlicense/

If you want to be as permissive as possible then it's a good choice.
MIT License: http://choosealicense.com/licenses/mit/ is basically the same as public domain, but you have to keep name of the original author, and this makes it very popular as well.


32/add verbosity switch

Adds verbosity environmental variable to silence output
[Fixes #32]
Thanks for writing this gem :)! I'm looking forward to using it as I branch out
into more generative testing.
PR can be utilized as follows:
Use RANTLY_VERBOSE=0 to silence output during tests.
Use RANTLY_VERBOSE=1 (default value if env isn't set) to display output during tests.
Allows users to silence output, if they wish.
PS - sorry the trailing whitespace commits ended up in this PR. I meant to submit them separately. If you'd like me to split them out, please let me know :smile_cat:.

Coverage decreased (-0.02%) when pulling<PHONE_NUMBER>7d7ad6121b551c168219ba392c0ab5 on zph:32/add_verbosity_switch into db76214c2039bafdf0ffe706513db87a7d076e24 on hayeah:master.


Mani.Zip

Hello, I have gone through this blog and it seems to be quite interesting but to my surprise I am not able to understand main.zip file as it is not uploaded in this repo. I mean from where main.zip is coming from ?
Thanks in advance .

hi @ypkalra, that is something I missed.
I updated the readme and I will also update the tutorial.
You need to run the following first:
pnpm run generate-assets -r

This comes from the local scripts in the workspace:

@function/ingestion - generate-assets script

generate-lambda-assets

This prepares the node_modules dependencies, run test and runs the build to create the zip

I hope this helps!


Printing a form

Is it possible to print a form?

Hmm I dont think this is strictly related to forge.forms, maybe search for something related to wpf itself? I'll check it out later

Check XML examples route in demo. I followed this article.

You probably need to fiddle with the settings but it's definitely possible. You could also add an Env flag print or something, such that when it's set you can hide buttons visible="!{Env printing}".

Thanks! @EdonGashi  I will give this a try

This works well


[Feature request]Rename pokemon to their IV

We should rename all pokemon to their IV

Duplicate
https://github.com/PokemonGoF/PokemonGo-Bot/issues/1679


add cut_flag, test completeness, etc.

This is a notebook from April/May 2021 when various tests were done on the completeness resulting from the various quality cuts applied to the Scylla data. This is also the notebook used to generate a vgst.fake output ASTs catalog which a cut_flag column where the catalog preserves all the original sources and designates those removed by the vgst cuts with a CUT_FLAG=1.
The results of the completeness tests are written up on the Scylla Notion Photometry page:
https://www.notion.so/Photometry-a6e18ca5ddf94f8fa8b82646337c5290
The notebook is in part based on the work which Yumi Choi did to test cuts on LUVIT data. It is a work in progress and needs to be cleaned up and summarized in a separate piece of code to generate vgst.fake catalogs with a CUT_FLAG column.

@cmurray-astro , I did not realize that I was approving a pull request for this notebook to the main Scylla-HST... :-|
Feel free to take a look, but this is the notebook I used to do all the visualizations and tests of the quality cuts on the Scylla data, some of it based on Yumi's work, and also the tests of the completeness based on the different cuts.
I am uploading it since Roger Cohen wanted to use it to generate vgst.phot catalogs with a CUT_FLAG for Scylla fields for which we have not yet generated these catalogs.
Ideally, I will summarize the code into a module so that upcoming catalogs can be easily generated with a CUT_FLAG column.

sounds great, Petia! thanks for uploading this -- will be extremely useful for all of us!


[ISSUE] Replace Zeebee gateway variable with correct Identity configuration properties

Related to "SUPPORT-20098"
Describe the issue:
In Zeebe 8.4.0,  the identity-spring-boot-autoconfigure  module was integrated, which provides an IdentityConfiguration Spring bean that we pass on to the identity-sdk instantiation in the Zeebe Gateway.

This means that the appropriate environment variables for the Identity configuration properties should be automatically picked up by the identity-spring-boot-autoconfigure module.

It's still possible to use the previous Zeebe configuration properties for Identity.

The existing Zeebe configuration properties take precedence over the IdentityConfiguration bean provided by the identity-spring-boot-autoconfigure  module

As the Zeebe Gateway and Zeebe Broker are both Spring Boot applications, the Spring mechanism for picking up environment variables and setting them to the appropriate configuration properties applies.
Actual behavior:

Zeebe Gateway deployment sets this variable CAMUNDA_IDENTITY_ISSUERBACKENDURL. The other components use the config map which sets CAMUNDA_IDENTITY_ISSUER_BACKEND_URL
Currently in the Camunda Helm chart we are not using the CAMUNDA_IDENTITY_ISSUER_BACKEND_URL environment variable, and using the CAMUNDA_IDENTITY_ISSUERBACKENDURL instead.
Expected behavior:
The new Identity properties should replace both the Standalone and Embedded Gateway properties since the IdentityAutoconfiguration class should provide the same Spring Bean for both

How to reproduce:
Suggested fix is to change ZEEBE_GATEWAY_SECURITY_AUTHENTICATION_IDENTITY_ISSUERBACKENDURL to CAMUNDA_IDENTITY_BASEURL this will then be picked up by the identity-spring-boot-autoconfigure module.
Confirmed using the Zeebe configuration property ZEEBE_GATEWAY_SECURITY_AUTHENTICATION_IDENTITY_ISSUERBACKENDURL is a valid workaround, meaning that Spring manages to pick up and map env vars correctly.
Environment:
Camunda 8.4 with multitenancy enabled.
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

Chart version: 9.0.4

Another support ticket raised for this issue - SUPPORT-20228

To fix the bug, the following needs to be done:

We need to replace ZEEBE_GATEWAY_SECURITY_AUTHENTICATION_IDENTITY_ISSUERBACKENDURL here with CAMUNDA_IDENTITY_BASE_URL.
These lines can be removed, as the Identity env var above will apply for both a Standalone and Embedded Gateway.
And we need to replace CAMUNDA_IDENTITY_ISSUERBACKENDURL here with CAMUNDA_IDENTITY_ISSUER_BACKEND_URL.

@mschoe it would be good if QA confirms that the bug has been resolved after the fix is merged.


Document for jetson.utils and jetson.inference

Hello,
Sorry but I am just a beginner and was looking for some docs for the jetson.utils and jetson.inference packages.
I have followed the tutorial and everything is working fine. However, I have created a Flask wrapper to my custom python project to receive inference requests through a REST interface.
When doing that, I am receiving an image encoded in base64 format.  I need to know the type of image format the imagenet classify operation requires.  I have decoded the image I receive and tried passing  that, but I get the following error:
class_idx, confidence = net.Classify(img)
Exception: jetson.utils -- function wasn't passed a valid cudaImage or cudaMemory object
I need help converting my base64 encoded image to one of the formats expected by the classify operation.
Any help will be greatly appreciated.

Hi @magallardo , this document might help you:
https://github.com/dusty-nv/jetson-inference/blob/master/docs/aux-image.md#image-capsules-in-python
imageNet/detectNet/segNet expects to receive cudaImage object in one of these formats:

rgb8
rgba8
rgb32f
rgba32f

If you convert your data from base64 into a numpy array, you can use cudaFromNumpy() function to get the cudaImage object:
https://github.com/dusty-nv/jetson-utils/blob/master/python/examples/cuda-from-numpy.py

@dusty-nv Thanks for your suggestion and I was able to get it working.  I don't know if it is the most efficient way, but it is working!!
Following is what I did and used Image from pillow.
b64decoded = base64.b64decode(image)
image = Image.open(io.BytesIO(b64decoded))
image_np = np.array(image)
cuda_img = jetson.utils.cudaFromNumpy(image_np)
Thanks again.

import jetson.inference
import jetson.utils
import cv2
import numpy as np
net = None
camera = None
def initialize_detector():
global net, camera
net = jetson.inference.detectNet("ssd-mobilenet-v2")
camera = jetson.utils.videoSource("/dev/video0")      # '/dev/video0' for V4L2
def get_detections():
person_detections = []
img = camera.Capture()
detections = net.Detect(img)
for detection in detections:
if detection.ClassID == 1: #remove unwanted classes
person_detections.append(detection)
fps = net.GetNetworkFPS()
return person_detections, fps, jetson.utils.cudaToNumpy(img)

import detector_mobilenet as detector
initialize_detector()
while True:
detections, fps, image = get_detections()
cv2.putText(image, str(fps), (50, 50), cv2.FONT_HERSHEY_SIMPLEX , 1, (0, 0, 255), 3, cv2.LINE_AA)
cv2.imshow("out", image)
cv2.waitKey(1)
I have bug with my code about " detections = net.Detect(img)"
Exception: jetson.utils -- function wasn't passed a valid cudaImage or cudaMemory object"

@QuocDuyTran, try adding this check after img = camera.Capture():
if img is None:
   return

camera.Capture() can return None in the event of a capture timeout, so your get_detections() function should check for it and try again

I trying to import the jetson_utils.cudaFromNumpy and doesn't work
it says to me:
ModuleNotFoundError: No Module named 'jetson_utils.cudaFromNumpy'
I try to rebuild the jetson_inference repository
it builds successfully.
but it doesn't work...
how can I solve that?

@SJavad are you able to run other scripts that use jetson_inference/jetson_utils (like video-viewer.py, imagenet.py, or detectnet.py) or is it just that cudaFromNumpy() function that gives you the error?

When I run from jetson_utils import cudaFromNumpy, I'm able to import it ok.
I wonder if when you build jetson-inference, it didn't detect the numpy dev packages?

When I run from jetson_utils import cudaFromNumpy, I'm able to import it ok.
I wonder if when you build jetson-inference, it didn't detect the numpy dev packages?

I build the Jetson-inference successfully and all numpy packages like python-numpy python3-numpy are installed

When I run from jetson_utils import cudaFromNumpy, I'm able to import it ok.
I wonder if when you build jetson-inference, it didn't detect the numpy dev packages?

@dusty-nv
when I import the: from jetson_utils import cudaFromNumpy with python 2.7
it is import successfully
but my problem for python3
looks like the jetson_utils it is not build for python3...
how can I fix that ?

-- detecting Python 3.6...
-- found Python version:  3.6 (3.6.9)
-- found Python include:  /usr/include/python3.6m
-- found Python library:  /usr/lib/aarch64-linux-gnu/libpython3.6m.so
-- CMake module path:  /home/deep/SSD_TEST_PYLON/jetson-utils/cuda;/home/deep/SSD_TEST_PYLON/jetson-utils/python/bindings
-- NumPy not found

Can you try installing python3-numpy package from apt (although jetson-inference should have already done this), or pip3 install --upgrade numpy

-- detecting Python 3.6...
-- found Python version:  3.6 (3.6.9)
-- found Python include:  /usr/include/python3.6m
-- found Python library:  /usr/lib/aarch64-linux-gnu/libpython3.6m.so
-- CMake module path:  /home/deep/SSD_TEST_PYLON/jetson-utils/cuda;/home/deep/SSD_TEST_PYLON/jetson-utils/python/bindings
-- NumPy not found

Can you try installing python3-numpy package from apt (although jetson-inference should have already done this), or pip3 install --upgrade numpy

@dusty-nv
yes I try to install python3-numpy and also upgrade pip3 install --upgrade numpy but two commands say the numpy version is the latest version and installed
also when I try to import the jetson_utils it gives me a warning:
jetson.utils -- compiled without Numpy array conversion support (warning)
jetson.utils -- if you wish to have support for converting NumPy arrays.
jetson.utils -- first run 'sudo apt-get install python-numpy python3-numpy'
warning: importing jetson.utils is deprecated. please 'import jetson_utils' instead

also when I try to import the jetson_utils (no jetson.utils), can't find it at all. even cudaMemcpy...
is there any environment variables that set the numpy library address?
my problem is that I can't import cudaFromNumpy...

-- detecting Python 3.6...
-- found Python version:  3.6 (3.6.9)
-- found Python include:  /usr/include/python3.6m
-- found Python library:  /usr/lib/aarch64-linux-gnu/libpython3.6m.so
-- CMake module path:  /home/deep/SSD_TEST_PYLON/jetson-utils/cuda;/home/deep/SSD_TEST_PYLON/jetson-utils/python/bindings
-- NumPy not found

Can you try installing python3-numpy package from apt (although jetson-inference should have already done this), or pip3 install --upgrade numpy

@dusty-nv yes I try to install python3-numpy and also upgrade pip3 install --upgrade numpy but two commands say the numpy version is the latest version and installed also when I try to import the jetson_utils it gives me a warning:
jetson.utils -- compiled without Numpy array conversion support (warning)
jetson.utils -- if you wish to have support for converting NumPy arrays.
jetson.utils -- first run 'sudo apt-get install python-numpy python3-numpy'
warning: importing jetson.utils is deprecated. please 'import jetson_utils' instead

also when I try to import the jetson_utils (no jetson.utils), can't find it at all. even cudaMemcpy... is there any environment variables that set the numpy library address?
my problem is that I can't import cudaFromNumpy...

also, try to build the numpy from the source.
but nothing happens.

jetson.utils -- compiled without Numpy array conversion support (warning)
jetson.utils -- if you wish to have support for converting NumPy arrays.
jetson.utils -- first run 'sudo apt-get install python-numpy python3-numpy'
warning: importing jetson.utils is deprecated. please 'import jetson_utils' instead

@SJavad I'm not sure why it's not detecting numpy for python3 on your system - you could try adding debug print-outs to this file to see what's happening:
https://github.com/dusty-nv/jetson-utils/blob/f0bff5c502f9ac6b10aa2912f1324797df94bc2d/python/bindings/FindNumPy.cmake
or you can run the jetson-inference container, which has this all built-in.

@dusty-nv
I apologize for this long conversation, thank you for all your efforts ❤🌸


feat: add payload builder service metrics

🤖 Generated by Copilot at dfd935e
This pull request adds metrics to the payload builder crate. It defines a PayloadBuilderServiceMetrics struct with three metrics fields, and updates the service.rs file to use and update the metrics.
ref #2345

Codecov Report

Merging #2347 (dfd935e) into main (370c395) will decrease coverage by 25.57%.
The diff coverage is 16.66%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2347       +/-   ##
===========================================
- Coverage   70.77%   45.21%   -25.57%
===========================================
  Files         480      481        +1
  Lines       58129    58147       +18
===========================================
- Hits        41142    26291    -14851
- Misses      16987    31856    +14869

Flag
Coverage Δ

integration-tests
14.66% <0.00%> (-1.79%)
:arrow_down:

unit-tests
39.54% <16.66%> (-27.32%)
:arrow_down:

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

Impacted Files
Coverage Δ

crates/payload/builder/src/lib.rs
100.00% <ø> (ø)

crates/payload/builder/src/service.rs
25.27% <14.28%> (-18.78%)
:arrow_down:

crates/payload/builder/src/metrics.rs
18.18% <18.18%> (ø)

... and 254 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Accept zero-length nullable fields (behavior only)

Only tackles behavior state, still need to do TLV

Yeah I think that's fine


How can build application for using live camera to get iris depth info from windows desktop?

Hello, I want to build an application demo for detecting iris depth under windows, I can go to the focal length of the external camera, I can build iris_tracking:iris_tracking_cpu now, how can I do it next? Looking forward to your reply and wish you a happy life.

这个功能类似iris_tracking:iris_depth_from_image_desktop，只是使用了live camera，并且我可以获取焦距，我想我需要一个实例来指导，谢谢你。

This function is similar to iris_tracking:iris_depth_from_image_desktop, but uses a live camera, and I can get the focal length, I think I need an example to guide, thank you.

Hi @cx68cx ,
Did you get a chance to check this issue https://github.com/google/mediapipe/issues/1033.

Dear sureshdagooglecom, I looked carefully at issue #1033, the question is iris_depth_from_image_desktop example, but what I need is iris_depth_from_live_camera_desktop examplex, looking forward to your reply

Please check MediaPipe document for live input and follow the steps mentioned.

Please check MediaPipe document for live input and follow the steps mentioned.

Dear sureshdagooglecom, I checked the documentation Solutions-Iris-Desktop carefully, according to "LIVE CAMERA INPUT", I don't know how to get the iris depth information. If you have time to guide me patiently, thank you very much.

Please check MediaPipe document for live input and follow the steps mentioned.

i mean “ iris depth information” is <output_stream: "LEFT_IRIS_DEPTH_MM:left_iris_depth_mm"> and <
output_stream: "RIGHT_IRIS_DEPTH_MM:right_iris_depth_mm">, thank you!

@cx68cx ,did you get the required information?

no bro, i'm confused, can you show me your config or code example, thanks.

Please check this graph https://github.com/google/mediapipe/blob/ecb5b5f44ab23ea620ef97a479407c699e424aa7/mediapipe/graphs/iris_tracking/subgraphs/iris_and_depth_renderer_gpu.pbtxt

Please check this graph https://github.com/google/mediapipe/blob/ecb5b5f44ab23ea620ef97a479407c699e424aa7/mediapipe/graphs/iris_tracking/subgraphs/iris_and_depth_renderer_gpu.pbtxt

hi @sureshdagooglecom , I think the problem is how can we get EXIF info from the data stream from webcamera. I had google a lot, but nothing found.


docs: Fix variable name in custom-matcher-api code example (#8581)

Summary

This PR fixes the issue described in #8581
Test plan

Tested changes made to the docs by:

Building the Jest website locally (following commands outlined in CONTRIBUTING.md)
Navigating to http://localhost:3001/docs/en/expect#thisutils
Inspecting changes made to the code example

Codecov Report

Merging #8582 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8582   +/-   ##
=======================================
  Coverage   63.24%   63.24%
=======================================
  Files         272      272
  Lines       11311    11311
  Branches     2760     2760
=======================================
  Hits         7154     7154
  Misses       3540     3540
  Partials      617      617

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 85d9698...932335c. Read the comment docs.

Thanks for the quick review! 😅


Proto Model Loading

I have refactored this PR to only include the proto model loading. I will add two subsequent PRs for the dump and the generator.

I just fixed all the docs and triple checked them!


[FEATURE] Add default options to packages

By default we need to add the go_package file option to out output
proto file so gogo/protobuf generates the code in the same package as
the original types.
This updates the example output as well.

Current coverage is 94.21% (diff: 100%)

Merging #16 into master will increase coverage by 0.04%

@@             master        #16   diff @@
==========================================
  Files            10         10
  Lines           635        640     +5
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            598        603     +5
  Misses           25         25
  Partials         12         12

Powered by Codecov. Last update 5d614b0...bad88cf


feat(network): handle mixed behaviour events in net mngr

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1914  👈
#1912
#1911
#1908
#1905
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nagmo-starkware and the rest of your teammates on  Graphite


Question about query used for template

Hi @jpotts:
First of all, thanks for the addon, it's a very nice and useful component.
I'm testing it with Alfresco <IP_ADDRESS> version. I have a question regarding the query used in the module.
I use several site dashboards defined in presets.xml. In particular, I defined two site / presets / space templates:

Collaboration Site --> "site-dashboard"
ZK Site --> "zk-site-dashboard"

creating the corresponding folder structure in Space Templates.
I found some strange behaviour regarding the query for copying the template.
Sometimes I found that "zk-site-dashboard" is ** always ** found as the space template (for both site types) - so I found problems when creating "Collaboration Sites".
Maybe this is related with the query:
String query = "+PATH:"/app:company_home/app:dictionary/app:space_templates/*" +@cm\:name:"" + sitePreset + """;
Some notes:

If I search "site-dashboard" (or @cm:name:"site-dashboard") in Alfresco search, I found two hits in the resultset (maybe is it appropiate to use = operator for getting an exact term?).
There is no problem with ZK Site (zk-site-dashboard) creation in any case.
In the case of Collaboration Site creation it seems to get the first hit of the resultset, and I think that the query is using some relevance criteria (so the result can change).
Finally, I found that if I delete site-dashboard space template and I create a "Collaboration Site" it uses zk-site-dashboard template directly.

I understand too, that a walkaround is just to rename the custom presets like "template-site-zk", avoiding collisions, between site name presets.
Could you confirm this behaviour ?
Best regards and thanks in advance.
--C.

Thanks for reporting this, I'm looking into it.

I cannot recreate this on 5.0.d. Here is what I did...
I already had a space template named site-dashboard (matches the default) with several folders. I created six additional presets named:

aaa-site-dashboard
bbb-site-dashboard
ccc-site-dashboard
site-dashboard-aaa
site-dashboard-bbb
site-dashboard-ccc

I then created a matching entry in Data Dictionary/Space Templates for all but ccc-site-dashboard and site-dashboard-ccc.
In each space template I placed one uniquely named folder so that it could be traced back to its source.
I was then able to create sites using all six presets. The four with existing space templates were created with the proper folders from the proper templates. The two with missing space templates were created with no folders.
If I go into the Alfresco node browser and run the Lucene search, I can unambiguously find all of my space templates using the query from the source code. When you are testing this, make sure to change the syntax to "Lucene" to match what the code does. If you leave it set to "Alfresco FTS" you will see ambiguous results unless you remove the + ("plus") signs and use "AND" instead.
So this appears to not be a problem. Perhaps your folders are not being indexed by Solr by the time you are creating your site.

Thanks for your reply and testing Jeff. Really appreciated.
I would say it is not easy for me to debug it, even to recreate it exactly (I explain myself a little more later).
What I'm trying to say is that, I have problems with the default template (site-dashboard), not with the "new" ones, due the type of search, based on @cm:name
The new templates are found because there is no collision when trying to find the template. Only when trying to apply / search the default template "site-dashboard" you may obtain more than 1 result in the search and so my issue (because it is not an exact term search and the name of the template is tokenised - this is what I think). I imagine that if there is some relevance criteria applied in the Alfresco Search when finding the space template, the order of this subset can change, and the first element for site-dashboard resulset too. And this is the reason for what I think I could not recreate it exactly.
Relating to your tests, I think also that, if you delete all your templates except aaa-site-dashboard (delete also site-dashboard) and then create a "Collaboration Site", you will obtain a Collaboration Site with aaa-site-dashboard contents inside.
Maybe with =@cm:name syntax in the query, will be enough.
Best regards.
--C.

I see what you are saying now. If any Space Templates contain "site-dashboard" as part of the name and you do not have a Space Template named "site-dashboard", creating a default Collaboration Site will cause the first Space Template that does contain that string to be used as the space template.
The reason it does this is because cm:name is tokenized. There is no way to do an exact match on a tokenized property.
A workaround is to create an empty Space Template named "site-dashboard". This works because that will always be the first one in the list, and the code always picks the first hit.
One fix for the code would be to do a string comparison on the folder name and the sitePreset, rejecting it if they are not an exact match.


online demo

I made this online demo tool to help my people test the utterance generation. I thought you might like to see it because a lot of the other utterance expanders have an online demonstration.
Thanks for such a neat project!

thanks for sharing!


chore: bump v0.2.14.post2

Motivation

Modifications

Checklist

[ ] Format your code according to the Contributor Guide.
[ ] Add unit tests as outlined in the Contributor Guide.
[ ] Update documentation as needed, including docstrings or example tutorials.

hold on


Uncaught TypeError

Hy,
I just used the plugin, but it's not working the documentation is not enough for a first-time user.
Attaching the code and error below

For using Annotorious in React, please follow the React guide here:
https://recogito.github.io/guides/annotorious-in-react/


CONTRIBUTING.md improvement suggested

Would you please resolve this issue https://github.com/codemaniac-sahil/codemaniac-sahil/issues/1

I will look and tell you on that issue over there only


Adds a callback

The callback is called when the process exits. This change also
provides access to the error code

Thanks for the pull! Sorry about the slow reply, published a new version now.


Type Definition Issue with SendBoxProps for SendBox Component

Describe the bug; what happened?
According to the prop types for the SendBox Component we should be able to pass a callback that registers after a message is sent.
From the documentation:
onSendMessage | Optional callback called when message is sent | onSendMessage?: (content: string) => Promise
However, when an empty promise is passed, the message in the send box is never sent.
<SendBox
    {...sendBoxProps}
    onSendMessage={(content) =>
        new Promise((resolve) => {
            // Message is never sent
        })
    }
/>

What behavior did you expect?
From the documentation, I expected this prop to be a way to fire side effects "when the message is sent", but passing any function here seems to break message sending from the ChatBox component.
In what environment did you see the issue?

"@azure/communication-react": "1.6.0",

"@azure/communication-chat": "1.3.1",

OS & Device: MacOS

Browser: Mozilla FireFox

Browser Version: 115.0.2

@jessihamel thanks for raising the issue, I will investigate and provide updates

Hi @jessihamel I think this is mistake in documentation on our side. The documentation seems to imply that this is a callback but instead its an override.
https://azure.github.io/communication-ui-library/?path=/docs/statefulclient-reacthooks-useselector--page#write-your-own-handler-function

Updating docs with a quick PR: https://github.com/Azure/communication-ui-library/pull/3433

Sorry for the confusion, I have updated the documentation to make it a bit more clear. Please let me know if there are any more questions.

This makes sense now. Thank you for the update.


Browse.vc.db is not invalidated in vs2019 when VcpkgTriplet changes

Describe the bug
Ignoring the recent break I reported (https://github.com/microsoft/vcpkg/issues/12062), when you set VcpkgTriplet in a vcxproj file, VS2015 and VS2017 consistently look in the correct location for the header files from the installed vcpkg ports. But in VS2019, while the compile behaves appropriately, when you try to open a header file from a port, it can look in the wrong location if you've changed the triplet. This is a bug and poor integration experience that seems to works correctly in VS2015 and VS2017.
Environment

OS: Win 1903, 1909
Compiler: Bad behavior in VS2019 16.6.2

To Reproduce

Install vcpkg without the recent .vcxproj triplet bug, and install minhook:x86-windows-static (just to have something to use):

git clone https://github.com/Microsoft/vcpkg.git vcpkg_before
cd vcpkg_before
git checkout 14514508d8d30bdbd645b2bec89696aec25497f1~1
.\bootstrap-vcpkg.bat
.\vcpkg.exe integrate install
.\vcpkg.exe install minhook:x86-windows-static

Now start visual studio 2019 (16.6.2), create a new c++ console application project with solution.
Add
#include "minhook.h"
immediately before the main() function.
Build the solution. It will correctly fail as only the static minhook is installed.
Right click on the text "minhook.h" in the text of the include line you added. Choose to go to document. This correctly fails.
Close visual studio.
Edit the .vcxproj project file to have the line:
<VcpkgTriplet>x86-windows-static</VcpkgTriplet>
at the bottom of the
<PropertyGroup Label="Globals">
section.
Open the solution.
Build the solution. It correctly succeeds since we now point to the static port.
Right click on the text "minhook.h" in the text of the include line you added. Choose to go to document. This incorrectly fails!!
Close the solution and visual studio.
Go to the solution folder, show hidden items, and delete the .vs folder at the top-level, This folder contains the browse info database.
Open the solution and then show the main cpp file
Right click on the text "minhook.h" in the text of the include line you added. Choose to go to document. This correctly succeeds

Expected behavior
Choosing to go to the included header file should work correctly after changing the VcpkgTriplet and reloading the project or reopening visual studio. To fix the behavior you have to delete the vc browse database. This workaround is not needed in vs2015 and vs2017, and without realizing what is happening, it leads to some very confusing/poor integration behavior.

I don't know if there's anything vcpkg can do about this. @yuehuang010 do you have any ideas on how to get the IDE to realize that that setting affects include paths?

Yeah, that makes sense. When I started writing up the issue, what I was seeing led me to think vcpkg was likely at fault, but by the time I was done and had solid reproduction steps, it definitely seems like it could be a VS2019 bug at the core. I'll see if I can find a similar way to trigger it without vcpkg .

Alright, I figured out how to trigger this with just VS2019. Verified the exact same sequence does not cause the bug in VS2017. We can go ahead and close this issue and I'll file one for VS 2019. Here's how to do it without vcpkg.

Create a new cpp console project and add #inlcude "foobar.h" to the main cpp file
Navigate to the property manager and open Microsoft.Cpp.,Win32.user under Debug | Win32C. Go the the User Macros section and add a macro named MyCustomMacro with the value c:\missing_include
Create a new directory at c:\good_include and a new empty text document at c:\good_include\foobar.h
Add $(MyCustomMacro) as to Include Directories by right clicking on the project in solution explorer, choosing Properties..., and going to VC++ Directories .
Build solution. It will correctly fail.
Close visual studio.
Open %localappdata%\Microsoft\MSBuild\v4.0\Microsoft.Cpp.Win32.user.props in notepad
Replace c:\missing_include with c:\good_include in the file
Save file and exit notepad
Reopen solution in VS2019.
Build solution. It succeeds correctly.
Right click on the text "foobar.h" and choose to go to Go to document "foobar.h". It will fail. This is incorrect behavior.

Link to VS2019 issue:
https://developercommunity.visualstudio.com/content/problem/1091182/vs2019-does-not-invalidate-browse-info-when-the-in.html


Rationalize macro helper, add support for tick cb's

Holy moly did someone say #20 ??

Adds support for options.scales[scale].callback as an FnWithArgs
Simplifies the rationalizing process with a rationalize!() macro (see utils.rs)

Looks good, can you please bump the Cargo.toml version? Thank you for fixing the issue!


outbound event pub protocol + kafka provider (GDEV-713)

Title for squash and merge:
outbound event pub protocol + kafka provider (GDEV-713)

Description for squash and merge:
Initialized the package with the following functionality:
- based on chassis-lib functionality (kafka-python library)
- include simple example app
- include tests
- not included: a test framework for use by implementing services

Thanks a lot @Cito for the awesome review. Let me know if you want to discuss this. I am ready for another round.

Great thanks a lot @Cito for the very helpful review.


Truncate toc entry if its length exceeds a single line

Depending the text
num_dots = ((bounds.width - (width_of %(#{sect_title}#{sect_page_num}), inline_format: true) - spacer_width) / dot_width).floor

can be negative.
In this case the next line (1571 in converter.rb):
<EMAIL_ADDRESS>|| DotLeaderDefault) * num_dots})

will fail with
Caused by: org.jruby.exceptions.RaiseException: (ArgumentError) negative argument

Would be great to

prevent negative size
print a message (warning?)

Zonk! I never thought of that case. This will definitely make a great test case.
I did some research on this and determined that a quick fix is to just set the number of dots to 0 if the calculated result is less than zero.
However, the title text will still wrap. So the next fix is to only allow the title to consume a single line.
However, then the text could still overlap the page number. The final fix is to prevent the title text from expanding past a fixed column (better that it is fixed I think for consistency). Perhaps something like 80 or 90% of the page. That should leave enough room for the page numbers. In this case, the dots get a bit off, but I don't think that's a huge concern atm.

I think I'll move forward with (a) and (b) right away so that the processor isn't crashing. Then, I'll try to arrive at a nice solution for (c).

I've done (a) in master just so that you can move forward.

personally I just used a max between computed number and 0. If it is not enough wrapping or whatever solution makes rendering less nice IMO and needs "writer" works. That said if you manage to get a nicer default it is really better.

:+1:
Btw, thanks for pointing this out!

@mojavelinux Per the release notes for Alpha 8, it says this issue is closed ... but it looks like it is still open?

This is only partially addressed. A quick fix is in place, but there's still work to do to make it cover all cases in the proper way.

The milestone should be set to 1.5.0.beta.1 for now.

I've decided to split the remaining changes off into #1152 and #1153. I've also added a test to cover the fix that was made in this issue. Therefore, this issue can now be closed.


Fuzz the wire parser in the lnwire package

Issue
Currently, within the lnwire package, we have a set that uses the testing/quick package to create a set of block-block tests that use the quickcheck testing paradigm to exercise our wire parser. This set of tests uses property based testing to ensure that the parser is able to adhere to the mainScenario, amongst other things, this ensures that we'll always be able to consume a message that we produced, ensuring correctness of our wire parsing implementation.
This set of tests are nice, but insufficient. What we really want to ensure (for safety/security properties) is that: no sequence or random bytes, partially correct wire encodings, or mutated wire encodings case lnd to crash. We
ll need to ensure that under the presence of arbitrary malicious input, lnd partially parses, them ignores them if invalid, and keeps on trucking. This can be achieved by what's known as fuzz testing.
There exists a popular fuzz-testing library written in golang, called go-fuzz, we can use this to being the process of first fuzzing encoding/decoding code within the lnwire package. In the future, we can expand our usage to cover other relevant areas of the codebase.
Steps To Completion

[ ] Get familiar with how the go-fuzz package is used by reading the documentation.

[ ] Create an applicable fuzz function within the lnwire package. This may closely resemble the mainScenario used within the tests, but should call panic rather than failing the test.

[ ] Next, gather an initial testing corpus. This should consist of known valid serialized wire messages. At the very least, there should be an entry for each of the known wire messages defined within the current specification. A diversity of input is desirable, so these can be obtained by either adding some code to lnd to dump valid messages into a file, or by generating them manually.

[ ] Execute the fuzzer with the defined fuzz function, and corpus.

[ ] Monitor the execution of the fuzzer, noting which inputs cause the fuzz function to panic. Examine the inputs, and the current parsing code, creating PR's fixing the panic for each input found.

[ ] ????

[ ] Profit 🎉

I can do this - I've used American Fuzzy Lop before so this is familiar territory.

I made a PR for one error that go-fuzz found: https://github.com/lightningnetwork/lnd/pull/310

Good finds! 😃  How hard would it be to add the fuzz test that found these errors together with the fix?

@halseth do you mean the malicious input?  I'm not sure where I'd put it and whether it belongs in a PR.  I could make a gist though...

I'm not familiar enough with go-fuzz to know what this input looks like 😛  It would be nice if the fuzz tests ran continuously together with the rest of the tests, to make sure the bugs are not introduced again, and maybe catch more?

@halseth I would agree, but the corpus that go-fuzz generates might get too large to include in a repo.  This is a specific test I made to follow the stacktrace that the fuzzer gave me upon crash: https://gist.github.com/Crypt-iQ/96ef579fb6229b6f47ec8c0d41aecd10

Aha, cool :) Let's hear what @Roasbeef was thinking. Thanks!

No problem !

One thing that go-fuzz found was that when deserializing MsgFundingSigned messages and then asserting equality after serialization, the two []byte (pre-deserialization and post-serialization) are not deeply equal.  This is because of line #54 here which is called only on serialization of MsgFundingSigned and alters *Signature.S.  Is it intended that the S value be different upon deserialization & serialization?  I ask since this seems a bit involved and I'd have to brush up on my cryptography to assess this.

I believe that go-fuzz has found all of the bugs it can find with the given corpus.  I simply started with a serialized message for each message type and let go-fuzz generate the rest of the corpus.  After several hours of running, it has found no more crashes.

Thanks for all the work on this @Crypt-iQ! Do you think you could add some documentation under the docs folder which details how you set up your harness for fuzzing? This would include the initial corpus (possible committed as a compressed file), and the fuzzing function you used.
I envision this to be useful as we'll likely want to re-run the fuzzer in the future as we make modifications to the wire parsing, and also simply for educational purposes 📚.

Of course! @Roasbeef

Current running fuzzing graveyard:

#310
#312

I have a machine with the fuzzing set up recently added running now. I'll continue to monitor this over the next few days/weeks and report here with any new issues found, re-opening as necessary.
Closing.


More from this collection pictures dont load?

on collection everything okay

Can you please share url of the collection?