Can debug info be removed from lib*.a files ?

Hi!
When trying to build a disassembly file from an elf file one get warnings about source files not found. For instance
/Volumes/LLVM-ET-Arm-18.1.3-Darwin-universal/LLVM-ET-Arm-18.1.3-Darwin-universal/bin/llvm-objdump -S FLASH.elf > FLASH.dis
/Volumes/LLVM-ET-Arm-18.1.3-Darwin-universal/LLVM-ET-Arm-18.1.3-Darwin-universal/bin/llvm-objdump: warning: 'FLASH.elf': failed to find source /workspace/workspace/llvm-embedded/llvm-18/build-and-test/build/picolibc/armv7em_hard_fpv4_sp_d16_exn_rtti/src/picolibc_armv7em_hard_fpv4_sp_d16_exn_rtti-build/../../../../../src/picolibc/newlib/libc/ssp/stack_protector.c
.
.
.

I tried modifying CMakeLists.txt to replace
PICOLIBC_BUILD_TYPE "minsize"
by
PICOLIBC_BUILD_TYPE "release"
as from my understanding of meson buildtype, minsize keeps debug whereas release does not.
But this was not solving the issue.
For now the workaround is to strip the installed libraries.
find ${PREFIX}/lib/clang-runtimes/arm-none-eabi -name "lib*.a" -exec ${PREFIX}/bin/llvm-strip --strip-unneeded {} \;

Any hint on how to modify CMakeLists.txt or options to be passed when invoking cmake is welcome. Thank you !

Hi,
Looking at the docs, https://mesonbuild.com/Builtin-options.html says that debug is there to "Enable debug symbols and other information."
So presumably debug=false meson option would remove debug symbols, however the table for buildtype https://mesonbuild.com/Builtin-options.html#details-for-buildtype already says that it implies debug=false for the release option, so changing the build type to release, as you suggested, should have worked.
May be a question for https://github.com/mesonbuild/meson

Seems that changing also in CMakeLists.txt
-DCMAKE_BUILD_TYPE=MinSizeRel
by
-DCMAKE_BUILD_TYPE=Release
is solving my question.


[sql lab] persist tables list in localStorage

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
In #7998 I removed some fields when persist redux state into localStorage.
Now i found tables list on the sql lab left panel is quite useful, which displayed columns name and type from tables that user previewed before. Currently when user reload sql lab from localStorage, this table list information is lost.
Solution:
Should persist this tables list into localStorage.
Should persist schema and height information for sql editor instance.
After this change, the content in redux but not persisted in localStorage will be schemaOptions and tableOptions in queryEditor.
Also, found a bug in current code, that resized panel size is not persisted in the redux state. Added fix for this issue.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before

After

TEST PLAN

ADDITIONAL INFORMATION

[x] Has associated issue: #7998

REVIEWERS
@etr2460 @michellethomas @betodealmeida @xtinec

Codecov Report

Merging #8054 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8054      +/-   ##
==========================================
+ Coverage   65.54%   65.54%   +<.01%
==========================================
  Files         469      469
  Lines       22482    22482
  Branches     2444     2444
==========================================
+ Hits        14735    14736       +1
+ Misses       7627     7626       -1
  Partials      120      120

Impacted Files
Coverage Δ

superset/assets/src/SqlLab/App.jsx
0% <ø> (ø)
:arrow_up:

...src/SqlLab/utils/reduxStateToLocalStorageHelper.js
100% <ø> (ø)
:arrow_up:

superset/db_engine_specs/postgres.py
72.72% <0%> (-22.73%)
:arrow_down:

superset/utils/core.py
87.83% <0%> (+0.16%)
:arrow_up:

superset/db_engine_specs/sqlite.py
66.66% <0%> (+20.83%)
:arrow_up:

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 ef1d4a6...9054e56. Read the comment docs.

added fix to persist panel size settings.

@graceguo-supercat, I'm doing the final tests on https://github.com/apache/incubator-superset/pull/8055.


Fix typos.

Fixed typos.
Used U.S. spelling consistently.

Thanks, that's great! I will merge it tonight certainly


Add Float16/Half-float logical type to Parquet

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
There is a proposal for an addition of Logical Float-16 (with Fixed Length Byte Array physical typed) to the Parquet Format: https://github.com/apache/parquet-format/pull/184.
The vote has passed.
Describe the solution you'd like
Float-16 is supported in arrow-rs, and it would be great to expand that support to Rust Parquet.

I'd like to take a stab at this if no one has yet

label_issue.py automatically added labels {'parquet'} from #5003


Docker image security issue

Bug description
Security issue - need to update alpine and push the rebuilt image.
letsencrypt-nginx-proxy-companion image version
Info: running letsencrypt-nginx-proxy-companion version v2.0.2

nginx-proxy-companion configuration
No specific configuration.
Trivy security output
{
  "image_id": "jrcs/letsencrypt-nginx-proxy-companion:2.0.2",
  "analysis": [
    {
      "Target": "jrcs/letsencrypt-nginx-proxy-companion:2.0.2 (alpine 3.12.3)",
      "Type": "alpine",
      "Vulnerabilities": [
        {
          "VulnerabilityID": "CVE-2021-23839",
          "PkgName": "libcrypto1.1",
          "InstalledVersion": "1.1.1i-r0",
          "FixedVersion": "1.1.1j-r0",
          "Layer": {
            "DiffID": "sha256:777b2c648970480f50f5b4d0af8f9a8ea798eea43dbcf40ce4a8c7118736bdcf"
          },
          "SeveritySource": "nvd",
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2021-23839",
          "Title": "openssl: incorrect SSLv2 rollback protection",
          "Description": "OpenSSL 1.0.2 supports SSLv2. If a client attempts to negotiate SSLv2 with a server that is configured to support both SSLv2 and more recent SSL and TLS versions then a check is made for a version rollback attack when unpadding an RSA signature. Clients that support SSL or TLS versions greater than SSLv2 are supposed to use a special form of padding. A server that supports greater than SSLv2 is supposed to reject connection attempts from a client where this special form of padding is present, because this indicates that a version rollback has occurred (i.e. both client and server support greater than SSLv2, and yet this is the version that is being requested). The implementation of this padding check inverted the logic so that the connection attempt is accepted if the padding is present, and rejected if it is absent. This means that such as server will accept a connection if a version rollback attack has occurred. Further the server will erroneously!
  reject a connection if a normal SSLv2 connection attempt is made. Only OpenSSL 1.0.2 servers from version 1.0.2s to 1.0.2x are affected by this issue. In order to be vulnerable a 1.0.2 server must: 1) have configured SSLv2 support at compile time (this is off by default), 2) have configured SSLv2 support at runtime (this is off by default), 3) have configured SSLv2 ciphersuites (these are not in the default ciphersuite list) OpenSSL 1.1.1 does not have SSLv2 support and therefore is not vulnerable to this issue. The underlying error is in the implementation of the RSA_padding_check_SSLv23() function. This also affects the RSA_SSLV23_PADDING padding mode used by various other functions. Although 1.1.1 does not support SSLv2 the RSA_padding_check_SSLv23() function still exists, as does the RSA_SSLV23_PADDING padding mode. Applications that directly call that function or use that padding mode will encounter this issue. However since there is no support for the SSLv2 protocol !
 in 1.1.1 this is considered a bug and not a security issue in that version. OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.0.2y (Affected 1.0.2s-1.0.2x).",
          "Severity": "HIGH",
          "CweIDs": [
            "CWE-326"
          ],
          "CVSS": {
            "nvd": {
              "V2Vector": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
              "V2Score": 5,
              "V3Score": 7.5
            },
            "redhat": {
              "V3Vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
              "V3Score": 3.7
            }
          },
          "References": [
            "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23839",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=30919ab80a478f2d81f2e9acdcca3fa4740cd547",
            "https://security.netapp.com/advisory/ntap-20210219-0009/",
            "https://www.openssl.org/news/secadv/20210216.txt"
          ],
          "PublishedDate": "2021-02-16T17:15:00Z",
          "LastModifiedDate": "2021-02-24T00:56:00Z"
        },
        {
          "VulnerabilityID": "CVE-2021-23840",
          "PkgName": "libcrypto1.1",
          "InstalledVersion": "1.1.1i-r0",
          "FixedVersion": "1.1.1j-r0",
          "Layer": {
            "DiffID": "sha256:777b2c648970480f50f5b4d0af8f9a8ea798eea43dbcf40ce4a8c7118736bdcf"
          },
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2021-23840",
          "Title": "openssl: integer overflow in CipherUpdate",
          "Description": "Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).",
          "Severity": "HIGH",
          "CVSS": {
            "redhat": {
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
              "V3Score": 7.5
            }
          },
          "References": [
            "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23840",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9b1129239f3ebb1d1c98ce9ed41d5c9476c47cb2",
            "https://security.netapp.com/advisory/ntap-20210219-0009/",
            "https://usn.ubuntu.com/usn/usn-4738-1",
            "https://www.debian.org/security/2021/dsa-4855",
            "https://www.openssl.org/news/secadv/20210216.txt"
          ],
          "PublishedDate": "2021-02-16T17:15:00Z",
          "LastModifiedDate": "2021-02-19T13:15:00Z"
        },
        {
          "VulnerabilityID": "CVE-2021-23839",
          "PkgName": "libssl1.1",
          "InstalledVersion": "1.1.1i-r0",
          "FixedVersion": "1.1.1j-r0",
          "Layer": {
            "DiffID": "sha256:777b2c648970480f50f5b4d0af8f9a8ea798eea43dbcf40ce4a8c7118736bdcf"
          },
          "SeveritySource": "nvd",
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2021-23839",
          "Title": "openssl: incorrect SSLv2 rollback protection",
          "Description": "OpenSSL 1.0.2 supports SSLv2. If a client attempts to negotiate SSLv2 with a server that is configured to support both SSLv2 and more recent SSL and TLS versions then a check is made for a version rollback attack when unpadding an RSA signature. Clients that support SSL or TLS versions greater than SSLv2 are supposed to use a special form of padding. A server that supports greater than SSLv2 is supposed to reject connection attempts from a client where this special form of padding is present, because this indicates that a version rollback has occurred (i.e. both client and server support greater than SSLv2, and yet this is the version that is being requested). The implementation of this padding check inverted the logic so that the connection attempt is accepted if the padding is present, and rejected if it is absent. This means that such as server will accept a connection if a version rollback attack has occurred. Further the server will erroneously!
  reject a connection if a normal SSLv2 connection attempt is made. Only OpenSSL 1.0.2 servers from version 1.0.2s to 1.0.2x are affected by this issue. In order to be vulnerable a 1.0.2 server must: 1) have configured SSLv2 support at compile time (this is off by default), 2) have configured SSLv2 support at runtime (this is off by default), 3) have configured SSLv2 ciphersuites (these are not in the default ciphersuite list) OpenSSL 1.1.1 does not have SSLv2 support and therefore is not vulnerable to this issue. The underlying error is in the implementation of the RSA_padding_check_SSLv23() function. This also affects the RSA_SSLV23_PADDING padding mode used by various other functions. Although 1.1.1 does not support SSLv2 the RSA_padding_check_SSLv23() function still exists, as does the RSA_SSLV23_PADDING padding mode. Applications that directly call that function or use that padding mode will encounter this issue. However since there is no support for the SSLv2 protocol !
 in 1.1.1 this is considered a bug and not a security issue in that version. OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.0.2y (Affected 1.0.2s-1.0.2x).",
          "Severity": "HIGH",
          "CweIDs": [
            "CWE-326"
          ],
          "CVSS": {
            "nvd": {
              "V2Vector": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
              "V2Score": 5,
              "V3Score": 7.5
            },
            "redhat": {
              "V3Vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
              "V3Score": 3.7
            }
          },
          "References": [
            "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23839",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=30919ab80a478f2d81f2e9acdcca3fa4740cd547",
            "https://security.netapp.com/advisory/ntap-20210219-0009/",
            "https://www.openssl.org/news/secadv/20210216.txt"
          ],
          "PublishedDate": "2021-02-16T17:15:00Z",
          "LastModifiedDate": "2021-02-24T00:56:00Z"
        },
        {
          "VulnerabilityID": "CVE-2021-23840",
          "PkgName": "libssl1.1",
          "InstalledVersion": "1.1.1i-r0",
          "FixedVersion": "1.1.1j-r0",
          "Layer": {
            "DiffID": "sha256:777b2c648970480f50f5b4d0af8f9a8ea798eea43dbcf40ce4a8c7118736bdcf"
          },
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2021-23840",
          "Title": "openssl: integer overflow in CipherUpdate",
          "Description": "Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).",
          "Severity": "HIGH",
          "CVSS": {
            "redhat": {
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
              "V3Score": 7.5
            }
          },
          "References": [
            "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23840",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9b1129239f3ebb1d1c98ce9ed41d5c9476c47cb2",
            "https://security.netapp.com/advisory/ntap-20210219-0009/",
            "https://usn.ubuntu.com/usn/usn-4738-1",
            "https://www.debian.org/security/2021/dsa-4855",
            "https://www.openssl.org/news/secadv/20210216.txt"
          ],
          "PublishedDate": "2021-02-16T17:15:00Z",
          "LastModifiedDate": "2021-02-19T13:15:00Z"
        },
        {
          "VulnerabilityID": "CVE-2021-23839",
          "PkgName": "openssl",
          "InstalledVersion": "1.1.1i-r0",
          "FixedVersion": "1.1.1j-r0",
          "Layer": {
            "DiffID": "sha256:96298cc8558b40dca0cd243c16f1b81ee6e5430876ab34ebd70611e01b12fd67"
          },
          "SeveritySource": "nvd",
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2021-23839",
          "Title": "openssl: incorrect SSLv2 rollback protection",
          "Description": "OpenSSL 1.0.2 supports SSLv2. If a client attempts to negotiate SSLv2 with a server that is configured to support both SSLv2 and more recent SSL and TLS versions then a check is made for a version rollback attack when unpadding an RSA signature. Clients that support SSL or TLS versions greater than SSLv2 are supposed to use a special form of padding. A server that supports greater than SSLv2 is supposed to reject connection attempts from a client where this special form of padding is present, because this indicates that a version rollback has occurred (i.e. both client and server support greater than SSLv2, and yet this is the version that is being requested). The implementation of this padding check inverted the logic so that the connection attempt is accepted if the padding is present, and rejected if it is absent. This means that such as server will accept a connection if a version rollback attack has occurred. Further the server will erroneously!
  reject a connection if a normal SSLv2 connection attempt is made. Only OpenSSL 1.0.2 servers from version 1.0.2s to 1.0.2x are affected by this issue. In order to be vulnerable a 1.0.2 server must: 1) have configured SSLv2 support at compile time (this is off by default), 2) have configured SSLv2 support at runtime (this is off by default), 3) have configured SSLv2 ciphersuites (these are not in the default ciphersuite list) OpenSSL 1.1.1 does not have SSLv2 support and therefore is not vulnerable to this issue. The underlying error is in the implementation of the RSA_padding_check_SSLv23() function. This also affects the RSA_SSLV23_PADDING padding mode used by various other functions. Although 1.1.1 does not support SSLv2 the RSA_padding_check_SSLv23() function still exists, as does the RSA_SSLV23_PADDING padding mode. Applications that directly call that function or use that padding mode will encounter this issue. However since there is no support for the SSLv2 protocol !
 in 1.1.1 this is considered a bug and not a security issue in that version. OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.0.2y (Affected 1.0.2s-1.0.2x).",
          "Severity": "HIGH",
          "CweIDs": [
            "CWE-326"
          ],
          "CVSS": {
            "nvd": {
              "V2Vector": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
              "V2Score": 5,
              "V3Score": 7.5
            },
            "redhat": {
              "V3Vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
              "V3Score": 3.7
            }
          },
          "References": [
            "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23839",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=30919ab80a478f2d81f2e9acdcca3fa4740cd547",
            "https://security.netapp.com/advisory/ntap-20210219-0009/",
            "https://www.openssl.org/news/secadv/20210216.txt"
          ],
          "PublishedDate": "2021-02-16T17:15:00Z",
          "LastModifiedDate": "2021-02-24T00:56:00Z"
        },
        {
          "VulnerabilityID": "CVE-2021-23840",
          "PkgName": "openssl",
          "InstalledVersion": "1.1.1i-r0",
          "FixedVersion": "1.1.1j-r0",
          "Layer": {
            "DiffID": "sha256:96298cc8558b40dca0cd243c16f1b81ee6e5430876ab34ebd70611e01b12fd67"
          },
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2021-23840",
          "Title": "openssl: integer overflow in CipherUpdate",
          "Description": "Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).",
          "Severity": "HIGH",
          "CVSS": {
            "redhat": {
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
              "V3Score": 7.5
            }
          },
          "References": [
            "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23840",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1",
            "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9b1129239f3ebb1d1c98ce9ed41d5c9476c47cb2",
            "https://security.netapp.com/advisory/ntap-20210219-0009/",
            "https://usn.ubuntu.com/usn/usn-4738-1",
            "https://www.debian.org/security/2021/dsa-4855",
            "https://www.openssl.org/news/secadv/20210216.txt"
          ],
          "PublishedDate": "2021-02-16T17:15:00Z",
          "LastModifiedDate": "2021-02-19T13:15:00Z"
        }
      ]
    }
  ]
}

Docker host

OS: Debian 4.19.171-2 (2021-01-30)
Docker version: 20.10.3

@buchdag you can close this issue. Big thanks for your quick fix!


How to run?

Hi,
Have not seen Electron before, but tried ./node_modules/electron-prebuilt/dist/Electron.app/Contents/MacOS/Electron . -- and it says "Error opening app"... that the dir does not have a valid electron app.
Could there be a quick paragraph in the README for newbies to run it?
Thanks

If you're using OS X or Linux, then just make; make run will work. Windows is not yet supported :cry:
For the detail, please refer to CONTRIBUTION.md and USERGUIDE.md.
Cheers!


Bump to go 1.19

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 7 (28.57%)  changed or added relevant lines in 6 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 21.597%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

build.go
0
1
0.0%

logger/opa.go
0
1
0.0%

query.go
0
1
0.0%

bundles.go
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

compile.go
1
0%

bundles.go
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
284

Relevant Lines:
1315

💛  - Coveralls


NinjaTrader 8 now working with FancyZones

Microsoft PowerToys version
0.78.0
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
Im trying to snap Ninja Trader 8 windows and can't snap to the zones and these doesn't even show up. I could snap other programs but couldn't with NT8 (windows snap works fine)
✔ Expected Behavior
snap NT8 windows to the zones
❌ Actual Behavior
NT8 windows won't snap to the zones and these don't light up
Other Software
No response

Can you show a screenshot of your settings for fancyzones?
Do you have "

Do you have allow child window snapping enabled?  /needinfo


feat: github migration [EXT-5009]

before we merge this: just want to make sure we have the github -> npm replication setup already? since this is a public package


Fix Jenkins cluster naming

Why is this PR needed?
The VMware load balancer was failing to setup because of how the clusters were being named by Jenkins. Also the cloud init wait wasn't waiting for the lb to be done.
Fixes #
What does this PR do?
Updates how we name the clusters with jenkins replacing / with -.
Makes it so the LB should be ready before the cloud init wait is started.
Anything else a reviewer needs to know?

Is it sufficient to replace just /, or are there other chars which might sneak in?  Would a "replace everything but [a-z0-9]" or something like that be doable?

Is it sufficient to replace just /, or are there other chars which might sneak in? Would a "replace everything but [a-z0-9]" or something like that be doable?

The names come from Jenkins based on the job name so we have some control over that. I think if we want to add any other replacement maybe it should go into testrunner.

approved in the interest of moving forward
But I'm thinking that if one character was incorrectly encoded it is likely that others are, or will be. Is this a more widespread issue with how we are generating the names, perhaps?

Names are usually chosen by who or what is running testrunner so in this case Jenkins was using the job name. Maybe an issue could be opened to look into this more.


Unable to install the olm

Hi,
I want install the olm in my cluster which have installed kube v1.13.6. I try use both options what you explain in release notes here
I still get error message:
customresourcedefinition.apiextensions.k8s.io/clusterserviceversions.operators.coreos.com configured
customresourcedefinition.apiextensions.k8s.io/installplans.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/subscriptions.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/catalogsources.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/operatorgroups.operators.coreos.com unchanged
namespace/olm unchanged
namespace/operators unchanged
clusterrole.rbac.authorization.k8s.io/system:controller:operator-lifecycle-manager unchanged
clusterrolebinding.rbac.authorization.k8s.io/olm-operator-binding-olm unchanged
clusterrole.rbac.authorization.k8s.io/aggregate-olm-edit unchanged
clusterrole.rbac.authorization.k8s.io/aggregate-olm-view unchanged
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": serviceaccounts "olm-operator-serviceaccount" is forbidden: unable to create new content in namespace olm because it is being terminated
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": deployments.apps "olm-operator" is forbidden: unable to create new content in namespace olm because it is being terminated
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": deployments.apps "catalog-operator" is forbidden: unable to create new content in namespace olm because it is being terminated
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": configmaps "olm-operators" is forbidden: unable to create new content in namespace olm because it is being terminated
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": catalogsources.operators.coreos.com "olm-operators" is forbidden: unable to create new content in namespace olm because it is being terminated
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": operatorgroups.operators.coreos.com "global-operators" is forbidden: unable to create new content in namespace operators because it is being terminated
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": operatorgroups.operators.coreos.com "olm-operators" is forbidden: unable to create new content in namespace olm because it is being terminated
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": subscriptions.operators.coreos.com "packageserver" is forbidden: unable to create new content in namespace olm because it is being terminated
Error from server (Forbidden): error when creating "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml": catalogsources.operators.coreos.com "operatorhubio-catalog" is forbidden: unable to create new content in namespace olm because it is being terminated

Could you help me with that?

Looks like you are trying to deploy OLM over a previous install where you tried to uninstall by deleting the namespace. The namespace is stuck in terminating state, most likely due to some finalizers. Easiest is to start from scratch using a new minikube.
Did you try to uninstall using kubectl delete -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml?

If you have a previously failed install, usually the thing keeping the namespace around is the apiserver:
kubectl delete apiservices.apiregistration.k8s.io v1.packages.operators.coreos.com
kubectl delete apiservices.apiregistration.k8s.io v1alpha1.packages.apps.redhat.com

(only one is needed, depends on how old your last install was).
I'm going to close this because I don't believe you would see this issue on a fresh cluster. If you continue to have issues installing, please open a new issue or comment here.

Deleting the API service did not help for me. Only when I remove the finalizer kubernetes on the namespace it is eventually deleted.

On fresh cluster it work probably some problem after upgrading olm, I try remove old and install new one.


Mailinglists: Link to Archive or Listinfo?

Some links to the osm.org-Mailinglists link to their Archive-Directory (/pipermail/), with the majority instead linking to the Listinfo (/listinfo/) - While I'm at it, I'd like to change all there to the Listinfo.
Any objections?

I agree - they should all go to the listinfo page.

Okay, will happen later today :)


COG source: colored pixels outside its bounding box

Hi,
I have a map that loads a COG file. When OL renders it I have colored pixels outside the extent of the layer?
The COG has NaN as null value.
Here a working example: https://codesandbox.io/s/ol-sgekdh?file=/main.js
What am I doing wrong?
Thank you

import GeoTIFF from "ol/source/GeoTIFF.js";
import Map from "ol/Map.js";
import TileLayer from "ol/layer/WebGLTile.js";
import colormap from "colormap";
import OSM from "ol/source/OSM";
import { register } from "ol/proj/proj4";
import proj4 from "proj4";
import { proj4Defs } from "./proj";
import { View } from "ol";

proj4.defs(proj4Defs);
register(proj4);

function getColorStops(name, min, max, steps, reverse) {
  const delta = (max - min) / (steps - 1);
  const stops = new Array(steps * 2);
  const colors = colormap({ colormap: name, nshades: steps, format: "rgba" });
  if (reverse) {
    colors.reverse();
  }
  for (let i = 0; i < steps; i++) {
    stops[i * 2] = min + i * delta;
    stops[i * 2 + 1] = colors[i];
  }
  return stops;
}

const url = "https://andy-aws.s3.eu-north-1.amazonaws.com/RNBR.tif";

const source = new GeoTIFF({
  normalize: false,
  sources: [
    {
      url: url,
      nodata: NaN
    }
  ]
});

const layer1 = ["band", 1];

const osm = new TileLayer({
  source: new OSM()
});

const layer = new TileLayer({
  source: source,
  style: {
    color: [
      "case",
      // if band 2 == 0, than set it transparent
      ["==", ["band", 2], 0],
      ["color", 0, 0, 0, 0],
      // otherwise, shades of green
      [
        "interpolate",
        ["linear"],
        layer1,
        ...getColorStops("greens", -2, 2, 9, true)
      ]
    ]
  }
});

const view1 = source.getView();

const view2 = new View({
  projection: "EPSG:4326",
  center: [31.8375, -13.12945],
  zoom: 12
});

const map = new Map({
  target: "map",
  layers: [osm, layer],
  view: view2
});

// Register onclick event listener on the map or layer
map.on("click", function (event) {
  var coordinate = event.coordinate;
  console.log("Clicked coordinate:", coordinate);

  const data = layer.getData(event.pixel);
  console.log(data);
});

For nodata, you should specify the number that represents nodata values. NaN is not a number in a GeoTIFF. If you comment out the incorrect nodate: NaN, the GeoTIFF source will try to get the nodata value from the COG's metadata. This is the reason why it works then.

Thank you @ahocevar


Add W&B embedding projector example

Hi,
I've added an example showing how to use the Weights & Biases embedding projector with OpenAI embeddings. Let me know if there's anything I can change to help it get merged.
Here's an example that was created by it: http://wandb.me/openai_embeddings
You can dynamically change what dimensionality reduction algorithm is used, along with choosing which of your logged data is shown with color & hover.

Looks great and happy to accept the contribution.
Before merging, I think it might be helpful to add an introductory blurb at the top explaining what W&B is, and why someone might want to use it (or not use it). Some people browsing the Cookbook may never have heard of W&B, so this is a good chance to explain what it is. Mind adding?

Of course, that's a good suggestion. I'll follow up with that soon

I've added that blurb now. Let me know if there's anything else I can do.

Looks awesome. One tiny request - do you mind rewording 'other top ML teams' to just 'other ML teams'? Would love to keep things as inclusive and humble as possible, especially since people reading this on the OpenAI Cookbook might think OpenAI is writing that about themselves.
After that small change (or equivalent), I'll approve and merge.

Great. That should be done now.

Merged. Thank you again!


Fixes type error in chapter

A quick fix to correctly set the type for the monster position.

This looks good, thank you! I'll have it merged this morning.


Webpack alias conflict with jest

Hi,
I am facing an issue while using jest. We have a Webpack alias setup (jest.config.js) for a Constants Folder we have as
// Webpack alias for jest
"moduleNameMapper": {
  "/Constants(.*)/": "/Users/****/Desktop/projects/*****/src/client/constants$1"
 },

STEPS

I made a index.test.tsx in the component that im testing and write code for the test.
run yarn test => which is a script that runs jest we defined in the project.

ERROR/CURRENT BEHAVIOUR
Configuration error:
    // EventConstants is not something that we defined
    Could not locate module ./EventConstants (mapped as /Users/*****/Desktop/projects/*****/src/client/constants)

    Please check:

    "moduleNameMapper": {
      "/Constants/": "/Users/****/Desktop/projects/*****/src/client/constants"
    },
    "resolver": undefined

EXPECTED BEHAVIOUR
For the tests to run smoothly with out experiencing this error.
SOLUTION THAT SEEMS TO WORK FOR ME
It seems that removing our alias from the jest.config.js file seems to make everything work as expected.
It seems at first glance that jest is trying to look for EventConstants in the webpack alias that we defined. I followed all the steps that are suggested here before opening the issue and the error seems to be re-occurring.

use latest version of jest
try re-installing your node_modules folder
run Jest once with c to see if that fixes the problem you are experiencing.

My question is Is jest using the CONSTANTS alias internally? if so Do we have to change the alias we defined or is there a work around to this problem?
I am using:

NODE: 8.4.0
NPM: 5.5.1
YARN: 1.0.1
JEST: 21.2.1

JEST CONFIG
module.exports = {
  "moduleFileExtensions": ["js", "jsx", "ts", "tsx"],
  ["moduleNameMapper"]: {
    // These take care of webpack's alias
    ["Redux(.*)"]: "<rootDir>/src/client/redux$1",
    ["Static(.*)"]: "<rootDir>/src/static$1",
    ["Components(.*)"]: "<rootDir>/src/client/components$1",
    ["Hoc(.*)"]: "<rootDir>/src/client/hoc$1",
    ["Services(.*)"]: "<rootDir>/src/client/services$1",
    ["Constants(.*)"]: "<rootDir>/src/client/constants$1",
    ["Scenes(.*)"]: "<rootDir>/src/client/scenes$1",
    ["Types(.*)"]: "<rootDir>/src/client/types",
    ["Helpers(.*)"]: "<rootDir>/src/client/helpers$1",
    ["\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$"]: "<rootDir>/src/__mocks__/fileMock.js",
    ["\\.(css|less)$"]: "<rootDir>/src/__mocks__/styleMock.js"
  },
  testPathIgnorePatterns: ["<rootDir>/src/build/", "<rootDir>/node_modules/"],
  transform: {
    ["^.+\\.(js|jsx|ts|tsx)$"]: "<rootDir>/src/build/test/transformer.js"
  },
  testMatch: [
    "**/*.test.(js|jsx|tsx|ts)"
  ],
  modulePaths: ["<rootDir>/src/client/", "<rootDir>/src/static/"]
}

It seems like you unblocked yourself. For questions please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions. Thank you :)


Update concept-default-purview-account.md

Modified Purview to Azure Purview as per latest guidance

@athenads : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; merging per https://github.com/MicrosoftDocs/azure-docs/pull/86342#issuecomment-1012242204.


Thought about automatic regen at midnight (or time you set)?

Love the regeneration feature!
What about automatically regenerating tasks by time instead of manually checking the parentless task with a recurring date?  Say you have a list of subtasks that need to be done every day and you need the list to start over regardless of whether you got them all done the day before.  Currently, you have to manually check the task to generate the subtasks (with the proper labels and switches, of course).  What if you created another label (regen_all_midnight) that triggered regeneration of subtasks at midnight every night regardless of whether they were done or not the previous day?
Just a thought...

Hi there, thanks for your suggestion! I like the idea of auto-regenerating the list. I'll still have to think if I want to do it at midnight, or give users a choice on when it should happen. This latter option requires a bit more thought on how I would keep the overall functionality streamlined.
In addition, all the current logic relies on a user checking the tasks, since Todoist then changes the date. I can then do a simple comparison of the old and new dates and detect if action is needed. With this mode selected, it would require a different check of the user's local time. Again, this is possible, but it requires a bit more thought to not make a mess of the code.
I'll give it some more thoughts and I'll let you know how it works it out!


Header Fields in API Response

Is your feature request related to a problem? Please describe.
We need to fetch the eTag header to implement our own caching. On Android this is already possible, on iOS we only get the data.
Describe the solution you'd like
The access should be similar to the Android version:
let response = try await Amplify.API.get(request: request)
let etag = response.headers["etag"]

Describe alternatives you've considered
It seems there is no way to access response headers at all or it is unclear from the documentation:
https://docs.amplify.aws/lib/restapi/fetch/q/platform/ios/#get-requests
Is the feature request related to any of the existing Amplify categories?
API
Additional context
No response

Thank you for posting this feature request. Our team will post an update on this ticket.

An option to explore here is creating overloads for each of the methods (get / put / post / delete / head / patch) with the @_disfavoredOverload annotation to prevent breaking due to ambiguity of overloaded return types.
// exists today - `RESTTask.Success` is a typealias for `Data`.
func get(request: RESTRequest) async throws -> RESTTask.Success

// new overload -- where `NewReturnType` encapsulates the additional information.
@_disfavoredOverload
func get(request: RESTRequest) async throws -> NewReturnType

The existing method that returns Data would likely be removed in the next major version of the library.

if some information returned as header like session id, which is not available when access response headers.
How can i access response header fields.

I am facing this issue with NodeJS library of amplify.

Hi @viru-rathore, are you using this library? https://github.com/aws-amplify/amplify-js If so, please open an issue over there with more details

Thank you for posting this feature request. Our team will post an update on this ticket.

Hi, has any update been shared on this request? I'm running into the same issue where we need to get the etag from response headers on a 200 response but I am not able to find any documentation on how this can be achieved. Thanks.

@SurajBastola-BO Hi, unfortunately there is no update on this request. We'll post on this issue when there's any update to provide.

@SurajBastola-BO Hi, unfortunately there is no update on this request. We'll post on this issue when there's any update to provide.

Thank you. Is this something that has been or being prioritized on your roadmap?


WARN: FromAsCasing when building Docker image on Linux

Issue
When running docker compose build factory under Docker Desktop for Linux, a warning is output:

=> [factory internal] load build definition from factory.Dockerfile
=> => transferring dockerfile: 4.84kB
=> WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 4)

The Build check FromAsCasing reports a cosmetic formatting inconsistency.
Similar warning messages are also present in CircleCI when images are built to be released to Docker Hub.
Environment
Ubuntu  22.04.4 LTS
Node.js v20.15.0
Docker version  27.0.3
Docker Desktop 4.31.0 (153195)
Steps to reproduce
git clone https://github.com/cypress-io/cypress-docker-images
cd cypress-docker-images
npm ci
cd factory
docker compose build factory

Logs
$ cd factory
$ docker compose build factory
[+] Building 83.6s (10/10) FINISHED                                                                        docker-container:builder
 => [factory internal] booting buildkit                                                                                16.0s
 => => pulling image moby/buildkit:buildx-stable-1                                                                            15.4s
 => => creating container buildx_buildkit_builder0                                                                             0.5s
 => [factory internal] load build definition from factory.Dockerfile                                                           0.0s
 => => transferring dockerfile: 4.84kB                                                                                0.0s
 => WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 4)                                                 0.0s
 => [factory internal] load metadata for docker.io/library/debian:12-slim                                                      2.4s
 => [factory internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [factory 1/3] FROM docker.io/library/debian:12-slim@sha256:f528891ab1aa484bf7233dbcc84f3c806c3e427571d75510a9d74bb5ec535b  4.3s
 => => resolve docker.io/library/debian:12-slim@sha256:f528891ab1aa484bf7233dbcc84f3c806c3e427571d75510a9d74bb5ec535b33        0.0s
 => => sha256:f11c1adaa26e078479ccdd45312ea3b88476441b91be0ec898a7e07bfd05badc 29.13MB / 29.13MB                               3.7s
 => => extracting sha256:f11c1adaa26e078479ccdd45312ea3b88476441b91be0ec898a7e07bfd05badc                                      0.5s
 => [factory internal] load build context                                                                                0.0s
 => => transferring context: 14.11kB                                                                                0.0s
 => [factory 2/3] RUN ls -la /root   && chmod 777 /root   && apt-get update   && apt-get install --no-install-recommends -y   43.1s
 => [factory 3/3] COPY ./installScripts /opt/installScripts                                                                    0.1s
 => [factory] exporting to docker image format                                                                                17.6s
 => => exporting layers                                                                                11.6s
 => => exporting manifest sha256:9537848362e4c2cb974ac4676db880a74a3ef7fa32d8ca51dbcd5f2c0190bd8c                              0.0s
 => => exporting config sha256:81b2c8c04e207476d6cfe745a5a403e76b2611248918f4da92317172a78fb5a2                                0.0s
 => => sending tarball                                                                                6.0s
 => [factory] importing to docker                                                                                4.0s
 => => loading layer 32148f9f6c5a 294.91kB / 29.13MB                                                                           4.0s
 => => loading layer 276926a83c45 134.81MB / 161.91MB                                                                          3.2s
 => => loading layer 85bc2f8c3f13 4.61kB / 4.61kB                                                                              0.0s

I have the same error with the same docker version and OS

@alejosv

I have the same error with the same docker version and OS

The issue I described here has already been resolved. If you are still seeing it, then make sure that you have updated your local clone of the repo to the latest commit (https://github.com/cypress-io/cypress-docker-images/commit/5322a16ceecb87a232475d4822c4f8fdef48cc96).


Unable to include specific file after excluding its file format in workspace settings

In my case, I would like to exclude all *.js files in my workspace, but include a specific file protractor.report.js. Tried with below workspace settings but it's not working.

It seems that this feature is not available in the VSCode, it would be great if this feature is enabled.

/findDuplicates

Duplicate of https://github.com/Microsoft/vscode/issues/869

I am sorry for the duplicate, #869 helped me.
Below setting worked in my scenario.
"**/*.js": {             "when": "$(basename).ts"         }


Update dev from master

The Contribution guide in the .md file says to build against dev but it is 56 commits behind master. When I try to merge I get conflicts.

Done. Thanks.


upgrade graphite to 1.1.1

to include the fix for the issue that carbon-query returns 0 sometimes. (https://graphite.readthedocs.io/en/latest/releases/1_1_1.html#bug-fixes)
Tested on VM cluster.
Testing on a physical cluster...

Can we document the steps to do the upgrade?
From what I see in package 'carbon-* calls in the recipe, graphite doesn't get restarted. So that needs to be done in an in place upgrade.
I maybe missing some other steps so operation/ deployments notes at the description of the PR would be good. I guess the test would be:

boot a VM cluster with graphite 1.0.x or 0.x
install graphite 1.1 bins in the bootstrap machine
do upgrade by cheffing the machines
restart graphite (and other needed steps to complete upgrade)

Add restart notification in the package resources.

PR updated for adding restart of carbon services.
Testing...

Tested on VM cluster.


Changes autoscalling replica number when the nodepool replica is not set

Before this change, when the NodePool replicas was not set or was nil and the autoscaling was enabled, the number of replicas was fixed to 1. Now it should match the minimum number of replicas set in the 'autoscaling' field of the nodepool spec file
Signed-off-by: Juan Manuel Parrilla Madrid<EMAIL_ADDRESS>Which issue(s) this PR fixes
Fixes #HOSTEDCP-795
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[x] This change includes unit tests.

/test verify

you got it

/retest

/approve
/lgtm

/retest


pos_category_multi incompatible with pos reporting

What's wrong
Here is the report with an runbot instance

When you populate pos_categ_ids, the report goes wrong
How it could be better
An onchange could populate pos_categ_id from pos_categ_ids with the first value.
What do you think @yelizariev  ?
side note: my customer use pos_category_multi as paid module.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

The description is missing :smiley_cat:

I canot use the report as i'm using pos_category_multi, the report mixup all the articles in the categories and its not trustfull.
Have a good reporting is mandatory, so the usage of pos_category_multi must take care of this Reporting issue.    Hope that can be solved asap.

Of course, when my company LFG buy this module 6 months ago, it was expected to have solid reporting.  Unfortunately it didn't work as it should for this purpose.

Hi @yelizariev, please give us you opinion on these questions:
1/ do you consider the problem described is real ?
2/ do you considerer the proposed solution is generic for your module and is the best answer or there any other proposal to consider ?

Hi @yelizariev.
Have you any news ? Thanks


init() got an unexpected keyword argument 'dataset_name'

Thanks so much for coming here to raise an issue. Please take a moment to 'check' the below boxes:

[x] I'm up-to-date with the latest release:
pip install -U talos

[x] I've confirmed that my Keras model works outside of Talos.

If you still have an error, please submit complete trace and a code with:

output of shape for x and y e.g. (212,12)
Talos params dictionary
The Keras model wired for Talos
Description of extra variables in the model

You can provide the code in pastebin / gist or any other format you like.

The code works flawlessly without the dataset_name and the experiment_no.
I have no idea what the issue could be! Thanks so much for making Talos.
TypeError                                 Traceback (most recent call last)

<ipython-input-8-ce880ac8d012> in <module>()
     79 t = ta.Scan(x=X_train, y=y_train, params = p, model=get_model,
     80             dataset_name='task_3',
---> 81             experiment_no='1')

TypeError: __init__() got an unexpected keyword argument 'dataset_name'

# https://towardsdatascience.com/hyperparameter-optimization-with-keras-b82e6364ca53
# Function to create model, required for KerasClassifier
def get_model(x_train, y_train, x_val, y_val, params):
# create model

    #parameters defined
    lr = params['lr']
    epochs= params['epochs']
    neurons = params['neurons']
    optimizer = params['optimizer']
    loss= params['loss']
    decay = params['decay']
    momentum=params['momentum']
    batch_size = params['batch_size']
    dropout_rate = params['dropout']

    input_shape = X_train.shape[1]

    model = Sequential()
    model.add(Dense(neurons, input_shape = (input_shape,))),
    model.add(LeakyReLU(alpha=0.01)),
    model.add(BatchNormalization()),

    model.add(Dropout(dropout_rate, seed=42)),
    model.add(Dense(neurons)),
    model.add(LeakyReLU(alpha=0.01)),
    model.add(BatchNormalization()),

    model.add(Dropout(dropout_rate, seed=42)),
    model.add(Dense(neurons)),
    model.add(LeakyReLU(alpha=0.01)),
    model.add(BatchNormalization()),

    model.add(Dropout(dropout_rate, seed=42)),
    model.add(Dense(neurons)),
    model.add(LeakyReLU(alpha=0.01)),
    model.add(BatchNormalization()),

    model.add(Dropout(dropout_rate, seed=42)),
    model.add(Dense(neurons)),
    model.add(LeakyReLU(alpha=0.01)),
    model.add(BatchNormalization()),

    model.add(Dropout(dropout_rate, seed=42)),
    model.add(Dense(5, activation='softmax'))
    # Compile model

    # https://stackoverflow.com/questions/54377668/talosreturnerror-talos-make-sure-that-input-model-returns-out-model-model-f

    if optimizer=="Adam":
            opt=keras.optimizers.Adam(lr=lr, beta_1=0.9, beta_2=0.999)
    if optimizer=="Adagrad":
            opt=keras.optimizers.Adagrad(lr=lr, epsilon=None, decay=decay)
    if optimizer=="sgd":
            opt=keras.optimizers.SGD(lr=lr, momentum=momentum, decay=decay, nesterov=False)

    model.compile(loss=loss,optimizer=opt,
                 metrics=['accuracy'])

    history = model.fit(x = x_train, y= y_train, validation_data=[x_val, y_val],
                        epochs=params['epochs'], batch_size = batch_size,verbose=1)

    return history, model

p = {'lr': [0.0001],
      'neurons':[1200,1500],
      'decay':[0],
      'optimizer': ["Adam"],
      'hidden_layers':[3],
      'momentum': [0.0],
      'batch_size': [128],
      'loss': ["sparse_categorical_crossentropy"],
      'epochs': [250],
      'dropout': [0.2,0.3]}

t = ta.Scan(x=X_train, y=y_train, params = p, model=get_model,
            dataset_name='task_3',
            experiment_no='1')

It's called experiment_name in the recent versions. Try that instead. It replaces dataset_name and experiment_no. Closing here.

Hi @mikkokotila many thanks for developing Talos! It's really helpful for my classifier development.
Anyway thanks also to you and @kenfus for pointing out this issue which I also am facing it. Think such info could probably be updated in Talos docs here. Thanks again.

I have train the model and showing like
Exception: Could not initialize MemoizationPolicy. init() got an unexpected keyword argument 'epochs'
how can resolve this

@surendramehra  I got this same error.
Exception: Could not initialize MemoizationPolicy. __init__() got an unexpected keyword argument 'epochs'
but when i add policy -name:  TEDPolicy into config.yml then error solved.
policies:
  - name: MemoizationPolicy
  - name: TEDPolicy
    max_history: 5
    epochs: 100
  - name: KerasPolicy
  - name: MappingPolicy
  - name: FormPolicy


Microphysics emulation piggy backed diagnostics.

Resolves #1454

Here is an example of the piggy backed diagnostics: https://wandb.ai/ai2cm/microphysics-emulation/runs/2hxkx27m?workspace=user-nbren12
I also reworked the inputs to use the "tag" as an the input that can be used to run the jobs in sequence.

I added the surface precipitation diagnostics upstream: https://github.com/ai2cm/fv3gfs-fortran/pull/244
I might wait to merge this PR until that merges (hopefully tomorrow AM).


Documentation around Runbooks

Coverage remained the same at 81.455% when pulling 1c1b10bca9744ef31670e7050c9b6dc3a0fb6f2e on develop into f89ffb47f754b0a1b8fa1f69de9f5aeaed5a27b4 on master.


How are GPT4V/Gemini models evaluated?

I notice the paper (VideoChat2) points out that GPT4V uses 16 frames (which I assume are sampled uniformly). However, how is this input into the model given it accepts only single images at a time? Is there some sample prompt for this?

For fairness, we input all video models with a uniform sampling of 16 frames into the model. You can refer to the official cookbook for examples: OpenAI Cookbook.

Thank you! That's really helpful


replace special char in scooter name for entity_id

replacing space and ' in scooter name get by api to entity_id
and lowercase

scootername fixed

Thanks !


Update README.md

:white_check_mark: Build PIX-BACEN-SDK-dotnet 1.1.158 completed (commit https://github.com/guibranco/PIX-BACEN-SDK-dotnet/commit/c6647c91c5 by @guibranco)


refactor(organisms):  SfTable

Checklist

[ ] No commented blocks of code left
[ ] Run tests and docs
[ ] Self code-reviewed

 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.

awesome @aniamusial 💚


pixelorama: init at 0.10.1

Description of changes
Adds Pixelorama: A free & open-source 2D sprite editor, made with the Godot Engine!
Based on @jrobsonchase's pixelorama derivation.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/944


Enable webpage auto-scroll when new messages are received after filling the entire screen

Hey i would like to work on this issue. Please assign this issue to me.

Awesome. I'm assigning this issue to you @jaiakash! I'd suggest you to create a Pull Request as soon as you start working on this issue so that your progress can be tracked.


Cryptoswap bonding_curve

Description
Updated curvesim.bonding_curve to output bonding curves for Cryptoswap pools.
Closes #148.
Hygiene checklist

[x] Changelog entry
[x] Everything public has a Numpy-style docstring
(modules, public functions, classes, and public methods)
[x] Commit history is cleaned-up with minor changes squashed together
and descriptive commit messages following Tim Pope's style

Cute Animal Picture

Waiting to hear if adding STABLESWAP = Union[CurvePool, CurveMetaPool, CurveRaiPool] and CRYPTOSWAP = Union[CurveCryptoPool] to the curvesim.pool module is a good idea before merging.


Add injection compatibility with istio 1.18

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
This PR has the goal of updating the OSS webhook to validate sidecar injection when present at non-zero index. Our driver by default injects at the 0th index and to validate that the sidecar is already present, we only perform the validation in the first index. This behavior does not work out well with istio webhook, which also prefers that the sidecar is injected at the beginning of the container list.
We previously added support to handle scenarios where the user is using Anthos Service Mesh (ASM) and GCSFuse CSI Driver enabled. However, this support was aimed for istio v1.19. This version of istio is not currently available in the regular channel which surfaced incompatibilities between our driver and ASM.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Update OSS webhook to validate sidecar injection when present at non-zero index

LGTM, thanks for the change!


Review IAM policies

Description
Review the IAM policies and ensure that full admin privs aren't specified
Acceptance Criteria
Review completed and IAM accounts confirmed to not have full admin privs
Design Consideration/Limitations
None
Dependencies
None
Additional context
Additional details on https://issues.newrelic.com/browse/NR-124472

This IAM policy is no longer needed. It has been deleted.


Add support for terraform workspaces

completed in #72
documented: https://diggerhq.gitbook.io/digger-docs/features/terraform-workpaces


error using pip install

I am using virutal environment in windows7. while installing using pip it gives error.
but using easy_install gives no error.
http://pastebin.com/Wm8mnwLt
But using easy_install is fine though. Since all my requirements are in requirements.txt file just wanted to include its requirement too.

The error is not related to xhtml2pdf, but to PIL. Using wheels works fine in Windows 7, try with
pip install --use-wheel --requirement=requirements.txt

Ticket can be closed as it works for me.


License headers shouldn't be in Javadoc style

In most open source java libraries the header looks like:
/*
 * The header
 */

This plugin uses a javadoc style:
/**
 * The header
 */

This becomes a problem when generating javadocs, because the license header content gets into all your documentation.

You are able to redefine the comment styles used. See the documentation for it. If it does not work, please reopen with more details to be helped.

it will be nice to paste a link to that section in documentation :) thanks


refactor: moved token manage modal (and sub-components) to icp-eth folder

Motivation
To create a general modal to manage tokens for Chain Fusion, we try and modify the existing IcManageTokensModal component used for ICP, since it is the most similar to the final result we would like to achieve.
As first step, we move it (and the related sub-components) to the common icp-eth folder.

yes, correct, i would just wait a bit, right before adding non-ICRC tokens, just to be consistent


Ordering of hooks

🐛 Bug
In PL 1.4, the order of hooks has changed.
in PL 1.3.8, it was
on_train_epoch_start
training_step
training_step
training_step
training_step
training_epoch_end
on_epoch_end
on_validation_epoch_start
validation_step
validation_step
validation_step
validation_step
validation_epoch_end
on_epoch_end

Now, in PL1.4, it is
on_train_epoch_start
training_step
training_step
training_step
training_step
on_validation_epoch_start
validation_step
validation_step
validation_step
validation_step
validation_epoch_end
on_epoch_end
training_epoch_end
on_epoch_end

i.e.  training_epoch_end runs after validation_epoch_end instead of the last training_step, which doesn't make sense since on_epoch_end is 'just next to it'. Also, note the proximity of the two on_epoch_end in PL 1.4
To Reproduce
You can use the following Colab link:
https://colab.research.google.com/github/mmg10/pl_bug/blob/main/pl_bug_138.ipynb
https://colab.research.google.com/github/mmg10/pl_bug/blob/main/pl_bug_140.ipynb
Environment
PyTorch Lightning 1.3.8 and 1.4.0 respectively
Significance
In PL 1.3.8, we could get the average of training loss across batches via
def training_epoch_end(self, outputs):
    self.avg_train_loss = torch.stack([x['loss'] for x in outputs]).mean().item()

but now we can't, Note that we still can run the following
def validation_epoch_end(self, outputs):
     avg_valid_loss = torch.stack([x['loss'] for x in outputs]).mean().item()

since the validation_epoch_end is preceeded by the last validation_step

@carmocca Any idea there ?

looks similar to #8654

The order was changed in #7357. See the linked PR for its reasoning.

but now we can't

Can you elaborate on why you can't anymore? Is it because you use the loss keyword during both training and validation?

@carmocca
I mentioned it. The outputs dictionary contains losses for all batches. It still does for the validation_epoch_end since it is run after the last validations_step. Not anymore for the training_epoch_end

@mmgxa - is it preferable for you to track the per-step results and reduce them in on_train_epoch_end or on_validation_epoch_end as you please? what are your thoughts on https://github.com/PyTorchLightning/pytorch-lightning/discussions/8690 ?

Dear @mmgxa,
I am not sure to follow how you can't get the loss on training_epoch_end.
This seem to work fine.
def test_epoch_end_hooks(tmpdir):

    seed_everything(42)

    class TestModel(BoringModel):

        def training_step(self, batch, batch_idx):
            loss = super().training_step(batch, batch_idx)
            loss["batch_idx"] = batch_idx
            return loss

        def validation_step(self, batch, batch_idx):
            loss = super().training_step(batch, batch_idx)
            loss["batch_idx"] =  -1 * batch_idx
            return loss

        def training_epoch_end(self, outputs) -> None:
            assert sum(x["loss"] for x in outputs).item() == 12.22606086730957
            assert sum(x["batch_idx"] for x in outputs) == sum(range(5))

        def validation_epoch_end(self, outputs) -> None:
            assert sum(x["loss"] for x in outputs).item() == 10.310195922851562
            assert sum(x["batch_idx"] for x in outputs) == -1 * sum(range(3))

    model = TestModel()
    trainer = Trainer(
        default_root_dir=tmpdir,
        max_epochs=1,
        limit_train_batches=5,
        limit_val_batches=3,
        num_sanity_val_steps=0,
    )
    trainer.fit(model)

@tchaton Not sure what this code does. But take a look at the following two notebooks and please try to explain why the results are different?
https://colab.research.google.com/github/mmg10/pl_bug/blob/main/pl_test_138.ipynb
https://colab.research.google.com/github/mmg10/pl_bug/blob/main/pl_test_140.ipynb
(Both train/valid loss should be the same as in the third cell - which is the case for 1.3.8, but not for 1.4.0. In PL 1.4, the train loss is 0 for first epoch, which is wrong, and in the second epoch, it reports the loss for the second step/batch only!)

@ananthsub but on_train_epoch_end doesn't support the output parameter and hence the loss can't be averaged. One needs to add variable in the __init__ to keep track of it.
My thoughts on #8690? Well, since it doesn't make sense to have the training_epoch_end run after the validation steps (just think about the blocks in the first comment) - yeah, it's better to remove them once and for all :smirk:

@mmgxa so the reason you are seeing a different behavior is as you said the hook order changed. You were computing a self.avg_train_loss and then referencing that (printing it) in the validation_epoch_end. The only solution I can suggest right now is to compute a running average directly in the training_step so you will be able to get the value in the validation hooks.


Update ptrace.h: include <asm/ptrace.h> for Linux

This fixes compilation error, which was found while using musl for powerpc:
In file included from attach.c:43:0:
ptrace.h:69:20: error: field 'regs' has incomplete type
     struct pt_regs regs;
                    ^~~~
<builtin>: recipe for target 'attach.o' failed

Looks good to me, thanks!

Wow, that was fast. Thanks.


UI change on F&F

Help Restore and Show Secondary Key

-Verified this issue on staging app v1.6.0(276)


1.8.0 Final Checklist

Overview
Here is a list of things that need to be fixed/changed before the 1.8.0 release. We are so close! I've assigned you guys to these issues, but if you don’t want to do it, or don't think you can, just comment and I'll re-assign.
Zach

[ ] Latest Text Preview doesn't update correctly for incoming messages (only for sent messages)
[x] Notifications in the shade don't get removed if you open the chat for a new notification before the new notification disappears
[x] Notifications in the shade won't get removed if you have the chat open, lock your phone, get a text from the same chat, then re-open the same chat by unlocking your phone
[x] Fix timezone bug from Monica
[x] Typing an incorrect password during setup will pop you back to the splash screen
[x] Fix responsiveness of Pinned Rows slider
[ ] When fully closed and having multiple notifications from different chats, tapping a chat notification will take you to the wrong chat (sometimes; hard to reproduce)

Tanay

[x] Image disappears after sending (and maybe downloading) an attachment. Will re-appear after a second.

Joel

[x] Fix spacing between message & reaction bar
[x] Add Reply as a default context menu option when Private API is enabled (and Big Sur+)
[x] Clean up Emoji Shortcut Widget (padding when subject is present)
[x] Test Emoji Shortcut widget in reverse scrolling (if UX is better, keep it)
[x] Make hitting enter while the Emoji Shortcut widget is visible select the highlighted emoji
[x] Pinned chats are highlighted after leaving a chat. This needs to be limited to desktop/web

Unassigned

[x] Keyboard state does not get honored after closing message details (reaction popup)
[ ] Dupe messages after leaving and re-entering chat (hard to reproduce)
[x] Replying via a notification, then swiping it away throws an error and the reply is not sent
[ ] images load infinitely: be in chat list -> go to home screen -> receive image notification -> open chat via tapping notification -> image loads indefinitely. This is very hard to reproduce from my experience

Can't reproduce this: Replying via a notification, then swiping it away throws an error and the reply is not sent. Seems to work for me

I also can't reproduce this: Latest Text Preview doesn't update correctly for incoming messages (only for sent messages). Not sure how or why I was running into it before


TIming race condition on canEditThoughtWithWebsockets test

Bug report
There is a bug within the canEditThoughtWithWebsockets test that only shows itself in TravisCI. The issue is that there needs to be more time waited when polling the websocket for the latest message or else this test and possibly others will fail. This should probably be raised to 10 seconds.

This code fix for testing has been shipped to PROD.


JEST 5.3.4 incompatibility

Spring boot 2.0.5 Upgraded JEST from 5.3.3 to 5.3.4
https://github.com/spring-projects/spring-boot/commit/bffc54240956c3ef8ccd1de2c24331a4a8115085
But JEST changed its CreateIndex API
https://github.com/searchbox-io/Jest/wiki/Changelog#-v534
Thus
Caused by: java.lang.NoSuchMethodError: io.searchbox.indices.CreateIndex$Builder.settings(Ljava/lang/Object;)Lio/searchbox/indices/CreateIndex$Builder;
	at com.github.vanroy.springdata.jest.JestElasticsearchTemplate.createIndex(JestElasticsearchTemplate.java:193)
	at com.github.vanroy.springdata.jest.JestElasticsearchTemplate.createIndexWithSettings(JestElasticsearchTemplate.java:1440)
	at com.github.vanroy.springdata.jest.JestElasticsearchTemplate.createIndexIfNotCreated(JestElasticsearchTemplate.java:1425)
	at com.github.vanroy.springdata.jest.JestElasticsearchTemplate.createIndex(JestElasticsearchTemplate.java:177)

Looking at the changes: https://github.com/searchbox-io/Jest/compare/v5.3.3...v5.3.4
Seems related to this: https://github.com/searchbox-io/Jest/commit/ac23e66f9b834cb8fec4bb93ddb9995b9f29b670

Fixed in 3.1.5 released today.
Thanks both for your help.

@VanRoy I still do not ser the new release available on maven repository.
Can you please confirm that this has been published?
Thanks

Indeed @DanielFran , publication failed. Thanks for your feedback.
I will re-publish soon.


Update CODEOWNERS file

As a first pass, replace Serokell people with my name.
I am also looking for others to share the load, either for particular components (whether they are currently listed or not) or globally. If people want to be added let me know and I'll add them in this PR.
Update: I'll collect all the volunteers and distribute them as per their wishes on Tuesday of next week to give people time to look at this.
Update II: People should volunteer for things that they work on, are closely related to what they work on or things they are specifically interested in.

@erikd Could you remove me from Documentation please? I don't work with documentation anymore. And please add me in the Wallet team.

Note to self: Replace Domen's name with Jake's.

Could you remove me from the CODEOWNERS file please? Thanks!

Thanks! :)

@adinapoli-iohk added you to update along with @parsonsmatt .
Will merge this when CI lets me.


[FIX,PROFILER] Fix PAPI test and test in CI

USE_PAPI=On was never added to task_config_build* so PAPI was never tested in CI.
Can't believe I missed this!
@areusch

thanks @tkonolige !

I forgot performance counters aren't available in the cloud so we cannot actually test PAPI in CI...


Add support for docker-compose.yml "restart" key on services

See https://docs.docker.com/compose/compose-file/compose-file-v2/#restart

Default value of restartPolicy in PodSpec  is 'Always'
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
But Kube-compose sets restartPolicy: Never in podSpec


Improve analytics by adding analytics for post and for variable time durations

Add analytics for each post.
Instead of just one there should be an option for 1 week, 6 months and 1 year

@DaniaZehra  ok u can do that will assign u  this issue


Is db.connection_string necessary?

Connection strings can have secrets and have very specific format which makes them not that useful for visualization tooling (or user queries).
They can also be long and redundant on every span.
They can (secrets redacted) be useful to log to help investigate configuration issues, but probably should not appear on spans/metrics.
Proposal is to remove the attribute or make it opt-in.

@open-telemetry/java-instrumentation-approvers do you know of anything important being done with db.connection_string that we are capturing in Java instrumentation?

Looking into https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-java-instrumentation+db_connection_string&type=code&p=1, it seems database instrumentation either  don't set connection string or set driver:schema://host:port.
host and port are covered with server.address|port and we can record schema with url.scheme (maybe for specific systems)?
We can also introduce attribute for driver (when applicable)

Maybe we should ping other maintainers here to get a final opinion?

cc @open-telemetry/go-approvers @open-telemetry/javascript-approvers @open-telemetry/python-approvers @open-telemetry/opentelemetry-python-contrib-approvers @open-telemetry/dotnet-approvers @open-telemetry/dotnet-contrib-approvers

Connection strings can have passwords.
Example from Go:  https://github.com/go-sql-driver/mysql/?tab=readme-ov-file#dsn-data-source-name
Example from .NET: https://learn.microsoft.com/en-us/dotnet/framework/data/adonet/connection-string-syntax
Sometimes the libraries have connection string parsing function that could allow redacting. I think it should be at least opt-in.

We think that changing the default behavior to omit/exclude the db.connection_string attribute will cause immediate degradation of some of our product features.  My preference would be to have the default include the attribute but somehow scrub passwords.

@breedx-splk can you provide a bit more details about how you are using db.connection_string? thanks

also, is this only for Java customers, or includes other languages as well?

I'd also prefer to drop db.connection_string or make it opt-in.
As mentioned above, in js-contrib we re-construct connection strings from other data that's added to the span already (host, port, db name).
I just reviewed all of our usages, and I think 100% of the data we add via the db.connection_string attribute is redundant.

@breedx-splk is there some specific information that you get from the connection string that's not available via other attributes?
If so, we can try to capture that information directly and/or document event/log that captures (scrubbed) connection string.

@breedx-splk can you provide a bit more details about how you are using db.connection_string? thanks

Sure, yeah. From what I understand, our APM UI leverages the db.connection_string as part of its fallback logic when naming inferred databases (eg. where a client span is talking to a non-instrumented database system). As @lmolkova suggested, we should be able to use other fields (like db.name and db.system) to infer the name/type, but we do use it as a fallback when the others aren't present.

@breedx-splk we can add a flag in Java instrumentation to keep around db.connection_string for a while if you need a transition period

@breedx-splk we can add a flag in Java instrumentation to keep around db.connection_string for a while if you need a transition period

Thanks, I appreciate that offer @trask. I'm checking with our internal folks to see what they think.
Another option too is to make it configurable, default it to false (excluded), and allow a distro to override the default (that way we can manage the time we need to keep it around while vanilla can remain spec compliant).


Suggestion : RangeSlider control

Example https://api.flutter.dev/flutter/material/RangeSlider-class.html
Default set of contols is missing one, and it is handy in lots of UI tasks

Good suggestion.


[SPARK-14414][SQL] Make DDL exceptions more consistent

What changes were proposed in this pull request?

How was this patch tested?
DDLCommandSuite et al.

Test build #57573 has started for PR 12853 at commit 12d5c8d.

Test build #57576 has started for PR 12853 at commit 871d2bc.

Test build #57573 has finished for PR 12853 at commit 12d5c8d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class NoSuchDatabaseException(db: String) extends AnalysisException(s\"Database '$db' not found\")
class NoSuchPartitionException(

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57573/
Test FAILed.

Merged build finished. Test FAILed.

Test build #57576 has finished for PR 12853 at commit 871d2bc.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57576/
Test FAILed.

Test build #57647 has started for PR 12853 at commit 45b06c7.

Test build #57647 has finished for PR 12853 at commit 45b06c7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57647/
Test FAILed.

Left a few minor parser comments. Looks pretty good overall.

Test build #57676 has started for PR 12853 at commit b933b13.

Test build #57676 has finished for PR 12853 at commit b933b13.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57676/
Test FAILed.

Test build #57688 has started for PR 12853 at commit 2a08025.

Test build #57688 has finished for PR 12853 at commit 2a08025.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57688/
Test PASSed.

Alright merging into master thanks for the review.


Fix scroll after closing the modal

https://github.com/Jacobs63/vue3-tabs-component/issues/53

I don't, currently, believe this is the correct solution, see #53 .


VSD - setup leaders

https://www.pivotaltracker.com/story/show/171194032
VSD is moving forward with categories more aligned with their Buyer's Guide.
Automation equipment
Cameras - visible
Cameras – 3D
Cameras – non-visible
Cameras – Specialty (High-speed, scientific)
Camera accessories
Image sensors
Lenses/optics
Lighting/illumination
Software
Image capture and system boards
Please place the Leaders block under the last row of content wells.

@brandonbk - could you take a look at this and let me know if I'm overlooking something? I've modeled it after your recent PRs.

VSD - Rounded/boxed

SIW - Not rounded/boxed


getAddress() returns old key

While implementing key rotation it was found that getAddress() does not return us the latest value but the signer still signs using the latest one. This mismatch in addresses is causing the signed docs to be invalid.
https://github.com/rjchow/ethers-aws-kms-signer/blob/8e3a4812b542e86ac9d3b6da02b794eb1b5be86d/src/index.ts#L23
Can we add an optional param to skip the if statement above?

You should probably be creating a new signer with a new keyid after rotating keys

Use a proxy as a permanent identity.
EOA (can be rotated) --> Identity Proxy --> Other smart contracts
*I'm assuming on-chain interaction here.

We are not using the keyids but rather an alias that the new key takes over. So right now using the alias the behaviour is that getAddress will still return the old one but the new key will be used when signing.
The signer is only ever instantiated once so isn't the expected behaviour that the returned value from getAddress is consistent with the key used to sign when calling signMessage?

None of that is the concern of this library - the library instantiates a Ethers Signer given a set of AWS credentials + KMS Key ID, and expects that the Key ID should not change out from under it.
You should be instantiating a new Signer whenever you expect to use a different KMS Key.


fix: help and documentation dropdown hides on blur

#3688

Reviewers
Functional: @tihuan @seve @atarashansky
Readability: @tihuan @seve @atarashansky

Changes

add
remove
modify

Help and Documentation dropdown closes when clicked out

QA steps (optional)
Notes for Reviewer

When you click on the "Help & Documentation" button again it closes it and reopens it immediately. Something is weird with how the onClick and onBlur works for the input dropdown

Thank you @tihuan for helping me wrap up this ticket!! ☺

Always a pleasure, Andrew 😄 !


Market Basket Analysis (MBA) with Apriori or FP-Growth algorithms

Hi! I am new to the MBA, and I found your repo. Do you think your DREAM implementation gives better results than the Apriori or FP-Growth algorithm?
Thanks in advance :)

I didn't compare DREAM with the frequent set based methods. In terms of the personalized basket prediction, DREAM may be better because the Apriori focuses on the general pattern among all users while DREAM attempts to capture the purchase pattern for individual users.


Fix configured pipeline autostart

This PR contains some fixes to actually make configured pipelines autostart.

Looks like there is still one test failure that should be investigated, did you miss an update to a reference file?

The behavior of the existing tests was unstable. I modified them accordingly now.


Use public URLs for submodules

So that users do not require authentication to clone.

Does this needs to be replicated in main?


Blazor - Improve incremental build times for pure html changes.

Is your feature request related to a problem? Please describe.
I am running a blazor client application in the browser.
It has an index.razor file containing purely html:

hi

If I make a modification to this one file by changing the html to:

hi you!

and then run a dotnet build --no-restore within the project directory.. the build takes longer than 7 seconds to complete and does a whole bunch of output actions which I don't think it needs to take because they are things that haven't been touched since the last build:

dotnet build --no-restore
Microsoft (R) Build Engine version 16.2.0-preview-19278-01+d635043bd for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

C:\Program Files\dotnet\sdk\3.0.100-preview6-012264\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(158,5): message NETSDK1057: You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview [C:\Users\DarrellTunnell\source\repos\HubCore\src\Hub.Platform\Hub.Platform.Client\Hub.Platform.Client.csproj]
Hub.Platform.Shared -> C:\Users\DarrellTunnell\source\repos\HubCore\src\Hub.Platform\Hub.Platform.Shared\bin\Debug\netstandard2.0\Hub.Platform.Shared.dll

WebCompiler: Begin compiling compilerconfig.json
WebCompiler: Done compiling compilerconfig.json
[C:\Users\DarrellTunnell\source\repos\HubCore\src\Hub.Platform\Hub.Platform.Client\Hub.Platform.Client.csproj]
Hub.Platform.Client -> C:\Users\DarrellTunnell\source\repos\HubCore\src\Hub.Platform\Hub.Platform.Client\bin\Debug\netstandard2.0\Hub.Platform.Client.dll
Processing embedded resource linker descriptor: mscorlib.xml
Duplicate preserve in resource mscorlib.xml in mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e of System.Threading.WasmRuntime (All).

[C:\Users\DarrellTunnell\source\repos\HubCore\src\Hub.Platform\Hub.Platform.Client\Hub.Platform.Client.csproj]
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:07.22
Why am I so concerned about this?
I want a quick development feedback loop where I can make changes to HTML and see those changes reflected in the browser, quickly. Having to wait 7-8 seconds may not seem like such a big deal, but other tools cater for this with almost instant reload times of html content and developers can be a lot more productive as a result.
Describe the solution you'd like
I'd like to see incremental builds be a lot more intelligent about what has changed.
I'd like to see a way for HTML changes to be reloaded, more quickly, without having to build a bunch of irrelevant assemblies.

Thanks for contacting us, @dazinator.
We will try to do something about this as part of https://github.com/aspnet/AspNetCore/issues/5483


PBS HD support (Was: Error Great Performances download)

Attempted to download a video from www.pbs.org.  The following is the error message.
c:>youtube-dl --verbose  -o e:\req "http://www.pbs.org/wnet/gperf/dudamel-condu
cts-verdi-requiem-hollywood-bowl-full-episode/3374/"
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', '-o', 'e:\req', 'http://www.pbs.org/wn
et/gperf/dudamel-conducts-verdi-requiem-hollywood-bowl-full-episode/3374/']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.8 - Windows-7-6.1.7601-SP1
[debug] Proxy map: {}
[PBS] 3374: Downloading webpage
ERROR: Unable to extract player URL; please report this issue on https://yt-dl.o
rg/bug . Be sure to call youtube-dl with the --verbose flag and include its comp
lete output. Make sure you are using the latest version; type  youtube-dl -U  to
update.
Traceback (most recent call last):
File "youtube_dl\YoutubeDL.pyo", line 517, in extract_info
File "youtube_dl\extractor\common.pyo", line 170, in extract
File "youtube_dl\extractor\pbs.pyo", line 98, in _real_extract
File "youtube_dl\extractor\pbs.pyo", line 79, in _extract_ids
File "youtube_dl\extractor\common.pyo", line 391, in _search_regex

Thanks
On 5/1/2015 7:43 AM, Sergey M. wrote:

Closed #3564 https://github.com/rg3/youtube-dl/issues/3564 via
5890eef
https://github.com/rg3/youtube-dl/commit/5890eef6b021845cb68882107364f1b04d773913.
—
Reply to this email directly or view it on GitHub
https://github.com/rg3/youtube-dl/issues/3564#event-294862324.


Fix TO API Update/Reval Pending Race

Currently, there's no way to set the Server Update Pending and Reval Pending flags, without a race condition.

ORT/Config Generation checks the flag, sees that a Reval is needed
ORT generates config with the reval
Someone issues a new Invalidation Job, which sets the Reval Pending flag (which was already set)
ORT unsets the Reval Pending flag.

We need some kind of mechanism in the API to say "unset the Reval/Update Pending, but only if it hasn't changed since this time."
There are several ways to accomplish this.
We're planning to add If-Unmodified-Since. But, the check and set endpoints are different (GET /update_status vs POST /update), so it would effectively require an IUS that applies to a different endpoint. We could add something custom. But I think the best solution would be to make new endpoint(s) that have GET+POST+/PUT for the same endpoint, so a proper IUS can be used.
I'm submitting a ...

bug report

Traffic Control components affected ...

Traffic Ops

Current behavior:
Impossible to set update or reval flags without risking someone having issued a new update and overwriting that.
Expected / new behavior:
Possible to set update or reval flags without risking someone having issued a new update and overwriting that.
Minimal reproduction of the problem with instructions:

ORT/Config Generation checks the flag, sees that a Reval is needed
ORT generates config with the reval
Someone issues a new Invalidation Job, which sets the Reval Pending flag (which was already set)
ORT unsets the Reval Pending flag.

Anything else:

Can this be done with an IUS PUT to /servers/{{ID}}?

Yeah, that should be fine. It's less efficient, but probably not enough to matter.

This issue was addressed with: #6569


Enable price feed hasura

Description

This PR enable hasura for the price feed module.
Checklist

[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@577bc47). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #79   +/-   ##
=========================================
  Coverage          ?   61.06%
=========================================
  Files             ?       24
  Lines             ?      994
  Branches          ?        0
=========================================
  Hits              ?      607
  Misses            ?      371
  Partials          ?       16

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 577bc47...34382e6. Read the comment docs.


SIGPIPE caught! found in goaccess

it is showing at every end month in my screen terminal SIGPIPE caught! then it the page static
and stop realtime data

It's okay to get a SIGPIPE as goaccess should take care of it. Can you post the output of running it via ltrace , e.g.,
ltrace -p <goaccess_pid> -o debug.log

and/or strace Thanks.

do u want this output

Yes, however, please let goaccess run for sometime while logging to ltrace and then attach the output here. Thanks

It's okay to get a SIGPIPE as goaccess should take care of it. Can you post the output of running it via ltrace , e.g.,
ltrace -p <goaccess_pid> -o debug.log

and/or strace Thanks.

should I run this command also goaccess command?

Yes, both of them. Either you could run ltrace from the beginning or simply attach goaccess pid once it has finished parsing the initial log.


Revise Target Group naming strategy to avoid conflicts

Currently, there are challenges when different clusters within the same account or even VPC which define services with overlapping names and namespaces. For example, these issues

#315
#408

Could be addressed by introducing a more robust naming strategy which takes the potential for overlapping names into account.
Internally, we've been discussing a number of options around target group naming chiefly to avoid conflicting names. Here's the TLDR of where we've landed:

TG names will have the form k8s-<namespace>-<name>-<random suffix>, including a random suffix so names cannot conflict
There will still be some level of truncation on namespace and name based on TG name max length
Disambiguation for TG names will be calculated via tags

Likely tags we will include are

cluster name
vpc id
service namespace
service name
parent ref type (either route or service export)
when parent ref == route, also include

route namespace
route name

While this approach includes a human-readable name with details of the origin k8s service, the TG name on its own can't be parsed to understand precisely where it came from. However, it does solve the uniqueness issue and has other useful properties, such as being able to reference the same service across multiple routes.
We are also considering patching the annotations on different k8s objects with Lattice resource IDs/ARNs to make it easier to find the matching Lattice resource, though that's probably further out.

Closed with PR #457. Will be available in the next release.


The Debian OpenSSL Bug: Backdoor or Security Accident?

https://freedom-to-tinker.com/2013/09/20/software-transparency-debian-openssl-bug/

This does not seem to be an attack, so we won't add it as example.


Add Git Tutorial Course

you have to also add in readme file

you have to also add in readme file

It is already in the readme file so i didn't add it

the same course ?

Yes

I'll add a new course


Dark mode?

Is there a possibility of adding a dark mode?
Would love to submit a PR to do it but not entirely sure where I would start.

Yea, I've thought about that a bit. Maybe a good way to get started would be to enable a dark mode extension on the site, see what looks good, and start from there. I'll take a first look today.


Support build rpm from CentOS

add rpm build CMake
put all public headers into a milvus folder

/cc @yhmo
/cc @ArkaprabhaChakraborty

/lgtm


Provide error type and request url when dynamic chunk failed to load (resolves #4595)

What kind of change does this PR introduce?
Enhancement.

Did you add tests for your changes?
Not yet. Need help about how to run tests at test/browsertest/ ? I had try to add, even modify tests to wrong deliberately at it. then run yarn test with a long time wait. but noting changed.

If relevant, link to documentation update:
Willing to do update if it can be merge.
Summary

Currently, when a dynamic chunk failed to load, we just receive an error event with less information.

This PR add the type property to the passed error event. which provide the error reason that one of these following we can detect:

timeout: aborted by our timeout limit.
error: what we usually received by browser. due to network cut off, DNS error, 404, etc. (see spec).
missing: loaded done but the chunk still not found in context. May occur if CDN/server replied error/not found with '200 OK' incorrectly or the script has broken by hijack or whatever.

And also provide a request property to show the url which was actually used to loaded. I think it's more friendly with analysis and statistics.

relative: https://github.com/webpack/webpack/issues/4595
Does this PR introduce a breaking change?
No breaking change.

Other information

And looking for help about the tests. @sokra. How could I run tests from test/browsertest/?
I noticed that you have write some error handle tests in it. but I don't know how to run. Also can't find guides about browsertest at CONTRIBUTING.md.

Any updates on this? Running into some issues with dynamic bundle loading and this would be a great help.

@jakemmarsh will be part of webpack 4

Thanks

So how do we do this? Is this documented in the Webpack 4 docs?
Would really love to know, thanks y'all!


src/highlight.js is not working when using it independently

I just downloaded highlight.js separately and included it in my local html file. It is not working.
CSS files are fine.
However, it was working when I replaced github's highlight.js with minified version provided in https://highlightjs.org/.

It's not supposed to work from source: https://github.com/isagalaev/highlight.js#getting-the-library


Getting Installation error in iOS platform

Hello,
When I try to install the MSAL plugin in my Cordova app I get an error.

Installing "cordova-plugin-msal" for ios
Failed to install 'cordova-plugin-msal': undefined
CordovaError: Promise rejected with non-error: '/bin/sh: /usr/local/bin/pod: /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby: bad interpreter: No such file or directory\n'
at /usr/local/lib/node_modules/cordova/bin/cordova:29:15
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Cordova info:
<EMAIL_ADDRESS>with:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Environment:
OS: darwin
Node: v12.16.1
npm: 6.13.4
iOS platform:
Xcode 12.0.1
Build version 12A7300
Please help me.:)

I fix this issue by running
sudo gem install -n /usr/local/bin cocoapods

I fix this issue by running
sudo gem install -n /usr/local/bin cocoapods


add missing logos and agendas for meetups

This PR adds missing agenda information for the Aarhus based meetups.
It further adds logos for the sponsor page.
@luxas I run into some problems when running generate:
make generate
generator/bin/generator --dry-run=false
error unmarshaling JSON: while decoding JSON: json: cannot unmarshal string into Go struct field Sponsors.other of type []*main.Company
make: *** [generate] Error 1

Nevermind.  Sponsors.other is an array. Changing it to an array fixes the problem.

Merging this now 👍