certificate verify failed (unable to get issuer certificate)

hi!
I'm trying to use your image on a Raspberry Pi 4.
aarch64 (ARM), 8Gb RAM, 22Gb free disk space.
I'm launching it with the recommended parameters:
docker run --name puppet --hostname puppet.vpn.rv.ua -p 8140:8140 -v ./code:/etc/puppetlabs/code -v ./ca:/etc/puppetlabs/puppetserver/ca ghcr.io/voxpupuli/container-puppetserver
The server starts up. Here are the logs.
System configuration values:
* HOSTNAME: 'puppet.vpn.rv.ua'
* hostname -f: 'puppet.vpn.rv.ua'
* PUPPETSERVER_HOSTNAME: 'puppet'
* PUPPETSERVER_PORT: '8140'
* Certname: 'puppet.pem'
* DNS_ALT_NAMES: ''
* SSLDIR: '/etc/puppetlabs/puppet/ssl'
CA Certificate:
subject=CN = "Puppet CA generated on puppet.vpn.rv.ua at 2024-01-16 14:31:17 +0000"
issuer=CN = Puppet Root CA: 1b57b4220adc31
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Key Usage: critical
                Certificate Sign, CRL Sign
            X509v3 Subject Key Identifier:
                4D:A0:F5:23:FC:B6:4A:4E:7F:EF:39:6C:E0:7D:73:1A:AB:60:9F:E8
            Netscape Comment:
                Puppet Server Internal Certificate
            X509v3 Authority Key Identifier:
                16:6C:70:7B:5D:56:FE:35:13:4F:64:1D:34:1C:C5:74:83:8C:26:B6
Certificate puppet.pem:
subject=CN = puppet
issuer=CN = "Puppet CA generated on puppet.vpn.rv.ua at 2024-01-16 14:31:17 +0000"
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:FALSE
            Netscape Comment:
                Puppet Server Internal Certificate
            X509v3 Authority Key Identifier:
                4D:A0:F5:23:FC:B6:4A:4E:7F:EF:39:6C:E0:7D:73:1A:AB:60:9F:E8
            X509v3 Extended Key Usage: critical
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 Subject Key Identifier:
                EE:43:BC:F1:6F:2C:A9:C5:62:26:42:BC:9D:21:B6:D1:D5:DA:9D:58
            <IP_ADDRESS>.4.1.343<IP_ADDRESS>:
                ..true
            X509v3 Subject Alternative Name:
                DNS:puppet, DNS:puppet

...

2024-01-16 14:33:39,574 INFO  [p.t.s.w.jetty9-core] Starting web server.
2024-01-16 14:33:39,589 INFO  [o.e.j.s.Server] jetty-9.4.53.v20231009; built: 2023-10-09T12:29:09.265Z; git: 27bde00a0b95a1d5bbee0eae7984f891d2d0f8c9; jvm 17.0.9+9-Ubuntu-122.04
2024-01-16 14:33:39,786 INFO  [o.e.j.s.h.ContextHandler] Started o.e.j.s.h.ContextHandler@7cedcbc9{/puppet-ca,null,AVAILABLE}
2024-01-16 14:33:39,790 INFO  [o.e.j.s.h.ContextHandler] Started o.e.j.s.h.ContextHandler@40ffcd92{/puppet-admin-api,null,AVAILABLE}
2024-01-16 14:33:39,855 INFO  [o.e.j.s.session] DefaultSessionIdManager workerName=node0
2024-01-16 14:33:39,856 INFO  [o.e.j.s.session] No SessionScavenger set, using defaults
2024-01-16 14:33:39,864 INFO  [o.e.j.s.session] node0 Scavenging every 600000ms
2024-01-16 14:33:39,994 INFO  [p.t.s.m.jolokia] Using policy access restrictor classpath:/jolokia-access.xml
2024-01-16 14:33:40,164 INFO  [o.e.j.s.h.ContextHandler] Started o.e.j.s.ServletContextHandler@79246c19{/metrics/v2,null,AVAILABLE}
2024-01-16 14:33:40,165 INFO  [o.e.j.s.h.ContextHandler] Started o.e.j.s.h.ContextHandler@284daed8{/puppet,null,AVAILABLE}
2024-01-16 14:33:40,259 INFO  [o.e.j.u.s.SslContextFactory] x509=X509@ef88faa(private key,h=[puppet],a=[],w=[]) for InternalSslContextFactory@470d0fef[provider=null,keyStore=null,trustStore=null]
2024-01-16 14:33:40,528 INFO  [o.e.j.s.AbstractConnector] Started ServerConnector@49c9371c{SSL, (ssl, http/1.1)}{<IP_ADDRESS>:8140}
2024-01-16 14:33:40,529 INFO  [o.e.j.s.Server] Started @91746ms
2024-01-16 14:33:40,548 INFO  [p.t.s.s.status-core] Starting background monitoring of cpu usage metrics
2024-01-16 14:33:40,564 INFO  [p.t.s.s.status-service] Registering status callback function for service 'status-service', version 1.1.2
2024-01-16 14:33:40,566 INFO  [p.t.s.s.status-service] Registering status service HTTP API at /status
2024-01-16 14:33:40,601 INFO  [o.e.j.s.h.ContextHandler] Started o.e.j.s.h.ContextHandler@2454e868{/status,null,AVAILABLE}
2024-01-16 14:33:40,662 INFO  [p.s.a.analytics-service] Puppet Server Update Service has successfully started and will run in the background
2024-01-16 14:33:40,674 INFO  [p.s.m.master-service] Puppet Server has successfully started and is now ready to handle requests
2024-01-16 14:55:03,325 INFO  [p.s.a.dropsonde] Successfully submitted module metrics via Dropsonde.

`
puppet agent config:
[main]
server = puppet.vpn.rv.ua
ca_server = puppet.vpn.rv.ua
environment = production
report = false
runinterval = 300
rundir = /var/run/puppet
factpath=$vardir/lib/facter
ssldir = /var/lib/puppet/ssl

[agent]
server = puppet.vpn.rv.ua

When a client tries to connect, I get an "unable to get issuer certificate" error.
logs on the client:
root@ip-172-31-1-176:~# puppet agent --verbose --onetime --no-daemonize --logdest console
Info: Creating a new SSL key for ip-172-31-1-176.us-east-2.compute.internal
Info: Caching certificate for ca
Info: csr_attributes file loading from /etc/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for ip-172-31-1-176.us-east-2.compute.internal
Info: Certificate Request fingerprint (SHA256): 85:DF:EA:7C:CB:28:80:36:E5:59:9A:9A:82:89:38:B1:44:0B:9C:C7:16:CF:1A:9F:22:2D:CC:50:3A:AE:D3:F0
Info: Caching certificate for ip-172-31-1-176.us-east-2.compute.internal
Error: request https://puppet.vpn.rv.ua:8140//puppet-ca/v1/certificate_revocation_list/ca failed: SSL_connect returned=1 errno=0 peeraddr=<IP_ADDRESS>:8140 state=error: certificate verify failed (unable to get issuer certificate)
Error: Could not request certificate: SSL_connect returned=1 errno=0 peeraddr=<IP_ADDRESS>:8140 state=error: certificate verify failed (unable to get issuer certificate): [unable to get issuer certificate for /CN=Puppet CA generated on puppet.vpn.rv.ua at 2024-01-16 14:31:17 \+0000]
Exiting; failed to retrieve certificate and waitforcert is disabled

logs on the server at the same moment:
<IP_ADDRESS> - - - 16/Jan/2024:15:25:22 +0000 "GET /puppet-ca/v1/certificate/ca?environment=production&fail_on_404=true HTTP/1.1" 200 2791 <IP_ADDRESS> <IP_ADDRESS> 8140 91
<IP_ADDRESS> - - - 16/Jan/2024:15:25:23 +0000 "GET /puppet-ca/v1/certificate/ip-172-31-1-176.us-east-2.compute.internal?environment=production& HTTP/1.1" 404 69 <IP_ADDRESS> <IP_ADDRESS> 8140 12
<IP_ADDRESS> - - - 16/Jan/2024:15:25:23 +0000 "GET /puppet-ca/v1/certificate_request/ip-172-31-1-176.us-east-2.compute.internal?environment=production& HTTP/1.1" 404 77 <IP_ADDRESS> <IP_ADDRESS> 8140 17
2024-01-16 15:25:25,475 INFO  [p.p.certificate-authority] Entity CA signed 1 certificate: ip-172-31-1-176.us-east-2.compute.internal.
<IP_ADDRESS> - - - 16/Jan/2024:15:25:25 +0000 "PUT /puppet-ca/v1/certificate_request/ip-172-31-1-176.us-east-2.compute.internal?environment=production& HTTP/1.1" 200 0 <IP_ADDRESS> <IP_ADDRESS> 8140 1412
<IP_ADDRESS> - - - 16/Jan/2024:15:25:25 +0000 "GET /puppet-ca/v1/certificate/ip-172-31-1-176.us-east-2.compute.internal?environment=production& HTTP/1.1" 200 1668 <IP_ADDRESS> <IP_ADDRESS> 8140 20

The client is a fresh EC2 instance, x86_64, Ubuntu 22 LTS.
only puppet-agent is installed, and the server configuration is specified.
please, help, how to solve it ?
thanks in advance

I normally run it from a compose.yaml. maybe this helps
services:
  puppet:
    image: ghcr.io/container-puppetserver:7.14.0-latest
    hostname: puppet
    environment:
      - PUPPETSERVER_HOSTNAME=puppet
      - PUPPETSERVER_PORT=8140
      - PUPPETDB_HOSTNAME=puppetdb
      - PUPPETDB_SSL_PORT=8081
      - USE_PUPPETDB=true
      - AUTOSIGN=true
      # For private repos, use git@github.com:user/repo.git and provide SSH keys
      # - R10K_REMOTE=https://github.com/betadots/demo-control-repo.git
    volumes:
      - puppetserver:/opt/puppetlabs/server/data/puppetserver
      - puppetserver-ssl:/etc/puppetlabs/puppet/ssl
      - puppetserver-ca:/etc/puppetlabs/puppetserver/ca
    restart: always
    ports:
      - 8140:8140

https://github.com/voxpupuli/crafty/blob/887019ac1ceff40a3659e526a4fb02e527e2ec65/puppet/oss/compose.yaml#L4-L22

Thank you for your response and advice.
I tried to reproduce...
I took a clean Ubuntu22 on ARM architecture at AWS.
Ubuntu 22.04 LTS, arm64 jammy image build on 2023-12-07
t4g.smalll, 2 vCPU, 2 GiB Memory, 20Gb EBS volume.

The security group is clear: allowing any traffic to any.
An external IP was added, domain 'puppet.vpn.rv.ua' was pointed to this external IP.
On this server, I performed the following tasks:

set hostname (puppet.vpn.rv.ua)
install docker (by official script curl -fsSL https://get.docker.com -o get-docker.sh)
install docker-compose
create docker-file.yml
and tried to run a container.

Using EXACTLY your file, I got these errors:"
ERROR: Named volume "puppetserver:/opt/puppetlabs/server/data/puppetserver:rw" is used in service "puppet" but no declaration was found in the volumes section.
and
ERROR: Head "https://ghcr.io/v2/container-puppetserver/manifests/7.14.0-latest": name invalid
i manually get an image:
root@puppet:~# docker pull voxpupuli/container-puppetserver:7.14.0-latest
...
Status: Downloaded newer image for voxpupuli/container-puppetserver:7.14.0-latest
docker.io/voxpupuli/container-puppetserver:7.14.0-latest

adjusted file to this state (just add volumes and use already downloaded image):
services:
  puppet:
    image: voxpupuli/container-puppetserver:7.14.0-latest
    hostname: puppet
    environment:
      - PUPPETSERVER_HOSTNAME=puppet
      - PUPPETSERVER_PORT=8140
      - PUPPETDB_HOSTNAME=puppetdb
      - PUPPETDB_SSL_PORT=8081
      - USE_PUPPETDB=true
      - AUTOSIGN=true
      # For private repos, use git@github.com:user/repo.git and provide SSH keys
      # - R10K_REMOTE=https://github.com/betadots/demo-control-repo.git
    volumes:
      - puppetserver:/opt/puppetlabs/server/data/puppetserver
      - puppetserver-ssl:/etc/puppetlabs/puppet/ssl
      - puppetserver-ca:/etc/puppetlabs/puppetserver/ca
    restart: always
    ports:
      - 8140:8140

volumes:
  puppetserver:
  puppetserver-ssl:
  puppetserver-ca:

run:
root@puppet:~# docker-compose up -d --build
Creating network "root_default" with the default driver
Creating volume "root_puppetserver" with default driver
Creating volume "root_puppetserver-ssl" with default driver
Creating volume "root_puppetserver-ca" with default driver
Creating root_puppet_1 ... done

container is successfully running:
root@puppet:~# docker ps
CONTAINER ID   IMAGE                                            COMMAND                  CREATED              STATUS                        PORTS                                       NAMES
2251fc060859   voxpupuli/container-puppetserver:7.14.0-latest   "dumb-init /docker-e…"   About a minute ago   Up About a minute (healthy)   <IP_ADDRESS>:8140->8140/tcp, :::8140->8140/tcp   root_puppet_1

logs are healthy:
...
2024-01-23 08:31:53,970 INFO  [p.s.a.analytics-service] Puppet Server Update Service has successfully started and will run in the background
2024-01-23 08:31:53,988 INFO  [p.s.m.master-service] Puppet Server has successfully started and is now ready to handle requests
2024-01-23 08:31:55,629 INFO  [p.d.version-check] Newer version 8.4.0 is available! Visit https://puppet.com/docs/puppetserver/latest/release_notes.html for details.
<IP_ADDRESS> - - - 23/Jan/2024:08:32:04 +0000 "GET /status/v1/simple HTTP/1.1" 200 7 <IP_ADDRESS> <IP_ADDRESS> 8140 109

now, going on the client instance
it's almost exactly the same instance, just on x86_64.
install puppet agent:
root@ip-172-31-0-177:~# apt update
root@ip-172-31-0-177:~# apt install puppet
...
Setting up puppet (5.5.22-4ubuntu0.2) ...

create a minimal config for puppet agent:
root@ip-172-31-0-177:~# cat /etc/puppet/puppet.conf
[main]
server = puppet.vpn.rv.ua
certname = test1
runinterval = 30m

and run agent:
root@ip-172-31-0-177:~# puppet agent -t
Info: Creating a new SSL key for test1
Info: Caching certificate for ca
Info: csr_attributes file loading from /etc/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for test1
Info: Certificate Request fingerprint (SHA256): F4:13:68:AD:A2:91:64:12:91:A0:76:CA:10:40:C7:3A:2F:CD:87:89:49:DC:3B:15:72:54:42:5D:85:F5:F0:3F
Info: Caching certificate for test1
Error: request https://puppet.vpn.rv.ua:8140//puppet-ca/v1/certificate_revocation_list/ca failed: SSL_connect returned=1 errno=0 peeraddr=<IP_ADDRESS>:8140 state=error: certificate verify failed (unable to get issuer certificate)
Error: Could not request certificate: SSL_connect returned=1 errno=0 peeraddr=<IP_ADDRESS>:8140 state=error: certificate verify failed (unable to get issuer certificate): [unable to get issuer certificate for /CN=Puppet CA generated on puppet at 2024-01-23 08:31:14 \+0000]
Exiting; failed to retrieve certificate and waitforcert is disabled

server logs shown:
<IP_ADDRESS> - - - 23/Jan/2024:08:39:30 +0000 "GET /puppet-ca/v1/certificate/ca?environment=production&fail_on_404=true HTTP/1.1" 200 2774 <IP_ADDRESS> <IP_ADDRESS> 8140 34
<IP_ADDRESS> - - - 23/Jan/2024:08:39:30 +0000 "GET /puppet-ca/v1/certificate/test1?environment=production& HTTP/1.1" 404 32 <IP_ADDRESS> <IP_ADDRESS> 8140 4
<IP_ADDRESS> - - - 23/Jan/2024:08:39:30 +0000 "GET /puppet-ca/v1/certificate_request/test1?environment=production& HTTP/1.1" 404 40 <IP_ADDRESS> <IP_ADDRESS> 8140 5
2024-01-23 08:39:31,124 INFO  [p.p.certificate-authority] Signed certificate request for test1
<IP_ADDRESS> - - - 23/Jan/2024:08:39:31 +0000 "PUT /puppet-ca/v1/certificate_request/test1?environment=production& HTTP/1.1" 200 0 <IP_ADDRESS> <IP_ADDRESS> 8140 595
<IP_ADDRESS> - - - 23/Jan/2024:08:39:31 +0000 "GET /puppet-ca/v1/certificate/test1?environment=production& HTTP/1.1" 200 1575 <IP_ADDRESS> <IP_ADDRESS> 8140 6

the problem still persist :(
please, help me solve a problem.
I can provide access to both the server and the client.

so you have two vms? on one docker with the puppetserver running? and the second vm is an agent?
when you start the server with docker internal name puppet and vm external name puppet.vpn.rv.ua this will be a cert miss match. try to set DNS_ALT_NAMES.
services:
  puppet:
    image: voxpupuli/container-puppetserver:7.14.0-latest
    hostname: puppet
    environment:
      - PUPPETSERVER_HOSTNAME=puppet
      - DNS_ALT_NAMES=puppet.vpn.rv.ua
      ...

there for you might need to throw your ca away. you can do that by purging the puppetserver-ssl, puppetserver-ca volumes or just use local bind mounts if you arent used to volumes.
you might use full pathes or relativ pathes
    volumes:
      - ./puppetserver:/opt/puppetlabs/server/data/puppetserver
      - ./puppetserver-ssl:/etc/puppetlabs/puppet/ssl
      - /my/path/on/the/host/puppetserver-ca:/etc/puppetlabs/puppetserver/ca

so you have two vms? on one docker with the puppetserver running? and the second vm is an agent?

no. It is a two separate machines (EC2).
on first is running puppet-server as a docker container.
the second one - is a 'destination', which should be provisioned by the puppet server

when you start the server with docker internal name puppet and vm external name puppet.vpn.rv.ua this will be a cert miss match. try to set DNS_ALT_NAMES.
- PUPPETSERVER_HOSTNAME=puppet
- DNS_ALT_NAMES=puppet.vpn.rv.ua

ok, will check soon

bad news, everyone
I used the next docker-compose.yml file on the server (a virgin clean new EC2):
services:
  puppet:
    image: voxpupuli/container-puppetserver:7.14.0-latest
    hostname: puppet
    environment:
      - PUPPETSERVER_HOSTNAME=puppet
      - DNS_ALT_NAMES=puppet.vpn.rv.ua
      - PUPPETSERVER_PORT=8140
      - PUPPETDB_HOSTNAME=puppetdb
      - PUPPETDB_SSL_PORT=8081
      - USE_PUPPETDB=true
      - AUTOSIGN=true
      # For private repos, use git@github.com:user/repo.git and provide SSH keys
      # - R10K_REMOTE=https://github.com/betadots/demo-control-repo.git
    volumes:
      - ./data:/opt/puppetlabs/server/data/puppetserver
      - ./ssl:/etc/puppetlabs/puppet/ssl
      - ./ca:/etc/puppetlabs/puppetserver/ca
    restart: always
    ports:
      - 8140:8140

changes are in:
envs	- add DNS_ALT_NAMES
volumes	- point directs to local folders
maintenance tasks:
set hostname, install docker & docker-composer, create docker-compose.yml, ...
run:
root@ip-172-31-0-184:~# docker-compose up -d --build
Creating network "root_default" with the default driver
Pulling puppet (voxpupuli/container-puppetserver:7.14.0-latest)...
7.14.0-latest: Pulling from voxpupuli/container-puppetserver
ce9ebea987c2: Pull complete
...
a7120fa89f31: Pull complete
Digest: sha256:65a37305a1e5a54703224af59157c275c8b8e2f8c87a47361c17e7f7d00a83f1
Status: Downloaded newer image for voxpupuli/container-puppetserver:7.14.0-latest
Creating root_puppet_1 ... done
server starts as it should:
root@ip-172-31-0-184:~# docker logs root_puppet_1 --follow
...
System configuration values:
* HOSTNAME: 'puppet'
* hostname -f: 'puppet'
* PUPPETSERVER_HOSTNAME: 'puppet'
* PUPPETSERVER_PORT: '8140'
* Certname: 'puppet.pem'
* DNS_ALT_NAMES: 'puppet.vpn.rv.ua'
* SSLDIR: '/etc/puppetlabs/puppet/ssl'
CA Certificate:
subject=CN = "Puppet CA generated on puppet at 2024-01-23 17:26:03 +0000"
issuer=CN = Puppet Root CA: 0e0f3db1b15c83
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Key Usage: critical
                Certificate Sign, CRL Sign
            X509v3 Subject Key Identifier:
                7B:77:5F:3F:23:DD:75:FF:86:9E:F2:6D:D5:9E:30:77:7D:F1:1B:AB
            Netscape Comment:
                Puppet Server Internal Certificate
            X509v3 Authority Key Identifier:
                6C:62:FB:CE:C0:D3:A8:3E:BC:3C:F0:26:80:01:6F:D9:EC:F1:FA:9A
Certificate puppet.pem:
subject=CN = puppet
issuer=CN = "Puppet CA generated on puppet at 2024-01-23 17:26:03 +0000"
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:FALSE
            Netscape Comment:
                Puppet Server Internal Certificate
            X509v3 Authority Key Identifier:
                7B:77:5F:3F:23:DD:75:FF:86:9E:F2:6D:D5:9E:30:77:7D:F1:1B:AB
            X509v3 Extended Key Usage: critical
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 Subject Key Identifier:
                EE:AA:7A:38:DE:CC:68:E1:80:42:4D:5B:D0:EC:B7:26:05:2D:61:C8
            <IP_ADDRESS>.4.1.343<IP_ADDRESS>:
                ..true
            X509v3 Subject Alternative Name:
                DNS:puppet, DNS:puppet.vpn.rv.ua

...

2024-01-23 17:26:33,734 INFO  [p.s.a.analytics-service] Puppet Server Update Service has successfully started and will run in the background
2024-01-23 17:26:33,759 INFO  [p.s.m.master-service] Puppet Server has successfully started and is now ready to handle requests
2024-01-23 17:26:33,866 WARN  [c.p.p.ShellUtils] Executed an external process which logged to STDERR: /opt/puppetlabs/puppet/bin/ruby: No such file or directory -- /opt/puppetlabs/server/data/puppetserver/dropsonde/bin/dropsonde (LoadError)
2024-01-23 17:26:33,883 WARN  [p.s.a.dropsonde] Failed to submit module metrics via Dropsonde. Error: /opt/puppetlabs/puppet/bin/ruby: No such file or directory -- /opt/puppetlabs/server/data/puppetserver/dropsonde/bin/dropsonde (LoadError)
2024-01-23 17:26:34,406 INFO  [p.d.version-check] Newer version 8.4.0 is available!
I can provide access to my EC2 for tests.

hmm maybe my comment was missleading. when you dont have/want a puppetdb you shouldn't configure it.
I tested your setup.
one vm (at gcp) as puppetserver:  puppet.priv.rw.betadots.training
one vm (at gcp) as agent: worker-0.priv.rw.betadots.training
both Ubuntu 22.04.3 LTS. Internal network open for all traffic.
on puppet.priv.rw.betadots.training installed docker. and run this compose.yaml
services:
  puppet:
    image: voxpupuli/container-puppetserver:7.14.0-latest
    hostname: puppet
    environment:
      - PUPPETSERVER_HOSTNAME=puppet
      - DNS_ALT_NAMES=puppet.priv.rw.betadots.training
      - PUPPETSERVER_PORT=8140
      - USE_PUPPETDB=false
      - AUTOSIGN=true
    volumes:
      - ./data:/opt/puppetlabs/server/data/puppetserver
      - ./ssl:/etc/puppetlabs/puppet/ssl
      - ./ca:/etc/puppetlabs/puppetserver/ca
    restart: always
    ports:
      - 8140:8140

root@puppet:~# docker compose up
...
puppet-1  | 2024-01-24 16:48:52,058 INFO  [p.s.m.master-service] Puppet Server has successfully started and is now ready to handle requests

on  worker-0.priv.rw.betadots.training I installed puppet agent. version 7.28.0.
root@worker-0:~# cat /etc/puppetlabs/puppet/puppet.conf
[agent]
server   = puppet.priv.rw.betadots.training
certname = test1

Agent Run
root@worker-0:~# puppet agent -t
Info: Creating a new RSA SSL key for test1
Info: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for test1
Info: Certificate Request fingerprint (SHA256): E2:A3:F0:0C:51:99:2A:AE:6D:6C:DE:A8:B8:F2:A6:04:2B:F1:D5:5B:F3:32:4F:D8:3E:35:16:DB:38:3B:E4:00
Info: Downloaded certificate for test1 from https://puppet.priv.rw.betadots.training:8140/puppet-ca/v1
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Notice: Requesting catalog from puppet.priv.rw.betadots.training:8140 (<IP_ADDRESS>)
Info: Caching catalog for test1
Info: Applying configuration version '1706115646'
Notice: Applied catalog in 0.01 seconds

PuppetServer Log
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:10 +0000 "GET /puppet-ca/v1/certificate/ca HTTP/1.1" 200 2776 <IP_ADDRESS> <IP_ADDRESS> 8140 23
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:10 +0000 "GET /puppet-ca/v1/certificate_revocation_list/ca HTTP/1.1" 200 1464 <IP_ADDRESS> <IP_ADDRESS> 8140 7
puppet-1  | 2024-01-24 17:00:14,628 INFO  [p.p.certificate-authority] Signed certificate request for test1
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:14 +0000 "PUT /puppet-ca/v1/certificate_request/test1 HTTP/1.1" 200 0 <IP_ADDRESS> <IP_ADDRESS> 8140 475
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:29 +0000 "GET /status/v1/simple HTTP/1.1" 200 7 <IP_ADDRESS> <IP_ADDRESS> 8140 10
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:44 +0000 "GET /puppet-ca/v1/certificate/test1 HTTP/1.1" 200 1573 <IP_ADDRESS> <IP_ADDRESS> 8140 6
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:45 +0000 "GET /puppet/v3/file_metadatas/plugins?recurse=false&links=manage&checksum_type=sha256&source_permissions=ignore&environment=production HTTP/1.1" 200 198 <IP_ADDRESS> <IP_ADDRESS> 8140 337
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:45 +0000 "GET /puppet/v3/file_metadatas/pluginfacts?recurse=true&max_files=-1&ignore=.svn&ignore=CVS&ignore=.git&ignore=.hg&links=follow&checksum_type=sha256&source_permissions=use&environment=production HTTP/1.1" 200 197 <IP_ADDRESS> <IP_ADDRESS> 8140 36
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:45 +0000 "GET /puppet/v3/file_metadatas/plugins?recurse=true&max_files=-1&ignore=.svn&ignore=CVS&ignore=.git&ignore=.hg&links=follow&checksum_type=sha256&source_permissions=ignore&environment=production HTTP/1.1" 200 200 <IP_ADDRESS> <IP_ADDRESS> 8140 26
puppet-1  | 2024-01-24 17:00:46,451 INFO  [puppetserver] Puppet Compiled catalog for test1 in environment production in 0.27 seconds
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:46 +0000 "POST /puppet/v3/catalog/test1?environment=production HTTP/1.1" 200 307 <IP_ADDRESS> <IP_ADDRESS> 8140 594
puppet-1  | 2024-01-24 17:00:46,636 INFO  [puppetserver] //test1/Puppet Using environment 'production'
puppet-1  | 2024-01-24 17:00:46,637 INFO  [puppetserver] //test1/Puppet Retrieving pluginfacts
puppet-1  | 2024-01-24 17:00:46,637 INFO  [puppetserver] //test1/Puppet Retrieving plugin
puppet-1  | 2024-01-24 17:00:46,638 INFO  [puppetserver] //test1/Puppet Requesting catalog from puppet.priv.rw.betadots.training:8140 (<IP_ADDRESS>)
puppet-1  | 2024-01-24 17:00:46,638 INFO  [puppetserver] //test1/Puppet Caching catalog for test1
puppet-1  | 2024-01-24 17:00:46,639 INFO  [puppetserver] //test1/Puppet Applying configuration version '1706115646'
puppet-1  | 2024-01-24 17:00:46,639 INFO  [puppetserver] //test1/Puppet Applied catalog in 0.01 seconds
puppet-1  | <IP_ADDRESS> - - - 24/Jan/2024:17:00:46 +0000 "PUT /puppet/v3/report/test1?environment=production HTTP/1.1" 200 7 <IP_ADDRESS> <IP_ADDRESS> 8140 108

This is working for me. 🤔
your EC2 instances use public ips? there isnt any filter in between? local firewall?
your log line looks a bit odd
Error: request https://puppet.vpn.rv.ua:8140//puppet-ca/v1/certificate_revocation_list/ca failed: SSL_connect returned=1 errno=0 peeraddr=<IP_ADDRESS>:8140 state=error: certificate verify failed (unable to get issuer certificate)

why is there a double slash 🤔
puppet.vpn.rv.ua:8140**//**puppet-ca
but this shouldn't cause such problems. 🤔

yes, i know that was Puppet Server version 5
but I don't think the way it works has changed significantly in version 7
today i tried your configs
as expected, it didn't work, the same error occurred :(
meanwhile, i installed Puppet Server 7.15.0
not as a container, but just on the host
for testing
i checked the agent – there's no problem with the certificate
but there's a strange thing: the Puppet Server is not listening to IPv4, only IPv6
But everything works
root@puppet:~# netstat -tulpan | grep LIST
tcp        0      0 <IP_ADDRESS>:53           <IP_ADDRESS>:*               LISTEN      349/systemd-resolve
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      619/sshd: /usr/sbin
tcp6       0      0 :::8140                 :::*                    LISTEN      1846/java

hmmmm very strange.... but netstat is sometimes missleading, it says tcp6 but means tcp4 and tcp6 🤔

I happened to come across the same issue, installed the server from the crafty repo docker compose setup, tried both 8.4 and 8.5, yet the 5.5.x client from a Ubuntu 22 LTS won't connect:
Error: Could not request certificate: SSL_connect returned=1 errno=0 peeraddr=<IP_ADDRESS>:8140 state=error: certificate verify failed (unable to get issuer certificate): [unable to get issuer certificate for /CN=Puppet CA generated on puppet-1.our.domain at 2024-04-11 09:17:52 +0000]

I've figured out:
Only a puppet-agent version 8 can connect to a Puppet server installed in a Docker container. Puppet agents of lower versions cannot connect due to an issue with a double slash in the certificate path.
However, if the Puppet server is installed directly on a host, any version of puppet-agent can connect to it.

still do not know where the //does come from, in my demo setups i couldn't reproduce this :(


Temporary ignore DB2 test in JDBCDriverTest

We have some problems with file space running out on CI, so the jdbc-test module, pulling a lot of database images, can potentially break the build.

Doesn't SimpleDb2Test need to be @Ignored as well? The cause of the failure could happen with either test, I think.

Whoops, missed those.


Numerous interface issues with a particular model

I have the following model:
model PonosJob {
    id          Bytes        @id @db.Binary(26)
    workerId    Bytes?       @db.Binary(26)
    payload     Json         @db.Json
    priority    Int          @default(0) @db.UnsignedTinyInt
    retry       Int          @default(0) @db.UnsignedTinyInt
    state       PonosJobType @default(queued)
    scheduledAt DateTime?
    retryAt     DateTime?
    createdAt   DateTime     @default(now())
    updatedAt   DateTime?    @updatedAt
    deletedAt   DateTime?

    // relations
    queue                PonosJobQueue          @relation(fields: [queueId], references: [id])
    queueId              Bytes                  @db.Binary(26)
    PonosJobErrorMessage PonosJobErrorMessage[]
}

Trying to do an insert:
_, err := m.store.dbClient.PonosJob.CreateOne(
		db.PonosJob.ID.Set([]byte(job.ID)),
		db.PonosJob.QueueID.Set([]byte(job.QueueID)),
		db.PonosJob.Payload.Set(job.Payload),
		db.PonosJob.ScheduledAt.SetOptional(&job.ScheduledAt),
		db.PonosJob.CreatedAt.Set(job.EnqueuedAt),
	).Exec(m.store.ctx)

I'm getting
missing method queueFieldcompilerInvalidIfaceAssign

on all the fields.
Also when I run generate, I get:
go run github.com/prisma/prisma-client-go generate

../../../../pkg/mod/github.com/prisma/prisma-client-go@v0.8.0/generator/types/types.go:6:2: missing go.sum entry for module providing package github.com/iancoleman/strcase (imported by github.com/prisma/prisma-client-go/generator/types); to add:
	go get<EMAIL_ADDRESS>
../../../../pkg/mod/github.com/prisma/prisma-client-go@v0.8.0/generator/types/types.go:7:2: missing go.sum entry for module providing package github.com/takuoki/gocase (imported by github.com/prisma/prisma-client-go/generator/types); to add:
	go get<EMAIL_ADDRESS>
This is a new install and it's been difficult to get to this point.  Thanks

Do you have more information about the error "missing method queueFieldcompilerInvalidIfaceAssign"? Where does it come from, when does it happen? Would be great to add as much info as possible.
The error you get before running generate for the first time is related to Go1.16 and tracked in #452.

Below are the following issues:
I am not understanding why I'm getting them as they are getting correct types.  I have other tables, which have no problems at all and have the same fields in some cases.
db.PonosJob.QueueID:
cannot use db.PonosJob.QueueID.Set([]byte(job.QueueID)) (value of type db.ponosJobSetParam) as db.PonosJobWithPrismaPayloadSetParam value in argument to m.store.dbClient.PonosJob.CreateOne: missing method getQuerycompilerInvalidIfaceAssign

db.PonosJob.Payload:
cannot use db.PonosJob.Payload.Set(job.Payload) (value of type db.ponosJobWithPrismaPayloadSetParam) as db.PonosJobWithPrismaQueueSetParam value in argument to m.store.dbClient.PonosJob.CreateOne: missing method queueFieldcompilerInvalidIfaceAssign

db.PonosJob.ScheduledAt:
cannot use db.PonosJob.ScheduledAt.SetOptional(&job.ScheduledAt) (value of type db.ponosJobSetParam) as db.PonosJobWithPrismaPayloadSetParam value in argument to m.store.dbClient.PonosJob.CreateOne: missing method getQuerycompilerInvalidIfaceAssign

db.PonosJob.CreatedAt:
cannot use db.PonosJob.CreatedAt.Set(job.EnqueuedAt) (value of type db.ponosJobSetParam) as db.PonosJobWithPrismaQueueSetParam value in argument to m.store.dbClient.PonosJob.CreateOne: missing method getQuerycompilerInvalidIfaceAssign

That's super weird.. I tried to reproduce your schema and your query but it compiles for me. Is there any chance you can maybe send the full schema (if you don't want to share it publicly, you can also send it to steeb@prisma.io)?

Thanks for sending the schema. It looks like the order doesn't match the expected one. If you check the arguments of CreateOne, you can see that the expected order is id, payload, queue, scheduledAt, createdAt. You can find this out by looking at the arguments of CreateOne.
I'm still not sure why you get this weird message, but when I
There is one bug currently which is that setting IDs directly (db.PonosJob.QueueID.Set) unfortunately doesn't work in CreateOne, but you can use the .Link syntax instead:
_, err := client.PonosJob.CreateOne(
	PonosJob.ID.Set([]byte(job.ID)),
	PonosJob.Payload.Set(job.Payload),
	PonosJob.Queue.Link(
		PonosJobQueue.ID.Equals([]byte(job.QueueID)),
	),
	PonosJob.ScheduledAt.Set(time.Now()),
	PonosJob.CreatedAt.Set(time.Now()),
).Exec(ctx)

I would have never guessed to look at CreateOne for the order.  I would have taken it as the order of how the model is formed.
I know what to do for next time.
I'm not getting any more issues in the IDE.  So thank you for your time.

I'm glad that it works now. The order should actually be the same as in the schema (id comes first, then payload, then at the bottom queue, and then the optional fields are listed).


[Enhancement] Add a property to a connection object to allow seeding of the QualifiedName and GUID fields.

Is there an existing issue for this?

[X] I have searched the existing issues

Please describe the new behavior that that will improve Egeria
In some environments  it's difficult for connector developers to generate GUID's and Qualified Names for top level entities such databases. The idea is to allow an extra property to a connection object that would allow a user to set the base of any qualified names and GUID's generated.
Alternatives
No response
Any Further Information?
No response
Would you be prepared to be assigned this issue to work on?

[X] I can work on this

The is the purpose of the configurationProperties in the Connection object.  This is a map of property names to values.  It is set up by the administrator when the connector is configured.
The ConnectorType that links off of the connection and is returned by the connecotr's ConnectorProvider class has the recognizedConfigurationProperties property.  This is a list of the names of properties that the developer of the connector expects the administrator to set up in the connection object.
Many of the integration connectors and governance action services in egeria.git use the confiration properties if you are looking for examples.

We do need to add support for this to the existing integration daemon connectors.
should we move this issue , or just  open a new one on the connector repo.


Duplicates in SObjects page

Feedback from @manindersfdc
Describe the bug
I still see duplicate sections when 2 objects have same label

To reproduce you create a custom object with the same label as a standard object .
here "Document__c" wth "Document" as label

I confirm this issue can be replicate in an org that contains no namespace.
Moreover the picklist/page seems to be confused with the Document (standard) and the Document__c (custom) objects.
Duplicates have been corrected, but fix need to be put in place to be able to retrieve description of the standard object.

So i have in a org without namespace two objects called Document (=label) but different API names (of course)

I can select the standard one:

No duplicates
And I can select the custom one as well:

But if I take a closer look i see that the sections in this example are the same (all correspond to the standard one).
So it needs more debugging! but we are approaching!!


Update for 2018 edition

r? @korken89
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks for the PR!
It seems from CI that some crate:: is missing, can you have a look?

Hah, I knew CI would catch something. Cargo fix missed it too. Anyway, updated, let's try again...

Thanks, LGTM!

bors r+


Asynchronous usage?

We want to replace marked with markdown-it in our project, but we're using an asynchronous syntax highlighting function:
https://github.com/npm/marky-markdown/blob/7317bc933c4c999c7f52b9f638a174d10b2a076e/lib/render.js#L5-L26
Is there a way to do this with markdown-it?
// @fengmk2 @puzrin

https://github.com/markdown-it/markdown-it/blob/master/docs/development.md#i-need-async-rule-how-to-do-it
marked does not really support async highlight, it does ugly hack. You should understand, that all such parsers are sync by nature. You can do manually:

parse
async highlight each fenced token
render (and override fenced rendered to not escape)

https://github.com/markdown-it/markdown-it/blob/master/lib/index.js#L399-L403
See what happens when you call markdown-it. Just cann those functions manually, and do async job between.


Mediasoup Sfu: Limit the number getStats can happen at once

Background
It seems that a high number of parallel getStats at the same time causes a spike in CPU usage (moreover it causes in every 25 minutes?!).
Solution
One thing is to make the getStats for the mediasoup sfu optinal (already done), and other course of action is to limit the number of parallel getstats can happen at the same time before the promises are resolved.

8ab7f5c8d04e409d140e8c139331f91df98c2426


ImportError: cannot import name 'DIRECTION_LTR' from 'pygame'

Describe the bug
When using the Quick Start Guide, I am constantly getting the following error:
ImportError: cannot import name 'DIRECTION_LTR' from 'pygame'
I am using an M1 Macbook Pro and my code is exactly as the quick start guide shows, with corrected formatting.
Quick Start Guide Code:

My Code:

To Reproduce
Steps to reproduce the behavior:

Install pygame
Test initial code in QuickStartGuide (this works fine)
Install pygame_gui using the exact commands in the QuickStartGuide
Test the next block of code

Expected behaviour
I expect that when I run the next block of code (or any code with pygame_gui imported), I don't get any bugs. This code, for example, should render the window with a button. However it also crashes:

Screenshots
If applicable, add screenshots to help explain your problem.
Platform and software (please complete the following information):

OS: MacOS Sonoma 14.5
Pygame GUI version 0.6.12
Pygame version 2.6.0

Additional context
Traceback:
pygame 2.6.0 (SDL 2.28.4, Python 3.12.3)
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
  File "/Users/jl/Desktop/GitHub/python-legends-and-legacies/game_window.py", line 2, in <module>
    import pygame_gui
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pygame_gui/__init__.py", line 7, in <module>
    from pygame_gui.ui_manager import UIManager
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pygame_gui/ui_manager.py", line 8, in <module>
    from pygame_gui.core.interfaces import IUIManagerInterface
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pygame_gui/core/__init__.py", line 1, in <module>
    from pygame_gui.core.ui_appearance_theme import UIAppearanceTheme
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pygame_gui/core/ui_appearance_theme.py", line 11, in <module>
    from pygame_gui.core.interfaces.gui_font_interface import IGUIFontInterface
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pygame_gui/core/interfaces/__init__.py", line 2, in <module>
    from pygame_gui.core.interfaces.font_dictionary_interface import IUIFontDictionaryInterface
  File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pygame_gui/core/interfaces/font_dictionary_interface.py", line 2, in <module>
    from pygame import DIRECTION_LTR
ImportError: cannot import name 'DIRECTION_LTR' from 'pygame' (/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pygame/__init__.py)

This is the same issue as discussed here: https://github.com/MyreMylar/pygame_gui/issues/587
I also had this, in my case I unknowingly had both pygame and pygame-ce installed in the environment I was using. The solution was to first uninstall pygame AND uninstall pygame-ce, and THEN install pygame-ce in the environment.
Dependent on what exactly your situation is, this should hopefully fix things for you the same way it did for me!

This is the same issue as discussed here: #587
I also had this, in my case I unknowingly had both pygame and pygame-ce installed in the environment I was using. The solution was to first uninstall pygame AND uninstall pygame-ce, and THEN install pygame-ce in the environment.
Dependent on what exactly your situation is, this should hopefully fix things for you the same way it did for me!

This was the fix that solved my issue. I had regular pygame installed as well. Uninstalled both, reinstalled pygame-ce and it worked.


Fix lj_auditlog double-inclusion and accidental globals

Fixes the segfault described in https://github.com/snabbco/snabb/issues/1301.  Test suite still not completing locally for me though.


ARROW-646: [Python] Conda s3 robustness, set CONDA_PKGS_DIR env variable and add Travis CI caching

+1. Let's keep an eye on how our build times are impacted going forward


Update docs

I am adding torques where they were missing, changing some symbols and cleaning it up a bit.

@rykerfish I updated the documentation and the README, can you please check it out and review?
The docs for this PR are rendered here:
https://libmobility.readthedocs.io/en/docs/

Git wouldn't let me call out the lines correctly in the review, but there seems to be a problem with how this block is rendering on the website as the autoclass block doesn't show up: https://github.com/stochasticHydroTools/libMobility/blob/c8445d89bd030140236c9cacb9f53c6400c2e4f9/docs/source/usage.rst?plain=1#L39-L45

I updated the documentation

Git wouldn't let me call out the lines correctly in the review, but there seems to be a problem with how this block is rendering on the website as the autoclass block doesn't show up at all in the docs
https://github.com/stochasticHydroTools/libMobility/blob/c8445d89bd030140236c9cacb9f53c6400c2e4f9/docs/source/usage.rst?plain=1#L39-L45

Awesome find, I forgot to call make install in the read the docs script.


Leaves can't load xgboost model which trained for java api?

when I load xgboost model return errs,model is trained for xgboost4j。

I use the Python interface to read the Java-trained model and save it. Leaves also can't read it. I see that the reason for the error is that NUM_ROOT is 0.


Delete options not applied after kicking the bot on Discord

None of the actions enabled in channel.deleteOptions were applied after kicking the bot on Discord's side. The portaled Matrix rooms kept their aliases, are still listed in the directory, can still be joined by anybody and are still haunted by ghosts.
Config snippet:
channel:
    deleteOptions:
       disableMessaging: false
       unsetRoomAlias: true
       unlistFromDirectory: true
       setInviteOnly: true
       ghostsLeave: true

The appservice's logs show some errors.

Log snippet

Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.446 [UserSync] info: Got update for [REDACTED] (From Matrix).
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.476 [UserSync] info: Applying new room state for @_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.477 [UserSync] info: Applying new room state for @_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.477 [UserSync] info: Applying new room state for @_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.495 [ChannelSync] info: Channel [REDACTED] was deleted but isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.496 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.499 [ChannelSync] error: Failed to delete channel from room: TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.500 [ChannelSync] info: Channel [REDACTED] was deleted but isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.500 [ChannelSync] info: Channel [REDACTED] was deleted but isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.500 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.501 [ChannelSync] warn: Couldn't find roomids for deleted channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.501 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.503 [ChannelSync] error: Failed to delete channel from room: TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.503 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.505 [ChannelSync] error: Failed to delete channel from room: TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.505 [ChannelSync] info: Channel [REDACTED] was deleted but isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.508 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.509 [ChannelSync] warn: Couldn't find roomids for deleted channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.509 [ChannelSync] info: Channel [REDACTED] was deleted but isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.509 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.510 [ChannelSync] warn: Couldn't find roomids for deleted channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.510 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.511 [ChannelSync] warn: Couldn't find roomids for deleted channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.511 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.512 [ChannelSync] warn: Couldn't find roomids for deleted channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.512 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.513 [ChannelSync] warn: Couldn't find roomids for deleted channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.513 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.514 [ChannelSync] warn: Couldn't find roomids for deleted channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.514 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26 12:58:10.514 [ChannelSync] warn: Couldn't find roomids for deleted channel [REDACTED]

amd how are we supposed to.do that if our bot with permissions is kicked?
Am 26. Juli 2019 14:38:14 MESZ schrieb Notkea<EMAIL_ADDRESS>
None of the actions enabled in channel.deleteOptions were applied
after kicking the bot on Discord's side. The portaled Matrix rooms kept
their aliases, are still listed in the directory, can still be joined
by anybody and are still haunted by ghosts.
Config snippet:
channel:
   deleteOptions:
      disableMessaging: false
      unsetRoomAlias: true
      unlistFromDirectory: true
      setInviteOnly: true
      ghostsLeave: true

The appservice's logs show some errors.

Log snippet

Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.446 [UserSync] info: Got update for [REDACTED] (From Matrix).
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.476 [UserSync] info: Applying new room state for
@_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.477 [UserSync] info: Applying new room state for
@_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.477 [UserSync] info: Applying new room state for
@_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.495 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.496 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.499 [ChannelSync] error: Failed to delete channel from room:
TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.500 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.500 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.500 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.501 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.501 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.503 [ChannelSync] error: Failed to delete channel from room:
TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.503 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.505 [ChannelSync] error: Failed to delete channel from room:
TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.505 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.508 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.509 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.509 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.509 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.510 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.510 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.511 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.511 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.512 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.512 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.513 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.513 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.514 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.514 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.514 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/Half-Shot/matrix-appservice-discord/issues/538

You should !discord unbridge prior to kicking
Am 26. Juli 2019 14:38:14 MESZ schrieb Notkea<EMAIL_ADDRESS>
None of the actions enabled in channel.deleteOptions were applied
after kicking the bot on Discord's side. The portaled Matrix rooms kept
their aliases, are still listed in the directory, can still be joined
by anybody and are still haunted by ghosts.
Config snippet:
channel:
   deleteOptions:
      disableMessaging: false
      unsetRoomAlias: true
      unlistFromDirectory: true
      setInviteOnly: true
      ghostsLeave: true

The appservice's logs show some errors.

Log snippet

Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.446 [UserSync] info: Got update for [REDACTED] (From Matrix).
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.476 [UserSync] info: Applying new room state for
@_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.477 [UserSync] info: Applying new room state for
@_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.477 [UserSync] info: Applying new room state for
@_discord_[REDACTED]:[REDACTED] to ![REDACTED]:[REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.495 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.496 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.499 [ChannelSync] error: Failed to delete channel from room:
TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.500 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.500 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.500 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.501 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.501 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.503 [ChannelSync] error: Failed to delete channel from room:
TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.503 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.505 [ChannelSync] error: Failed to delete channel from room:
TypeError: Cannot read property '0' of undefined
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.505 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.508 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.509 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.509 [ChannelSync] info: Channel [REDACTED] was deleted but
isn't a text channel, so ignoring.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.509 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.510 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.510 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.511 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.511 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.512 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.512 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.513 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.513 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.514 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.514 [ChannelSync] info: Channel [REDACTED] has been deleted.
Jul 26 12:58:10 matrix matrix-appservice-discord[388]: Jul-26
12:58:10.514 [ChannelSync] warn: Couldn't find roomids for deleted
channel [REDACTED]

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/Half-Shot/matrix-appservice-discord/issues/538

amd how are we supposed to.do that if our bot with permissions is kicked?

The bot has been kicked only on the Discord side.
It is still present in the Matrix rooms to delete, with full permissions.

You should !discord unbridge prior to kicking

Indeed, but it failed with the following error: ERROR: insufficiant permissions to use this command! Try !discord help to see all available commands.
I didn't had the admin permissions in this room since it was  a portaled room (joined using the room alias).
Now that I'm thinking about it, I should have tried using the adminme script first.

Sorunome on #discord:half-shot.uk:
oh, you can't unbridge those currently, so just kicking the bot on the discord side should do it

The log indeed seems to indicate that the bridge does attempt to delete the rooms (or channels?).
I'm not sure that the changes are propagated in the right way, as it says that it failed to delete a (discord?) channel from a (Matrix?) room.

Also, this other issue might be related: https://github.com/Half-Shot/matrix-appservice-discord/issues/524


Example won't work

Hi!
Thanks for your work, but I'm afraid your example isn't working. The error just keeps going up and up, even raising the epochs number. There is no going down...

Is there any way to fix this?
Thanks in advance!

Thanks Angelo. I'm afraid I'm not sure why you are seeing those results. I
haven't looked at this code for several years, but it was definitely
working when the package was first created and should work with Python 2.
My only suggestion is to debug as the mechanics of ANFIS have not changed!
On Mon, 14 May 2018, 19:56 Ângelo Paulino<EMAIL_ADDRESS>wrote:

Hi!
Thanks for your work, but I'm afraid your example isn't working. The error
just keeps going up and up, even raising the epochs number. There is no
going down...
[image: figure_1]
https://user-images.githubusercontent.com/6752809/40017274-3fb836c4-578f-11e8-8a4b-5919bc35725c.png
[image: figure_2]
https://user-images.githubusercontent.com/6752809/40017275-3fd98036-578f-11e8-9ab9-91bc78ec2808.png
Is there any way to fix this?
Thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/twmeggs/anfis/issues/3, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxrdIYpTlCvOhTsTSW3tGvcZB1Bys6Eks5tydM_gaJpZM4T-VAn
.

I've tried running in Python 2.7 as well, but with the same results.
Do you have any other example code?
Thanks again for the prompt answer!
Em seg, 14 de mai de 2018 16:30, twmeggs<EMAIL_ADDRESS>escreveu:

Thanks Angelo. I'm afraid I'm not sure why you are seeing those results. I
haven't looked at this code for several years, but it was definitely
working when the package was first created and should work with Python 2.
My only suggestion is to debug as the mechanics of ANFIS have not changed!
On Mon, 14 May 2018, 19:56 Ângelo Paulino<EMAIL_ADDRESS>wrote:

Hi!
Thanks for your work, but I'm afraid your example isn't working. The
error
just keeps going up and up, even raising the epochs number. There is no
going down...
[image: figure_1]
<
https://user-images.githubusercontent.com/6752809/40017274-3fb836c4-578f-11e8-8a4b-5919bc35725c.png
[image: figure_2]
<
https://user-images.githubusercontent.com/6752809/40017275-3fd98036-578f-11e8-9ab9-91bc78ec2808.png
Is there any way to fix this?
Thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/twmeggs/anfis/issues/3, or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ABxrdIYpTlCvOhTsTSW3tGvcZB1Bys6Eks5tydM_gaJpZM4T-VAn
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/twmeggs/anfis/issues/3#issuecomment-388935120, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGcKKW6jLPjFVwgEC2KEMiFtqKLmltrjks5tydtigaJpZM4T-VAn
.

@twmeggs,
I got the same results mentioned by @Raphango. Please, run again the example and show us your results. Thanks!

I have the same issue

@Raphango @erralves @gcunhase
Thanks for your patience.  I've altered the initial state values for some of the parameters of the membership functions in the tests.py and the results converge now.  In general, altering the initial parameters values has a large effect on how the algorithm then performs.


Feature/npm version release fix

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


Support Body.formData

Needed for adobe/helix-logging#450 - URL encoded form data is needed, multipart form data is optional.

Workaround for the mentioned use case:
if (/^application\/x-www-form-urlencoded/.test(request.headers.get('content-type'))) {
  const data = new URLSearchParams(await request.text());

Supporting body.formData() (returning a spec-compliant implementation) would require adding another dependency (increasing install size) or implementing FormData from scratch. Neither seems justified given the trivial workaround. I'd therefore rather not support it at this time.
BTW: node-fetch doesn't support it: https://github.com/node-fetch/node-fetch#interface-body.
whatwg-fetch doesn't seem to support it on node either.

Ok


invalid API key

When i try to use this with the fronted am getting this error invalid API key. How can it be solved?

Hello, thank you for exploring my project!
If you have successfully seeded your llm-structurizer database using the command npx prisma db seed, you will find a valid key in the API_KEY table. You just need to copy the value from the id field into your frontend .env file and you should be good to go.

Thank you, I will check it out.
On Sat, Apr 27, 2024, 6:21 PM Lazar Pavicevic @.***>
wrote:

Hello, thank you for exploring my project!
If you have successfully seeded your llm-structurizer database using the
command npx prisma db seed, you will find a valid key in the API_KEY
table. You just need to copy the value from the id field into your
frontend .env file and you should be good to go.
—
Reply to this email directly, view it on GitHub
https://github.com/Lazzzer/llm-structurizer/issues/41#issuecomment-2080892235,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANHLSLBYI5XACYPAAMGZKPTY7O7ABAVCNFSM6AAAAABGQVMFOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQHA4TEMRTGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Refactor paginator

Description
This refactors the paginator.
Instead of having the user manually page through the pages of search results, this improved paginator is a python iterator.
So users, can just loop through the results with for node in paginator as you would expect from python.
A new change is also that the paginator now directly returns nodes instead of JSON that can be converted to nodes.
Changes
Tests are adjusted to the new design.
Known Issues
Untestested at the moment, since I don't have a valid token at the moment.
(And I don't think we have a test users token for CI/CD either.)
Notes
Tagging @duboyal for visibility.
Checklist

[x] My name is on the list of contributors (CONTRIBUTORS.md) in the pull request source branch.
[x] I have updated the documentation to reflect my changes.
[x] My code changes have been verified by automated tests and pass all relevant test scenarios.

Merge #429 first.


Add syntax highlight and code completion to CLI

Is it possible to add those features? Even at some basic level.
I found this tool that already implemented those features https://github.com/waf/CSharpRepl. It uses https://github.com/waf/PrettyPrompt to do its CLI magic.
It could be an additional flag to load that functionality:
dotnet-script -i --syntax-highlight --code-completion

If there is a possibility of implementing either of those things we could split them into 2 separate issues.

This is out of the scope of this project I am afraid. We use Omnisharp for providing language support like Intellisense.

@amine-aboufirass I switched to https://github.com/waf/CSharpRepl. It's fast and has those features enabled by default.


oauth support for bubs next preview mode

Simple and secure auth for preview mode. Working in WPengine staging.

I was able to successfully deploy this to a project today. Ready to merge if no other feedback.


Added two governmental sites

What kind of change does this PR introduce?

[x] Bug Fix
[x] Documentation change
[x] Added a new website
[x] Other(s)

Why was this change needed?

Other information

Thank you for your contribution @ori-on1 !


Ensure nuspec is modified if package is modified

This actions fails if a package has been modified, but the nuspec hasn't. It doesn't check that the version of the nuspec has been (correctly) modified, but let's start simple and improve it after some testing.
Partially addresses: https://github.com/mandiant/VM-Packages/issues/6

I will remove 7d3b446 before merging. I have added as it may help with the review (as you can see how it fails).

I think the path "packages/$package/$package.nuspec" may not always hold true (e.g., see path for notepadpp.vm's .nuspec file)

isn't that nuspec name wrong? I thought the directory and the nuspec should have the same name. 🤔

@MalwareMechanic should we fix this? 🤔


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.4.178",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=26b3901d20bf9da2c6a00cb1fb48932166f80a45"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "26b3901d20bf9da2c6a00cb1fb48932166f80a45",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "btrfs: fix deadlock between quota disable and qgroup rescan worker\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.178 by commit 26b3901d20bf9da2c6a00cb1fb48932166f80a45. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000170


Update HCODE image to hw022018a.op910

Level: hw022018a.op910
Included Commits:
1b7f3a8 - Prasad Bg Ranganath, 13 days ago : PM: Fix Global Parameter Block and PGPE size checks in p9_hcode_image_build
bf1cbfb - Michael Floyd, 2 weeks ago : CME Code Size Reduction ATTEMPT#3 plus CME Size Reduction Fixes


addition: check_snapshot_name_contract

check_snapshot_name_contract is similar in behaviour to check_model_name_contract
Impacts to existing code
get_snapshots (in dbt_checkpoint/utils.py) now returns a generator of Model, previously it returned a list of strings detailing the filename of snapshots.  In order to evaluate the name for the snapshot additional information is needed. This has resulted in a change to dbt_checkpoint/check_model_has_properties_file.py

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (783ceed) 0.00% compared to head (6a74974) 97.95%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##           main     #184       +/-   ##
=========================================
+ Coverage      0   97.95%   +97.95%
=========================================
  Files         0       51       +51
  Lines         0     2497     +2497
  Branches      0      330      +330
=========================================
+ Hits          0     2446     +2446
- Misses        0       32       +32
- Partials      0       19       +19

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hey @ryancollingwood, could you please resolve conflicts? We've modified snapshot obtention and some logic on the latest PRs.
Later this week we'll release a new version, and your PR could become part of it.

@BAntonellini resolved the conflict, although there are failing tests for dbt_checkpoint/check_model_has_properties_file.py
Potentially related to changes in https://github.com/dbt-checkpoint/dbt-checkpoint/pull/181 ?

@ryancollingwood could you please merge main and try to fix such tests?


Add openssh-client packages into base image to ensure SSH in all downstream images

Spun off fix for PPM build failure in #608


Stochasticity in M3GNet prediction

Hi Shyueping and Kenko
The dgl implentation of M3GNet gives stochastic predictions, while this was not observed with the original M3GNet implementation.
I'm worrying this might associated to some serious bug that needs attention to.
Please have a look:

Hmm interesting. The MEGNet implementation doesn't suffer from this problem. So it must be in the threebody computations. @kenko911 pls fix this asap.

I debugged a little. I can confirm that in the forward method, the node_feat and edge_feat are consistent. But the
node_vec = self.readout(g)
vec = torch.hstack([node_vec, state_feat]) if self.inc...```

are stochastic. So there must be some issue with the readout layer. MEGNet does not use the same readout.

@BowenD-UCB Thanks a lot for reporting the issue and I will figure out the problem and fix it ASAP.

It seems that M3GNet UP is not having this issue.

Because the UP is not intensive and so does not call the readout.

I have confirmed that the stochasticity resulted from the Set2Set in dgl.nn. For instance, I replaced the set2set call in Set2SetReadout by the following code:
            for i in range(3):
                set2set = Set2Set(in_feats, n_iters=self.num_steps, n_layers=self.num_layers)
                print(g.ndata["node_feat"])
                out_tensor = set2set(g, g.ndata["node_feat"])
                print(f"out={out_tensor}")

The out tensor is different all three times, despite there being no change in initialization and the input.

I just pushed a fix. The trick is to init the Set2Set only once. Every time it is init, it introduces stochasticity.

However, it should be noted that multiple loads of the model will still lead to stochasticity. I am not sure how to solve that. I am reopening this issue for now.

@kenko911 I think you need to look into whether there is some random seed somewhere that needs to be fixed for dgl.nn for the Set2Set initialization. It is rather strange it is not deterministic.

I found the actual solution, but not sure what is the best approach. @BowenD-UCB @kenko911 if we set dgl.seed(42) (or whatever int), then the answer is completely deterministic. But I am not sure that we should be hard-coding a random seed into matgl. It seems the LSTM process in Set2Set is inherently stochastic. I am happy to hear recommendations.

Scratch what I wrote previously. The dgl.seed does not do anything. Right now, the stochasticity with single model loading is solved. But the stochasticity with multiple model loadings is not.
from pymatgen.core import Lattice, Structure
import matgl
import torch
torch.manual_seed(0)
import random
random.seed(0)
import dgl
dgl.seed(0)
# This is the structure obtained from the Materials Project.
struct = Structure.from_spacegroup("Pm-3m", Lattice.cubic(4.1437), ["Cs", "Cl"], [[0, 0, 0], [0.5, 0.5, 0.5]])
for i in range(10):
    model = matgl.load_model("M3GNet-MP-2018.6.1-Eform")
    eform = model.predict_structure(struct)
    print(f"The predicted formation energy for CsCl is {float(eform.numpy()):.3f} eV/atom.")

still gives stochastic results.

Note that it seems that if you fix the torch.manual_seed, all stochasticity is gone.
This is the fix that I pushed. I am still not sure why this non-deterministic behavior occurs in m3gnet but not MEGNet. MEGnet seems to work fine without any manual seed set. It may be due to the number of layers in the set2set? M3Gnet uses 3 layers while MEGnet uses just 1.

@BowenD-UCB Just a note that Kenko pushed a final fix this morning. A new version has been released. The main issue was that the final layer was not in the init and so the weights were not saved. The new code fixes this problem. The only model that was affected was the M3GNet formation energy model. I also added an integration test to make sure it does not recur in future.


InjectedInputPointerInfo doesn't work with multi-monitor setup

Describe the bug
We are investigating the usage of Windows.UI.Input.Preview.Injection to automate our UWP testing.
The sample found at Simulate user input through input injection however doesn't work with a multi-monitor setup.
It is clicking in the wrong places. We tried different mult-monitor setups (changing scales on both monitors to 100%, switch primary displays etc..) but it didn't help.
The sample code seems to be OK.
Steps to reproduce the bug

Run the sample at Simulate user input through input injection on a multi-monitor system.

Expected behavior
InputInjection works with multi-monitor setups
Screenshots
No response
NuGet package version
WinUI 2 - Microsoft.UI.Xaml 2.8.1
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Unfortunately we are not currently investigating WinUI2 issues that are not business or security critical (more on the policy here).


Annotation required parameters are ignored

This bug appears on both:

Dart SDK version: 2.16.2 (stable)
Dart 2.18.0 (build 2.18.0-91.0.dev)

Given the following code snippet:
class MyAnnotation {
  final String foo;

  const MyAnnotation({
    required this.foo,
  });
}

@MyAnnotation()
class MyClass {}

void main() {
  MyAnnotation();
}

The analyzer does not complain that the required foo parameter is missing when used as an annotation. However, it does when the class is instantiated (within main). I am able to omit the required values from the annotation when they should be required.

@scheglov

https://dart-review.googlesource.com/c/sdk/+/243925

Dang thanks for the quick action!


docs: update sequence diagram

Description

Updates chat sequence diagram to better represent the chat flow with it's constitute parts.

Issue(s)
Fixes #576
How to test

Go to the folder on the branch on Github: https://github.com/oaknational/oak-ai-lesson-assistant/blob/AI-576-chat-sequence-diagram/docs/diagrams/chat-sequence.md
The new sequence diagram should show and be correct.

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


Add segment manifest and its (de-)serialization

See individual commits for details

Depends on https://github.com/aiven/tiered-storage-for-apache-kafka/pull/140


Feature request: option to define a y axis label formatter

I’m creating a chart with values in the hundreds of thousands range. Currently the Y axis labels look like this:
300000
200000
100000

I’d love to be able to define a formatter so that I could, for example, group the numbers per thousands:
300,000
200,000
100,000

...or using short notation:
300K
200K
100K

Note that this is very similar to the tooltip formatters that are already supported — just that the formatter would be applied on the Y axis labels.
(Here's the chart I'm talking about, in case it helps to understand my use case: https://mathiasbynens.github.io/covid-19-vaccinations-germany/)

I’ve implemented this horrible, horrible workaround:
  // Work around https://github.com/frappe/charts/issues/322.
  const fixLabels = () => {
    const compactFormatter = new Intl.NumberFormat('en', {
      notation: 'compact',
    });
    const labels = document.querySelectorAll('text[x="-10"]');
    for (const label of labels) {
      const number = Number(label.textContent);
      label.textContent = compactFormatter.format(number);
    }
  };

  // TODO: Use a mutation observer instead, if we can find a reliably
  // detectable DOM modification that signals the charts are fully
  // rendered.
  setTimeout(() => {
    fixLabels();
  }, 1000);

There's an axis option to shorten these.
Can be used as follows
const chart = new Chart("#app", {
  data: financialData,
  type: "line",
  axisOptions: {
    shortenYAxisNumbers: true,
  },
});

@mathiasbynens I've created a PR on your project to enable this behaviour, you can check it out.
I have another suggestion I've highlighted in the issue here It has instructions to upgrade to v2 beta if you wish to do that

Hi!  Aside from "shortenYAxisNumbers", will there be a simple "append" option where I could add text like "%" or "pts"?  thanks!


PR #91323 - tenant: add apiv2 support for sql-over-http

Exalate commented:
Related PR: https://github.com/cockroachdb/cockroach/pull/91323
Commit: https://github.com/cockroachdb/cockroach/commit/cb938ed462f96ecb74f55c6cdd8f9ea91eb44edb

Release note (ops change): sql tenants now support the HTTP endpoint under
/api/v2/sql which allows the caller to execute an HTTP request containing SQL
statements to execute. The JSON response contains the results. This endpoints
works identically as on a non-tenant server, except that it naturally scopes to
the target tenant for SQL execution.
Epic: CRDB-17356
Jira Issue: DOC-6179

serverless feature. no docs required.


Custom authorizer is not called

I am using ember-django-adapter with ember-simple-auth and have written the custom authorizer for token authentication. I am able to obtain the token from server but not able to inject it into the api requests using the adapter.
app/authorizers/application.js
import Ember from 'ember';
import Base from 'ember-simple-auth/authorizers/base';

const { service } = Ember.inject;

export default Base.extend({

  session: service('session'),

  init: function () {
    console.log('Intialize authorizer');
  },

  authorize(data, block) {
    const accessToken = data['access_token'];
    if (this.get('session.isAuthenticated') && !Ember.isEmpty(accessToken)) {
      block('Authorization', `Token ${accessToken}`);
      console.log("authorizer called with token: " + accessToken);
    }
  }
});

app/adapters/application.js
import Ember from 'ember';
import DRFAdapter from 'ember-django-adapter/adapter/drf';
import DataAdapterMixin from 'ember-simple-auth/mixins/data-adapter-mixin';

const { service } = Ember.inject;

export default DRFAdapter.extend(DataAdapterMixin, {
  session: service('session'),
  authorizer: 'authorizer:application'

});

app/authenticators/token.js
import Ember from 'ember';
import Base from 'ember-simple-auth/authenticators/base';

export default Base.extend({
  serverTokenEndpoint: 'http://localhost:8000/ember-auth/',

  authenticate: function(email, password) {
    return new Ember.RSVP.Promise((resolve, reject) => {
      Ember.$.ajax({
        url: this.serverTokenEndpoint,
        type: 'POST',
        data: JSON.stringify({
          email: email,
          password: password
        }),
        contentType: 'application/json;charset=utf-8',
        dataType: 'json'
      }).then(function(response) {
        console.log('Got token: ' + response.token);

        Ember.run(function() {
          resolve({
            token: response.token
          });
        });
      }, function(xhr) {
        var response = xhr.responseText;
        Ember.run(function() {
          reject(response);
        });
      });
    });
  },

  invalidate: function() {
    console.log('invalidate...');
    return Ember.RSVP.resolve();
  }
});

Ember tries to transition to protected route but due to non injection of Authorization header the request fails with 403 error.
Any help is appreciated.

The authenticator resolves with
resolve({
  token: response.token
});

but in the authorizer you're using const accessToken = data['access_token']; which is null then of course so that the Authorization header will actually be sent with an empty token.

I'm trying to migrate from ember-simple-auth 0.8.0 to 1.0.0 but I'm having trouble with custom authorizer. Basically I need to set some headers for each request made.
On 0.8.0 version I had a custom Authorizer with following code:
    import Base from 'simple-auth/authorizers/base';

    export default Base.extend({
      authorize: function(jqXHR) {
        if (this.get('session.isAuthenticated')) {
          jqXHR.setRequestHeader('Authorization', 'Bearer token');
          jqXHR.setRequestHeader('X-Custom-Header', 'data');
        }
      }
    });

I'm a bit confused how I would to translate previous code into new ember-simple-auth version 1.0.0.
BTW, I have similar code of @gauravdott and authorizer is not called.

I have figured out what going on with authorizer, quote doc

Unlike in previous versions of Ember Simple Auth, authorization will not happen automatically for all requests the application issues anymore

As I understand (and tested on my code) you need call this this.get('session').authorizer('authorizer:application', (data, header) => { }) in order to perform you custom authorizer.
In my case I need to fix a lot of code in order to set the app headers :-1: I do not know what is the reason of this changes but it would be good know it.

@deivinsontejeda auto authorization introduced some global state and in general was very implicit - that's the reason why it was removed in 1.0. If you're doing a lot of non Ember Data (where you could use the DataAdapterMixin) requests, I'd suggest you use a service to do so which would then be the only part of the application that would have to call the session's authorize method to add auth headers.

Thanks for suggestion. Indeed I have thought add something you said. But I
wonder what about a initializer which set necessary header using
Ember.$.ajaxPrefilter, makes sense this approach?
On Feb 6, 2016 11:30 AM, "Marco Otte-Witte"<EMAIL_ADDRESS>wrote:

@deivinsontejeda https://github.com/deivinsontejeda auto authorization
introduced some global state and in general was very implicit - that's the
reason why it was removed in 1.0. If you're doing a lot of non Ember Data
(where you could use the DataAdapterMixin
http://ember-simple-auth.com/api/classes/DataAdapterMixin.html)
requests, I'd suggest you use a service to do so which would then be the
only part of the application that would have to call the session's
authorize method to add auth headers.
—
Reply to this email directly or view it on GitHub
https://github.com/simplabs/ember-simple-auth/issues/865#issuecomment-180774919
.

I would not recommend using a global hook anymore as that can never be reset. That adds a lot of pain in e.g. testing mode and was the main reason it was removed in 1.0.

Am 06.02.2016 um 15:50 schrieb Deivinson Tejeda<EMAIL_ADDRESS>Thanks for suggestion. Indeed I have thought add something you said. But I
wonder what about a initializer which set necessary header using
Ember.$.ajaxPrefilter, makes sense this approach?
On Feb 6, 2016 11:30 AM, "Marco Otte-Witte"<EMAIL_ADDRESS>wrote:

@deivinsontejeda https://github.com/deivinsontejeda auto authorization
introduced some global state and in general was very implicit - that's the
reason why it was removed in 1.0. If you're doing a lot of non Ember Data
(where you could use the DataAdapterMixin
http://ember-simple-auth.com/api/classes/DataAdapterMixin.html)
requests, I'd suggest you use a service to do so which would then be the
only part of the application that would have to call the session's
authorize method to add auth headers.
—
Reply to this email directly or view it on GitHub
https://github.com/simplabs/ember-simple-auth/issues/865#issuecomment-180774919
.

—
Reply to this email directly or view it on GitHub.

I know this is no the focus of this issue but I would like heart any suggestions about this tiny service which wrap request to set custom HEADER or whatever you want.

If it's a decent approach I promise (async) I will write down a post about this. I pretty sure many devs would like to know how this was fixed.


Feature/errors

The last of the things I've been meaning to PR back into Hyperspace for a while. A few things we've side loaded into Hyperspace to aid with decoding empty responses and surfacing more information about the request in errors.

Warnings

:warning:
No CHANGELOG entry added.

  Generated by :no_entry_sign: Danger Swift against de91f214010c5f99e6283facc51b1c095cfba532

Addresses #112 and #113

@earlgaspard @tylermilner I cleaned up a few things after your last reviews, any additional feedback here?

I don't have any additional feedback.


738 audit log staff

Pull Request Overview

Audit logs only visible to staff
Get of the list returns the full information
Get of Faults only now actually works
CLI utils added to be able to get the same data from the CLI prompt

REST API Updates
[GET] /api/v1/audit_logs/
[
    {
        "audit_type": "Houston Fault",
        "created": "2022-02-10T07:34:44.910004+00:00",
        "duration": null,
        "module_name": null,
        "message": "409 Conflict: A conflict happened while processing the request. The resource might have been modified while the request was being processed.",
        "guid": "4ca572a8-079a-4659-af9c-1655b2564d7f",
        "user_email": "anonymous user",
        "item_guid": null
    },
    {
        "audit_type": "Access",
        "created": "2022-02-10T07:34:47.364658+00:00",
        "duration": null,
        "module_name": "User",
        "message": "Deactivating",
        "guid": "b9b0e3f6-7bb4-4a87-bc6a-e242978b1e3a",
        "user_email"<EMAIL_ADDRESS>        "item_guid": "d3a29c64-7a04-476b-baa5-239396eab968"
    },
    {
        "audit_type": "Delete",
        "created": "2022-02-10T07:34:47.888134+00:00",
        "duration": null,
        "module_name": "Sighting",
        "message": "",
        "guid": "a5c8707e-ea70-46ea-ab39-97991234b506",
        "user_email"<EMAIL_ADDRESS>        "item_guid": "462ce929-6b16-4f93-b2e8-a675971511fe"
    },
    {
        "audit_type": "Delete",
        "created": "2022-02-10T07:34:47.966986+00:00",
        "duration": null,
        "module_name": "Sighting",
        "message": "",
        "guid": "397b2673-fc75-455a-a734-47ba01c7c8fc",
        "user_email"<EMAIL_ADDRESS>        "item_guid": "d7495663-76c7-4082-bc87-d7e76b1753b3"
    },
    {
        "audit_type": "Access",
        "created": "2022-02-10T07:42:58.092592+00:00",
        "duration": 0.02,
        "module_name": null,
        "message": "Setting path:site.custom.regions to {'_value': {'locationID': [{'id': 'f450438a-cb54-4477-9a6a-06f2bdb86f05', 'name': 'Wiltshire'}]}}",
        "guid": "56a4f20a-88a5-43a3-8eab-bea7222d6a3b",
        "user_email"<EMAIL_ADDRESS>        "item_guid": null
    },
    {
        "audit_type": "Access",
        "created": "2022-02-10T07:43:38.003108+00:00",
        "duration": 0.03,
        "module_name": null,
        "message": "Setting path:site.species to {'_value': [{'commonNames': ['Example'], 'scientificName': 'Exempli gratia', 'id': '8139412e-2253-42b9-82ba-b1efe054ce31'}, {'scientificName': 'Equus grevyi', 'commonNames': [\"Grevy's zebra\"], 'itisTsn': 202400}]}",
        "guid": "90c6a2c5-a1cd-46f2-9720-d6f9fe153a2b",
        "user_email"<EMAIL_ADDRESS>        "item_guid": null
    },
]

[GET] /api/v1/audit_logs/faults
[
    {
        "audit_type": "Houston Fault",
        "created": "2022-02-10T07:32:38.731057+00:00",
        "duration": null,
        "module_name": null,
        "message": "[Errno 2] No such file or directory: '/data/var/asset_group/f4e89db6-cac8-4fa0-8001-1d9d20743708/_assets/50979e08-db88-4eda-a362-3142935217a3.jpg'",
        "guid": "802e2dfd-2226-4f64-857a-156aa3e54f8b",
        "user_email"<EMAIL_ADDRESS>        "item_guid": null
    },
    {
        "audit_type": "Back End Fault",
        "created": "2022-02-10T07:33:09.885802+00:00",
        "duration": null,
        "module_name": null,
        "message": "Failed: sighting.data delete failed {'args': {'id': '0ecb370c-04b9-4aaf-b876-f28aa3ae58f4', 'class': 'org.ecocean.Occurrence'}, 'key': 'not_found'} 404 404",
        "guid": "fcfcdde4-3262-444f-a26d-8689c2b50210",
        "user_email"<EMAIL_ADDRESS>        "item_guid": null
    },
    {
        "audit_type": "Houston Fault",
        "created": "2022-02-10T07:33:13.300744+00:00",
        "duration": null,
        "module_name": null,
        "message": "404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.",
        "guid": "86a5a67a-4113-41e1-af15-830d19373db0",
        "user_email"<EMAIL_ADDRESS>        "item_guid": null
    },
    {
        "audit_type": "Houston Fault",
        "created": "2022-02-10T07:33:29.256869+00:00",
        "duration": null,
        "module_name": null,
        "message": "409 Conflict: A conflict happened while processing the request. The resource might have been modified while the request was being processed.",
        "guid": "3fd4b6a7-ccbd-4594-877a-ce8508a394c2",
        "user_email": "81aca770-8b01-46b5-9fdd-f3e75a93f396@localhost",
        "item_guid": null
    },
    {
        "audit_type": "Houston Fault",
        "created": "2022-02-10T07:33:29.625974+00:00",
        "duration": null,
        "module_name": null,
        "message": "409 Conflict: A conflict happened while processing the request. The resource might have been modified while the request was being processed.",
        "guid": "2524a997-83dd-4b53-8e17-6bccd64c9dfe",
        "user_email"<EMAIL_ADDRESS>        "item_guid": null
    },
]

[GET] /api/v1/audit_logs/09dbeb7b-12a2-42b5-af2f-28a4bcd6904b
[
{
"audit_type": "Update",
"created": "2022-02-10T07:33:53.124778+00:00",
"duration": 0.01,
"module_name": "AssetGroupSighting",
"message": "Patch: add annotations, 653ea4c6-1835-4107-ad6a-14622783abd9 ",
"guid": "5c08ac04-47cd-42b8-aa9e-152127f9d115",
"user_email"<EMAIL_ADDRESS>"item_guid": "09dbeb7b-12a2-42b5-af2f-28a4bcd6904b"
}
]
**Invoke CLI Updates **
Here is an example invoke that shows the new functionality
$ invoke app.audit-logs.all
2022-02-10 07:29:39.776806: Access executed by<EMAIL_ADDRESS>in 0.03 seconds message: Setting path: to {'site.name': 'My test site', 'site.private': True, 'site.look.themeColor': '#68F6E5', 'site.general.tagline': 'Welcome to my test site', 'site.general.taglineSubtitle': 'AI for the conservation of zebras.', 'site.general.description': 'Researchers use my test site to identify and organize sightings of zebras.', 'site.needsSetup': False}
2022-02-10 07:29:40.908950: Update executed by<EMAIL_ADDRESS>on User guid: 3a594a41-401d-45ab-9687-8146819ecfa5 in 0.01 seconds message: Patch: replace full_name, Test admin
2022-02-10 07:29:58.777202: Access executed by<EMAIL_ADDRESS>in 0.04 seconds message: Setting path:site.species to {'_value': [{'commonNames': ['Example'], 'scientificName': 'Exempli gratia'}]}
2022-02-10 07:29:58.870731: Access executed by<EMAIL_ADDRESS>in 0.02 seconds message: Setting path: to {'site.custom.customFields.Occurrence': {'definitions': [{'name': 'occ_test_cfd', 'type': 'string', 'multiple': False}]}}
2022-02-10 07:29:58.897672: Access executed by<EMAIL_ADDRESS>in 0.01 seconds message: Setting path: to {'site.custom.customFields.Encounter': {'definitions': [{'name': 'enc_test_cfd', 'type': 'string', 'multiple': False}]}}
2022-02-10 07:29:59.383762: User Create executed by<EMAIL_ADDRESS>on AssetGroup guid: d4c77490-5dd8-4eb4-a05c-53127961ef35 in 0.46 seconds
2022-02-10 07:32:21.835738: System Create executed by<EMAIL_ADDRESS>on Annotation guid: 0a1e2650-1458-4038-a6d6-9e849bdaec75 message: from Sage detection response
2022-02-10 07:32:34.804263: Update executed by<EMAIL_ADDRESS>on AssetGroupSighting guid: 4b9f8f85-4ac2-43a4-aa35-118fa92a1512 message: Patch: add decimalLatitude, 52.152029  add decimalLongitude, 2.318116
2022-02-10 07:32:34.834663: Update executed by<EMAIL_ADDRESS>on AssetGroupSighting guid: 4b9f8f85-4ac2-43a4-aa35-118fa92a1512 message: Patch: replace sex, None
2022-02-10 07:32:35.053195: User Create executed by<EMAIL_ADDRESS>on Encounter guid: d23b3a0d-d6ab-4b91-8521-52eeb3321273 message:  for owner 3a594a41-401d-45ab-9687-8146819ecfa5
2022-02-10 07:32:35.074596: User Create executed by<EMAIL_ADDRESS>on Sighting guid: 62642d22-2bf3-479b-b169-387d77d1e2dd in 0.22 seconds message: with 1 encounter(s)
2022-02-10 07:32:35.254580: Delete executed by<EMAIL_ADDRESS>on Sighting guid: 62642d22-2bf3-479b-b169-387d77d1e2dd

$ invoke app.audit-logs.all-faults
2022-02-11 19:01:47.355889: Houston Fault executed by anonymous user message: <execute_merge_request 654034b0-63b4-473b-886d-8842aa04f852> failed validation
2022-02-11 11:32:17.304166: Houston Fault executed by<EMAIL_ADDRESS>message: get() missing 1 required positional argument: 'args'
2022-02-11 11:15:41.663210: Houston Fault executed by<EMAIL_ADDRESS>message: Query.order_by() being called on a Query which already has LIMIT or OFFSET applied. To modify the row-limited results of a  Query, call from_self() first.  Otherwise, call order_by() before limit() or offset() are applied.
2022-02-11 09:18:27.780849: Houston Fault executed by anonymous user message: <execute_merge_request ab177d9a-0530-494b-9068-eef1d8e05b37> failed validation
2022-02-10 18:10:05.616521: Houston Fault executed by anonymous user message: <execute_merge_request a22e21be-ace8-4bd3-b7ac-0aa148961331> failed validation
2022-02-10 17:55:26.115220: Houston Fault executed by anonymous user message: <execute_merge_request a473f317-8d00-4560-9349-71019faef30a> failed validation
2022-02-10 15:49:36.008974: Houston Fault executed by<EMAIL_ADDRESS>message: 'bool' object is not callable
2022-02-10 15:47:57.893555: Houston Fault executed by<EMAIL_ADDRESS>message: object of type 'BaseQuery' has no len()

invoke app.audit-logs.object-logs 09dbeb7b-12a2-42b5-af2f-28a4bcd6904b
2022-02-10 07:33:53.124778: Update executed by<EMAIL_ADDRESS>on AssetGroupSighting guid: 09dbeb7b-12a2-42b5-af2f-28a4bcd6904b in 0.01 seconds message: Patch: add annotations, 653ea4c6-1835-4107-ad6a-14622783abd9

/rebase


How to reach the object data inside the component? [question]

Hi,
As gitter chat looks not very active, I would ask the question here. If there is some other proper place to ask such questions, please, point me there.
I started to use vue.js and met one issue.
I have the vue instance, which has an array under it's $data. It's possible to put another value to the data, by clicking the button.

Based on this array, using the v-repeat directive, I print another component response.

My question is, assuming that I put an object to the data {uuid:xxx}, how can I reach this object value in the component? In particular in the data function?
This approach doesn't work:

I even am able to see the uuid, when printing this

But can't reach it in any way. I only able to reach it from the template, while want to have the access to it from the code.
Here is the full code:
https://jsfiddle.net/4pqu1t8w/5/
Any advice is appreciated.
Regards,

Questions should be posted to vuejs/Discussion.
The data function is used to create the initial/default state for your component; it is called before merging with the external data. Use other lifecycle hooks such as created or compiled to access fully resolved data.


Add a [sqrt] square root scale option to sinter plot

Starting an axis name with '[sqrt]' will now use a square root scale
Heavily refactor the plot method to clarify how plots are being scaled

Fixes https://github.com/quantumlib/Stim/issues/506

Note to self: add unit tests testing the sqrt data path, and leave this PR for a bit so I have the opportunity to catch plots looking funny in my dev environment since it's impossible to properly unit test this stuff.


Extend docker test with deploy check

As the docs already mention, manage.py check --deploy requires the production settings, otherwise it fails on security related settings. In turn, running the production settings require the production dependencies.
This PR references the production requirements in requirements/local.txt so the dependencies like collectfast are available during development. This gives us the possibility to use the production settings in the local docker image and run check --deploy. For convenience I added the --database to check since they aren't run by default.
Fixes #4462

Do you think it would be worth changing test_bare.sh to run this deploy check as well?

I don't think it is worth it since the production settings do not contain any logic that differ between bare and docker.

Do you think it would be worth changing test_bare.sh to run this deploy check as well?

I don't think it is worth it since the production settings do not contain any logic that differ between bare and docker.

fair enough. Anyway, LGTM! I will feel a tiny bit more confident in merging updates to our prod dependencies now. Thanks for that.