[3.0.0] Multiple test failures on HP-UX 32bit

Hey guys,
We've got another issue with some HP-UX tests using the native compiler with a 32bit build. 64bit passes all tests on the same machine. I have tried to reduce compiler optimization to +O1 to no avail.
Failing tests:
Test Summary Report
-------------------
20-test_enc_more.t               (Wstat: 256 Tests: 137 Failed: 1)
  Failed test:  87
  Non-zero exit status: 1
30-test_evp.t                    (Wstat: 256 Tests: 103 Failed: 1)
  Failed test:  72
  Non-zero exit status: 1
30-test_evp_extra.t              (Wstat: 512 Tests: 3 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
30-test_evp_libctx.t             (Wstat: 512 Tests: 3 Failed: 2)
  Failed tests:  2-3
  Non-zero exit status: 2
80-test_dtls_mtu.t               (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
80-test_ssl_new.t                (Wstat: 256 Tests: 30 Failed: 1)
  Failed test:  25
  Non-zero exit status: 1
80-test_ssl_old.t                (Wstat: 512 Tests: 11 Failed: 2)
  Failed tests:  3-4
  Non-zero exit status: 2
80-test_sslcorrupt.t             (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
90-test_bio_enc.t                (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
90-test_sslapi.t                 (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=240, Tests=3375, 2331 wallclock secs (20.81 usr  2.37 sys + 1765.58 cusr 376.51 csys = 2165.27 CPU)
Result: FAIL
Makefile:1532: recipe for target 'run_tests' failed
gmake[1]: *** [run_tests] Error 1

Build config:
Command line (with current working directory = .):
    /opt/perl64/bin/perl ./Configure --prefix=/bamboo/hpux11_3/acc06_28/release32 hpux-ia64-cc shared enable-fips
Perl information:
    /opt/perl64/bin/perl
    5.20.1 for IA64.ARCHREV_0-thread-multi-LP64-ld
Enabled features:
    acvp-tests
    aria
    asm
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    bulk
    cached-fetch
    camellia
    capieng
    cast
    chacha
    cmac
    cmp
    cms
    comp
    ct
    deprecated
    des
    dgram
    dh
    dsa
    dso
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    engine
    err
    filenames
    fips
    fips-securitychecks
    gost
    idea
    legacy
    loadereng
    md4
    mdc2
    module
    multiblock
    nextprotoneg
    ocb
    ocsp
    padlockeng
    pic
    pinshared
    poly1305
    posix-io
    psk
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    secure-memory
    seed
    shared
    siphash
    siv
    sm2
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    ssl-trace
    static-engine
    stdio
    tests
    threads
    tls
    ts
    ui-console
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method
Disabled features:
    afalgeng            [not-linux]      OPENSSL_NO_AFALGENG
    asan                [default]        OPENSSL_NO_ASAN
    buildtest-c++       [default]
    crypto-mdebug       [default]        OPENSSL_NO_CRYPTO_MDEBUG
    devcryptoeng        [default]        OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128 [default]        OPENSSL_NO_EC_NISTP_64_GCC_128
    egd                 [default]        OPENSSL_NO_EGD
    external-tests      [default]        OPENSSL_NO_EXTERNAL_TESTS
    fuzz-afl            [default]        OPENSSL_NO_FUZZ_AFL
    fuzz-libfuzzer      [default]        OPENSSL_NO_FUZZ_LIBFUZZER
    ktls                [default]        OPENSSL_NO_KTLS
    makedepend          [unavailable]
    md2                 [default]        OPENSSL_NO_MD2 (skip crypto/md2)
    msan                [default]        OPENSSL_NO_MSAN
    rc5                 [default]        OPENSSL_NO_RC5 (skip crypto/rc5)
    sctp                [default]        OPENSSL_NO_SCTP
    trace               [default]        OPENSSL_NO_TRACE
    ubsan               [default]        OPENSSL_NO_UBSAN
    unit-test           [default]        OPENSSL_NO_UNIT_TEST
    uplink              [no uplink_arch] OPENSSL_NO_UPLINK
    weak-ssl-ciphers    [default]        OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                [default]
    zlib-dynamic        [default]
    ssl3                [default]        OPENSSL_NO_SSL3
    ssl3-method         [default]        OPENSSL_NO_SSL3_METHOD
Config target attributes:
    AR => "ar",
    ARFLAGS => "qc",
    CC => "cc",
    CFLAGS => "+O2",
    HASHBANGPERL => "/usr/bin/env perl",
    RANLIB => "ranlib",
    RC => "windres",
    asm_arch => "ia64",
    bin_lflags => "-Wl,+s,+cdp,../:,+cdp,./:",
    bn_ops => "SIXTY_FOUR_BIT",
    build_file => "Makefile",
    build_scheme => [ "unified", "unix" ],
    cflags => "-Ae +DD32 +Olit=all -z",
    cppflags => "-D_REENTRANT",
    defines => [ "OPENSSL_BUILDING_OPENSSL", "_XOPEN_SOURCE", "_XOPEN_SOURCE_EXTENDED", "_HPUX_ALT_XOPEN_SOCKET_API" ],
    disable => [  ],
    dso_scheme => "dlfcn",
    enable => [  ],
    ex_libs => "-ldl -lpthread",
    includes => [  ],
    lflags => "",
    lib_cflags => "",
    lib_cppflags => "-DB_ENDIAN",
    lib_defines => [  ],
    module_cflags => "+Z",
    module_cxxflags => undef,
    module_ldflags => "-b -Wl,-B,symbolic,+vnocompatwarnings,-z,+s,+cdp,../:,+cdp,./:",
    multilib => "/hpux32",
    perl_platform => "Unix",
    perlasm_scheme => "void",
    shared_cflag => "+Z",
    shared_defines => [  ],
    shared_ldflag => "-b -Wl,-B,symbolic,+vnocompatwarnings,-z,+s,+cdp,../:,+cdp,./:",
    shared_rcflag => "",
    shared_sonameflag => "-Wl,+h,",
    shared_target => "self",
    thread_defines => [  ],
    thread_scheme => "pthreads",
    unistd => "<unistd.h>",
Recorded environment:
    AR =
    ARFLAGS =
    AS =
    ASFLAGS =
    BUILDFILE =
    CC =
    CFLAGS =
    CPP =
    CPPDEFINES =
    CPPFLAGS =
    CPPINCLUDES =
    CROSS_COMPILE =
    CXX =
    CXXFLAGS =
    HASHBANGPERL =
    LD =
    LDFLAGS =
    LDLIBS =
    MT =
    MTFLAGS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    RM =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =
Makevars:
    AR              = ar
    ARFLAGS         = qc
    CC              = cc
    CFLAGS          = +O2
    CPPDEFINES      =
    CPPFLAGS        =
    CPPINCLUDES     =
    CXXFLAGS        =
    HASHBANGPERL    = /usr/bin/env perl
    LDFLAGS         =
    LDLIBS          =
    PERL            = /opt/perl64/bin/perl
    RANLIB          = ranlib
    RC              = windres
    RCFLAGS         =
NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    Makefile
build file:
    Makefile
build file templates:
    Configurations/common0.tmpl
    Configurations/unix-Makefile.tmpl

Verbose test logs:
../../util/wrap.pl ../../apps/openssl enc -chacha20 -k test -provider-path ../../providers -provider default -provider legacy -e -in ./testdatafile -out ./testdatafile.chacha20.cipher => 139
not ok 87 - chacha20

#   Failed test 'chacha20'
#   at test/recipes/20-test_enc_more.t line 60.
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
../../util/wrap.pl ../../apps/openssl enc -des -k test -provider-path ../../providers -provider default -provider legacy -e -in ./testdatafile -out ./testdatafile.des.cipher => 0
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
../../util/wrap.pl ../../apps/openssl enc -des -k test -provider-path ../../providers -provider default -provider legacy -d -in ./testdatafile.des.cipher -out ./testdatafile.des.clear => 0

../../util/wrap.pl ../../test/evp_test -config ../../test/default-and-legacy.cnf ../../test/recipes/30-test_evp_data/evpciph_chacha.txt => 139
not ok 72 - running evp_test -config ../../test/default-and-legacy.cnf evpciph_chacha.txt

#   Failed test 'running evp_test -config ../../test/default-and-legacy.cnf evpciph_chacha.txt'
#   at test/recipes/30-test_evp.t line 140.
    # Subtest: ../../test/evp_test

../../util/wrap.pl ../../test/evp_extra_test => 139
not ok 1 - running evp_extra_test

#   Failed test 'running evp_extra_test'
#   at test/recipes/30-test_evp_extra.t line 19.
    # Subtest: ../../test/evp_extra_test
    1..42

../../util/wrap.pl ../../test/evp_extra_test -context => 139
not ok 2 - running evp_extra_test with a non-default library context

#   Failed test 'running evp_extra_test with a non-default library context'
#   at test/recipes/30-test_evp_extra.t line 22.
    # Subtest: ../../test/evp_extra_test2
    1..9

../../util/wrap.pl ../../test/evp_libctx_test -config ../../test/default.cnf => 139
not ok 2 - running default evp_libctx_test

#   Failed test 'running default evp_libctx_test'
#   at test/recipes/30-test_evp_libctx.t line 37.
    # Subtest: ../../test/evp_libctx_test
    1..9

../../util/wrap.pl ../../test/evp_libctx_test -config ../../test/default-and-legacy.cnf => 139
not ok 3 - running default-and-legacy evp_libctx_test

#   Failed test 'running default-and-legacy evp_libctx_test'
#   at test/recipes/30-test_evp_libctx.t line 41.
# Looks like you failed 2 tests of 3.
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/3 subtests

# The results of this test will end up in test-runs/test_dtls_mtu
1..1
    # Subtest: ../../test/dtls_mtu_test
    1..1
    # INFO:  @ test/dtls_mtu_test.c:176
    # PSK-AES256-GCM-SHA384 OK
../../util/wrap.pl ../../test/dtls_mtu_test => 139
not ok 1 - running dtls_mtu_test

#   Failed test 'running dtls_mtu_test'
#   at test/recipes/80-test_dtls_mtu.t line 21.
# Looks like you failed 1 test of 1.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests

../../util/wrap.pl ../../test/ssl_test 25-cipher.cnf.none none => 139
    not ok 3 - running ssl_test 25-cipher.cnf

    #   Failed test 'running ssl_test 25-cipher.cnf'
    #   at test/recipes/80-test_ssl_new.t line 171.
../../util/wrap.pl /opt/perl64/bin/perl -I ../../util/perl ../../test/generate_ssl_tests.pl ../../test/ssl-tests/25-cipher.cnf.in default > 25-cipher.cnf.default => 0
    ok 4 - Getting output from generate_ssl_tests.pl.
    ok 5 # skip Skipping generated source test for 25-cipher.cnf
        # Subtest: ../../test/ssl_test
        1..1
            # Subtest: test_handshake
            1..9
            ok 1 - iteration 1
            ok 2 - iteration 2
            ok 3 - iteration 3
            ok 4 - iteration 4
            ok 5 - iteration 5
            ok 6 - iteration 6
            ok 7 - iteration 7
            ok 8 - iteration 8
../../util/wrap.pl ../../test/ssl_test 25-cipher.cnf.default default => 139
    not ok 6 - running ssl_test 25-cipher.cnf

    #   Failed test 'running ssl_test 25-cipher.cnf'
    #   at test/recipes/80-test_ssl_new.t line 171.
../../util/wrap.pl /opt/perl64/bin/perl -I ../../util/perl ../../test/generate_ssl_tests.pl ../../test/ssl-tests/25-cipher.cnf.in fips > 25-cipher.cnf.fips => 0
    ok 7 - Getting output from generate_ssl_tests.pl.
    ok 8 # skip Skipping generated source test for 25-cipher.cnf
        # Subtest: ../../test/ssl_test
        1..1
            # Subtest: test_handshake
            1..8
            ok 1 - iteration 1
            ok 2 - iteration 2
            ok 3 - iteration 3
            ok 4 - iteration 4
            ok 5 - iteration 5
            ok 6 - iteration 6
            ok 7 - iteration 7
            ok 8 - iteration 8
        ok 1 - test_handshake
../../util/wrap.pl ../../test/ssl_test 25-cipher.cnf.fips fips ../../test/fips-and-base.cnf => 0
    ok 9 - running ssl_test 25-cipher.cnf
    # Looks like you failed 2 tests of 9.
not ok 25 - Test configuration 25-cipher.cnf

#   Failed test 'Test configuration 25-cipher.cnf'
#   at /localhome/bamboo/bamboo-agent-home/xml-data/build-dir/ThirdParty/openssl/3.0.0/_src/openssl-3.0.0-src/openssl-3.0.0/util/perl/OpenSSL/Test.pm line 1296.
# Subtest: Test configuration 26-tls13_client_auth.cnf
    1..9
../../util/wrap.pl /opt/perl64/bin/perl -I ../../util/perl ../../test/generate_ssl_tests.pl ../../test/ssl-tests/26-tls13_client_auth.cnf.in none > 26-tls13_client_auth.cnf.none => 0

../../util/wrap.pl ../../test/ssl_old_test -s_key ../../test/certs/ee-key.pem -s_cert certU.ss -c_key ../../test/certs/ee-key.pem -c_cert certU.ss -config ../../test/default-and-legacy.cnf -provider default -provider legacy -s_cert certD.ss -s_key keyD.ss -s_cert certE.ss -s_key keyE.ss -cipher 'ECDHE-ECDSA-CHACHA20-POLY1305:@SECLEVEL=0' -ciphersuites '' -tls1_2 => 139
    not ok 36 - Testing ECDHE-ECDSA-CHACHA20-POLY1305:@SECLEVEL=0

    #   Failed test 'Testing ECDHE-ECDSA-CHACHA20-POLY1305:@SECLEVEL=0'
    #   at test/recipes/80-test_ssl_old.t line 497.
../../util/wrap.pl ../../test/ssl_old_test -s_key ../../test/certs/ee-key.pem -s_cert certU.ss -c_key ../../test/certs/ee-key.pem -c_cert certU.ss -config ../../test/default-and-legacy.cnf -provider default -provider legacy -s_cert certD.ss -s_key keyD.ss -s_cert certE.ss -s_key keyE.ss -cipher 'ECDHE-RSA-CHACHA20-POLY1305:@SECLEVEL=0' -ciphersuites '' -tls1_2 => 139
    not ok 37 - Testing ECDHE-RSA-CHACHA20-POLY1305:@SECLEVEL=0

    #   Failed test 'Testing ECDHE-RSA-CHACHA20-POLY1305:@SECLEVEL=0'
    #   at test/recipes/80-test_ssl_old.t line 497.
../../util/wrap.pl ../../test/ssl_old_test -s_key ../../test/certs/ee-key.pem -s_cert certU.ss -c_key ../../test/certs/ee-key.pem -c_cert certU.ss -config ../../test/default-and-legacy.cnf -provider default -provider legacy -s_cert certD.ss -s_key keyD.ss -s_cert certE.ss -s_key keyE.ss -cipher 'DHE-RSA-CHACHA20-POLY1305:@SECLEVEL=0' -ciphersuites '' -tls1_2 => 139
    not ok 38 - Testing DHE-RSA-CHACHA20-POLY1305:@SECLEVEL=0

    #   Failed test 'Testing DHE-RSA-CHACHA20-POLY1305:@SECLEVEL=0'
    #   at test/recipes/80-test_ssl_old.t line 497.
Doing handshakes=1 bytes=256
TLSv1.2, cipher TLSv1.2 ECDHE-ECDSA-AES256-CCM8, 256 bits EC (prime256v1), temp key: 253 bits X25519, digest=SHA256
../../util/wrap.pl ../../test/ssl_old_test -s_key ../../test/certs/ee-key.pem -s_cert certU.ss -c_key ../../test/certs/ee-key.pem -c_cert certU.ss -config ../../test/default-and-legacy.cnf -provider default -provider legacy -s_cert certD.ss -s_key keyD.ss -s_cert certE.ss -s_key keyE.ss -cipher 'ECDHE-ECDSA-AES256-CCM8:@SECLEVEL=0' -ciphersuites '' -tls1_2 => 0

../../util/wrap.pl ../../test/ssl_old_test -s_key ../../test/certs/ee-key.pem -s_cert certU.ss -c_key ../../test/certs/ee-key.pem -c_cert certU.ss -config ../../test/default-and-legacy.cnf -provider default -provider legacy -s_cert certD.ss -s_key keyD.ss -s_cert certE.ss -s_key keyE.ss -cipher '' -ciphersuites TLS_CHACHA20_POLY1305_SHA256 => 139
    not ok 121 - Testing

    #   Failed test 'Testing '
    #   at test/recipes/80-test_ssl_old.t line 497.
Doing handshakes=1 bytes=256
TLSv1.3, cipher TLSv1.3 TLS_AES_128_GCM_SHA256, 256 bits EC (prime256v1), temp key: 253 bits X25519, digest=SHA256
../../util/wrap.pl ../../test/ssl_old_test -s_key ../../test/certs/ee-key.pem -s_cert certU.ss -c_key ../../test/certs/ee-key.pem -c_cert certU.ss -config ../../test/default-and-legacy.cnf -provider default -provider legacy -s_cert certD.ss -s_key keyD.ss -s_cert certE.ss -s_key keyE.ss -cipher '' -ciphersuites TLS_AES_128_GCM_SHA256 => 0
    ok 122 - Testing
    # Looks like you failed 4 tests of 122.
not ok 3 - Testing ciphersuites

#   Failed test 'Testing ciphersuites'
#   at /localhome/bamboo/bamboo-agent-home/xml-data/build-dir/ThirdParty/openssl/3.0.0/_src/openssl-3.0.0-src/openssl-3.0.0/util/perl/OpenSSL/Test.pm line 1296.
# Subtest: RSA/(EC)DHE/PSK tests
    1..6
Doing handshakes=10 bytes=256
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
DONE via BIO pair: TLSv1, cipher SSLv3 ADH-AES256-SHA, temp key: 1024 bits DH
Approximate total server time:   0.10 s
Approximate total client time:   0.08 s
../../util/wrap.pl ../../test/ssl_old_test -s_key ../../test/certs/ee-key.pem -s_cert certU.ss -c_key ../../test/certs/ee-key.pem -c_cert certU.ss -config ../../test/default-and-legacy.cnf -provider default -provider legacy -v -bio_pair -tls1 -cipher ADH -dhe1024dsa -num 10 -f -time => 0

../../util/wrap.pl ../../test/ssl_old_test -psk<PHONE_NUMBER> -cipher '@SECLEVEL=2:DHE-PSK-AES128-CCM' => 139
    not ok 6 - test auto DH meets security strength

    #   Failed test 'test auto DH meets security strength'
    #   at test/recipes/80-test_ssl_old.t line 566.
    # Looks like you failed 1 test of 6.
not ok 4 - RSA/(EC)DHE/PSK tests

#   Failed test 'RSA/(EC)DHE/PSK tests'
#   at /localhome/bamboo/bamboo-agent-home/xml-data/build-dir/ThirdParty/openssl/3.0.0/_src/openssl-3.0.0-src/openssl-3.0.0/util/perl/OpenSSL/Test.pm line 1296.
# Subtest: Custom Extension tests
    1..1
Doing handshakes=1 bytes=256
TLSv1, cipher TLSv1.0 ECDHE-RSA-AES256-SHA, 2048 bits RSA, temp key: 253 bits X25519, digest=MD5-SHA1
../../util/wrap.pl ../../test/ssl_old_test -s_key ../../test/certs/ee-key.pem -s_cert certU.ss -c_key ../../test/certs/ee-key.pem -c_cert certU.ss -config ../../test/default-and-legacy.cnf -provider default -provider legacy -bio_pair -tls1 -custom_ext => 0

../../util/wrap.pl ../../test/sslcorrupttest ../../apps/server.pem ../../apps/server.pem => 139
not ok 1 - running sslcorrupttest

#   Failed test 'running sslcorrupttest'
#   at test/recipes/80-test_sslcorrupt.t line 19.
# Looks like you failed 1 test of 1.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests

not ok 1 - running bio_enc_test

#   Failed test 'running bio_enc_test'
#   at /localhome/bamboo/bamboo-agent-home/xml-data/build-dir/ThirdParty/openssl/3.0.0/_src/openssl-3.0.0-src/openssl-3.0.0/util/perl/OpenSSL/Test/Simple.pm line 77.
# Looks like you failed 1 test of 1.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests

not ok 1 - running sslapitest

#   Failed test 'running sslapitest'
#   at test/recipes/90-test_sslapi.t line 32.
    # Subtest: ../../test/sslapitest

I hope these are some use to you, some don't seem to give much detail when using verbose logging.
As always, any help is appreciated. :)

There should be information before the failure message that provides the failure details.

My bad, the output is a bit too verbose to make sense of. Here's the raw output:
testoutput.txt

Looks like things are crashing with a common "chacha" theme. Possibly other issues. As an example:
../../util/wrap.pl ../../apps/openssl enc -chacha20 -k test -provider-path ../../providers -provider default -provider legacy -e -in ./testdatafile -out ./testdatafile.chacha20.cipher => 139
not ok 87 - chacha20

139 is typical of a segfault. Can you try the above "enc" command directly and see if you can replicate the crash?

Yes, I get a core dump but it looks like it could be corrupted?
-bash-4.4$ pwd
/localhome/bamboo/bamboo-agent-home/xml-data/build-dir/ThirdParty/openssl/3.0.0/_src/openssl-3.0.0-src/openssl-3.0.0/test-runs/test_evp_more
-bash-4.4$ ../../util/wrap.pl ../../apps/openssl enc -chacha20 -k test -provider-path ../../providers -provider default -provider legacy -e -in ./testdatafile -out ./testdatafile.chacha20.cipher
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
-bash-4.4$ gdb -e ../../apps/openssl -c core
HP gdb 6.5 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.
Copyright 1986 - 2011 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.5 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.

warning: Unknown symbols for 'core'; use the 'symbol-file' command.
Core was generated by `openssl'.
Program terminated with signal 11, Segmentation fault.
SEGV_MAPERR - Address not mapped to object
#0  0x60000000c62c8890 in <unknown_procedure> ()
(gdb) symbol-file
No symbol file now.
(gdb) bt
#0  0x60000000c62c8890 in <unknown_procedure> ()
warning: Attempting to unwind past bad PC 0x60000000c62c8890
#1  0x60000000c668db90 in <unknown_procedure> ()
(gdb)

@mattcaswell I have reproduce this crash on HPUX 32-bit.  I used gdb to look into the core file and this is the stack trace.
$ ../../apps/openssl enc -chacha20 -k test -provider-path ../../providers -provider default -provider legacy -e -in ./testdatafile -out ./testdatafile.chacha20.cipher
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
Segmentation fault (core dumped)
$ gdb ../../apps/openssl  core
HP gdb 6.7 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.
Copyright 1986 - 2011 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.7 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..
Core was generated by `openssl'.
Program terminated with signal 11, Segmentation fault.
SEGV_MAPERR - Address not mapped to object
#0  0x60000000c8008d70:0 in ChaCha20_ctr32+0x4b0 ()
   from /build/scottz/openssl-3.0.1-hpux-ipf32/libcrypto.so.3
(gdb) where
#0  0x60000000c8008d70:0 in ChaCha20_ctr32+0x4b0 ()
   from /build/scottz/openssl-3.0.1-hpux-ipf32/libcrypto.so.3
#1  0x60000000c8008000:0 in chacha20_cipher ()
    at ../openssl-3.0.1/providers/implementations/ciphers/cipher_chacha20_hw.c:89
#2  0x60000000c7fb1d30:0 in ossl_cipher_generic_stream_update ()
    at ../openssl-3.0.1/providers/implementations/ciphers/ciphercommon.c:469
#3  0x60000000c7fd1460:0 in EVP_EncryptUpdate ()
    at ../openssl-3.0.1/crypto/evp/evp_enc.c:628
#4  0x60000000c804b230:0 in EVP_CipherUpdate ()
    at ../openssl-3.0.1/crypto/evp/evp_enc.c:404
#5  0x60000000c81b7ca0:0 in enc_write ()
    at ../openssl-3.0.1/crypto/evp/bio_enc.c:266
#6  0x60000000c80c9c10:0 in bwrite_conv ()
    at ../openssl-3.0.1/crypto/bio/bio_meth.c:77
#7  0x60000000c7e4fbe0:0 in bio_write_intern ()
    at ../openssl-3.0.1/crypto/bio/bio_lib.c:362
#8  0x60000000c7e4fa30:0 in BIO_write ()
    at ../openssl-3.0.1/crypto/bio/bio_lib.c:381
#9  0x40c5000:0 in enc_main () at ../openssl-3.0.1/apps/enc.c:612
#10 0x40d0c60:0 in do_cmd () at ../openssl-3.0.1/apps/openssl.c:417
#11 0x406fde0:0 in main () at ../openssl-3.0.1/apps/openssl.c:311

@t8m Yes, configure with no-asm make test passes.

Are the crashes only in Chacha20 or also in other assembler implementations? One option would be to just disable the chacha20 asm implementation on 32bit Itanium.

@t8m Chacha20 was the one that crashes but there were other test failures that I had also reproduced (noted in the issue description).  These test failures do not occur when no-asm option was used in configure.

I've been able to build OpenSSL 3.0.9 with just chacha assembly disabled for HPUX 32-bit (native HP compiler) builds, and all tests are passing.  Other assembly code seems to work (passes tests at least).
What's a good way to separate out this one assembly module?  I did this, roughly:

used a new asm_arch, something like ia64_hpux32
updated all the assembly configurations in various build.info files to have definitions for xxx_ia64_hpux32 that are identical to regular xxx_ia64
except for crypto/chacha/build.info, where I did not define $CHACHAASM_ia64_hpux32

But maybe there's a better way?  Some way to do inheritance/override of the assembly architecture?

Please submit a PR, we can discuss it there.

I looked at the other (working) ia64 assembly sources for a while,
and think I see a difference here, but have no way to try it out.
Could you try this out for me?
--- a/crypto/chacha/asm/chacha-ia64.pl
+++ b/crypto/chacha/asm/chacha-ia64.pl
@@ -46,6 +46,8 @@ ChaCha20_ctr32:
        ADDP            @k[11]=4,$key
        .save           ar.lc,r3
        mov             r3=ar.lc                }
+{ .mmi;        ADDP            $out=0,$out
+       ADDP            $inp=0,$inp             }
 { .mmi;        ADDP            $key=0,$key
        ADDP            $counter=0,$counter
        .save           pr,r14

I looked at the other (working) ia64 assembly sources for a while,
and think I see a difference here, but have no way to try it out.
Could you try this out for me?

I can only test HP-UX itanium systems.  But looks good there:
For 32-bit HPUX, yes, that change eliminates all the exit code 139 (signal 11 failures) I was seeing in the test suites.
For 64-bit HPUX, with assembly enabled, the old code didn't hit any failures (passed all tests as of 3.0.9 for me), and the new code passes all the chacha tests.  (On master branch, my build environment can't run 04-test_bio_dgram.t nor 75-test_quicapi.t on any platforms, so those fail, but everything else passes for HP-UX 64-bit mode).

Thanks for testing my idea, that is exactly what I was looking for.
See #21681


Plot shows infinite spinner if some series can downsample but others can't

Description
If you have a plot w/ multiple series, an infinite loader is shown if some of the series can downsample while others can't.
Steps to reproduce
Run this Python
from deephaven import empty_table
t = empty_table(100000).update(["X=Instant.ofEpochMilli(ii)", "Y=ii", "Z=Y*2"])
plot_xy_scatter = (
    Figure()
    .plot_xy(series_name="Y", t=t, x="X", y="Y")
    .axes(plot_style=PlotStyle.SCATTER)
    .x_twin()
    .plot_xy(series_name="Z", t=t, x="X", y="Z")
    .show()
)

Expected results
Downsample error overlay
Actual results
Line series draws. Scatter does not. Plot loader shown infinitely and a browser error logged about needing to disable downsampling.
Versions
Engine Version: 0.34.0-SNAPSHOT
Web UI Version: 0.74.0
Java Version: 11.0.19
Barrage Version: 0.6.0
Browser Name: Chrome 123
OS Name: Linux

This is an issue as far back as Jackson: 1.20221001.343
Tested with the Groovy snippet:
t = emptyTable(100000).update("X=currentTime() + ii", "Y=ii", "Z=Y*2")
plotXyScatter = plot("Y", t, "X", "Y").plotStyle("scatter").twinX().plot("Z", t, "X", "Z").show()

Note it works if the scatter plot does not need downsampling, e.g.:
t = emptyTable(10000).update("X=currentTime() + ii", "Y=ii", "Z=Y*2")
t2 = emptyTable(100000).update("X=currentTime() + ii", "Y=ii", "Z=Y*2")
plotXyScatter = plot("Y", t, "X", "Y").plotStyle("scatter").twinX().plot("Z", t2, "X", "Z").show()

We should show the downsample error for that one series. If the user decides to dismiss the downsampling error, you should be able to see the other plots that were successful: https://github.com/deephaven/web-client-ui/pull/1850#discussion_r1516266855


[CS:GPU::Part 1] Add GPUShape type, conversion operators, and generalized shape helpers.

[ ] [CS:GPU::Part 1] Note: do not merge until all parts[1-4] have been reviewed and approved. After approvals: merge part 4 into 3, then 3 -> 2, 2 -> 1, and finally 1 -> master after CI passes.

This PR adds type GPUShape.

Conversion operators ensure tensor dimensions are not greater than 2^32 elements for the GPU backend.
The Shape helpers row_major_strides and shape_size are now specialized to allow for generic operability with different shape types.
Updated row_major_strides implementation to avoid reverse-copy.

Overall, the question is whether we will exceed 32 bits for a single axis. In our internal kernel implementations we can still utilize 64 bit where necessary.
For example, in the above case of a 4 dimensional tensor with each axis having 1000 elements, the GPU allocation will exceed 32 bits in the total number of elements (i.e. its shape_size will be > 2^32) as @fengleitian points out. Internally that is ok, because we will store that as size_t and we can index into the dense flat array as usual. The only thing GPUShape does is to ensure that a single axis does not exceed 2^32 elements because this is not supported in cuDNN descriptors.
If we make replacement kernels for each of the cuDNN ops that we can fall back to in these cases, then GPUShape wouldn't be needed. This doesn't require any changes to current CUDA kernels which support 64 bit tensor descriptors.

leave it for 32bit now, we can add 64bit support when we need. I was worried it will take more time to add 64bit support later than now.

TESTNOW


When changing the namespace, the workload remains in the old namespace

What happened:
When changing the namespace, the workload remains in the old namespace.

before
% kubectl get deployment -n test simple-hoge
NAME          READY   UP-TO-DATE   AVAILABLE   AGE
simple-hoge   2/2     2            2           12m

after
% kubectl get deployment -n test2 simple-hoge
NAME          READY   UP-TO-DATE   AVAILABLE   AGE
simple-hoge   2/2     2            2           7m8s

What you expected to happen:
It would be nice to delete the old resource successfully.
How to reproduce it:
Environment:

piped version:
control-plane version:
Others:

[Root cause]
Resources in the old namespace cannot be deleted because the namespace is not included in the conditions for searching the deletion target resources.
Inside PipeCD, resources are identified by four types: apiVersion, kind, namespace, and name.
However, based on the live state and the manifest on git, in the pruning phase, the deletion target seems to be searched for only three things except for the namespace.
https://github.com/pipe-cd/pipecd/blob/c0d5b795de2e89ff6d3c1b7221fb2480c094ce72/pkg/app/piped/executor/kubernetes/sync.go#L131C2-L144C3

NOTE:

For the same prune feature but in the config of PRIMARY_ROLLOUT we allow users to remove/prune the resource from previous/old namespace
This issue only happened if using prune feature in config of K8S_SYNC (QUICK_SYNC prune true)


No Transient Source

Hello,
I was wondering if it would be possible to implement a simple ConstantSource that is a Source but with no phase. That could for instance be a Star. It would only need a spectra.
Worse case scenario I could create a Source and then give phase=0 all the time, but that is a not so elegant.
Cheers

something like that I think work but is not nice
class ConstantSource(  sncosmo.TimeSeriesSource ):

    def __init__(self, wave, flux, name=None, version=None):
        #
        nphase_bins = 2
        phase = np.linspace(-1., 1., nphase_bins)
        # w
        return super().__init__(phase, wave, np.repeat(flux[None,:], nphase_bins, axis=0),
                                name=name, version=version, time_spline_degree=1)

    def bandmag(self, band, magsys):
        return super().bandmag(band, magsys, 0)

    def bandflux(self, band, zp=None, zpsys=None):
        """ """
        return super().bandflux( band, phase=0, zp=None, zpsys=None)

    def flux(self, wave):
        """ """
        return super().flux(0, wave)

Initially, I like the idea, but what is the story behind this feature? What would people want to accomplish with a constant source?

I am writting a simulation tool. I am using sncosmo to simulate them, and I would liek to be able to simulate stars !

That is exactly what needs to be done, but it changes the fundamental spirit of some core functions of sncosmo that expect phase_or_time.
But indeed the hierarchy should be something like
Source # very very generic
ConstantSource( Source ) # flux depend on band no time
VariableSource(Source ) # flux depend on band and time or Period
PeriodicSource( VariableSource) # like Cepheids !
Star( ConstantSource ) # here we could imaging having the calspec as default template
VariableSource would then be what is currently called Source
so TimeSeriesSource( VariableSource )

I have been thinking that SNCosmo could transition to a broader transient package. A change like this would need to be a new major release. We would also need to figure out how SNCosmo differs from other simulation tools like galsim. I wonder if it is best to let galsim focus on static sources, and we focus on transients.

Does https://sncosmo.readthedocs.io/en/stable/api/sncosmo.Spectrum.html work?


Won't import book if ' in the title

When downloading a book with an ' in the title it will not import. However, it will import if feed manually into Calibre Web Automated bypassing calibre-web-automated-book-downloader.
Seems like when it goes though calibre-web-automated-book-downloader it is failing to use the escape character on the ' when attempting to make the directory.   i.e using ' instead of \'
Calibre Web Automated logs show:
Traceback (most recent call last):
File "calibre/db/cache.py", line 1857, in set_metadata
File "calibre/db/cache.py", line 1780, in set_cover
File "calibre/db/backend.py", line 1769, in set_cover
File "os.py", line 225, in makedirs
PermissionError: [Errno 13] Permission denied: "/calibre-library/Lev Grossman/The Magician's Land (384)"
Traceback (most recent call last):
File "runpy.py", line 198, in _run_module_as_main
File "runpy.py", line 88, in _run_code
File "site.py", line 47, in
File "site.py", line 43, in main
File "calibre/db/cli/main.py", line 253, in main
File "calibre/db/cli/main.py", line 40, in run_cmd
File "calibre/db/cli/cmd_add.py", line 471, in main
File "calibre/db/cli/cmd_add.py", line 236, in do_add
File "calibre/db/cli/main.py", line 184, in run
File "calibre/db/cli/cmd_add.py", line 177, in implementation
File "calibre/db/cli/cmd_add.py", line 144, in book
File "calibre/db/cli/cmd_add.py", line 96, in do_adding
File "calibre/db/cli/cmd_add.py", line 53, in add_book
File "calibre/db/cache.py", line 2194, in add_books
File "calibre/db/cache.py", line 1979, in add_format
File "calibre/db/cache.py", line 1935, in _do_add_format
File "calibre/db/backend.py", line 1862, in add_format
File "os.py", line 225, in makedirs
PermissionError: [Errno 13] Permission denied: "/calibre-library/Lev Grossman/The Magician's Land (384)"

Hi !
Could you share your docker-compose ?
Also, which book are you trying to download ?
CWA-BD renames all books into {MD5}.epub so there should be no special characters
Also, it drops the books directly into the root of the folder, and does not create a sub directory
In your stack trace, it seems that some permission issues in your calibre-library folder
A 'hack' would be to just run chmod 777 /calibre-library/ this might help
Or change to the proper ownership


Configure proper log level for the standalone image

The log level is too verbose. Proposal will be to align the log at the same level as odm premise sample server

Closed in the dev branch


docs: self hosted s3(minio)

Area of Improvement
Either explain in the docs, why self-hosted s3(like minio) is not supported, or add support for it.
Link to related docs
No response
Additional information
No response
👨👧👦 Contributing

[ ] 🙋♂ Yes, I'd be down to file a PR implementing the suggested changes!

I see, this is a product and not only a library. 😅 I see self hosting will be an enterprise feature, so that explains why.


Update show_wlan.py

If there isn't a WiFi NIC connected to the WLAN Pi, the service will fail with the following message:
Feb 23 09:45:15 wlanpi python3[5907]: Traceback (most recent call last):
Feb 23 09:45:15 wlanpi python3[5907]:   File "/opt/wlanpi-chat-bot/wlanpi-chat-bot", line 146, in
Feb 23 09:45:15 wlanpi python3[5907]:     main()
Feb 23 09:45:15 wlanpi python3[5907]:   File "/opt/wlanpi-chat-bot/wlanpi-chat-bot", line 131, in main
Feb 23 09:45:15 wlanpi python3[5907]:     msg = GLOBAL_CMD_DICT[command].run(args_list)
Feb 23 09:45:15 wlanpi python3[5907]:   File "/opt/wlanpi-chat-bot/wlanpi_commands/show_wlan.py", line 122, in run
Feb 23 09:45:15 wlanpi python3[5907]:     return self._render(interface_info)
Feb 23 09:45:15 wlanpi python3[5907]: UnboundLocalError: local variable 'interface_info' referenced before assignment
The script "show_wlan.py" is using Regex to look for "wlan" in the output of ifconfig. If it's not there, the logic currently in place to check for that doesn't match to allow a more graceful failure.
Instead of "if interface_re is None:", "if not interface_re:" seems to work.

Thanks Keith!


Add --charset option to the db:dump command

# download this build
curl https://pr-832-kgcph7y-mpaw4nkgdwaea.eu-2.platformsh.site/platform.phar -o ./platform.phar

# create a dump with the utf8mb4 character set encoding
php platform.phar db:dump --charset utf8mb4

+1
that works for our use case.


Push jobs fails to install correctly

Description
push jobs fails to install correctly. some dependencies seem to be missing so it cannot start the service and fails
Push Jobs Client Version
2.2.0
Platform Version
Windows Server 2008R2
Replication Case
Method 1: use pushjobs cookbook to update the push jobs client to 2.2.0 > Result is pushjobs service fails to start
Method 2: uninstall manually old version and install version 2.2.0 from scratch > > Result is pushjobs service fails to start
Method 3: manually run installer for 2.2.0 without uninstalling old version first > Result is pushjobs service fails to start
Stacktrace
[2017-04-04T14:39:12-04:00] FATAL: SystemCallError: windows_service[push-jobs-client] (push-jobs::service_windows line 6
3) had an error: SystemCallError: The service did not respond to the start or control request in a timely fashion. - Sta
rtService: The service did not respond to the start or control request in a timely fashion.

PS C:\Users\Administrator> c:\opscode\push-jobs-client\embedded\bin\ruby.exe c:\opscode\push-jobs-client\embedded\lib\ru
by\gems\2.3.0\gems\opscode-pushy-client-2.2.0\lib\pushy_client\windows_service.rb -c C:\chef/push-jobs-client.rb
Unable to load this gem. The libzmq library (or DLL) could not be found.
If this is a Windows platform, make sure libzmq.dll is on the PATH.
If the DLL was built with mingw, make sure the other two dependent DLLs,
libgcc_s_sjlj-1.dll and libstdc++6.dll, are also on the PATH.
For non-Windows platforms, make sure libzmq is located in this search path:
["C:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/ffi-rzmq-core-1.0.5/lib/ffi-rzmq-core/../../ext/libzmq.d
ll", "%SystemRoot%\\system32\\WindowsPowerShell\\v1.0\\/libzmq.dll", "c:\\Program Files\\7-Zip\\/libzmq.dll", "C:\\Windo
ws\\system32/libzmq.dll", "C:\\Windows/libzmq.dll", "C:\\Windows\\System32\\Wbem/libzmq.dll", "C:\\Windows\\System32\\Wi
ndowsPowerShell\\v1.0\\/libzmq.dll", "C:\\opscode\\chef\\bin\\/libzmq.dll", "C:/opscode/push-jobs-client/embedded/lib/li
bzmq.dll", "/usr/local/lib/libzmq.dll", "/opt/local/lib/libzmq.dll", "/usr/lib64/libzmq.dll"]
C:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/ffi-rzmq-core-1.0.5/lib/ffi-rzmq-core/libzmq.rb:57:in `res
cue in <module:LibZMQ>': The libzmq library (or DLL) could not be loaded (LoadError)
        from C:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/ffi-rzmq-core-1.0.5/lib/ffi-rzmq-core/libzmq.
rb:10:in `<module:LibZMQ>'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/ffi-rzmq-core-1.0.5/lib/ffi-rzmq-core/libzmq.
rb:7:in `<top (required)>'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `re
quire'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `re
quire'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/ffi-rzmq-core-1.0.5/lib/ffi-rzmq-core.rb:3:in
 `<top (required)>'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `re
quire'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `re
quire'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/ffi-rzmq-2.0.4/lib/ffi-rzmq.rb:66:in `<top (r
equired)>'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `re
quire'
        from C:/opscode/push-jobs-client/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `re
quire'
        from c:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/opscode-pushy-client-2.2.0/lib/pushy_client/p
rotocol_handler.rb:18:in `<top (required)>'
        from c:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/opscode-pushy-client-2.2.0/lib/pushy_client.r
b:21:in `require_relative'
        from c:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/opscode-pushy-client-2.2.0/lib/pushy_client.r
b:21:in `<top (required)>'
        from c:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/opscode-pushy-client-2.2.0/lib/pushy_client/w
indows_service.rb:25:in `require_relative'
        from c:/opscode/push-jobs-client/embedded/lib/ruby/gems/2.3.0/gems/opscode-pushy-client-2.2.0/lib/pushy_client/w
indows_service.rb:25:in `<main>'

Downgrading to 2.1.4 is the current workaround.

Created internally as BUG-409.


feat(e2e): add e2e workflows, uptest and fix exmaples

Description of your changes

fix a few issues in v0.1.0 like:

    case.go:363: XServiceAccount.platform.acme.co "Xserviceaccount1" is invalid: metadata.name: Invalid value: "Xserviceaccount1": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
    case.go:363: Subnetwork.platform.acme.co "subnetwork1" is invalid: [spec.parameters.ipCidrRange: Required value, spec.parameters.networkRef: Required value, spec.parameters.region: Required value]

add uptest e2e workflows
test configuration with uptest
fix examples
enable renovate

Fixes #
I have:

[x] Read and followed Upbound's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested
--- PASS: kuttl (92.09s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/case (91.58s)
PASS
19:28:16 [ OK ] running automated tests

we need to add a few CI Variables that the workflows will work XPKG_ACCESS_ID and XPKG_TOKEN because automatic build and push is missing here ;) v0.1.0 is done by hand i guess

Yes, publishing was done by hand because I figured the image shouldn't be changing much.


Application form

design changes in compare applicants

:tada: This PR is included in version 1.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Feature]: Add Discord

Package Scope

[x] Add to an existing package

Package name: @suspensive/docs
Overview

Describe the solution you'd like

Additional context

@minsoo-web Could you lead us this?

Of course! It is my pleasure

@minsoo-web Could you share your approximate end date?

Sorry for late reply. I will do this at least tomorrow

Our new Discord https://discord.gg/cmz6NfrNCM

I'm going to configure the Discord server more and close this issue. (Add apps, add web hooks, etc.)

@minsoo-web I remind you softly

Thank you, it's a work I've forgotten. I'll give you a notification after I finish this work


Added support of AMD and common.js module

added support of AMD module (e.g. for require.js) and common.js (e.g. for browserify)
Could you please publish this as npm package?
How to publish NPM package

Thanks. I will publish Waves on npm as soon as possible.

keep in mind that there is already a package names "waves" in npm - https://www.npmjs.com/package/waves

Noted. I put it under node-waves.


Can you add a default loading progress dialog?

I think this should be included in the package.

It wouldn't be any different from the stock progress dialog, so it would be redundant


KNL-1400; mail from yahoo not working

I believe this is the approach that the core team agreed to in the last call.
After trying it, I don't think we need "On behalf of," though you can configure it as an option. The advantage of not having text is that it isn't language-dependent.
So the default behavior is to always replace the From with postmaster, and move the original value to reply-to. Exception: addresses using the Sakai server name.
Options:

disable
configure a regex for addresses that won't be replaced
configure text, e.g. "On behalf of {}"
configure a from address other than postmaster

I think I've tried all the options.

When we can find a Java library for DMARC, it can be used rather than (or together with) the regex to control when the replacement happens.


 Would you mind doing a new PR against https://github.com/narmitech/react-native-os for the other commit? I've been made a maintainer of the NPM package and we'll move development to that fork.

Done

Hi @staltz, I don't have contributor rights on this repo specifically, but I've cherrypicked your commit here: https://github.com/aprock/react-native-os/commit/8dfb18bbaa3abfa0f2d9b96a79636abf45edf473. And published a new version https://www.npmjs.com/package/react-native-os.

Given that your repo is being published on npm, I find it sufficient that work continues on that repo. Thanks for cherry-picking. :)


feature: S3C-3568 Convert Existing Marshalling/ Unmarshalling to Generic

Moved the existing basic and common code (like initiating, invoking Vault API) to BaseServicesClient.
So AccountServicesClient will hold only business logic for Account related web Services
Converted the existing Marshalling/Unmarshalling classes to Generic Marshalling/Unmarshalling classes to ease future engineering. All the future developments can just extend the generic classes with ease.

Note to Reviewers:

Please go through each and every commit to get detailed understanding of the changes

Hello saitharunthodupunuru,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

/approve

In the queue
The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.
The changeset will be merged in:

:heavy_check_mark: development/1.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.
The following options are set: approve

I have successfully merged the changeset of this pull request
into targetted development branches:

:heavy_check_mark: development/1.0

Please check the status of the associated issue S3C-3568.
Goodbye saitharunthodupunuru.


[zero] _apply_to_tensors_only handle torch.Tensor subclasses

In a complex code base I run into this warning:

[WARNING] [parameter_offload.py:55:_apply_to_tensors_only] A module has unknown inputs or outputs type (<class 'torch.nn.parameter.Parameter'>) and the tensors embedded in it cannot be detected. The ZeRO-3 hooks designed to trigger before or after backward pass of the module relies on knowing the input and output tensors and therefore may not get triggered properly.

But torch.nn.parameter.Parameter is a subclass of torch.Tensor.
This PR fixes this by replacing the exact check for torch.Tensor with a more flexible check that includes its subclasses as well.
Thank you!
@tjruwase

the megatron CI failure seems to be related to a wrong numpy version - unrelated to this PR

Funny enough, I added similar code in an old PR w. @awan-10: https://github.com/microsoft/DeepSpeed/pull/2127/commits/0ec57a41f90b0c62d43b25845c2b1a2016cc20ec. The CI logs won't load anymore but I recall it was removed it due to a test failing for a strange reason we didn't understand at the time (https://github.com/microsoft/DeepSpeed/pull/2127/commits/7ef1ca8583c3d5a36431985777347db754355b6f). If all the tests pass now then that's wonderful :)

@jeffra, in:
elif isinstance(outputs, (torch.Tensor, torch.nn.parameter.Parameter)):

if i'm not mistaken torch.nn.parameter.Parameter will never be reached because it's a subclass of torch.Tensor so the first check will always succeed for an output type of either of the 2.

@jeffra, in 0ec57a4:
elif isinstance(outputs, (torch.Tensor, torch.nn.parameter.Parameter)):

if i'm not mistaken torch.nn.parameter.Parameter will never be reached because it's a subclass of torch.Tensor so the first check will always succeed for an output type of either of the 2.

I agree, I believe my old commit and yours will do the same thing. But the current code in master will only match on Tensor and not Parameter. I recall something strange happened previously when including Parameters, but hopefully it’s resolved now since it’s been almost 6mo

and if there is a problem, should it not assert and not warn and do nothing? it's so so difficult to notice these warnings - there are so many logs.

and if there is a problem with the model, should it not assert and not warn and do nothing? it's so so difficult to notice these warnings - there are so many logs.
My personal opinion is that warnings should be completely eliminated in modern software - at least in the DL software with tens of thousands of logs. If there is a problem assert, if there is no problem move along.
Also this particular warning doesn't tell user much about what to do to solve it. The wording makes sense to the designer of the deepspeed code but is not very actionable for the user reading it. IMHO. As you can see I tried to fix the warning rather than try to understand why it was triggered as I have no idea what the problem is.

It appears the test failed. I agree with you I think warnings are way too easy to get ignored and in this case also agree it's not even clear what the user should do.
Notice the output of the print statements:
class DanglingAttention(torch.nn.Linear):
    def __init__(self, dim=16, return_obj=False):
      ....

    def forward(self, input):
        out = super().forward(input)
        if self.return_obj:
            out_obj = self.d_linear(out)
            assert out_obj.bias.ds_status == ZeroParamStatus.AVAILABLE
            # forward the external param
            return out_obj.out, out_obj.bias
        else:

          out, bias = self.d_linear(out)
          print(f"Parameter Ids: {[id(p) for p in self.d_linear.parameters()]}")
          print(f"Original vs returned bias id: {(id(self.d_linear.bias), id(bias))}")
          assert self.d_linear.bias.ds_status == ZeroParamStatus.AVAILABLE
          return out, bias

Output:
Parameter Ids: [139751043104336,<PHONE_NUMBER>04416]
Original vs returned bias id:<PHONE_NUMBER>04416,<PHONE_NUMBER>70176)

The assertion fails because bias is not the same as self.d_linear.bias. The latter is part of the module as you can see the id matches one of the parameter IDs of the module and has been converted in a ZeRO3 parameter, but the former has a different id.
Looks like python function might be making a copy of the tensor before returning it.

Thank you for the investigation, @samyam. always awesome to hear your insights!
Once we remove the recursive list/dict handling _apply_to_tensors_only can be reduced to just (pseudo-code):
if outputs is torch.Tensor:
 return functional.apply(module, backward_function, outputs)
else:
 return outputs

and this PR changes it to do that for any subclass of torch.Tensor.
and so you're saying that backward_function mutates the tensor and strips all the deepspeed paritioned tensor metadata from it.
Should it then check if it's a non-partitioned DS tensor instead?

@stas00, @samyam and I deep dived this issue and think we figured out what is going on. Samyam created a new PR from your branch and pushed it here: https://github.com/microsoft/DeepSpeed/pull/2642
It appears that the bias parameter was being registered which is good but that the returned bias was modified (thus new object id) which meant it was lost. We modified the way zero handles this case to stash the original parameter so it can be updated in the external parameters dictionary correctly.

Closing as https://github.com/microsoft/DeepSpeed/pull/2642 is covering this now


html-preview job fails

Run larsoner/circleci-artifacts-redirector-action@master
  with:
    repo-token: ***
    artifact-path: 0/html/index.html
    circleci-jobs: html_demo
Error: Cannot read properties of undefined (reading 'length')

Here is the solution: https://github.com/larsoner/circleci-artifacts-redirector-action/issues/40#issuecomment-1505543564


Assess sample ADT messages for ETOR (TI)

User Story
As an ETOR sender/receiver, I want to be sure that the messages going through the Universal Pipeline are properly converted/translated.
Description/Use Case
We received a few sample messages from the Flexion team that model the messages that will go through the Universal Pipeline for the TI ETOR support. We should assess those messages to identify any gaps so that we can address those as soon as we can. This ticket focuses on the sample ADT message.
Risks/Impacts/Considerations
In early attempts, the sample ADT message was not able to go through the pipeline at all. It's unclear whether that is due to the specifics of the sample, or some shortcoming on our end or in the HAPI library. The causes for failures so far should be investigated and handled as part of this ticket. If any blockers come up that warrant a separate ticket or separate discussion, that can happen as well.
Dev Notes
This spreadsheet shows an example of how similar assessments have been completed in the past, with one major difference in this case being that we'll be converting the ADT message to FHIR. This thread covers the sample messages, which are also present in the Trusted Intermediary repo here.
These messages would be used at different points in the overall ETOR process, so the architecture diagram here can provide useful context. An ADT message would represent the HL7v2 we would receive from a hospital and send to TI as FHIR.
Acceptance Criteria

[ ] An ADT sample message has been sent through the pipeline
[ ] The Flexion team has been provided with a Postman collection or curl command that can be used to send the message to ReportStream in the staging environment
[ ] Input/output differences have been recorded in some spreadsheet in sharepoint
[ ] Follow-up tickets to address differences have been created (if needed)

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jack-h-wang @JessicaWNava @jimmyfagan @luis-pabon-tf @mkalish @thetaurean

Please add your planning poker estimate with Zenhub @JFU-NAVA-PBC

@thetaurean just checking on status of this ticket


[NS] Remove chevron scories from git

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


Error when import requests

I have the following error that I don't understand when I import requests
/Users/mathieu/Code/Python/masto-bookmarks/lib/python3.9/site-packages/urllib3/__init__.py:34: NotOpenSSLWarning: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with 'LibreSSL 2.8.3'. See: https://github.com/urllib3/urllib3/issues/3020
  warnings.warn(

Updating to python 3.11.5 solved the issue 🤓


Install on ubuntu14 : could not insert 'uvcvideo'

Required Info

Camera Model
SR300

Firmware Version
???

Operating System & Version
Linux (Ubuntu 14)

Kernel Version (Linux Only)
(4.4.0-040400)

Platform
PC

SDK Version
????

Issue Description
I am installing librealsense following the doc
I installed it step by step according to the instructions until the 4th step in Video4Linux backend preparation: ./scripts/patch-realsense-ubuntu-xenial.sh .
There came an error:

Handle uvcvideo :  Applying the patched module ... modprobe: ERROR: could not insert 'uvcvideo': Invalid argument
Failed to insert the patched module. Operation is aborted, the original module is restored
Verify that the current kernel version is aligned to the patched module version
modprobe: ERROR: could not insert 'uvcvideo': Invalid argument

In the previous installation process, there are two things I'm not sure about. I don't know if this is related to the error.

After updating Ubuntu, I reboot the computer and at Grub2 Boot Menu -> "Advanced Options for Ubuntu" , I selected the top one 'ubuntu Linux 4.4.0-040400', (I think the latest updated kernel version is probably at the top.) While there are some other kernel version  underneath it such as Linux 4.4.0-119xxx and 4.4.0-116xxx...Do I choose the right kernel version?
When it runs ./scripts/patch-realsense-ubuntu-xenial.sh, there are too many options I don't understand, for example,  Appraise integrity measurements (IMA_APPRAISE) [Y/n/?]
I press the Enter key all the time and I think this is the default option. Is it right to do this ?

[Realsense Customer Engineering Team Comment]
Hi @dan0910,
You can try below instructions to install DKMS package directly without running the patch script. Ubuntu 16.04 is recommended.
https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md

Hi @RealSense-Customer-Engineering ,
Thank you for your reply.
My system is ubuntu14, and the kernel version is 4.4.0-040400. Need I upgrade my system to ubuntu16? (I need ubuntu14 for ros-indigo development…)
I follow the instructions to install DKMS package (ubuntu14) .  But when I run realsense-viewer , it comes:

realsense-viewer: relocation error: /usr/lib/x86_64-linux-gnu/librealsense2.so.2: symbol _ZTVNSt7__cxx1119basic_istringstreamIcSt11char_traitsIcESaIcEEE, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference

[Realsense Customer Engineering Team Comment]
Hi @dan0910,
Per my test configuration: Ubuntu 14.04.5 + Kernel 4.4.0-119 + DKMS package, to build the realsense-viewer app from the source code of librealsense 2.10.3, the app can run normally without your link issue. Please check if the library installed and linked  is correct.

[Realsense Customer Engineering Team Comment]
Hi @dan0910,
If no further issue, will close this.


Add crypto hash of all files, perhaps to PackageArchiveEntries or another table

Right now we only have it on some files in PackageContents table and PackageAssemblies table.
Workaround is Crc32 + file size on PackageArchiveEntries but this is not a crypto hash with all of its strength.

Done with https://github.com/NuGet/Insights/commit/a05b7d0218837a991e26390e1a622aabe12ba821.


SchemaFieldNotFoundError When Loading Preprocessed Data

Current Behavior
When loading preprocessed data using the Dataset.load() method with the preprocessed=True flag, I encounter a SchemaFieldNotFoundError related to the trialId column. The preprocessed data already has renamed columns, and the error occurs because the renaming operation is performed again, regardless of whether the data is preprocessed or not.
Expected Behavior
The preprocessed data should be successfully loaded without any errors.
Minimum Acceptance Criteria

[ ] Ensure the dataset.load(preprocessed=True) can correctly load preprocessed data without column renaming issues.

Failure Information (for bugs)
Steps to Reproduce

Load the JuDo1000 public dataset.
Perform preprocessing steps like pix2deg and pos2vel.
Save the preprocessed data using dataset.save().
Attempt to reload the saved preprocessed data using dataset.load(preprocessed=True).

Code to Reproduce
dataset = pm.Dataset('JuDo1000', path='/mnt/scratch/chwastek/datasets/Judo1000/')
dataset.download()
dataset.load(subset={'subject_id': 1})

dataset.pix2deg()
dataset.pos2vel(method='savitzky_golay', window_length=7, degree=2)

dataset.save()
dataset.load(preprocessed=True)

Error Log
---------------------------------------------------------------------------
SchemaFieldNotFoundError                  Traceback (most recent call last)
Cell In[33], line 9
      6 dataset.pos2vel(method='savitzky_golay', window_length=7, degree=2)
      8 dataset.save()
----> 9 dataset.load(preprocessed=True)

File /mnt/scratch/chwastek/anaconda3/lib/python3.11/site-packages/pymovements/dataset/dataset.py:122, in Dataset.load(self, events, preprocessed, subset, events_dirname, preprocessed_dirname, extension)
    119 self.scan()
    120 self.fileinfo = dataset_files.take_subset(fileinfo=self.fileinfo, subset=subset)
--> 122 self.load_gaze_files(
    123     preprocessed=preprocessed, preprocessed_dirname=preprocessed_dirname,
    124     extension=extension,
    125 )
    127 if events:
    128     self.load_event_files(
    129         events_dirname=events_dirname,
    130         extension=extension,
    131     )

File /mnt/scratch/chwastek/anaconda3/lib/python3.11/site-packages/pymovements/dataset/dataset.py:187, in Dataset.load_gaze_files(self, preprocessed, preprocessed_dirname, extension)
    159 """Load all available gaze data files.
    160
    161 Parameters
   (...)
    184     If file type of gaze file is not supported.
    185 """
    186 self._check_fileinfo()
--> 187 self.gaze = dataset_files.load_gaze_files(
    188     definition=self.definition,
    189     fileinfo=self.fileinfo,
    190     paths=self.paths,
    191     preprocessed=preprocessed,
    192     preprocessed_dirname=preprocessed_dirname,
    193     extension=extension,
    194 )
    195 return self

File /mnt/scratch/chwastek/anaconda3/lib/python3.11/site-packages/pymovements/dataset/dataset_files.py:216, in load_gaze_files(definition, fileinfo, paths, preprocessed, preprocessed_dirname, extension)
    205     filepath = paths.get_preprocessed_filepath(
    206         filepath, preprocessed_dirname=preprocessed_dirname,
    207         extension=extension,
    208     )
    210 gaze_data = load_gaze_file(
    211     filepath=filepath,
    212     preprocessed=preprocessed,
    213     custom_read_kwargs=definition.custom_read_kwargs,
    214 )
--> 216 gaze_data = gaze_data.rename(definition.column_map)
    218 # Add fileinfo columns to dataframe.
    219 gaze_data = add_fileinfo(
    220     definition=definition,
    221     df=gaze_data,
    222     fileinfo=fileinfo_row,
    223 )
    .......
    SchemaFieldNotFoundError: trialId

Relevant Code Snippets
The datasets DatasetDefinition describes a column_map for renaming columns in the raw input data.
column_map: dict[str, str] = field(
    default_factory=lambda: {
        'trialId': 'trial_id',
        'pointId': 'point_id',
    },
)

I tested by running the code with removing the column map, and it worked:
dataset = pm.Dataset('JuDo1000', path='/mnt/scratch/chwastek/datasets/Judo1000/')
dataset.definition.column_map = {}
dataset.load(preprocessed=True)

Context

Project Version / Commit: 0.17.0
Operating System: Linux

Checklist

[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I have provided sufficient information for the team

we should integrate:
dataset.save()
dataset.load(preprocessed=True)
to our integration-test

Thank you for creating this bug report!

we should integrate: dataset.save() dataset.load(preprocessed=True) to our integration-test

Actually this is a functional tests you are talking about, and this should go into a new file called dataset_processing.py in the functional tests directory.
Of course adding it to the integration tests won't hurt, but remember:

Integration tests test the integration with 3rd party systems (this way we can identify e.g. faulty dataset definitions).
Functional tests test use cases (like in your example, loading in a dataset, do preprocessing, saving, and loading the data again)

Wouldn't it be necessary to extend the databases test files to at least 2 files for each dataset to properly test loading. Otherwise I would need to adjust the filename format and thus leave out parsing the attributes in filenames.


[BEAM-10959] Fix circle buffer.

Fix the off by one error in the circle buffer.
I originally intended to clean up the abstraction for better unit testing but it would lose significant clarity since we only sometimes add to the remove queue, and we also GC failed bundles, and try to put that into an abstraction for testing.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @youngoli


fix for windows

Codecov Report

Merging #17 into master will decrease coverage by 0.28%.
The diff coverage is 29.62%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   68.96%   68.68%   -0.29%
==========================================
  Files          17       17
  Lines        2365     2382      +17
==========================================
+ Hits         1631     1636       +5
- Misses        587      595       +8
- Partials      147      151       +4

Impacted Files
Coverage Δ

udp.go
88.88% <0%> (-7.12%)
:arrow_down:

client.go
60.37% <34.78%> (-1.44%)
:arrow_down:

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 25e7527...285697b. Read the comment docs.


Dartanalyzer reports error message for sync* and async* functions in a strong mode

class TestItearble<E> extends Iterable<E> {

  @override
  Iterator<E> get iterator => null;
}

TestItearble c() sync* { } // [error] Functions marked 'sync*' must have a return type assignable to 'Iterable'

main() {
  Iterable i = new TestItearble(); // Ok here
  c();
}

In a strong mode analyzer reports that "Functions marked 'sync*' must have a return type assignable to 'Iterable'". But TestItearble from above has type assignable to Iterable. Seems that there should be no error message at all.
The same issue exists for async* functions
import 'dart:async';

class TestStream<T> extends Stream<T> {

  @override
  StreamSubscription<T> listen(void onData(T event),
      {Function onError, void onDone(), bool cancelOnError}) => null;
}

TestStream c() async* { }// [error] Functions marked 'async*' must have a return type assignable to 'Stream'

main() {
  c();
}

There are two parts to this bug: the error message that isn't "correct", and the question if we should even allow it.
Clearly, the sync* and async* will never return a subclass of Iterable/Stream, so the analyzer is right in telling users that this will not work.
However, I don't think that the language currently prohibits implicit downcasts in the return type for sync* and async* functions. I opened https://github.com/dart-lang/sdk/issues/27470 for the language.

this was an intentional strong mode bug fix. Your return type of TestStream will always fail. Offhand I don't remember the bug but I might be able to dig it up.

This was https://github.com/dart-lang/sdk/issues/25854.

The message is wrong, though.
The given return type is assignable to Iterable.

sure, we can tweak the wording. The return type must be Iterable<T> for some T.

It can also be Object.

Spec is now changed to "must be a supertype of Iterable<T> for some T" (basically, must be a supertype of Iterable<⊥>).
That also allows dynamic and Object, as well as Iterable<T>, but doesn't allow any subclass of Iterable.
If it is, e.g., Iterable<int> then the yield sematnics will complain if it isn't yielding int values.

this error message could still be improved.

This error is still present. ☹


Error: Failed to read the given file as a state or plan file

I tried using the standard plan file, and the JSON file, either way, I get a complaint about the "version" missing. Confused because the documentation doesn't say anything about converting the binary output file to JSON before parsing it - or maybe it's failing it's own internal JSON parsing because of the version mismatch? I use tfenv in the pipeline to set the version for whatever the workspace is using - in this case my workspace is using 1.5.5, but it looks like the task is defaulting to whatever the latest version is.
Assuming it's just a version issue, is there a way to force the task to use a specific version? Or somehow allow it to be dynamic enough to read the currently used terraform version? I'm using the -chdir flag to hot swap workspaces within the pipeline, which, incidentally is the same as the below parameter: ${{ parameters.workspace }}
  - task: TerraformOutput@1
    displayName: Terraform Show
    inputs:
      outputFilePath: $(Build.ArtifactStagingDirectory)/output.tfplan
      artifactName: ${{ parameters.workspace }}

Starting: Terraform Show
==============================================================================
Task         : Terraform Load Output
Description  : Load Terraform Output into Terraform Tab
Version      : 1.1.34
Author       : Jayden Maalouf
Help         :
==============================================================================
##[error]Terraform Output failed with Exit Code: 1
      Error Message: ╷
│ Error: Failed to read the given file as a state or plan file
│
│ State read error: Error reading /agent/_work/1/a/output.tfplan as a
│ statefile: 2 problems:
│
│ - Unsupported state file format: The state file could not be parsed as
│ JSON: syntax error at byte offset 1.
│ - Unsupported state file format: The state file does not have a "version"
│ attribute, which is required to identify the format version.
│
│ Plan read error: plan file was created by Terraform 1.5.5, but this is
│ 1.5.7; plan files cannot be transferred between different Terraform
│ versions
╵

Try running the Terraform installer (available in the Microsoft Terraform extension) before executing the Terraform Show task
steps:
  - task: TerraformInstaller@0
    displayName: Install Terraform v1.5.7
    inputs:
      terraformVersion: 1.5.7
  - task: TerraformOutput@1
    ...


bad option: --force

I have some issues after installing macOS Mojave.
Can't use gulp-grunt with node 11.1.0:
/usr/local/Cellar/node/11.1.0/bin/node: bad option: --force
/usr/local/Cellar/node/11.1.0/bin/node: bad option: --force=true

Even grunt-cli installing doesn't help ( https://stackoverflow.com/questions/52150323/grunt-force-fails-with-node-bad-option?rq=1 )
When I pass param:
require('gulp-grunt')(gulp, {
force: false
});
I still get:
/usr/local/Cellar/node/11.1.0/bin/node: bad option: --force=false

My pull request with fix:
https://github.com/maxov/gulp-grunt/pull/34


"k2cli version" blows up

Probably because none of the input strings have non-nil values.

can we get a full description of the issue please.

I've seen this break before, but interestingly, I can not recreate it now. I get,
rodin:go dwat$ k2cli version
1.0.5-alpha+git.sha.e04ae0d98289565ab71424fd7b83072bfaed8f66
rodin:go dwat$

This is what I get, is that what you're seeing @NathanZook ?
Invalid character(s) found in major number "-alpha+git"
panic: Invalid character(s) found in major number "-alpha+git"

goroutine 1 [running]:
panic(0x425540, 0xc42024b730)
	/usr/local/go/src/runtime/panic.go:500 +0x1a1
github.com/samsung-cnct/k2cli/cmd.glob..func22(0x6ebfa0, 0x70f580, 0x0, 0x0)
	/Users/guineveresaenger/samsung/go/src/github.com/samsung-cnct/k2cli/cmd/version.go:36 +0x270
github.com/samsung-cnct/k2cli/vendor/github.com/spf13/cobra.(*Command).execute(0x6ebfa0, 0x70f580, 0x0, 0x0, 0x6ebfa0, 0x70f580)
	/Users/guineveresaenger/samsung/go/src/github.com/samsung-cnct/k2cli/vendor/github.com/spf13/cobra/command.go:636 +0x443
github.com/samsung-cnct/k2cli/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x6e9fc0, 0xc420171ee8, 0x5f8b, 0xc42006e058)
	/Users/guineveresaenger/samsung/go/src/github.com/samsung-cnct/k2cli/vendor/github.com/spf13/cobra/command.go:722 +0x367
github.com/samsung-cnct/k2cli/vendor/github.com/spf13/cobra.(*Command).Execute(0x6e9fc0, 0xc4200d6b40, 0x0)
	/Users/guineveresaenger/samsung/go/src/github.com/samsung-cnct/k2cli/vendor/github.com/spf13/cobra/command.go:681 +0x2b
github.com/samsung-cnct/k2cli/cmd.Execute()
	/Users/guineveresaenger/samsung/go/src/github.com/samsung-cnct/k2cli/cmd/root.go:65 +0x31
main.main()
	/Users/guineveresaenger/samsung/go/src/github.com/samsung-cnct/k2cli/main.go:23 +0x22

This sounds like a type error, probably expecting number type and getting something alphanumeric.

@guineveresaenger can i see what you have in cmd/version.go?

@alejandroEsc here you go (no pun intended)
// Copyright © 2016 Samsung CNCT
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
//     http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

package cmd

import (
	"fmt"
	"github.com/blang/semver"
	"github.com/spf13/cobra"
)

var K2CliMajorMinorPatch string
var K2CliType = "alpha"
var K2CliGitCommit string

// versionCmd represents the version command
var versionCmd = &cobra.Command{
	Use:   "version",
	Short: "Display cli version",
	Long:  `Display cli version information`,
	Run: func(cmd *cobra.Command, args []string) {
		semVer, err := semver.Make(K2CliMajorMinorPatch + "-" + K2CliType + "+git.sha." + K2CliGitCommit)
		if err != nil {
			fmt.Println(err)
			panic(err)
		}
		fmt.Println(semVer.String())
	},
}

func init() {
	RootCmd.AddCommand(versionCmd)
}

@guineveresaenger could you add the first 10 lines of your Makefile.? I do find it interesting that k2clitype is hardcoded with alpha there....

NAME      := k2cli
VERSION   := 1.0.5
TYPE      := alpha
COMMIT    := $(shell git rev-parse HEAD)
godep=GOPATH=$(shell godep path):${GOPATH}

build:
	@godep go build -ldflags "-X github.com/samsung-cnct/k2cli/cmd.K2CliMajorMinorPatch=$(VERSION) \
		-X github.com/samsung-cnct/k2cli/cmd.K2CliType=$(TYPE) \
		-X github.com/samsung-cnct/k2cli/cmd.K2CliGitCommit=$(COMMIT)"

this will occur if you run k2cli version with a version of k2cli that you have built yourself.  This subcommand only currently works for versions that have gone through the release process.

hmm, I am not seeing that @coffeepac, running k2cli install locally, and using the file in the binary go path.

@alejandroEsc 'k2cli installed locally' do you mean via brew? or are you running something that you did a go build on yourself?

i do not mean brew, I am assuming this ticket has nothing to do with brew, so what i mean when i say i ran locally i mean ~/Development/go/bin/k2cli version and i ran go install on my local k2cli git directory which looks like ~/Development/go/src/github.com/samsung-cnct/k2cli/

interesting!  I'm quite surprised.  what is the output you're getting from calling ~/Development/go/bin/k2cli version?

1.0.5-alpha+git.sha.4ae8cd60beb7b1415a4b70a1beade2d98e66dea4```

in addition:

go version go1.8.3 darwin/amd64

Note, that I did want full context in the issue description. So we can avoid these type of environment questions etc.. and we can reproduce these things correctly.

Think we can close this. @alejandroEsc's post above suggests that k2cli version does not panic for him. There is no evidence this occurs unless the user compiles k2cli themselves without setting the necessary build variables.


Add mobile support for cryptopunks component

Related to #378
Note : Please disable TransactionsOnChain component while previewing, as it causes width to increase more than 100vh and displaces all other sections.

But it is working nicely! I will merge it when you address the comments


Reimplement federation with Rancher Prometheus

Use the Prometheus CRD additionalScrapeConfigs instead of a ServiceMonitor to configure federation. This way, honor_labels should be working correctly.
Fixes #13
Checklist

[x] Keep pull requests small so they can be easily reviewed.
[ ] Update the documentation.
[x] Link this PR to related issues.

Note, as a side-effect of this change, the namespace selector configured in https://github.com/projectsyn/component-rancher-monitoring/blob/1ac18cd9cfa34fc9756dd70fc069a91505f855a3/component/rules.jsonnet#L168 actually has an effect now, and alerts will only be generated for namespaces belonging to Kubernetes, Rancher or Project Syn.
I will create a follow-up PR to make this namespace selector configurable through the hierarchy.


Support Kotlin Gradle DSL

This: fun methodMissing(name: String, args: Any): Any is not practical to use with Kotlin Gradle DSL.
This is also not typesafe.

For anyone wanting to use the SqlDelight Gradle plugin from Gradle Kotlin DSL until this issue is solved, here's a small example that should work:
sqldelight {
    methodMissing("MyDatabase", arrayOf(closureOf<SqlDelightDatabase> {
        packageName = "com.example.db"
        sourceFolders = listOf("db")
        schemaOutputDirectory = file("build/dbs")
        dependency project(":OtherProject")
    }))
}

Does anyone have a build.gradle.kts example?  I can't get the sqldelight stanza to even be accepted although the plugin appears to have been loaded.

@nwillc My example shown above should work. Note that you need to have this enableFeaturePreview("GRADLE_METADATA") in your settings.gradle.kts for it to work as it's still need for Kotlin multiplatform for now.

I think adding an extension method would suffice for now. How does this look?
fun SqlDelightExtension.createDataBase(dataBaseName: String, configuration: SqlDelightDatabase.() -> Unit) {
    methodMissing(dataBaseName, arrayOf(closureOf(configuration)))
}

sqldelight {
    createDataBase("Database") {
        packageName = "com.example.pacakge"
    }
}

Fixed by #1306


Fixed typo in pypi URL

PyPI expects a hyphen instead of an underscore (though somehow an underscore still works!)

@all-contributors please add @bourque for maintenance


View with SCHEMABINDING avoids to set SYSTEM_VERSIONING = OFF

Here should be a note about the impossibility to switch SYSTEM_VERSIONING OFF when a view with SCHEMABINDING exists on the versioned table.
What is the reason for such restriction? Setting the  SYSTEM_VERSIONING = ON is allowed w/o restrictions.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5b3e6674-aa5d-6b80-ae29-514954988128
Version Independent ID: 01e72b93-3f3c-408f-b0b7-06fbb0076640
Content: Stopping System-Versioning on a System-Versioned Temporal Table - SQL Server
Content Source: docs/relational-databases/tables/stopping-system-versioning-on-a-system-versioned-temporal-table.md
Product: sql
Technology: table-view-index
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@pcelba -- thank you for your feedback.  Please see these resources for your question:

DBA Stack Exchange
Stack Overflow

@CarlRabeler -- please look into this issue.

Thanks. I've found similar issues but not an explanation why this restriction exists. My post is valid for SQL Server 2017. I did not test it on SQL 2019.
If this restriction is intended then the documentation should mention it. To drop all indexes on schema bound views then to make these views non-schema bound, switch the SYSTEM_VERSIONING OFF and redefine all the views + index creation is doable but annoying.

investigating...

@pcelba Thanks for asking this question. I have added (published later today) explaining this restriction.
Basically, If we allow SYSTEM_VERSIONING to be set to OFF, these objects (views , functions) will fail
The point of schema binding is to prevent that, right ?
On the other hand, setting SYSTEM_VERSIONING to ON would not introduce breaking changes to schema bounded objects as temporal does not break querying of current data
Please let me know if you have follow-up questions.
Carl

@CarlRabeler Thanks for the explanation but I would need more details.
If you have a table with schema bound view you can add new columns, drop columns which are not included in the view and you can set SYSTEM_VERSIONING to ON.  OK.
But I still cannot understand why the setting the SYSTEM_VERSIONING to OFF can affect the schema change harmful to the underlying view or function. All columns remain in place, all values remain unchanged, just the history tracking is switched off. But this history info does not have any bindings to the schema bound views.
What could fail here? What is the reason to disallow the SYSTEM_VERSIONING to OFF?

@pcelba following up with the product team

this is the reason
2 things must be fulfilled
•	Object created with schema binding
•	Object using temporal query extension  (like SELECT * from myTable AS OF ‘2020.01.01’)
If we allow setting SYSTEM_TIME to OFF on myTable , the view using query above will start failing
This is against promise of schema binding

OK, this explanation is clear and thanks for it.
But either this explanation or the SQL Server 2017 behavior seems to be incorrect.
I have an object (view) with schema binding on versioned table but I don't have any view using temporal query extension (of course, the SYSTEM_VERSIONING was set ON right before an attempt to set it OFF).

What temporal query extension is used in the view? Or is it the table [dbo].[JustCols] itself?
TIA
Pavel

Addition to the above SQL script
If I add a new column
ALTER TABLE dbo.JustCols ADD SomeNewColumn char(20) NULL
Then the column is added to both original and temporal tables. And I can simply DROP it even when the view with schema binding exists:
ALTER TABLE dbo.JustCols DROP COLUMN SomeNewColumn
And the column is removed from both tables even when it contains history data...
So why cannot be simply set SYSTEM_VERSIONING = OFF ?
This is needed when we would like to watch just a subset of tables in certain tasks and a different subset in other tasks.
Thanks and Regards
Pavel

If standard (non-temporal) table has a view with schema binding then upgrading table to temporal will not cause any behavior changes. View cannot use temporal features so adding temporal feature will not break existing functionality.
If temporal table has schema bound view this view can use some temporal functionalities and disabling temporal will break it if someone uses temporal functionalities on that view.
a.	In the example below, the view don’t have some  FOR SYSTEM_TIME AS OF in the view definition, but someone might use SELECT * FROM view FOR SYSTEM TIME AS OF. Disabling underlying table will break this. Schema binding ensures that this cannot happen.
Example with adding/dropping column is not valid because SELECT * do not explicitly references any existing or new column (it will pick whatever it finds in the view). Schema binding guarantees that view will not break but not that it will return same results. However, if they add a column, then alter view to explicitly reference new column and try to drop the column they will get the error (see example below).

#reassign:jovanpop-msft

@pcelba Hello, this appears that you have an issue with the way the product works.  If you would like to suggest the ability to set SYSTEM_VERSIONING to OFF when a view with SCHEMABINDING exists, you can submit your suggestions or ideas for improvement for the product at https://aka.ms/sqlfeedback. I will go ahead with closing this issue. The @notification mechanism continues to work even after an item is closed, in case further communication is needed. We hope to hear from you again.

#assign:julieMSFT

#please-close


How to run medallia Word2Vec Java implementation in windows machine

Sir,
I got the llink https://github.com/medallia/Word2VecJava as word2vec java implementation. I would like to run the implementation in my windows machine. currently i am using Netbean 8 for java development along with maven.
Thanks in advance.

Thanks for your interest in word2vecJava, @dwijenrudrapal !
You can include word2vec-java via Maven as a dependency, as seen in the README.md.
In com.medallia.word2vec.Word2VecTest you can see different test cases how you can start the algorithm on your data.

Thank you sir.
I will let you know regarding the status.
Regards
Dwijen
On Wed, May 6, 2015 at 2:33 PM, Philip Gillißen<EMAIL_ADDRESS>wrote:

Thanks for your interest in word2vecJava, @dwijenrudrapal
https://github.com/dwijenrudrapal !
You can include word2vec-java via Maven as a dependency, as seen in the
README.md https://github.com/medallia/Word2VecJava/blob/master/README.md
.
In com.medallia.word2vec.Word2VecTest
https://github.com/medallia/Word2VecJava/blob/master/src/test/java/com/medallia/word2vec/Word2VecTest.java
you can see different test cases how you can start the algorithm on your
data.
—
Reply to this email directly or view it on GitHub
https://github.com/medallia/Word2VecJava/issues/13#issuecomment-99389955
.

The error you receive here is the same as in #21. Please try to use different text corpus and/or training settings to search for words you want. UnknownWordException its not uncommon, but not avoidable by the framework. You have to deal with unknown words in your own code.

@wko27 would you be so kind and close this issue as resolved? Thanks!


Detect if port disconnected or manually closed

SerialPort Version: 6.1.1

NodeJS Version: 9.4.0

Operating System and Hardware Platform: MacOS 10.13.3 / iMac (27-inch, Late 2013)

Have you checked the right version of the api docs?: AFAIK this is the latest

Are you having trouble installing and you checked the Installation Special Cases docs? No trouble

Are you using Electron and have you checked the Electron Docs?: Yes, but no trouble

Summary of Problem
(Electron/React application)
I'd like to be able to distinguish between an open port being manually closed via SerialPort.close() and it being randomly disconnected. There are a number of tasks I need my app to perform if the hardware is disconnected without manually closing the connection.
So far I am having to track in my component state whether the close button was pressed in order to determine whether the port was gracefully closed or not, but I am concerned of edge cases using this method and how to "clean up".
Is there any way to capture this type of disconnection in this version of node-serialport?
Steps and Code to Reproduce the Issue
N/A

Thanks for the fast reply, why didn't I think to check the error event contents!
event is null on graceful close, and contains an error if there is one.
Issue resolved, closing!


Automate the release process

Of all the available tools, this one is the most popular.
https://github.com/semantic-release/semantic-release
It requires writing commits in a specific format. (Alternatives also follow the same guidelines).

[ ]  Try it out locally
[ ]  If it works, then update the contribution rules to follow the commit conventions
[ ]  Can we add checks to PR to ensure commits conform to the rules?
[ ]  Add CI support so that whenever we merge to master a new version is released
[ ]  Exclude documentation updates in the master branch, i.e., do not release a new version if only documentation has been updated

(This list is a WIP)

4fb3edee8d97795b427dd44c61f052bb12186e83

Okay so this explains the rapid releases. Are we following semver style (major.minor.patch)? Some of the most recent releases could have just been limited to a patch release, as they seem to contain bugfixes alone.

It depends on the commits. If we have feat commits then it's a minor release. If we have fix, then it's a patch release. If we have breaking change, then it's a major release.
Recent releases are mostly feat hence the minor release.
We don't control the versioning manually. It's all handled automatically. We just need to make sure our commits follow the convention.
Let me know if you have more questions.

Thanks for the clarification! I should really study the development machinery that you guys have put together. Seems very modern.

I am writing help articles to describe it. That should help.


Generate default styles in the backend

Fixes #9339
Fixes #9478
Synopsis
Styles receive definition from cartographies and can be rendered as CartoCSS (.to_cartocss).
This is a bit over engineered in the sense that it defines a structure where you could pass arbitrary definition from a cartography to a Point style, and it would generate the appropriate CartoCSS for it. If you pass no definition, the one by default is used. You could argue we only need the default case, but it wasn't so much more complicated to do it in this way and you never know.
Not too bad I guess.
CARTOGRAPHY -> DEFINITION -> STYLE -> CARTOCSS
and if no definition is provided:
STYLE (default cartography -> default definition) -> CARTOCSS (default for that style)
Please CR, @juanignaciosl
cc/ @xavijam

This looks quite good, but I'd take a second look after your replies or commits.

I switched it around a little. Now all styles return arrays with CartoCSS statements. The presenter has the task to format them. This is motivated by the maybe future need to mix two definitions: you just merge the arrays and pass them to the presenter. You still have the .to_cartocss method that will return the presenter parsed version for just that style.

Ping me again on 🍏  and after closing all discussion threads (specially the one about the class variable).

Hey @juanignaciosl, I singleton'd cartography and made some renaming as well as adding some tests.
Can you take a final look?

It looks almost ok, but I've made a couple of comments that you should probably consider (flatten and log ones, mostly).

LGTM 👍

Let's have @javitonino have the last go (some minor things have changed)
Namely:

tile_style method split-up
Cartography is now Definition (and can and should be used to load any JSON definition, not just cartography)
Some tests

:+1:
Left a comment about my own code (self-CR). Maybe we should change that?
I like that split :smile:

Namespacing was getting ridiculous, had to switch it up. sorry @javitonino, have another look please!
lib/carto/styles
├── line.rb
├── point.rb
├── polygon.rb
├── presenters
│   └── cartocss.rb
└── style.rb

So styles are independent from cartocss. In the future we can add another conversion with another presenter.

It seems everything is fine, although I trust the tests more than myself to catch if there was some problem with the namespace changes. :+1: after :green_apple: (and merge)


refactor: use zuehlke reveal package via cdn

closes #2
State
It works! (For almost all pages out of the box).
To Do

[x] figure out why one slide doesn't look as expected (code not highlighted) -> Chapter 06 Hooks -> Slide 02/02 contains the following code

    // define a name state with the initial value of ""
    const [name, setName] = useState("");

    // The variable contains the current state value

Name: {name}

Nice, thank you!
The index.html shows the serif font for me though, although it should be sans-serif even according to the computed CSS.. We should look into that.
And if one of us gets to it, I think we should also replace the background picture of index.html to adapt to the new look. What do you think should we do it in this PR or merge this now and have a look later? Other than that it looks good to me.

Nice, thank you!
The index.html shows the serif font for me though, although it should be sans-serif even according to the computed CSS.. We should look into that.
And if one of us gets to it, I think we should also replace the background picture of index.html to adapt to the new look. What do you think should we do it in this PR or merge this now and have a look later? Other than that it looks good to me.

thanks for the review @felixmokross - I think I can probably fix it in this PR. Hopefully, in the next few days:

[ ] fix font
[ ] replace background image

Thanks for the review @felixmokross - I think I can probably fix it in this PR. Hopefully, in the next few days:

[x]  fix font
[ ]  replace background image

Replacing the background image will be done as part of a follow-up story. See here: https://github.com/webplatformz/react-training-slides-v2/issues/22 @felixmokross did you have something specific in mind?


🎪 Storage Tent Alert

Storage tents should

[x] Raise an alert before deletion
[x] Should drop all items after being deleted

28912b9f1188993dae004d320651e944da9eed98


Capture and properly test expected non-match errors

Is this solved by your error recorder PR or is this issue about recording specific non-match tests?  If the latter, would be good to be a bit more specific about which tests we should add.  If the former let's close


branding change

changed the branding
fixes #28
image :

@Sanskriti1102 Hope it is proper now!

@Abheeshta-P Refer to the current UI Join us podcast is overlapping that shouldnt be the case

@Abheeshta-P Refer to the current UI Join us podcast is overlapping that shouldnt be the case

this fix was done prior to that bug fix of podcast so it is this way, should i do it again after sync??

@Sanskriti1102 could you please add hactober label please

@Abheeshta-P the file is having some conflicts do resolve it asap

@Abheeshta-P the file is having some conflicts do resolve it asap

@Sanskriti1102 could you check it now??? if it is resolved can you add hactober and gssoc-ext label to this please

@Abheeshta-P the conflict hasn't been resolved yet

@Sanskriti1102 check it now!!, also please add hactober,gssc-ext label to this!!

@Abheeshta-P do resolve the conflicts


added log4js-node

By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖
⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆
https://github.com/log4js-node/log4js-node

By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖

You clearly did not.


LIBXSMM_CODE_MAXSIZE is too small for some PyFR kernels

While investigating the performance of the p6 PyFR hexahedral kernels (https://github.com/hfp/libxsmm/tree/master/samples/pyfr) it was found that some of the sparse register kernels fail to JIT due to hitting the max code size limit (128 KiB).  This causes them to fall back to dense kernels.  Doubling the max code size resolves this issue and results in substantially better performance.
Ideally, we would work to reduce the size of the generated kernels (and I have some ideas here).  But as an interim solution it would be nice if the size could be increased (or made flexible enough so that the sparse generation kernels can request a higher limit to avoid regressions elsewhere).

Would a compile time adjustment be fine (when compiling LIBXSMM for pyfr)?

Yes, that would be ideal as most of our users compile libxsmm themselves.  Is the code size currently accessible through the makefile?

Not yet, I was just wondering if this is an acceptable solution.


weave container has no IP address

I get the following error message when launching scope with weave already running:
weave container has no IP address; is Docker networking enabled?
If I launch scope before weave, then scope starts up fine.
DOCKER_HOST is not set.

Hi bergtwvd; this is because you're running the latest Weave (1.2).  We've go a fix (#560) in the the next release of Scope, which should be out in the next few days.  In the meantime, you use a master build of Scope (grab a scope script from here https://raw.githubusercontent.com/weaveworks/scope/master/scope) that should work.
Thanks
Tom


{GSSOC '23]Allow Loading of Custom Password File for Brute-Force Login

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to restart the script every time I want to perform a brute-force login attempt with a different password file.
Describe the solution you'd like
I would like the script to have an option to load a custom password file for each login attempt. This way, I can specify a different password file without restarting the script.
Describe alternatives you've considered
One alternative is to modify the script each time I want to use a different password file. However, this approach is time-consuming and inconvenient.
Additional context
The current version of the script already includes a menu with options to perform a brute-force login and exit. I propose adding an additional option in the menu to load a custom password file. When selected, the script should prompt the user to enter the custom password file path and perform the login attempt with the specified file.
Do I want to work on this:

[x]  Yes
[ ] No

@avinashkranjan @omazoz  pls assign this to me

Go Ahead @slayerrr12


Feature: Detect whether Protoss building is powered

I don't believe there is a way of detecting this nicely. Would be nice if a unit instance had a bool to show if it was powered or not

This was implemented in 1d174be6e2cd47a63293eb0ef6efe588f0515502 and will be functional when 3.17 goes live.