Addressing a lot of security vulnerabilities in the Cadence release v0.25

Version of Cadence server, and client(which language)
This is very important to root cause bugs.

Server version: v.0.25.0
Client version:
Client langauge:

Describe the bug
There are a lot of CVEs found by scanning the latest release image v0.25.0.
To Reproduce
Is the issue reproducible?  Yes
Steps to reproduce the behavior:
A clear and concise description of the reproduce steps.
cadence % /usr/local/bin/twistcli images scan --details docker.io/ubercadence/server:0.25.0

Scan results for: image ubercadence/server:0.25.0 sha256:acaa5f69b5ad10191ae71deebf24d367322f9352948ff934f808db7a0b59df33
Vulnerabilities
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
|       CVE        | SEVERITY | CVSS |               PACKAGE               |              VERSION               |                   STATUS                   |  PUBLISHED  | DISCOVERED |                    DESCRIPTION                     |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-42915   | critical | 9.80 | curl                                | 7.80.0-r3                          | fixed in 7.80.0-r4                         | > 4 months  | < 1 hour   | curl before 7.86.0 has a double free. If curl is   |
|                  |          |      |                                     |                                    | > 4 months ago                             |             |            | told to use an HTTP proxy for a transfer with a    |
|                  |          |      |                                     |                                    |                                            |             |            | non-HTTP(S) URL, it sets up the connection to the  |
|                  |          |      |                                     |                                    |                                            |             |            | rem...                                             |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-32221   | critical | 9.80 | curl                                | 7.80.0-r3                          | fixed in 7.80.0-r4                         | > 3 months  | < 1 hour   | When doing HTTP(S) transfers, libcurl              |
|                  |          |      |                                     |                                    |                                            |             |            | might erroneously use the read callback            |
|                  |          |      |                                     |                                    |                                            |             |            | (`CURLOPT_READFUNCTION`) to ask for data to send,  |
|                  |          |      |                                     |                                    |                                            |             |            | even when the `CURLOPT...                          |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2023-23914   | critical | 9.10 | curl                                | 7.80.0-r3                          | fixed in 7.80.0-r6                         | 20 days     | < 1 hour   | A cleartext transmission of sensitive information  |
|                  |          |      |                                     |                                    | 28 days ago                                |             |            | vulnerability exists in curl <v7.88.0 that could   |
|                  |          |      |                                     |                                    |                                            |             |            | cause HSTS functionality fail when multiple URLs   |
|                  |          |      |                                     |                                    |                                            |             |            | ar...                                              |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2023-23916   | high     | 7.50 | curl                                | 7.80.0-r3                          | fixed in 7.80.0-r6                         | 20 days     | < 1 hour   | An allocation of resources without limits or       |
|                  |          |      |                                     |                                    | 28 days ago                                |             |            | throttling vulnerability exists in curl <v7.88.0   |
|                  |          |      |                                     |                                    |                                            |             |            | based on the \"chained\" HTTP compression          |
|                  |          |      |                                     |                                    |                                            |             |            | algorithms, me...                                  |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2023-0215    | high     | 7.50 | openssl                             | 1.1.1q-r0                          | fixed in 1.1.1t-r0                         | 35 days     | < 1 hour   | The public API function BIO_new_NDEF is a helper   |
|                  |          |      |                                     |                                    | 36 days ago                                |             |            | function used for streaming ASN.1 data via a BIO.  |
|                  |          |      |                                     |                                    |                                            |             |            | It is primarily used internally to OpenSSL to      |
|                  |          |      |                                     |                                    |                                            |             |            | suppo...                                           |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-4450    | high     | 7.50 | openssl                             | 1.1.1q-r0                          | fixed in 1.1.1t-r0                         | 35 days     | < 1 hour   | The function PEM_read_bio_ex() reads a PEM file    |
|                  |          |      |                                     |                                    | 36 days ago                                |             |            | from a BIO and parses and decodes the \"name\"     |
|                  |          |      |                                     |                                    |                                            |             |            | (e.g. \"CERTIFICATE\"), any header data and the    |
|                  |          |      |                                     |                                    |                                            |             |            | payload...                                         |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-43551   | high     | 7.50 | curl                                | 7.80.0-r3                          | fixed in 7.80.0-r5                         | 82 days     | < 1 hour   | A vulnerability exists in curl <7.87.0 HSTS        |
|                  |          |      |                                     |                                    | 84 days ago                                |             |            | check that could be bypassed to trick it to keep   |
|                  |          |      |                                     |                                    |                                            |             |            | using HTTP. Using its HSTS support, curl can be    |
|                  |          |      |                                     |                                    |                                            |             |            | instructe...                                       |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-42916   | high     | 7.50 | curl                                | 7.80.0-r3                          | fixed in 7.80.0-r4                         | > 4 months  | < 1 hour   | In curl before 7.86.0, the HSTS check could be     |
|                  |          |      |                                     |                                    | > 4 months ago                             |             |            | bypassed to trick it into staying with HTTP. Using |
|                  |          |      |                                     |                                    |                                            |             |            | its HSTS support, curl can be instructed to use    |
|                  |          |      |                                     |                                    |                                            |             |            | HTTP...                                            |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-41725   | high     | 7.50 | go                                  | 1.17.13                            | fixed in 1.19.6                            | 15 days     | < 1 hour   | A denial of service is possible from               |
|                  |          |      |                                     |                                    | 6 days ago                                 |             |            | excessive resource consumption in net/http and     |
|                  |          |      |                                     |                                    |                                            |             |            | mime/multipart. Multipart form parsing with        |
|                  |          |      |                                     |                                    |                                            |             |            | mime/multipart.Reader....                          |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-41724   | high     | 7.50 | go                                  | 1.17.13                            | fixed in 1.19.6                            | 15 days     | < 1 hour   | Large handshake records may cause panics in        |
|                  |          |      |                                     |                                    | 6 days ago                                 |             |            | crypto/tls. Both clients and servers may send      |
|                  |          |      |                                     |                                    |                                            |             |            | large TLS handshake records which cause servers    |
|                  |          |      |                                     |                                    |                                            |             |            | and clients,...                                    |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-41723   | high     | 7.50 | go                                  | 1.17.13                            | fixed in 1.19.6                            | 15 days     | < 1 hour   | A maliciously crafted HTTP/2 stream could cause    |
|                  |          |      |                                     |                                    | 6 days ago                                 |             |            | excessive CPU consumption in the HPACK decoder,    |
|                  |          |      |                                     |                                    |                                            |             |            | sufficient to cause a denial of service from a     |
|                  |          |      |                                     |                                    |                                            |             |            | small n...                                         |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-41715   | high     | 7.50 | go                                  | 1.17.13                            | fixed in 1.19.2, 1.18.7                    | > 5 months  | < 1 hour   | Programs which compile regular expressions from    |
|                  |          |      |                                     |                                    | > 5 months ago                             |             |            | untrusted sources may be vulnerable to memory      |
|                  |          |      |                                     |                                    |                                            |             |            | exhaustion or denial of service. The parsed regexp |
|                  |          |      |                                     |                                    |                                            |             |            | repre...                                           |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-2880    | high     | 7.50 | go                                  | 1.17.13                            | fixed in 1.19.2, 1.18.7                    | > 5 months  | < 1 hour   | Requests forwarded by ReverseProxy include the     |
|                  |          |      |                                     |                                    | > 5 months ago                             |             |            | raw query parameters from the inbound request,     |
|                  |          |      |                                     |                                    |                                            |             |            | including unparseable parameters rejected by       |
|                  |          |      |                                     |                                    |                                            |             |            | net/http. T...                                     |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-2879    | high     | 7.50 | go                                  | 1.17.13                            | fixed in 1.19.2, 1.18.7                    | > 5 months  | < 1 hour   | Reader.Read does not set a limit on the maximum    |
|                  |          |      |                                     |                                    | > 5 months ago                             |             |            | size of file headers. A maliciously crafted        |
|                  |          |      |                                     |                                    |                                            |             |            | archive could cause Read to allocate unbounded     |
|                  |          |      |                                     |                                    |                                            |             |            | amounts of ...                                     |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-27664   | high     | 7.50 | go                                  | 1.17.13                            | fixed in 1.19.1, 1.18.6                    | > 6 months  | < 1 hour   | In net/http in Go before 1.18.6 and 1.19.x before  |
|                  |          |      |                                     |                                    | > 6 months ago                             |             |            | 1.19.1, attackers can cause a denial of service    |
|                  |          |      |                                     |                                    |                                            |             |            | because an HTTP/2 connection can hang during       |
|                  |          |      |                                     |                                    |                                            |             |            | closing...                                         |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2023-0286    | high     | 7.40 | openssl                             | 1.1.1q-r0                          | fixed in 1.1.1t-r0                         | 35 days     | < 1 hour   | There is a type confusion vulnerability relating   |
|                  |          |      |                                     |                                    | 36 days ago                                |             |            | to X.400 address processing inside an X.509        |
|                  |          |      |                                     |                                    |                                            |             |            | GeneralName. X.400 addresses were parsed as an     |
|                  |          |      |                                     |                                    |                                            |             |            | ASN1_STRIN...                                      |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-41723   | high     | 7.00 | golang.org/x/net                    | v0.0.0-20211015210444-4f30a5c0130f | fixed in 0.7.0                             | 15 days     | < 1 hour   | A maliciously crafted HTTP/2 stream could cause    |
|                  |          |      |                                     |                                    | 26 days ago                                |             |            | excessive CPU consumption in the HPACK decoder,    |
|                  |          |      |                                     |                                    |                                            |             |            | sufficient to cause a denial of service from a     |
|                  |          |      |                                     |                                    |                                            |             |            | small n...                                         |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-27664   | high     | 7.00 | golang.org/x/net                    | v0.0.0-20211015210444-4f30a5c0130f | fixed in 0.0.0-20220906165146-f3363e06e74c | > 6 months  | < 1 hour   | In net/http in Go before 1.18.6 and 1.19.x before  |
|                  |          |      |                                     |                                    | 26 days ago                                |             |            | 1.19.1, attackers can cause a denial of service    |
|                  |          |      |                                     |                                    |                                            |             |            | because an HTTP/2 connection can hang during       |
|                  |          |      |                                     |                                    |                                            |             |            | closing...                                         |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-27191   | high     | 7.00 | golang.org/x/crypto                 | v0.0.0-20210921155107-089bfa567519 | fixed in 0.0.0-20220314234659-1baeb1ce4c0b | > 12 months | < 1 hour   | The golang.org/x/crypto/ssh package before         |
|                  |          |      |                                     |                                    | 26 days ago                                |             |            | 0.0.0-20220314234659-1baeb1ce4c0b for Go           |
|                  |          |      |                                     |                                    |                                            |             |            | allows an attacker to crash a server in certain    |
|                  |          |      |                                     |                                    |                                            |             |            | circumstances invo...                              |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-21698   | high     | 7.00 | github.com/prometheus/client_golang | v1.4.1                             | fixed in 1.11.1                            | > 1 years   | < 1 hour   | client_golang is the instrumentation library for   |
|                  |          |      |                                     |                                    | 29 days ago                                |             |            | Go applications in Prometheus, and the promhttp    |
|                  |          |      |                                     |                                    |                                            |             |            | package in client_golang provides tooling around   |
|                  |          |      |                                     |                                    |                                            |             |            | HTTP...                                            |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2021-44716   | high     | 7.00 | golang.org/x/net/http2              | v0.0.0-20211015210444-4f30a5c0130f | fixed in 0.0.0-20211209124913-491a49abca63 | > 1 years   | < 1 hour   | net/http in Go before 1.16.12 and 1.17.x before    |
|                  |          |      |                                     |                                    | 36 days ago                                |             |            | 1.17.5 allows uncontrolled memory consumption      |
|                  |          |      |                                     |                                    |                                            |             |            | in the header canonicalization cache via HTTP/2    |
|                  |          |      |                                     |                                    |                                            |             |            | requests...                                        |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2021-43565   | high     | 7.00 | golang.org/x/crypto                 | v0.0.0-20210921155107-089bfa567519 | fixed in 0.0.0-20211202192323-5770296d904e | > 6 months  | < 1 hour   | The x/crypto/ssh package before                    |
|                  |          |      |                                     |                                    | 26 days ago                                |             |            | 0.0.0-20211202192323-5770296d904e of               |
|                  |          |      |                                     |                                    |                                            |             |            | golang.org/x/crypto allows an attacker to panic an |
|                  |          |      |                                     |                                    |                                            |             |            | SSH server.                                        |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2023-23915   | medium   | 6.50 | curl                                | 7.80.0-r3                          | fixed in 7.80.0-r6                         | 20 days     | < 1 hour   | A cleartext transmission of sensitive information  |
|                  |          |      |                                     |                                    | 28 days ago                                |             |            | vulnerability exists in curl <v7.88.0 that could   |
|                  |          |      |                                     |                                    |                                            |             |            | cause HSTS functionality to behave incorrectly     |
|                  |          |      |                                     |                                    |                                            |             |            | when...                                            |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-43552   | medium   | 5.90 | curl                                | 7.80.0-r3                          | fixed in 7.80.0-r5                         | 34 days     | < 1 hour   | A use after free vulnerability exists in curl      |
|                  |          |      |                                     |                                    | 84 days ago                                |             |            | <7.87.0. Curl can be asked to *tunnel* virtually   |
|                  |          |      |                                     |                                    |                                            |             |            | all protocols it supports through an HTTP proxy.   |
|                  |          |      |                                     |                                    |                                            |             |            | HTTP p...                                          |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-4304    | medium   | 5.90 | openssl                             | 1.1.1q-r0                          | fixed in 1.1.1t-r0                         | 35 days     | < 1 hour   | A timing based side channel exists in the OpenSSL  |
|                  |          |      |                                     |                                    | 36 days ago                                |             |            | RSA Decryption implementation which could be       |
|                  |          |      |                                     |                                    |                                            |             |            | sufficient to recover a plaintext across a network |
|                  |          |      |                                     |                                    |                                            |             |            | in a...                                            |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-41716   | medium   | 5.40 | go                                  | 1.17.13                            | fixed in 1.19.3, 1.18.8                    | > 4 months  | < 1 hour   | Due to unsanitized NUL values, attackers may be    |
|                  |          |      |                                     |                                    | > 4 months ago                             |             |            | able to maliciously set environment variables on   |
|                  |          |      |                                     |                                    |                                            |             |            | Windows. In syscall.StartProcess and os/exec.Cmd,  |
|                  |          |      |                                     |                                    |                                            |             |            | inv...                                             |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| PRISMA-2022-0164 | medium   | 5.30 | github.com/aws/aws-sdk-go           | v1.34.13                           | fixed in v1.40.27                          | > 10 months | < 1 hour   | github.com/aws/aws-sdk-go module prior to v1.40.27 |
|                  |          |      |                                     |                                    | > 10 months ago                            |             |            | is vulnerable to Information Exposure. The SDK     |
|                  |          |      |                                     |                                    |                                            |             |            | did not automatically suppress sensitive API       |
|                  |          |      |                                     |                                    |                                            |             |            | paramet...                                         |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2023-24532   | medium   | 5.30 | go                                  | 1.17.13                            | fixed in 1.20.2, 1.19.7                    | 7 days      | < 1 hour   | The ScalarMult and ScalarBaseMult methods of       |
|                  |          |      |                                     |                                    | 13 hours ago                               |             |            | the P256 Curve may return an incorrect result if   |
|                  |          |      |                                     |                                    |                                            |             |            | called with some specific unreduced scalars (a     |
|                  |          |      |                                     |                                    |                                            |             |            | scalar la...                                       |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-41717   | medium   | 5.30 | go                                  | 1.17.13                            | fixed in 1.19.4, 1.18.9                    | > 3 months  | < 1 hour   | An attacker can cause excessive memory growth in a |
|                  |          |      |                                     |                                    | > 3 months ago                             |             |            | Go server accepting HTTP/2 requests. HTTP/2 server |
|                  |          |      |                                     |                                    |                                            |             |            | connections contain a cache of HTTP header keys    |
|                  |          |      |                                     |                                    |                                            |             |            | ...                                                |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+
| CVE-2022-41717   | moderate | 4.00 | golang.org/x/net/http2              | v0.0.0-20211015210444-4f30a5c0130f | fixed in 0.4.0                             | > 3 months  | < 1 hour   | An attacker can cause excessive memory growth in a |
|                  |          |      |                                     |                                    | 57 days ago                                |             |            | Go server accepting HTTP/2 requests. HTTP/2 server |
|                  |          |      |                                     |                                    |                                            |             |            | connections contain a cache of HTTP header keys    |
|                  |          |      |                                     |                                    |                                            |             |            | ...                                                |
+------------------+----------+------+-------------------------------------+------------------------------------+--------------------------------------------+-------------+------------+----------------------------------------------------+

Vulnerabilities found for image ubercadence/server:0.25.0: total - 30, critical - 3, high - 19, medium - 8, low - 0
Vulnerability threshold check results: PASS

Compliance Issues
+----------+------------------------------------------------------------------------+
| SEVERITY |                              DESCRIPTION                               |
+----------+------------------------------------------------------------------------+
| high     | (CIS_Docker_v1.3.1 - 4.1) Image should be created with a non-root user |
+----------+------------------------------------------------------------------------+
| high     | Private keys stored in image                                           |
+----------+------------------------------------------------------------------------+

Compliance found for image ubercadence/server:0.25.0: total - 2, critical - 0, high - 2, medium - 0, low - 0
Compliance threshold check results: PASS

List of CVEs raised:
curl

CVE-2022-42915
CVE-2022-32221
CVE-2023-23914
CVE-2023-23916
CVE-2022-43551
CVE-2022-42916
CVE-2023-23915
CVE-2022-43552

go

CVE-2022-41725
CVE-2022-41724
CVE-2022-41723
CVE-2022-41715  fixed by #5035 (pending review)
CVE-2022-2880 fixed by #5035 (pending review)
CVE-2022-2879  fixed by #5035 (pending review)
CVE-2022-27664  fixed by #5035 (pending review)
CVE-2022-41716  fixed by #5035 (pending review)
CVE-2023-24532
CVE-2022-41717

golang.org

CVE-2022-27191
CVE-2021-43565
CVE-2022-41723
CVE-2022-27664
CVE-2021-44716
CVE-2022-41717

openssl

CVE-2023-0215
CVE-2022-4450
CVE-2023-0286
CVE-2022-4304

github.com

PRISMA-2022-0164
CVE-2022-21698

Compliant issues:

CIS_Docker_v1.3.1 - 4.1 Image should be created with a non-root user
Private keys stored in image

Expected behavior
CVEs scanned by twistlock are fixed
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here, E.g. Stackstace, workflow history.

Since new version of cadence/server is released and many CVEs are remediated, I'd like to close this issue


Add waves to cdnjs

Would be nice to see Waves added to cdnjs (https://github.com/cdnjs/cdnjs)

+1

Happy to handle this with permission.

It seems someone has add Waves to cdnjs. To the person who do this, thank you very much! :+1:


MethodType takes different number of arguments on Python 3?

See https://github.com/timj/scons/blob/u/timj/python3/src/engine/SCons/Util.py#L1435
Is a problem on Windows (MSVC) Python 3.5

See also http://bugs.python.org/issue25435

Get bound method with function.get(obj.class, obj)


Double click does not activate box for scrolling

When without a wheel mouse, I absolutely need to use arrow keys and PgDn PgUp to move up and down. But double click on e.g. somewhere in the Editor box does not activate the box, and it is still another box which is scrolling down rather than this one, thus forcing me to use the vertical slider rather than arrow keys.

This is specific to Firefox, Chrome, and Chrome-based browsers work. I will inspect the reasoning behind this...

I am going to remove the user-select: none;, which will enable users to copy text. Also, I am adding window.getSelection()?.removeAllRanges(); before the middle panels resize to "deselect" the accidentally selected text. This is a compromise to this issue and issue #892.
https://user-images.githubusercontent.com/12932677/219655050-26323818-5669-4574-89fc-88bb327a7597.mp4


Filtering off Log-Messages in Formatter not possible

Version: 2.1.0
When i try to only return text for the defined log-level like this:
this.logger.add(
        new SlackHook({
          webhookUrl: slackHookURl,
          level: 'verbose',
          formatter: (info) => {
            if (info.level == 'verbose') {
              return { text: info.message };
            }
          },
        }),
      );

the Hook will not work anymore.
Only if i return something in every other case, it starts working again.
this.logger.add(
        new SlackHook({
          webhookUrl: slackHookURl,
          level: 'verbose',
          formatter: (info) => {
            if (info.level == 'verbose') {
              return { text: info.message };
            }
            return { text: ' ' };
          },
        }),
      );

Crap, I did not realize this issue existed... apologies for the delay!
That's an interesting issue there... I suppose if we have a default payload in the event nothing is returned that should address it? I'll play around with it and see what can be done.

Fixed in v2.2.3. Thanks again to @ArturAralin for the fix!


Update to es6 module syntax

module myModule from 'my-module' became import * as myModule from 'my-module'
http://jsmodules.io/
I think many of you are already aware of that. I'm just posting it as an issue because it needs to be addressed.

Released in 3.0.2


Keyboard shortcut

Hi, great plugin.
Could you add keyboard shortcut to toggle search bar?
https://github.com/monsterkodi/tree-view-filter use ctrl-alt-shift-f and I think it's a nice one.

Nice advice.
I will add keyboard shortcut as soon as.


Add 3D line plot and zlabel function.

3D line plot function (named plot3) to add Axes3D.plot functionality. Also added zlabel. Tested with my local anaconda 2.7 and 3.7 distributions with and without -DWITHOUT_NUMPY. Example and .png included.

Nice, thanks for contributing!

Hi, I'm using python3.8 on Ubuntu20.04. When I use plot3(), I met the runtime error 'No axis'. How to resolve this?


Green Screen should build and run in debug mode successfully

Fixes #728
Description of the changes:

Changed linking for debug builds for Green Screen and Open CV Compatibility
Changed linking for all all projects to not static link VC binaries.

With this change I am currently getting the following error:
LINK : warning LNK4098: defaultlib 'LIBCMTD' conflicts with use of other libs; use /NODEFAULTLIB:library

for:

transformation_example.exe
test_dynlib_1_2.dll
k4arecorder.exe
and others


"Suggestion" Hide Function

Like in the MW Tracker, so I can hide the Weapons that are not important to get DM Ultra

I'll look into it!

Added a filter that hides the rest of the weapons in each category when that category is completed.


weight conversion for styleCLIP input

Hi, I am currently trying to convert weights so i can obtain checkpoints for stylegan2 trained on the car and church dataset to input into styleCLIP. However my conversion does not seem to be correct as I feel somehow the colours are being distorted

I think it is a resolution problem. I think you have used 1024px when checkpoint is trained on 256px. You need to use 256px models.


Not able to use zod validations in front-end. process is undefined error.

I am using a mono-repo have defined the tables, their types & zod validations in a common package, where the db is not initialised & only the the tables are defined.
orchid has a devDependency of pg. which uses process.env in their code. Which is throwing an error in frontend as process is undefined. Is there a work around for this? My frontend is Reactjs + Vite.
Thanks

I tried defining process at the global so the above issue was bypassed but ran into other issues like it is now searching for the crypto library.  Buffer is not defined error.
Is there someway we can use generated zod validations on the frontend? I dont want to re-write them, it leads to only errors in the long-run.

I was a bit busy earlier, and planning to start figuring out new issues today and tomorrow.
As for this issue, I should make it clear in the docs that it is not suited for reusing zod validations in the frontend.
It's only suitable to use in the backend.
Because if you try to use the derived zod validation in your monorepo frontend, it means that your frontend will also pull the code of orchid orm and pg, increasing bundle size drastically.
So I'm afraid that for now, the only thing to do here is to define zod schemas manually separately from orchid-orm.
In the future, there could be a feature to generate those zod schemas separately, but that's for the future without ETA.

Totally get that. Maybe this is something we can work on when we adapt orchid for serverless environment, which would need proper modularisation & seperation of concerns... wheneever that is 🤞


rename HeaterCooler_T to PrescribedOutlet

using a conversion script as described in #98
Opening the PR, so the changes are easily visible,
but more work is needed as the examples still do not work

PrescribedOutlet is more capable than HeaterCooler_T was and because of that has more inputs/outputs. Since all instances of the old HeaterCooler_T are used as heaters only, we can substitute HeaterCooler_T with the new Heater_T instead of PrescribedOutlet which has the same connectors.


Prohibited Validation rule fails on empty array

Laravel Version: 9.25.1
PHP Version: 8.1.6
Database Driver & Version: N/A

Description:
$v = Validator::make(['test' => []], ['test' => 'prohibited']);
$v->fails();

This returns true.
Docs for this validation rule say:

The field under validation must be empty or not present.

So I expected this to pass. (Array is empty after all). Not sure if this is a bug or incomplete docs?

I think this specifically was added for strings, not array but I do agree with the confusion here. Will talk it over with the team.

Similar result with NULL.
$v = \Illuminate\Support\Facades\Validator::make(['test' => NULL], ['test' => 'prohibited']);
$v->fails(); //true

$v = \Illuminate\Support\Facades\Validator::make(['test' => ''], ['test' => 'prohibited']);
$v->fails(); // false

@SamuelMwangiW that's expected actually. The key test is present. So I'd expect that to fail.

I've sent in a PR to the docs to clarify that this rule only works with strings. Thanks

@driesvints It seems that the documentation corrected in laravel/docs#8150 has been reverted back to the incorrect description by laravel/docs@edf107be3918200984e2f5723c3e1137dbe6469d.
If the behavior has not changed due to an update, I believe it needs to be corrected again.

Honestly it's been too long since I gave this any thought. If you feel the docs are incorrect feel free to attempt a PR 👍

@proudust I just tested with the latest version of the framework and validation no longer fails on an empty array or NULL.
Below is my test.
use Illuminate\Support\Facades\Validator;

test('prohibited allows empty values',function (mixed $value){
    $v = Validator::make(['test' => $value], ['test' => 'prohibited']);

    expect($v->fails())->toBeFalse();
})->with([
    'null' => [null],
    'empty array' => [[]],
    'empty string' => [''],
    'empty collection' => [collect()],
]);


Bundling of Tokens

Aggregating multiple, distinct underlying assets

we can do this in the metadata without having to alter the behavior of the contract

Need to determine if this work is still relevant


Startup Overlay

For the life of me I can not figure out how to set when my MagicMIrror starts up to default from "wind" to "Rain, Thunder".
Any ideas?

Figured it out. Thought I’d share.
Had to add:
overlay: ‘rain’,
To the config: section within the config.js file in MagicMirror/config/


Overheat Sensors all changed

Just upgraded to 2.9.0 and noticed that all devices (I only have four...) seem to have changed their overheat sensors.
Largely cosmetic but I do have some old entities to delete now.
The old overheat sensors (with a fire icon) have been replaced with an _2 sensor with a thermometer icon

this is across some lights and smart plugs

Upgrade to 2.9.1 which fixes overheat icon. Remove both entity and reload integration


Provide an ability to silence logs being emitted by nltk

Hey team,
Thanks for the awesome work you folks have done.
I needed help with one small thing. Right now, we do in the code nltk.download(package), which emits some logs in unstructured format, and hence is polluting in our observability platform.
Is there a way to disable this behavior?
nltk provides this ability by passing quiet parameter to download function.. Source
Is there an easy way to disable this?
Thanks so much once again!

Hi @SinghCoder ! Thanks for the suggestion. We'll add this in when we get a chance, or feel free to open a PR and we'd be happy to review.

@MthwRobinson, faced the same problem in my agentic app and decided to quiet the logs from the function above. I am adding a PR for this issue for your review.

Thanks @tonykipkemboi ! I'll review that today

Closed #3350 because we stopped using nltk.download in #3361 due to CVE-2024-39705. Going to close this issue because we no longer hit the function that emits the logs.


@W-15490276@ Improved auth error logging for PWA Kit v2

This is the v2 version of #2028 and is related to #1829
There are a few ways in which a call to SLAS to consume a refresh token can fail. For example, the client id the refresh token is associated with might be different from the client id included with the request.
Before this change, when the refresh token call fails, we do not clear the bad refresh token from local / cookie storage. As a result, when the user tries to log in again, the system will re-try with the same bad refresh token until the refresh token expires after 90 days or is manually cleared.
This change clears the refresh token when the refresh token fails.
This change also updates logging so that calls to the SLAS /authorize, /authenticate, and /token endpoints are logging error messages when they fail.
For v2, I updated SLAS calls to include the channel_id property
Testing the changes:
Refresh login (note: the refresh login request happens client side only):

Start the app with these changes locally (this will start the app against zzrf-001)
Delete the access token in your local store
On a different browser window, open up https://test.phased-launch-testing.com/ and grab the refresh token
Copy the refresh token from test.phased-launch-testing into the cc-nx-g cookie on the tab that is open on zzrf-001 (on v2, the refresh token is on local storage by default)
Refresh the tab on zzrf-001
See in the browser console that there is a log entry for commerce-sdk-react ERROR invalid organizationId
Verify that your refresh token was replaced with a new one that is usable for zzrf-001

New guest login:

In default.js, set an invalid client ID
Start the app (make sure you don't have an existing refresh token or access token)
In server logs, see that there is a log entry for 400 Bad Request with a descriptive SLAS error message (ie. client_id must be 36 chars)
In browser console, see the same message.

@vcua-mobify What are the incentives of merging into v2.8? The change is in the template itself, existing customers are not able to consume these changes from upgrading npm, and there will be no new customers using v2. What we can do is refer customers to this PR so they can make change if needed, we don't need to merge it

As the change is to the template-retail-react-app, we will not merge as we do not expect any new projects to begin on v2.
Existing v2 projects should refer to this PR to see how refresh token and new guest login errors can be handled.


Suppress warnings on macOS 10.12.

This came in while I was preparing to merge #50 into the pu branch.
Let us know if you find out whether the wrapper is still effective or no longer necessary (or if the OS has regressed and is once again necessary even for pasteboard access).

Oops, I did not realize the existence of #50. 😿


Add 'Singles' type alongside 'Collections'

Original idea as outlined by @erquhart
Idea:
Allow for a 'Singles' content type, designed for one-off, often publicly-published pages such as 'About', 'Contact', etc. Anything that would not be appropriate as a repeatable object template in the way that 'folder' type Collections work in the CMS today.
This allows for the distinction in the 'Content' interface of these different content types. Collections allow for (+) buttons, Singles do not, as they are one-off.  This is largely represented in the 'file' Collection type available in the CMS today.

@erquhart Please let me know if I've made anything unclear or vague here

This looks good on the UX side. I would only add that the CMS would need to support singles before this could move forward. It may be as simple as giving different treatment to file type collections with only one entry.

We've sort of discussed this elsewhere, but because the distinction between "collections" and "singles" is more of an implementation detail, I don't think having this automatic sorting in the UI is going to be helpful to editors.
It would be a bigger lift, but I think a more useful way of handling this would be to give implementers a way to group the labels in the sidebar. That way the UI can be made to fit the content it represents. It could be cool to have labels for each group, but even being able to add a separator somewhere in the list would be an improvement.

@verythorough that's an excellent point, and it has strong precedent in major SAAS CMS solutions like Contentful. Either way, we need to handle singles (clicking the link in the sidebar opens an entry directly), but the "editable sidebar" you're describing would be a great add post-1.0.
We should port this to a separate issue for proper tracking.

@tech4him1 I arrived at a similar idea in a duplicate. The terms are slightly different, but same idea:
...
collections:
    - name: blog
      label: Blog
      folder: collections/blog
      create: true
      fields:
        - { name: "title", label: "Blog posting title" }
        - { name: "published", label: "Published", widget: "boolean", default: true}
        - { name: "date", label: "Date", widget: date }
        - { name: "author", label: "Author"}
        - { name: "body", label: "Resume", widget: "markdown" }
  - name: author
    label: Author
    file: collections/author.yaml
    fields:
      # somehow make this a list
      - { name: "id", label: "ID" }
      - { name: "bio", label: "Biography" }
  - group: "News items"
    - name: news
      label: Articles
      folder: collections/news
      create: true
      fields:
        - { name: "title",
        ...

Please, be a good bot and don't close this. @erquhart promised us changes soon. Let him close it when it's time 🙂

Marking as pinned so it won't get flagged again

Any update on that ?

Hi @LeoMartinDev, the best way to move this forward is through a contribution.

With the new maintainers taking over, this issue would be good to revist.


OCPP 1.6J - fully compliant?

Hello,
Is the library fully compliant with OCPP 1.6J?
Thanks!

Hello, the library is OCPP-J 1.6 compliant (OCPP 2.0.1 coming soon), except for the security extension. I will include the extension as soon as v2.0.1 is finished, since many of the security features are in common.
There are currently no plans to support OCPP-S, as this was dropped from v2 onwards anyway.
Cheers!


Is it possible to copy a file from normal Android file storage into scoped storage?

Hello, sorry as I should probably be able to figure this out on my own...but it is possible to call copyFile to move a file from a normal file storage directory, into a scoped storage directory?
By "normal" file storage directory I mean files saved to the paths that react-native-fs provides:

MainBundlePath (String) The absolute path to the main bundle directory (not available on Android)
CachesDirectoryPath (String) The absolute path to the caches directory
ExternalCachesDirectoryPath (String) The absolute path to the external caches directory (android only)
DocumentDirectoryPath (String) The absolute path to the document directory
DownloadDirectoryPath (String) The absolute path to the download directory (on android only)
TemporaryDirectoryPath (String) The absolute path to the temporary directory (falls back to Caching-Directory on Android)
LibraryDirectoryPath (String) The absolute path to the NSLibraryDirectory (iOS only)
ExternalDirectoryPath (String) The absolute path to the external files, shared directory (android only)
ExternalStorageDirectoryPath (String) The absolute path to the external storage, shared directory (android only)

Whenever I call copyFile using these paths (although I haven't tried all of them yet) I get a read/write permission error, such as:

Error: 'file://storage/emulated/0/Android/data/com.podverse/files/imYqxyt4gk.mp3'does not have permission to read/write

We're using react-native-background-downloader, and I haven't been able to figure out a way to get files downloaded with it into scoped storage...it seems like react-native-background-downloader library just won't work with content:// as a destination, and react-native-scoped-storage can't read files from the paths I listed above...so it seems like we're stuck? No workarounds? Any info or advice would be appreciated.

@mitchdowney yes it is possible.
copyfile takes three arguments
uri of source
uri of destination
and callback
make sure you provide uri only not path . and the uri should not be document tree selected uri

Update to 1.9.3. it supports reading and writing to normal paths such as cache and data directory.

@ambessh hmm I have 1.9.3 installed, and I'm not sure what I'm doing wrong then...
When I call this:
const result = await ScopedStorage.stat(file:/${origDestination})
and origDestination = "/data/user/0/com.podverse/files/_qhiTuJQT.mp3"
I get:

Error: 'file://data/user/0/com.podverse/files/_qhiTuJQT.mp3'does not have permission to read/write

Is that an invalid uri?
Also, the copyFile call I am attempting is:
await ScopedStorage.copyFile(file://data/user/0/com.podverse/files/6NvramAVN.mp3, content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodcasts/document/01F6-AC3F%3APodcasts/6NvramAVN.mp3, () => {})
That doesn't throw an error, but the file doesn't get saved to the SD card either...is there anything you can see I'm doing wrong? I'm not using a callback, but I'm not sure I need to?

@ambessh hmm I have 1.9.3 installed, and I'm not sure what I'm doing wrong then...
When I call this:
const result = await ScopedStorage.stat('file://data/user/0/com.podverse/files/_qhiTuJQT.mp3')
I get:

Error: 'file://data/user/0/com.podverse/files/_qhiTuJQT.mp3'does not have permission to read/write

Is that an invalid uri? (that is the RNFS.DocumentDirectoryPath btw)
Also, the copyFile call I am attempting is:
await ScopedStorage.copyFile(`file://data/user/0/com.podverse/files/6NvramAVN.mp3`, content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodcasts/document/01F6-AC3F%3APodcasts/6NvramAVN.mp3, () => {})

That doesn't throw an error, but the file doesn't get saved to the SD card either...is there anything you can see I'm doing wrong? I'm not using a callback, but I'm not sure I need to?

+1

@mitchdowney during copy file i had the same issue . it was not saving it and the callback was returning nothing.
Go to -> node modules/react-native-scoped-storage/android/src/main/java/com/amaarahmed/scopedstorage/RNScopedStorageModule.java
search copyFile function in that java file and replace with this
@ReactMethod
 public void copyFile(String path, String dest, Callback callback) {
     String pathToUri = Uri.fromFile(new File(path)).toString();
     AsyncTask.execute(() -> {

         InputStream in = null;
         OutputStream out = null;
         String message = "";

         try {
             if (!exists(pathToUri)) {
                 message = "Source file does not exist";
                 callback.invoke((message));
                 return;
             }
             ParcelFileDescriptor inputDescriptor = reactContext.getContentResolver().openFileDescriptor(Uri.parse(pathToUri), "rw");
             in = new FileInputStream(inputDescriptor.getFileDescriptor());

             if (!exists(dest)) {
                 message = "Destination file does not exist. Please create destination file with createFile.";
                 callback.invoke((message));
                 return;
             }

             ParcelFileDescriptor outputDescriptor = reactContext.getContentResolver().openFileDescriptor(Uri.parse(dest), "rw");
             out = new FileOutputStream(outputDescriptor.getFileDescriptor());

             byte[] buf = new byte[10240];
             int len;
             while ((len = in.read(buf)) > 0) {
                 out.write(buf, 0, len);
             }
         } catch (Exception err) {
             message += err.getLocalizedMessage();
         } finally {
             try {
                 if (in != null) {
                     in.close();
                 }
                 if (out != null) {
                     out.close();
                 }
             } catch (Exception e) {
                 message += e.getLocalizedMessage();
             }
         }

         if (message != "") {
             callback.invoke(message);
         } else {
             callback.invoke();
         }

    });

 }

and now in react javascript dont pass uri in the first argument of copyfile function . just pass normal path . It will work.
laters you can create a patch of the package.

@ammarahm-ed I tried your code, updated RNScopedStorageModule.java (verified the changes are used in the react native app), then call this:
await ScopedStorage.copyFile("/storage/emulated/0/Download/lwx0wMYSjP.mp3", "content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodverse/document/01F6-AC3F%3APodverse/lwx0wMYSjP.mp3", (msg) => {
  console.log('ScopedStorage.copyFile msg', msg)
})

But then I get:

ScopedStorage.copyFile msg Failed to open for writing: java.io.FileNotFoundException: open failed: EISDIR (Is a directory)

Any ideas what the "EISDIR is a directory" is about? That path and uri does not seem like a directory to me...
I also tried this:
await ScopedStorage.createFile("content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodverse/document/01F6-AC3F%3APodverse/", `${episode.id}${ext}`, 'audio/mpeg')
await ScopedStorage.copyFile("/storage/emulated/0/Download/lwx0wMYSjP.mp3", "content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodverse/document/01F6-AC3F%3APodverse/lwx0wMYSjP.mp3", (msg) => {
  console.log('ScopedStorage.copyFile msg', msg)
})

And I verified the file is created as expected...but I still get the "is a directory" error.

@ammarahm-ed eureka! copyFile works for me is I use the uri:
content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodverse/document/01F6-AC3F%3APodverse%2Flwx0wMYSjP.mp3
With the URL encoded %2F character instead of /. Not sure why it's necessary...but it's finally saving to the SD card! Thank you for your help 🙏

@ammarahm-ed ahhh...but there's a bug with this...
It seems like the %2F sometimes works, and sometimes throws a "ENOENT No such file or directory" error:
Works:

content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodcasts/document/01F6-AC3F%3APodcasts%2Fesgi0q1Pm.mp3
content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodcasts/document/01F6-AC3F%3APodcasts%2FuJbRmLuc0.mp3

Fails with ENOENT error:

content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodcasts/document/01F6-AC3F%3APodcasts%2FGwHcavR3a.mp3
content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodcasts/document/01F6-AC3F%3APodcasts%2F6gWMTVqam.mp3

I guess there is some kind of URL encoded clash, depending on the first character of the file id?

@mitchdowney pls dont hardcode it . Get uri from when you create the file .

@ambessh I was getting very buggy and inconsistent results with this...but I think it may have been conflicts caused by identical files already existing in the temporary Documents directory path previously.
After wiping the app completely and deleting all data, this code seems to work consistently when run in the react-native-background-downloader done method:
if (customLocation) {
    const tempDownloadFileType = await ScopedStorage.stat(origDestination)
    const newFileType = await ScopedStorage.createFile(customLocation, `${episode.id}${ext}`, 'audio/mpeg')
    if (tempDownloadFileType && newFileType) {
      const { uri: tempFileUri } = tempDownloadFileType
      const { uri: newFileUri } = newFileType
      await ScopedStorage.copyFile(tempFileUri, newFileUri, (msg) => {
        console.log('ScopedStorage.copyFile msg', msg)
      })
      await ScopedStorage.deleteFile(tempFileUri)
    }
}

HOWEVER, stat throws a "cannot read/write" permissions error. I had to go into the RNScopedStorageModule and modify the hasPermission function so that it always returns true. This is obviously no good...but why is read/write permission even needed for the DocumentsDirectoryPath? Shouldn't it only be "read" permission that is needed? And isn't this a path that we should be able to read/write to by default anyway, even with scoped storage?

@mitchdowney yes it is possible.
copyfile takes three arguments
uri of source
uri of destination
and callback
make sure you provide uri only not path . and the uri should not be document tree selected uri

Can you please share some code ?

@ammarahm-ed eureka! copyFile works for me is I use the uri:
content://com.android.externalstorage.documents/tree/01F6-AC3F%3APodverse/document/01F6-AC3F%3APodverse%2Flwx0wMYSjP.mp3
With the URL encoded %2F character instead of /. Not sure why it's necessary...but it's finally saving to the SD card! Thank you for your help 🙏

hey bro , i am facing issue "source file not exist" and i  used this uri : 'content://com.android.externalstorage.documents/tree/primary%3AAndroid%2Fmedia%2Fcom.whatsapp%2FWhatsApp%2FMedia%2F.Statuses/document/primary%3AAndroid%2Fmedia%2Fcom.whatsapp%2FWhatsApp%2FMedia%2F.Statuses%2F'
could you pls tell me where i am wrong ?


Kubernetes 1.22 dose not work with pouch

Ⅰ. Issue Description
Kubelet cannot start containers.
Aug 12 17:26:37 alma8 kubelet[9233]: E0812 17:26:37.202196    9233 pod_workers.go:747] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-controller-manager\" with CreateContainerError: \"failed to apply container security context for container \\\"kube-controller-manager\\\": failed to generate seccomp security options: undefault profile \\\"runtime/default\\\" should prefix with \\\"localhost/\\\"\"" pod="kube-system/kube-controller-manager-alma8" podUID=520e787941d90fc4adceac0d0d920cf1

Ⅲ. Describe what you expected to happen
Kubernets woking with pouch.
Ⅳ. How to reproduce it (as minimally and precisely as possible)
I installed my invironment based your documentation:
https://github.com/alibaba/pouch/blob/master/docs/kubernetes/pouch_with_kubernetes_deploying.md
Ⅵ. Environment:

pouch version (use pouch version):
OS (e.g. from /etc/os-release): alamlinux 8
Kernel (e.g. uname -a): Linux alma8 4.18.0-305.el8.x86_64 #1 SMP Wed May 19 18:55:28 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
Install tools: kubeadm 1.22.0

@Novicei When it will be released? The last release was in 2019. Is this project still alive?

i thins it is dead


add the controller for meetings only have post or talk

Purpose
Give the ability for single meeting to only have poster or talk. Closes https://github.com/CenterForOpenScience/osf.io/issues/1365.

Please double-check your syntax here and test locally. When that's done, I'll do next pass.

@sloria rdy for review

#OSF-4211

Pass finished.
Two small comments, but otherwise this looks good.
Please always run your code and examine the page before submitting something to code review. (the script workarounds we discussed yesterday should work)

Changes look good to me. :shipit:

In order for us to test this on staging, the dev_populate_conferences.py script will also need to be updated. @chennan47 Can you look into this?

@sloria update done. Rdy for another pass.


Add dynamic post params

Hi,
Would it be possible to add dynamic parameters when uploading a file?
I thought the query: key would do this on construction of a new Resumable, but I cannot provide a callback.
Whenever I try that I get that function submitted to the server instead of the return value of the function.

query is currently just a flat hash, can you provide an example of how you would want to extend functionality?
Steffen

I was thinking about the possibility to add a callback function as a value in that map.
However, I just found out that I can mutate the opts.query map when adding a file, which is sufficient in my case, it just was not obvious to me.


Metadata unification step

Coverage remained the same at 100.0% when pulling 960b39ae024f98eb73f18d30b5904492f1cd366d on CyberiaResurrection:MetadataUnificationStep into 4381fdd0e8f09df7ebe9c4f889fd596a0e7352b8 on Algo-Web:master.

Coverage remained the same at 100.0% when pulling 960b39ae024f98eb73f18d30b5904492f1cd366d on CyberiaResurrection:MetadataUnificationStep into 4381fdd0e8f09df7ebe9c4f889fd596a0e7352b8 on Algo-Web:master.

Coverage remained the same at 100.0% when pulling 1a53127580612fab9866e7223d859ee14a144c4c on CyberiaResurrection:MetadataUnificationStep into 4381fdd0e8f09df7ebe9c4f889fd596a0e7352b8 on Algo-Web:master.

Coverage remained the same at 100.0% when pulling 1a53127580612fab9866e7223d859ee14a144c4c on CyberiaResurrection:MetadataUnificationStep into 4381fdd0e8f09df7ebe9c4f889fd596a0e7352b8 on Algo-Web:master.

Coverage remained the same at 100.0% when pulling 1a53127580612fab9866e7223d859ee14a144c4c on CyberiaResurrection:MetadataUnificationStep into 4381fdd0e8f09df7ebe9c4f889fd596a0e7352b8 on Algo-Web:master.

Coverage remained the same at 100.0% when pulling 0c4be9227a827a9b2a4911993cdc3814295c9b05 on CyberiaResurrection:MetadataUnificationStep into 4381fdd0e8f09df7ebe9c4f889fd596a0e7352b8 on Algo-Web:master.

Coverage remained the same at 100.0% when pulling 1b291a75dfc919525d868cff551ae3cae6e2f136 on CyberiaResurrection:MetadataUnificationStep into 4381fdd0e8f09df7ebe9c4f889fd596a0e7352b8 on Algo-Web:master.


Add INIT_SGA_PERCENTAGE for smarter memory allocation

This is another take for the issue reported in https://github.com/oracle/docker-images/pull/2238.
I believe this is a much better and cleaner approach than the one used in https://github.com/oracle/docker-images/pull/1742, and that's why it replaces the existing one.
Furthermore, now the default configuration is smarter. If the user allocates 3GB for the container, it will be used. Previously, to make use of more than 2GB, the user would have
to:

Know that the default configuration is limited to 2GB. This is already something that most users would not know.
Allocate more than 2GB by tweaking INIT_SGA_SIZE and INIT_PGA_SIZE, which in turn would require some manual calculations as well (which is always error prone).

Some more caveats are:

The user would need to remember to re-do these calculations everytime the memory allocated for the container is changed.

Now, just out of curiosity, why do we bother tweaking SGA/PGA values instead of just tweaking the total memory?

@felipecrs INIT_SGA and INIT_PGA are honoured when the database is created. If a pre-created database is started again then INIT_SGA and INIT_PGA params are not used. The situation with INIT_SGA_PERCENTAGE is also the same.
So, in the case of prebuiltdb extension, the database is created at the build time and then added as an additional layer on top of the base image. So, neither INIT_SGA/INIT_PGA nor INIT_SGA_PERCENTAGE would work if a database is started using the prebuiltdb extended image. Hence, the prebuiltdb image will not be portable after building on the large envrionments.
Also, we have other products(e.g. OraOperator) that uses the INIT_SGA/INIT_PGA params of SIDB image, so changing that to INIT_SGA_PERCENTAGE will harm this dependence.
PR #2238 will definitely be helpful in this context.

Got it, thanks!


Unable to publish Javascript bot using AZ CLI 2.36.0

Describe the bug
Following this doc to deploy javascript bot:
https://docs.microsoft.com/en-us/azure/bot-service/provision-and-publish-a-bot
After copying this deploymentTemplates  folder into my sample bot.
I ran into an error while using az cli 2.36.0 when attempting to create an app service using the latest ARM template and parameter files after running this command:
az deployment group create –-resource-group <resource-group> --template-file <template-file-path> --parameters <parameters-file-path>

{'code': 'InvalidTemplate', 'message': "Deployment template validation failed: 'The template resource of type 'Microsoft.Web/serverfarms' at line '129' an
d column '5' is not valid. The name property cannot be null or empty. Please see https://aka.ms/arm-template/#resources for usage details.'.", 'additional Inf
o': [{'type': 'TemplateViolation', 'info': {'lineNumber': 129, 'linePosition': 5, 'path': 'properties. template.resources [0]'}}]}

Ultimately, using az cli 2.39.0 and starting over from scratch (w/a few modifications) from the docs, I was able to deploy successfully.
Sharing the steps I took to deploy:

Installed az cli 2.39.0 (latest)
For section Create an identity resource,

Instead of az ad app create --display-name "<name>" --password "<password>" --available-to-other-tenants
I used : az ad app create --display-name "<name>" --sign-in-audience "AzureADandPersonalMicrosoftAccount"

After the above 2 changes, I no longer face issues with the deployment process in the docs.

Note: for step #2.2, signInAudience values can be found here https://docs.microsoft.com/en-us/graph/api/resources/application?view=graph-rest-1.0#signinaudience-values

To Reproduce
Steps to reproduce the behavior:

Use az cli 2.36.0
Follow this doc to deploy a bot
Progress through step 1 in section Create resources with ARM templates
See error after running command az deployment group create –-resource-group <resource-group> --template-file <template-file-path> --parameters @<parameters-file-path>

Summary
Cant deploy JavaScript bot using az cli 2.36.0. Upgrading az cli to 2.39.0 and creating an identity resource with command
az ad app create --display-name "<name>" --sign-in-audience "AzureADandPersonalMicrosoftAccount" solved the issue.
Also, --sign-in-audience parameter doc found here .

Updated instructions for C# and JavaScript are merged and should be live after noon. Waiting on more info to fix the Python and Java instructions.

@ramfattah  - Closing, as I despair of any update to the Java ARM templates. Reopen if hope yet exists.


Tab View Navigation Inconsistent

When viewing a single resulting row with 'TAB' view, I can click on foreign keys and go straight to the foreing record.
Through the left and arrow green keys I can go back and forward trought the selected tables. But when I press the left arrow to go back to my initial result, the tab view is showing me another record.
Step to reproduce:

select * from table1
move to the result grid, select a specific row (the first for example) and press 'TAB' key
select a foreign key on a column -> you should be ported to a tabbed view of the foreing record
press green arrow to go back
RESULT: the previous table is show, but on a different result row
EXPECTED: the arrow should reset to the exact row you previously selected with TAB.

It's likely that the left arrow force dbeaver to redo the initial query, but the order output can be different, so it redirect me in a random row I didn't selected in the first place.

thanks for the report

Does it still reproducible in the latest DBeaver version?


python37Packages.PyGithub: 1.47 -> 1.51

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-PyGithub/versions.
meta.description for python37Packages.PyGithub is: "A Python (2 and 3) library to access the GitHub API v3"
meta.homepage for python37Packages.PyGithub is: "https://github.com/PyGithub/PyGithub"
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.51 with grep in /nix/store/d6rqv69jv1pvg3l9fb4n739g7a80w6nj-python3.7-PyGithub-1.51

directory tree listing: https://gist.github.com/540047c732c7fe41112c11a1b2cf8093

du listing: https://gist.github.com/8e74ebcdbbec51f2de5e2de877426042

Rebuild report (if merged into master) (click to expand)

16 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cligh
python37Packages.PyGithub
python38Packages.PyGithub
sourcehut.dispatchsrht

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d6rqv69jv1pvg3l9fb4n739g7a80w6nj-python3.7-PyGithub-1.51 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python37Packages.PyGithub https://github.com/r-ryantm/nixpkgs/archive/bcdb483cc5c846d98c0b66ab55d46c5a91717bf3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d6rqv69jv1pvg3l9fb4n739g7a80w6nj-python3.7-PyGithub-1.51
ls -la /nix/store/d6rqv69jv1pvg3l9fb4n739g7a80w6nj-python3.7-PyGithub-1.51/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

4 packages built:
- cligh
- python37Packages.PyGithub
- python38Packages.PyGithub
- sourcehut.dispatchsrht

Maintainer pings
cc @jhhuh for testing.

conflict


GroupBy support in emulator

The document states:
Azure Cosmos DB currently supports GROUP BY in .NET SDK 3.3 or later. Support for other language SDK's and the Azure Portal is not currently available but is planned.
However, a group by seems to work in the Azure Portal, but not in the local emulator. What is the plan for the emulator? ETA?

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

ID: c1053c8e-5ce2-c3b4-0aae-576823d19186
Version Independent ID: aa7efcaf-f0fe-34e5-e43b-324e5f3d6432
Content: GROUP BY clause in Azure Cosmos DB
Content Source: articles/cosmos-db/sql-query-group-by.md
Service: cosmos-db
GitHub Login: @timsander1
Microsoft Alias: tisande

@Mortana89 We are checking this and we will get back to you.

@timsander1 As confirmed before you had conveyed that the cross partition group by will available on Portal with the single partition group by very soon.
Please confirm if this has been implemented.
Also please confirm when this will be available for Emulator.

Hi @Mortana89. I can confirm that Group By works (cross-partition or single partition) in the latest .NET sdk, JavaScript sdk, and the Azure Portal. There is support in the Azure Cosmos DB Emulator as well in version 2.7.0 or later.

@Mortana89 As conveyed by our Product group Azure Cosmos DB Emulator version 2.7.0 or later supports this as well.
Please get back to us if you have any further question or we will go ahead and close this thread by EOD.
@timsander1 Thanks for confirming.


Update xml-rs to 0.7.0 and bump version

Sorry for the late merge - thanks!

Can this be released ?

Sorry, I need to figure out the troubles we are having on #427 first. I'll see if I can look at it tonight!

Sure, good luck with that :)

Published!


Define full set of interfaces for client-side implementations

Things like Speckle.RhinoConverter and its Speckle.RevitConverter cousin should implement the same ISpeckleConverter interface. This came out of issue 4 on SpeckleRevit repo where I realised there wasn't a base class or interface defined for what these converters should implement as a minimum.
Same goes for the clients themselves, for example the Rhino client defines an interface for itself in the client repo  (filename doesn't match contents btw @didimitrie @fraguada ) but it doesn't look like Speckle.Core defines or has any opinions on what a client should implement.
Provisional list of interfaces required :

[ ] ISpeckleConverter

[ ] ISpeckleClient

[ ] ISpeckleSender & ISpeckleGetter ?

I might be off-base here, keen to hear what others think ?

@radumg this seems like the right approach in general, though I would defer to those who know better than I about how to handle conversion in Revit. I think for the senders and the receivers it makes sense. This will put some pressure on SpeckleRhino to clean itself up a bit!

Thanks @fraguada - We routinely have to wrap/unwrap Revit classes so To/From extension methods are common i would say, but which ones are need is the question the interface would answer, providing a mini-roadmap of what the Revit converter would need.
For example, i assume to/from points, lines, curves etc are needed, but how far do we go with the other more complex things (breps 😍 ) which don't always have a direct equivalent in Revit ?

I'm really not sure how things map between geoms and revit geoms. I just know @teocomi said it's not simple, and i'll trust him on that.
I think the whole compatibility map should happen at one point. And mostly I'm interested in what happens for Revit <-> Revit communications -  what other types would need to be added to the core, etc.
Right now there's the convention for ToSpeckle, ToNative extension methods, but by all means, you guys go ahead. Just as long as we don't end up here i'm happy...


added MaxMSP and Orca icons

closes tandpfun/skill-icons#989, closes tandpfun/skill-icons#990

@mgxy0 why did you closed it ?

Sorry, wrong pull request

on what are you doing your icons ?

With a simple macos app from app Store... I thought it was enough to upload the svg file. I apologize for the error, what do you recommend I use?

With a simple macos app from app Store... I thought it was enough to upload the svg file. I apologize for the error, what do you recommend I use?

I recommend you read the contribution guideline (use figma)

@mgxy0 if you like, you can check the old merged PRs, its can also help you.

i made this svg files with figma, but i don't understand how to continue.. I apologize again

@mgxy0 can you send me the figma file, I'm going to give you instructions on it, will be easier

@mgxy0 do you need help?

ok here are the final SVGs files

@mgxy0 please, commit the icons

I will close it since it's being stale for a very long time


Fix KTX2 image loading fails

The resource.url has a timestamp suffix, causing ktx2Regex.test() return false. As a result, ktx2 image loading fails.

Thanks for the pull request @bimangle!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Thanks @bimangle! Would you be able to describe how the replicate the issue for testing?

@ggetz
Test url: http://fs3.bimangle.net/cesium/t20221025-test-ktx2/index-online.html
Test data: http://fs3.bimangle.net/cesium/t20221025-test-ktx2.zip

Thanks @bimangle! Could you please add an item to CHANGES.md describing what was fixed?
@sanjeetsuhag Would you be able to take a look and merge once ready?

@bimangle Aside from updating the CHANGES.md, it would also be helpful to add a test to ensure the URL query removal is working as expected.

@ggetz @sanjeetsuhag  The CHANGES.md has been updated, and a test has been added.  Please take a look, thanks.


[question] Switches not sending status when manually pressed

I have a couple in-wall switches that I moved over to z2m, but when they are manually pressed, no status is sent showing they are on/off. The first switch is a Leviton switch (DS15S-1BZ) with add-ons for 3 and 4 way configurations and what's bizarre is it will send an instant status when the main switch is turned on/off, but any add-on switches don't. The other is a NuTone NWS15Z which doesn't send any status updates when turned on/off manually. I have tried to enable polling on both device types, but the system immediately crashes once discovery is complete. I also have "verify value" enabled, but that doesn't help.  The logs don't show anything specific, but the web page shows a "yellow icon" in the right corner and it loses connection. I have tried values 1-30.

strange you don't see anything in logs, the yellow icons means the socket is disconnected and it means the server crashes

Are the only logs contained in OZW_log.txt ? I can clear them, set the value and try again.

Don't you have a console that is showing logs? OZW_log.txt it's only for ozw related things

I'm running it in Docker, and the only logs I see are the OZW logs. Is there somewhere else I should be looking?

Depends on how you are starting the container so. docker logs or docker-compose logs ?

Thanks. I set the value and it crashed...digging through the docker logs on the container right now....more to follow..

I found this error below:
z2m:Zwave Network scan complete. Found: 17 nodes +2s
2020-06-03 09:51:25.170 Detail, Node018, Notification: NodeAdded
2020-06-03 09:51:25.172 Warning, Node016, Node::GetValue - Couldn't find ValueID in Store: HomeID: 0xe0a10345, ValueID: (Id 0x0000000010494010, NodeID 16, Genre user, CC 0x25, Instance 1, Index 0, Type bool)
2020-06-03 09:51:25.173 Warning, Exception: Manager.cpp:1570 - 101 - Invalid ValueID passed to GetValueLabel
terminate called after throwing an instance of 'OpenZWave::OZWException'
  what():  Manager.cpp:1570 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel

Actually, it looks like after that error above, it came back to life and rescanned everything again only to come up with a similar error:
  z2m:Zwave Node added 2 +2ms
2020-06-03 09:56:24.735 Warning, Node008, Node::GetValue - Couldn't find ValueID in Store: HomeID: 0xe0a10345, ValueID: (Id 0x0000000008494010, NodeID 8, Genre user, CC 0x25, Instance 1, Index 0, Type bool)
2020-06-03 09:56:24.735 Warning, Exception: Manager.cpp:1570 - 101 - Invalid ValueID passed to GetValueLabel
terminate called after throwing an instance of 'OpenZWave::OZWException'
  what():  Manager.cpp:1570 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel

Both node 8 and node 16 are these devices in question that I enabled polling. There are 3 total.

@Fishwaldo

I think it’s pretty self explanatory:

2020-06-03 09:56:24.735 Warning, Exception: Manager.cpp:1570 - 101 - Invalid ValueID passed to GetValueLabel

The ValueID doesn’t exist. Additionally the wrapper isn’t handling exceptions. Not a OZW error.

It never happened since before, need to check if something has change

Quick update: I figured out the issue with the Leviton switches not sending updates when manually pressed. Two out of three had 1.15 firmware and the other had 1.20. The one with updated firmware functioned properly. I was able to get the other 2 flashed using Z-Flash and they now function properly.
As for the Nortek switches that don't send updates, I have polling working at 30 sec, but it took a couple restarts to get the zwave network up without it crashing. However, if I make another change or reboot, it may drop out again.

I think it's a device issue so?

@jasonsinclair5 I have just released a patch for openzwave-shared that is ready to bump in a PR here

Yes, the manual press for the Leviton switch was firmware, but the polling crash was not. I’ll test out the new build when it’s ready and let you know. Thanks for your help with this!

Let me know


VersionInfoListener is not fired when app is not found on the Store

This step covers something that, in my opinion, needs to be processed, since I would like to handle this situation in code before publishing the app.
In that case, I suggest that VersionInfoListener should have another method called onFailure with or without providing some error code, you decide.
Best,
Drasko

compile 'com.robohorse.gpversionchecker:gpversionchecker:1.2.0'

I added  void onErrorHandled(Throwable throwable);
in VersionInfoListener class