Running Vespa on Multi-node AWS EC2 nodes is not working

What I did so far?
I followed all the instructions in the documentation mentioned at the following link: https://docs.vespa.ai/en/vespa-quick-start-multinode-aws.html
I made sure that everything was exactly the same with all its details.
Error

While typing curl -s --head http://ip-172-1-1-3.us-east-2.compute.internal:8080/ApplicationStatus (changing the hostname to my stateless1 hostname, it returns nothing at all in the terminal.

While typing vespa-get-cluster-state, it returns the following error:

Failed to fetch cluster state of content cluster 'music':
500 Can't connect to ip-10-188-206-62.eu-west-1.compute.internal:19050
(Connection refused)
Content-Type: text/plain
Client-Date: Mon, 14 Mar 2022 15:36:58 GMT
Client-Warning: Internal response

Can't connect to ip-10-188-206-62.eu-west-1.compute.internal:19050 (Connection
refused)

LWP::Protocol::http::Socket: connect: Connection refused at
/usr/share/perl5/LWP/Protocol/http.pm line 51.

Checking the listening processes on the stateless nodes returns the following processes:
Netid State      Recv-Q Send-Q                      Local Address:Port                                     Peer Address:Port
udp   UNCONN     0      0                                       *:68                                                  *:*                   users:(("dhclient",pid=3797,fd=6))
udp   UNCONN     0      0                               <IP_ADDRESS>:323                                                 *:*                   users:(("chronyd",pid=2346,fd=1))
udp   UNCONN     0      0                                     ::1:323                                                :::*                   users:(("chronyd",pid=2346,fd=2))
tcp   LISTEN     0      128                             <IP_ADDRESS>:41735                                               *:*                   users:(("containerd",pid=3859,fd=9))
tcp   LISTEN     0      128                                     *:22                                                  *:*                   users:(("sshd",pid=4114,fd=3))
tcp   LISTEN     0      128                                    :::19090                                              :::*                   users:(("java",pid=11584,fd=24))
tcp   LISTEN     0      128                                    :::22                                                 :::*                   users:(("sshd",pid=4114,fd=4))
tcp   LISTEN     0      128                                    :::19097                                              :::*                   users:(("vespa-config-se",pid=31550,fd=15))
tcp   LISTEN     0      128                                    :::19098                                              :::*                   users:(("vespa-config-se",pid=31550,fd=19))

Any idea why it is not working despite using the same recommended OS (centos 7)?
Let me know what is not clear or if I missed something.

Did you use t2-medium flavor?
Were you able to deploy the configuration ?

vespa-deploy prepare src/main/application && vespa-deploy activate

It could indicate that you have used a too-small flavor for Vespa to start container processes which listens to port 8080, you can easily verify by logging into the node ip-172-1-1-3.us-east-2.compute.internal and run vespa-logfmt (/opt/vespa/bin/vespa-logfmt).

Yes I am using 5 t2.medium instances with 30 GB storage each.
I could deploy the configuration as shown here:
[centos@ip-10-188-206-59 album-recommendation]$ vespa-deploy prepare src/main/application && vespa-deploy activate
Uploading application 'src/main/application' using http://localhost:19071/application/v2/tenant/default/session
Session 22 for tenant 'default' created.
Preparing session 22 using http://localhost:19071/application/v2/tenant/default/session/22/prepared
WARNING: Host named 'ip-10-188-206-62.eu-west-1.compute.internal' may not receive any config since it differs from its canonical hostname '<IP_ADDRESS>' (check DNS and /etc/hosts).
WARNING: Host named 'ip-10-188-206-76.eu-west-1.compute.internal' may not receive any config since it differs from its canonical hostname '<IP_ADDRESS>' (check DNS and /etc/hosts).
WARNING: Host named 'ip-10-188-206-133.eu-west-1.compute.internal' may not receive any config since it differs from its canonical hostname '<IP_ADDRESS>' (check DNS and /etc/hosts).
WARNING: Host named 'ip-10-188-206-225.eu-west-1.compute.internal' may not receive any config since it differs from its canonical hostname '<IP_ADDRESS>' (check DNS and /etc/hosts).
Session 22 for tenant 'default' prepared.
Activating session 22 using http://localhost:19071/application/v2/tenant/default/session/22/active
Session 22 for tenant 'default' activated.
Checksum:   8e99a5a2c1d27a1a5c2e8b62cb90945d
Timestamp:<PHONE_NUMBER>980
Generation: 22

After logging in to the node and running vespa-logfmt, I got the following output:
[2022-03-15 09:09:25.257] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:28.263] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:28.263] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:31.266] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:31.266] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:34.280] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:34.280] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:37.284] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:37.284] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:40.312] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:40.312] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:40.312] WARNING : config-sentinel  sentinel.sentinel.env	Bad network connectivity (try 41)
[2022-03-15 09:09:41.163] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-62.dev.linkfluence.internal'
[2022-03-15 09:09:42.142] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-133.dev.linkfluence.internal'
[2022-03-15 09:09:42.243] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-225.dev.linkfluence.internal'
[2022-03-15 09:09:43.316] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:43.316] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:46.321] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:46.321] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:49.324] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:49.324] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:52.328] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:52.329] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:55.333] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:55.333] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:09:58.337] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:09:58.337] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:01.341] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:01.341] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:04.345] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:04.345] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:07.350] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:07.350] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:10.358] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:10.358] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:10.358] WARNING : config-sentinel  sentinel.sentinel.env	Bad network connectivity (try 51)
[2022-03-15 09:10:13.363] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:13.363] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:16.366] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:16.366] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:19.375] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:19.375] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:22.378] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:22.378] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:25.382] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:25.382] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:28.387] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:28.387] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:31.390] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:31.390] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:34.393] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:34.393] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:37.399] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:37.399] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:40.445] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:40.445] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:40.445] WARNING : config-sentinel  sentinel.sentinel.env	Bad network connectivity (try 61)
[2022-03-15 09:10:41.254] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-62.dev.linkfluence.internal'
[2022-03-15 09:10:42.323] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-133.dev.linkfluence.internal'
[2022-03-15 09:10:42.351] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-225.dev.linkfluence.internal'
[2022-03-15 09:10:43.448] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:43.448] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:46.451] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:46.451] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:49.454] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:49.454] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:52.460] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:52.461] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:55.464] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:55.464] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:10:58.467] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:10:58.467] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:01.471] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:01.471] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:04.477] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:04.477] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:07.480] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:07.481] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:10.485] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:10.485] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:10.485] WARNING : config-sentinel  sentinel.sentinel.env	Bad network connectivity (try 71)
[2022-03-15 09:11:13.488] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:13.488] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:16.491] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:16.491] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:19.495] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:19.495] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:22.498] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:22.498] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:25.501] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:25.501] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:28.505] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:28.505] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:31.508] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:31.508] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:34.511] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:34.511] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:37.514] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:37.514] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:40.541] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:40.541] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:40.541] WARNING : config-sentinel  sentinel.sentinel.env	Bad network connectivity (try 81)
[2022-03-15 09:11:41.383] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-62.dev.linkfluence.internal'
[2022-03-15 09:11:42.415] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-133.dev.linkfluence.internal'
[2022-03-15 09:11:42.483] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-225.dev.linkfluence.internal'
[2022-03-15 09:11:43.546] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:43.546] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:46.551] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:46.552] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:49.555] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:49.555] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:52.566] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:52.566] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:55.574] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:55.574] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:11:58.577] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:11:58.577] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:12:01.581] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:12:01.581] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)
[2022-03-15 09:12:04.587] WARNING : config-sentinel  sentinel.sentinel.connectivity	3 of 5 nodes up but with network connectivity problems (max is 1)
[2022-03-15 09:12:04.587] WARNING : config-sentinel  sentinel.sentinel.connectivity	Only 1 of 5 nodes are up and OK, 20.0% (min is 50%)

Could you please assist me what's going wrong to try fix it and start using Vespa in multinode mode?

[2022-03-15 09:10:40.445] WARNING : config-sentinel  sentinel.sentinel.env	Bad network connectivity (try 61)
[2022-03-15 09:10:41.254] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-62.dev.linkfluence.internal'
[2022-03-15 09:10:42.323] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-133.dev.linkfluence.internal'
[2022-03-15 09:10:42.351] WARNING : config-sentinel  sentinel.vespalib.net.async_resolver	could not resolve host name: 'ip-10-188-206-225.dev.linkfluence.internal'

The hostnames in the ``hosts.xml` need to match up with the hostname of the host and in DNS.

Now I configured  the hostname of the hosts:
I changed the aws_bootstrap.sh to set the hostnames on the nodes:
#!/bin/bash -e
## Copyright 2017 Yahoo Holdings. Licensed under the terms of the Apache 2.0 license. See LICENSE in the project root.

export VESPA_HOME=/opt/vespa
configserver_addr=$1
current_host=$2

if [ $# -eq 0 ]; then
        configserver_addr=localhost
fi

echo "Installing Vespa"
yum -y install yum-utils epel-release
yum-config-manager --add-repo https://copr.fedorainfracloud.org/coprs/g/vespa/vespa/repo/epel-7/group_vespa-vespa-epel-7.repo
yum -y install vespa bind-utils git

fqdn=$(hostname)
echo "Setting hostname to fqdn '$fqdn'"
sudo -i hostnamectl set-hostname "$current_host"

echo "Setting VESPA_CONFIGSERVERS=$configserver_addr"
echo "override VESPA_CONFIGSERVERS $configserver_addr" >> $VESPA_HOME/conf/vespa/default-env.txt

if [ "$configserver_addr" = "$fqdn" ]; then
	echo "Starting vespa configuration server "
	service vespa-configserver start
else
    echo "Starting vespa services"
    service vespa start
fi

and then I ran the following command:
for host in $(cat hosts.txt); do \
  (ssh $host "sudo bash aws_bootstrap.sh $(head -1 hosts.txt) $host" 2>&1 | tee /tmp/aws_bootstrap_$host.log) & done; \
  wait; \
  echo "Bootstrap done"

I logged in to the different hosts and made sure that their hostnames were changed to .compute.internal. But still, I am getting the same error. Do you think I need to change things as well in the DNS?

They need to talk to each other with the names used in the hosts.xml file.

I changed the /etc/hosts adding the .compute.internal record for each one of those instances.
After running vespa-logfmt on machine3, I got the following:
2022-03-15 10:52:37.587] INFO    : configproxy      configproxy.com.yahoo.vespa.config.proxy.RpcConfigSourceClient	Could not connect to config source at tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070
[2022-03-15 10:52:37.592] INFO    : configproxy      configproxy.com.yahoo.vespa.config.proxy.RpcConfigSourceClient	Could not connect to any config source in set [tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070], please make sure config server(s) are running.
[2022-03-15 10:52:38.088] INFO    : configproxy      configproxy.com.yahoo.vespa.config.JRTConnection	Connecting to tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070
[2022-03-15 10:52:44.748] INFO    : configproxy      configproxy.com.yahoo.vespa.config.JRTConnection	Connecting to tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070
[2022-03-15 10:52:53.625] WARNING : configproxy      configproxy.com.yahoo.vespa.config.proxy.DelayedResponseHandler	Timed out (timeout 15000) getting config name=cloud.config.sentinel,configId=hosts/localhost, will retry
[2022-03-15 10:52:57.661] INFO    : configproxy      configproxy.com.yahoo.vespa.config.JRTConnection	Connecting to tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070
[2022-03-15 10:52:57.824] WARNING : config-sentinel  sentinel.config.frt.frtconnection	Connection to tcp/localhost:19090 failed or timed out
[2022-03-15 10:52:57.825] WARNING : config-sentinel  sentinel.config.frt.frtconnection	FRT Connection tcp/localhost:19090 suspended until 2022-03-15 10:53:57.824 UTC
[2022-03-15 10:52:57.825] INFO    : config-sentinel  sentinel.config.frt.frtconfigagent	Error response or no response from config server (key: name=cloud.config.sentinel,configId=hosts/localhost) (errcode=103, validresponse:0), trying again in 6.000000 seconds
[2022-03-15 10:53:22.058] INFO    : configproxy      configproxy.com.yahoo.vespa.config.proxy.RpcConfigSourceClient	Subscribe for 'name=cloud.config.sentinel,configId=hosts/localhost,fd1703c6a260ae5f7300326a8cd2b53f' failed, closing subscriber
[2022-03-15 10:53:22.063] INFO    : configproxy      configproxy.com.yahoo.vespa.config.JRTConnection	Connecting to tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070
[2022-03-15 10:53:27.132] INFO    : configproxy      configproxy.com.yahoo.vespa.config.JRTConnection	Connecting to tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070
[2022-03-15 10:53:29.624] WARNING : configproxy      configproxy.com.yahoo.vespa.config.proxy.DelayedResponseHandler	Timed out (timeout 25000) getting config name=cloud.config.sentinel,configId=hosts/localhost, will retry
[2022-03-15 10:53:33.861] WARNING : config-sentinel  sentinel.config.frt.frtconnection	Connection to tcp/localhost:19090 failed or timed out
[2022-03-15 10:53:33.861] WARNING : config-sentinel  sentinel.config.frt.frtconnection	FRT Connection tcp/localhost:19090 suspended until 2022-03-15 10:55:33.861 UTC
[2022-03-15 10:53:33.861] INFO    : config-sentinel  sentinel.config.frt.frtconfigagent	Error response or no response from config server (key: name=cloud.config.sentinel,configId=hosts/localhost) (errcode=103, validresponse:0), trying again in 7.000000 seconds

Any idea if things are good to go now or am I still missing something?

[2022-03-15 10:52:38.088] INFO    : configproxy      configproxy.com.yahoo.vespa.config.JRTConnection	Connecting to tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070
[2022-03-15 10:52:44.748] INFO    : configproxy      configproxy.com.yahoo.vespa.config.JRTConnection	Connecting to tcp/ip-10-188-206-59.eu-west-1.compute.internal:19070

This node attempts to talk to the configuration service on ip-10-188-206-59.eu-west-1.compute.internal:19070, it needs that to be able subscribe to configuration to start services (as configured services.xml). Either it has not started, or there is another network issue.

Just another question, can we add a node dynamically to the cluster while it is running or I need to do the whole >process from the beginning?

See https://github.com/vespa-engine/sample-apps/tree/master/examples/operations/multinode-HA for a high availability multi-node deployment. That one is using docker but the same applies for centos/baremetal.
To add a new node to the cluster, you need to add it to the hosts.xml (and same type of network/hostname restrictions) applies. re-deploy the application and start services on the node and the node will join the cluster. If it's a node running content services, data will be re-balanced.

To handle one billion data records, how many machines of stateless, content and admin do you think I would need?

Stateless nodes is just for stateless processing, for content nodes, it's highly dependent on the type of application/schema and flavor.

Thank you for the pretty useful information. I will check those links and see what best suits my application.
While I was feeding data through the pyvespa client, it reaches 900K and I try to make a vespa-get-cluster-state and it give me the following:
Cluster image_embedding_content is down. Too few nodes available.
image_embedding_content/distributor/0: up
image_embedding_content/distributor/1: up
image_embedding_content/storage/0: down
image_embedding_content/storage/1: down

After stopping the feeding and waiting for few minutes it changed to the following:
Cluster image_embedding_content:
image_embedding_content/distributor/0: up
image_embedding_content/distributor/1: up
image_embedding_content/storage/0: up
image_embedding_content/storage/1: up

Is there an explanation for this behavior?
I checked the disks of the content nodes they got 34%.
Any other thing that may cause this behavior?

A t2-medium flavor only has 4GB of memory, so how much you can fit into those nodes depends very much on the schema and especially attribute fields. See https://docs.vespa.ai/en/attributes.html. See also generally sizing guide at https://docs.vespa.ai/en/performance/sizing-search.html

I'm resolving this ticket - feel free to open a separate ticket on how to best scale, flavor types and so on.


Update Navie @appland/components to 4.22.0

:tada: This PR is included in version 0.65.0 :tada:
The release is available on:

v0.65.0
GitHub release

Your semantic-release bot :package::rocket:


Cannot export library to a .bib file on MacOS

Debug log ID
G3QYRPAE-euc/6.7.182-7
What happened?
Exported .bib file of the entire library stopped updating. According to last modified date it stopped updating on April 10. Tried to re-export, but I get an error "An error occurred while trying to export the selected file.".
When I delete the file and remove it from export in settings of BBT, it reappears in exported files again after restart.
Tried to disable caching but it does not work.

Please install build 6181 and send a new log

Done
W7MAYF3D-euc/<IP_ADDRESS>67.6181-7

Again with vuild 6186 please

Again with 6195 please

ZGDZ2JGQ-euc/<IP_ADDRESS>67.6195-7

Thanks for the quick resolution by the way! It really helped me!


Implemented Collaborators API using the new pattern

@pengwynn please take a look

Looking good @dhruvsinghal. Gonna tackle the other GET and the mutating methods while you're in here?

Implemented the remaining GET call. @pengwynn Please take a look.

Had one question on this one @dhruvsinghal. Ping me and add the needs-review label if you need me to take another look.

@pengwynn Please take a look.


create_network_from_weights does not support lycoris

I want to load a previous trained lycoris to continue the training, it seems that create_network_from_weights is the function for it? Any way it seems to only support regular lora at the moment, and cannot load lycoris.
Got this output
create LoRA network from weights
create LoRA for Text Encoder: 0 modules.
create LoRA for U-Net: 0 modules.

@kohya-ss what does that support mean?
And in general, if we detect say hada_w1a in state dicts when matching module, and have a function to convert all format to original unet weight shape, could it work?

can you share working snippet for lycoris create_network_from_weights?


Docs improvement

As mentioned in #94, docs where somewhat confusing, wrong and/or outdated.
So i turned the configuration options into a table, fixing a few, adding missing ones, declaring default values and configuration priorities.
Also fixed AWS CLI examples that where using aws s3api instead of aws s3.
Oh, and also uppercased AWS where it was supposed to be...

@jormaechea
Thank! I greatly appreciate your contribution to this PR and #95.
This makes our documents prettier and more readable.


Research crypto data API

As a developer, I need a data source to populate various areas of the application. Research should be documented somewhere (README, Google Sheet, etc.) and shared with everyone.
Research topics

Is it free? What does the free tier offer?
What is the process for acquiring an API key?
What is the request limit?

CoinGecko

Documentation:

Free API Plan
50 calls/minute (varies)
Shared infrastructure
30+ market data endpoints
50+ fiat/crypto conversions
8+ years historical data
12,000+ crypto assets coverage
FAQ Support
KuCoin

Documentation:

Pricing:
Essential Free
This API might be one of our best options .  It definitely looks to have a lot of useful features that are relevant to what we want in this project. Only common complaint is bad server latency.
Nomics

Documentation:

Pricing:

Seemingly versatile, and unlimited requests at the free tier (or so it claims).  What is not to love?
Messari

Documentation:

Pricing:
Basic API is Free and provides crypto prices, market data metrics, on-chain metrics, and qualitative information.
Good option for creating custom solutions.  Seems to be geared towards traders and seems to be well recognized within the Crypto community.


filesize: add support for the ronna and quetta prefixes

changelog: skip

Hi! I have no idea how to add a "PR label".

I'll add the PR label, thanks! (And it's an addition not skip.)
Please could you add some test cases so Y, TiB, and TB are still covered somehow?

Please could you add some test cases so Y, YiB, and YB are still covered somehow?

Done.

Thanks!


Did you ever get to the bottom of this?

I'm currently struggling with the same issue (I think):
http://stackoverflow.com/questions/42602021/specializing-related-polymorphic-functions-without-inlining

https://ghc.haskell.org/trac/ghc/ticket/13376

Thanks for filing the bug. I did not get the chance to follow up on this or check with more recent GHC versions.

$ ghc --version
The Glorious Glasgow Haskell Compilation System, version <IP_ADDRESS>70507
I had to use --allow-newer and fiddle with dependency versions a little, but was able to run with the version above.
Results: for this test case GHC 8.2 seems to do a good job optimizing the version without specialize: 10x faster than GHC 8.0, and about 3x faster than 8.0 with your SPECIALIZE pragma. Oddly I found that uncommenting the SPECIALIZE in Main.hs caused a significant regression in 8.2 (although it was still faster than either version with 8.0)! I'm not sure if that's expected and might file a bug.


Can the Base component be changed to "NuxtIcon" instead of "Icon" with the "name" attribute?

In my own projects I want to name how I build the component "Icon".
I think as a package it would make way more sense for the component name to be "NuxtIcon" with an "icon" class instead of just "Icon" with name.
Also see this:
https://vuejs.org/style-guide/rules-essential.html#use-multi-word-component-names
(not super relevant due to how I would use it probably lol)
I'd like to look at my own codebase and make the icon component custom, like:
<!-- Icon.vue -->
<template>
<div class="aspect-square rounded-full h-20 text-2xl flex items-center justify-center text-white">
    <NuxtIcon :icon="icon" />
</div>
</template>

<script setup>
defineProps({ icon: String })
</script>

I thought I was the only one thinking about this, but It honestly would make more sense and will also follow the vue ecosystem naming conventions (vuetify, quasar and other popular libraries use prefixes).
It is not a huge dealbreaker for me since we can still create our own component, but still is something that could be better in my opinion.

I am up for that and I think it would make sense. What do you think /cc @Atinux @benjamincanac?

prefix option works for me haha

In that case, it's already customizable: https://github.com/nuxt-modules/icon/blob/221d1932eb52568b468e37d06df339a99c7b3fe6/src/module.ts#L26
So I think we would still keep the default as Icon while it's possible for users to change it. Consider this issue solved

Ah cool!

In that case, it's already customizable:
https://github.com/nuxt-modules/icon/blob/221d1932eb52568b468e37d06df339a99c7b3fe6/src/module.ts#L26
So I think we would still keep the default as Icon while it's possible for users to change it. Consider this issue solved

actually, how do you use it to add the option? I couldn't find in the docs 😅

Oh it's
export default defineNuxtConfig({
  modules: [
    'nuxt-icon',
  ],
  icon: {
    componentName: 'NuxtIcon',
  },
})

Oh it's
export default defineNuxtConfig({
  modules: [
    'nuxt-icon',
  ],
  icon: {
    componentName: 'NuxtIcon',
  },
})

Hi, so I just tried this but it still only appears when using <Icon name="..." /> :|


style: add more php-cs-fixer rules

This one's for you, @aidan-casey 😄
This pull request adds more rules to the current CS Fixer config. Most of these rules are motivated by habits I have, working with a stricter CS Fixer config on my projects, and seeing some of the auto-fixes not being applied when working on Tempest.
This includes trailing comas everywhere, spaces after casts, ordered imports (eg. use function after normal uses), explicit variables in strings, and some more.
Notes:

This PR is better reviewed commit-by-commit, the first one being the rule changes, and the last one being the new rules applied to the codebase
If this is going to be merged, it should be done after all current PRs to minimize the risk of conflict
I'm obviously totally open to adding more rules or removing some that we don't think should be added

Very nice, @innocenzi! I like it.
I am wondering about the following additions while we are at it:

@PHP84Migration - primarily deals with handling nullable type declarations. I don't think we a have a lot but seems we've had a few
ordered_attributes - might as well order attributes
ordered_traits - might as well order traits too
attribute_empty_parentheses - removes parenthesis if no arguments are passed to the attribute
yoda_style - I'd love to see this get added. I prefer non-yoda style, but it'd be nice to be standardized
class_keyword - convert FQDNs to ::class

That's probably enough additions. 😜

I love all of this, the stricter the better. Regarding yoda style, I like both styles so I don't have a preference, as long as it's consistent.
I'll add these tomorrow

Thanks for your work on this!

Hey 👋
Pretty cool rules and PR !
Just giving personal opinion on Yoda style :
While we can think of them as something more readable, in fact most of people don't write them in this order, so this may be weird to change habits of 90% people.
Also, coming from WordPress which have yoda style as standard, they were adopted a long time ago and are contested by more and more people in the community, for example Human Made ( which is a big actor in WP ecosystem ) has made their own coding standard and removed yoda styles ( e.g. https://engineering.hmn.md/standards/style/php/#yoda-conditions )
Furthermore I think there is no PHP Framework that use yoda conditions ( e.g. Larevel/Symfony ).
WDYT ?

Let's use non-Yoda style 👍

Nice touch adding the parallel runner, by the way. 🙂

Any idea why CI fails but local is fine?

@innocenzi - I'm guessing the GitHub action is using an older version of PHP so the linter is failing. We'd get more detail if the arguments had -vvv instead of just -v.
My suggestion would be to avoid using the GitHub action for cs-fixer and simply build up PHP + Dependencies like we are for PHPStan and run CS-Fixer from the vendor directory. We don't want to run composer csfixer because it should be a dry run only.

Well, I didn't expect this to be harder to debug than the console PR. I got confused with the multiple workflow files, too.
@aidan-casey if this look good to you, we can merge!

Sorry, I really should document those. 😛
Looks good to me. Let's get this merged!


fix ampm parsing (12am and 13am)

Summary of changes
Timex.parse("12 am", "{h12} {am}")  now returns T00:00 instead of noon.
Timex.parse("17 am", "{h24} {am}") now returns T17:00 instead of T05:00.
Checklist

[X ] New functions have typespecs, changed functions were updated
[X ] Same for documentation, including moduledocs
[X ] Tests were added or updated to cover changes
[X ] Commits were squashed into a single coherent commit

Coverage decreased (-0.09%) to 70.39% when pulling bb9dcb5bfa04c9fbac584381b2361d0e784d831b on casellepete:fix_ampm_parsing_oddities into c5cb58dd02dd4fa490af427b688ad59322aad35c on bitwalker:master.

Coverage decreased (-0.09%) to 70.39% when pulling 6afa155128b065e7d1cece7383fd82e1e4583748 on casellepete:fix_ampm_parsing_oddities into c5cb58dd02dd4fa490af427b688ad59322aad35c on bitwalker:master.

I am new to coveralls, so I may be mistaken, but is coveralls reporting that coverage decreased on the file lib/time/time.ex?  Is it reporting that line 84 (def to_seconds) went from being tested one time (1x) in the previous commit, to not being tested at all in this commit?  Don't lines 84-90 of test/time_test.ex test that function multiple times?

I wouldn't worry about it, coveralls is not always 100% accurate with coverage I've found. A lot of the time the difference comes from the total number of lines changing, and the uncovered portion representing a larger amount of what remains. Anyway, the code looks good to me, so I'm merging regardless.


Snapshot Distribution Does not include jar files

The sanpshot distribution in https://oss.sonatype.org/content/repositories/snapshots/org/bdgenomics/adam/adam-distribution-spark2_2.11/0.23.0-SNAPSHOT/ is not complete. The jar files are not in the distribution.
Eg. adam-distribution_2.11-0.23.0-20170711.025002-241-bin.tar.bz2 expands to:
[adam-distribution-spark2_2.11-0.23.0-SNAPSHOT]$ ls -la
total 196
drwxrwxr-x 5 hadoop hadoop   4096 Jul 13 16:30 .
drwxr-xr-x 6 hadoop hadoop   4096 Jul 13 16:41 ..
drwxr-xr-x 2 hadoop hadoop   4096 Jul 11 02:35 bin
-rw-r--r-- 1 hadoop hadoop 123491 Jun 24 11:20 CHANGES.md
-rw-r--r-- 1 hadoop hadoop   5151 Jun 24 11:20 CONTRIBUTING.md
drwxr-xr-x 3 hadoop hadoop   4096 Jul 11 02:52 javadocs
-rw-r--r-- 1 hadoop hadoop  16714 Jun 24 11:20 LICENSE.txt
-rw-r--r-- 1 hadoop hadoop  24094 Jun 24 11:20 README.md
drwxr-xr-x 5 hadoop hadoop   4096 Jul 11 02:46 scaladocs

Thanks for flagging this @pbashyal-nmdp! I see exactly what's going on here; we changed the assembly JAR name and forgot to change it in the distribution package.


Today Work @ Toolbox - Turn into coders

Some edited files with new functions

Hi @alby177, thanks for your contribution!
LGTM, merging


OpenWLANMap can never find GPS fix

It's starts, no exceptions in logs, initiates GPS connection but even when it's established still "Waiting for GPS fix...". Same with OpenWLANMapMini
Logs

UnifiedNlp is not providing GPS data. Applications can request the system to only use GPS location and not Network-based location. Those applications will never receive a location update from UnifiedNlp. And that's what causing the problem with OpenWLANMap here, as it requires GPS fix, not Network-based location.


[New Primitive] LiveCursor

I'm not sure what the primitive would be called but LiveCursor paints a more accurate picture in my mind of the idea that originated here https://github.com/radix-ui/primitives/discussions/1090.
Obviously this pattern is likely difficult to make readable by SRs and may even be an a11y failure so perhaps it can follow a similar approach to HoverCard in that it would be for sighted users only.
Examples in the wild:

Figma multiplayer mode
Liveblocks live cursor
Vercel conference marketing website multiplayer (can't find a link for this now but here is a video showing the gist)

Chris from Liveblocks recently posted a great article on animating live cursors and dealing with latency.
https://liveblocks.io/blog/how-to-animate-multiplayer-cursors
Could come in handy!

https://github.com/radix-ui/primitives/discussions/1090#discussioncomment-6620771


Add date-range filtering for TimeEntry.

lgtm

Coverage increased (+0.02%) to 93.269% when pulling fa91026c07aec823dc703eaf59efe11c04b9cc13 on date-range into 37e577fe786a060f9e58285ac6809e49b343cbd1 on master.


WIP: add Table Component

Basic Table Component
Missing features

Try CSS Grid System
better border styling system
one component = one element - component can use all react DOM API through props.
more complex Examples in a storybook.

===================================================

[x] Tests have been added/adjusted for my new feature
[ ] New Components are registered in index.js of my project
===================================================

What's the state of this pull request? Isn't it abandoned?


Make "detect key" change song octave instead of shift notes

The code for this is in change.ts, specifically in the ChangeDetectKey class. I assume the shifting is done by the appended ChangeTranspose?

Apparently this would require the octave setting to be changed into a slider


[3.x] Discrete Level of Detail

Add scene side discrete level of detail.
New LOD node for UI. LODManager added within World for automatically updating child visibilities based on distance from cameras.
Supersedes #53778
Fixes https://github.com/godotengine/godot/issues/40784
Demo Projects
Examine in the editor while moving viewer. Run, and use cursors to move camera.
testlod2.zip
Run, and use cursors to move. Contains multiple LOD nodes.
testlod3.zip
https://github.com/godotengine/godot/assets/21999379/e2039203-049b-4cf2-8c0b-5057005fab1e
Explanation
After exploring some fixes to #53778 I decided to try a scene side LOD system (like @Calinou 's addon).
LOD Node showing 3 example MeshInstances to be used as LODs

LOD Node properties

Spatial properties
The old unused LOD properties are removed from GeometryInstance. The lod_range determines how much of the distance range is used by this LOD. So first child with 2 range will cover distance 0-2, second child with 5 range will cover distance 2-7, etc.
Children of these Spatials will also automatically be shown / hidden as a consequence of the scene tree, as the LODs are automatically selected.

Advantages & Disadvantages
There are advantages and disadvantages to using either scene side or server side approach:
Server side
Advantages

Can change LOD per camera

Disadvantages

Changing LOD per camera doesn't play nice with shadows, especially OMNI and SPOTs, so you either have to deal with self shadowing artefacts or do user side workarounds.
Only deals with displaying the final mesh, cannot throttle down animations, sound, script
Hidden LODs still do significant processing (BVH, culling, pairing etc)
All LOD calcs are done every frame.
Calculations based on AABB centre may miscalculate overlap between different LODs, resulting in either flickering gaps or overlap (and consequently more processing used, when the objective is to increase performance!).
Has to use new visibility_parent system in VisualServer to work around inability to use the hierarchy.

Scene side
Advantages

Can calculate a "best compromise" LOD based on the closest camera
Shadows can use the LOD chosen and thus no self shadowing artefacts, and shadows also scale
Can also throttle down animations, sound, scripts etc.
Can totally turn off display at distance from the camera.
Is very processing friendly, hidden LODs are removed from BVH and do no processing server side.
Processing is done in round robin fashion with queues, so LOD processing is limited per frame.
Can use the hierarchy to determine visibility - any child that is an ancestor of the LOD children will in turn be shown or hidden as per the normal scene tree behaviour, no special changes are required. Additionally, visibility change notifications can be used as normal to drive behaviour.

Disadvantages

LOD chosen does not vary per camera

Notes

There seems to be significant demand for this in 3.x based on recent twitter threads (https://twitter.com/TheConceptBoy/status/1727003872202539151 )
This is fairly simple but should be very flexible, would welcome further input.
Removes the existing stubs in VisualServer and GeometryInstance as these make no sense with this PR.
I may have a go at progressive LOD for 3.7 but this should do for a lot of basic use cases, and covered HLOD where multiple models are replaced by a single model at distance.
The generating of the threshold distances is pretty inefficient here, but is enough to get started and can be made a lot more efficient with #82248 which adds children_changed signal (so the calculation can be pushed on demand instead of pulled every time).
After writing support for Ortho cameras, I decided for now to simply disable calculations for ortho cameras until we have a use case. The use case does not seem convincing, and these are likely to cause edge case bugs as the distance is from the plane and not the camera.
Cameras can turn on and off affects_lod property. Notably this is used for editor preview windows to prevent hidden windows affecting LOD.
I removed the lod_enabled property in GeometryInstance as I realised it wasn't necessary. If users want to have nodes unaffected by LOD, they can either parent the LOD node to a Spatial and hang the nodes from this, or use Spatial nodes as direct children of LOD (as these are not GeometryInstances they and their children will be unaffected by the LOD node).
There are 5 priority settings available in the LOD node properties to choose the update rate.
The first LOD is always chosen during saving from the editor, to prevent unnecessary diffs in files.
Updating LODs can be turned on and off in the editor via the view menu in the 3d view.

Discussion
This only took me today to do as an exploratory look. Discrete LOD can be done using an addon, but there seems some interest in a core solution so I put this up as an option.
Note that this also won't deal sensibly with MultiMeshes (as these are dealt with as a block rather than performing LOD on each instance within the MultiMesh). If there is demand we could maybe add functionality to manage multimeshes, perhaps for vegetation, where otherwise drawcalls would be a bottleneck. These would probably have to be dealt with quite differently internally, although the user interface could probably be similar / shared.

Even though they don't do anything I'd say removing these properties is breaking compatibility, they still set values so nominally someone could be using them for their own implementation, right?

To my dismay, yes. And they're not duds, either. They do set something in the VisualServer (even if it doesn't actually do anything).

Even though they don't do anything I'd say removing these properties is breaking compatibility, they still set values so nominally someone could be using them for their own implementation, right?

See #57196 . We planned to remove these properties, but it was only delayed due to #53778 , which is superseded by this PR.

It's been so long that the likelihood of these properties being used by someone out there is... still low, but not impossible. The documentation was never even changed to state that they have been removed in the future.

It is possible it was used by e.g. an addon, but it's fairly simple to update an addon, and we shouldn't let it hold up core development imo. Banditing existing non-working properties for an addon must be considered "subject to change" and caveat emptor.
Leaving these non-working properties / functions in place just in case is likely to create confusion if there is now working LOD functionality, which doesn't use them.

Just because it breaks compatibility doesn't mean this shouldn't be merged in my opinion, at least.

I'll look into designing an icon for the LOD node.

That would be fantastic. :+1:

When setting up a new LOD system, the visibility for LOD's child nodes in the scene tree dock is only updated when you save the scene. Before I saved the scene, all nodes were visible even though their distance was already configured

I'll have a look at this, it's not stop ship, but could be a quality of life improvement.

Child nodes' visibility changes while in the editor and when saving, which can be distracting if your node is expanded:
Maybe we should hide the visibility icon for children of a LOD node that inherit from Spatial, as there's no point in manually toggling visibility for those in the editor (changes will instantly be reverted).

I'll have a look whether this is possible, no idea where the visibility icon is handled. Can also see pros and cons to this. An alternative (which I could easily put in) is a setting in the editor to turn on and off LOD in the editor, to prevent it becoming distracting.

LOD update speed seems a bit slow when you have lots of instances. This might be an issue if your camera moves fast, as low-detail LODs will remain visible for a while after the camera gets close to objects. Is there a way to speed up the update rate (at the cost of increased CPU utilization)?

Yes, this is exactly what the lod_queue was for, which exists internally but is hidden from the UI .. maybe I should reinstate it. :thinking: I'll do this.
I was worried it would be overkill for users, but it does allow you to set exactly this update rate (by choice of 5 priority queues), and if you have noticed this so quickly, then users will no doubt find it useful.

When setting up a new LOD system, the visibility for LOD's child nodes in the scene tree dock is only updated when you save the scene. Before I saved the scene, all nodes were visible even though their distance was already configured:

Ok I've fixed it up so now in the editor, if view_level_of_detail is switched on, if you change visibility manually of a node it will automatically override it (it detects the situation where the number of visible children is not 1, and does a full recalculate of LOD for that node).
This is good in some ways, but it's rather frustrating when you do try and change the visibility of the children and nothing happens, so I'm not entirely sure about it. Perhaps we can improve the user experience here somehow. Maybe an error warning in the output.. :man_shrugging:
I've also added code to completely remove LOD node from the queues when it is hidden to save on processing. That was an oversight on my part.

An attempt at an icon (it aims to represent a low-detail object, i.e. a circle turned into some kind of hexagon): icon_l_o_d.zip
I've made the sides thicker so it looks more different from the Spatial icon.

Here's an attempt at an icon

Fantastic! Thanks. I'll add it to the PR.
I also managed to get the visibility icons to grey out in the scene tree dock. It actually looks pretty good now and is far simpler than I thought it would be, just a few lines of code.

LOD nodes with no valid children or only 1 valid child could emit a node configuration warning, so you know that at least 2 valid child nodes are needed for LOD to have an effect. (A valid child node is one that extends from Spatial.)
When initially loading a scene, LOD is progressively applied with the selected priority, which can make it obvious in certain cases:

Yes, as you say, easy to do in follow up. :+1:

Thanks!

Woot woot, issue closed after 4 years!


Handling for Rate Limiter errors - Too many requests

SystemLink Enterprise's services implement rate limiters to limit the client's requests per second. Whenever a client crosses the rate limiter, the client experiences Too many requests error. Currently, the clients do not have any support for a back-off-retry mechanism to simplify the usage.

FileClient incorporates a basic rate limiter handler described in #65

DataFrameClient incorporates a basic rate limiter handler described in #80


TaxRate on the Product model should be a choice field

I want to merge this change because...
TaxRate on the Product model should be a choice field #2829
Screenshots

Pull Request Checklist

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] GraphQL schema and type definitions are up to date.

Hey @axce1, your PR contains changes that were already merged to master. Could you pull the latest master and rebase your branch against it? You can only pick changes that you've made using git rebase --interactive master. Also, there is a conflict in one file.

Looks good to me, @axce1 could you please rebase against the latest master?

@Pacu2 I tried, but did not succeed
may i create new PR?

@axce1 I don't think that creating a new PR is necessary.
Assuming that your local branch is in the same state as this one, just do
git pull origin master --rebase
Assuming that you have https://github.com/mirumee/saleor.git added as a origin

thx, I think I did it
why so many commits? may be something wrong?

Right, there should be only commits containing changes you've introduced.
Not sure what you did wrong, but you might want to:

note down hashes of commits you've introduced
reset hard to mirumee/master
cherry-pick the commits you've noted at first

Here's a nice git tutorial you might want to check:
https://try.github.io/

@axce1 please let me know if you're able to finish this PR, or shall we

@Pacu2 sorry, i try to finish next week

Closing for now. Please reopen if you'll have time to finish this PR!


Add extended ascii character test for isogram.

Tests a word which includes both upper and lower case of an extended ascii character. See issues #359 and #323.

Many thanks for this contribution


[Backport 2.x] [Search Pipelines] Split search pipeline processor factories by type

Backport https://github.com/opensearch-project/OpenSearch/commit/eb51f2b73a68b6f6886e2aefff0dccb32f1a323b from https://github.com/opensearch-project/OpenSearch/pull/7597.
Added a commit to update the version check (and remove the TODO talking about updating the version check).

Once this PR (#7669) is merged, we should more or less immediately merge https://github.com/opensearch-project/OpenSearch/pull/7672.

Test Result (1 failure / ±0)
org.opensearch.search.SearchWeightedRoutingIT.testStrictWeightedRoutingWithCustomString

The specific failure is:
 java.lang.AssertionError
	at __randomizedtesting.SeedInfo.seed([C69981F124D97109:931EACA63F04B615]:0)
	at org.junit.Assert.fail(Assert.java:87)
	at org.junit.Assert.assertTrue(Assert.java:42)
	at org.junit.Assert.assertTrue(Assert.java:53)
	at org.opensearch.search.SearchWeightedRoutingIT.assertSearchInAZ(SearchWeightedRoutingIT.java:844)
	at org.opensearch.search.SearchWeightedRoutingIT.testStrictWeightedRoutingWithCustomString(SearchWeightedRoutingIT.java:1124)

It's not the same test as https://github.com/opensearch-project/OpenSearch/issues/5957, but I suspect it's related.


Translate JavaScript algorithms and comments to English.

Please help translate the algorithms and comments in JavaScript from Portuguese to English, as this would help increase the visibility of the repository, and it's the standard used by the company/people.
--
Por favor ajudem a traduzir os algoritmos e comentários em JavaScript do português para o inglês, pois isso ajudaria a aumentar a visibilidade do repositório, e é o padrão utilizado por empresa/pessoas.

Hello, I would like to work on your translation of the different algorithms from Portuguese to English if you are interested @ricardocarva @kelvins

Hello, @Konebachirou .
Contributions are welcome. Please see this  on how to contribute.
This article might also be helpful.

Hello @ricardocarva .
I would like to contribute by resolving issues that have not been resolved if this is possible of course.

Hey can I be assigned this issue?

Hello, yes you can
Le dim. 1 oct. 2023, 12:42, Tejjus Bhat @.***> a écrit :

Hey can I be assigned this issue?
—
Reply to this email directly, view it on GitHub
https://github.com/kelvins/Algoritmos-e-Estruturas-de-Dados/issues/186#issuecomment-1742038804,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARJKDH4NMG2C2PCWNLNGMLLX5FCHVANCNFSM6AAAAAA45STV24
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

Done


Add syntax for AssemblyAttribute Item in SDK-style project files

This documentation only shows how to add assembly attributes in code. Please add examples of using the AssemblyAttribute Item from an SDK-style project file.

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

ID: 05564545-8159-1cbf-57fc-64e1e7d30de3
Version Independent ID: 08bf245d-52b5-1c1d-5d5c-d69c9f1c7130
Content: Set assembly attributes
Content Source: docs/standard/assembly/set-attributes.md
Product: dotnet-fundamentals
GitHub Login: @IEvangelist
Microsoft Alias: dapine

Hi 👋 @sonicbhoc
Thank you so much for posting this issue. We really appreciate it. That is a good call to action, is this something you'd be interesting in adding to this doc yourself if you have time? If not, I'll try to get to it this month. Thanks

I thought I would get around to it last weekend, but my weekend did not quite go as planned. I will try to find the time, but don't wait for me if you're ready to do it.

We could possibly just link here (https://docs.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props#assembly-info-generation-properties) and update that section, if necessary.


Notebook VM in particular VNET

I am unable to select particular virtual network when creating Notebook VM in Azure Machine Learning service - is it possible?

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

ID: e8e02dfa-9387-30bc-1099-a4a302f023c3
Version Independent ID: 4387542f-0e10-d6dd-ad37-c5c00bdedc0d
Content: Run experiments and inference in a virtual network - Azure Machine Learning service
Content Source: articles/machine-learning/service/how-to-enable-virtual-network.md
Service: machine-learning
Sub-service: core
GitHub Login: @aashishb
Microsoft Alias: aashishb

@michalmar
Thanks for the feedback! We are currently investigating and will update you shortly.

Not possible today. This is a high priority feature on our backlog.

@michalmar We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Mistake in viz.compute_cdf()?

Hi!
I think there is a small error in the way the cdf is computed. I think it should be like this.
def compute_cdf(pdf):
"""Compute the cumulative distribution function (cdf) given a pdf."""
values = np.array([np.trapz(pdf.iloc[:x**+1**], pdf.index[:x**+1**]) for x in range(pdf.size)])
cdf = pd.Series(values, index=pdf.index.values)
return cdf
Before the first two values were 0, because when x=0 there are no points in pdf.iloc[:0] and the integral over one point pdf.iloc[:1] is 0 and the last points wasn't evaluated. This should be changed in future versions of pyam.

Makes sense. We should tell David.


Timeout cannot be set as variable

Server - VSTS
Agent - Hosted or Private

If the 'Timeout' value under 'Control Options' is set as a variable, $(variable_name), after saving the changes, the field displays the original integer value.

Service side issue.  Not an issue with tasks in this repo.  You can repo on developer community.


Replace np.int with np.int64 for compatibility with latest NumPy versions

Due to NumPy's recent depreciation of the np.int type, scikit-video is now no longer compatible with the latest version of NumPy.
This MR is replacing all casts using the now depreciated np.int to the most common default type for such casts, which is np.int64.

Closed as just realised it is duplicate of: https://github.com/scikit-video/scikit-video/pull/169


Hours and minutes returned as 00

Similar to this issue:
https://github.com/phstc/jquery-dateFormat/issues/112
On Android Chrome v67, confirmed on multiple devices, hours and minutes are being returned as 00
I do not see the issue on Chrome v67 Mac High Sierra as described in the above link.

Any update on this please? Or even acknowledgement would be nice :-)


Fix docs workflow

It turns out the issue with the docs workflow was a clash between two plugins: mknotebooks and include-markdown (it appears they may run together, but very intensive and takes > 2 hours so not useable in practice).
This PR includes a manual pre-processing script to mimic the functionality of include-markdown. The included syntax is the same (without flexibility) - we simply look for the tag within docs .md files, and replace the tags with the content of the supplied path. It is not hugely robust, but should be fine given our currently minimal use of inclusions.
It is primarily designed to be run in CI - running manually alters the files and so runs the slight risk that altered files get committed to the repo (and thus become insensitive to future code changes), but this should be picked up in review, and I imagine the script will be used pretty minimally anyhow. At any rate if it becomes annoying (and the issue with the plugins remains unresolved) then we could always wrap the functionality of the script in our own minimal mkdocs plugin.

Workflow run and results thereeof.


Machine Learning option not available in Add menu on F# project

System Information (please complete the following information):

Model Builder or CLI Version: The one that comes with Visual Studio version 16.8.6
Visual Studio Version (if applicable): 16.8.6

Describe the bug

On which page of the tutorial did you run into an issue (URL): https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/create
Clear description of the problem: The option to add Machine Learning is just not there. See screenshot.
This does work for C# projects. Is F# intentionally not supported? I can't find that condition documented anywhere.

To Reproduce

Install the ML.NET Model Builder (Preview) component in Visual Studio Installer
In options tick the box that says Enable ML.NET Model Builder in Options > Environment > Preview Features
Right click on the project
Hover over Add
The option isn't listed

Expected behavior
For the option to be listed in the Add menu for F# projects.
Screenshots

Additional context
It only appears to not work or F# projects. It does seem to work for C#.
This is a .NET 5.0 F# project. However it doesn't work with .NET Core 3.1 either.

Hey @Arrow7000!
It doesn't work today - from Model Builder we generate code and unfortunately our generation only supports C# today.
For now - does it work to have a C# project for creating the ML.NET Models and reference C# project from your F# project? After it's generated the model and consumption code ... you could try porting that to F# project as well.
I haven't tried using ML.NET with F# directly but if you do try it out ... can you share your results and feedback? If we can get an understanding of what the F# experience should be like ... we can try to fit it into our planning to add F# support.
Cheers,
Jake

I think what I'll try is, like you say, generating C# code and then porting it to F# manually. Thanks @JakeRadMSFT :)
What would be the best way to leave feedback on the F# experience?

@Arrow7000  right here! Let me know how it went!

Thanks for reporting this issue @Arrow7000. I'm closing this issue since there's been no activity on it. If you have any additional suggestsions, questions, or problems, please feel free to open another issue.


Add ability to authenticate against private JFrog registry when adding custom cluster in Rancher

What kind of request is this (question/bug/enhancement/feature request):
Enhancement
Details
It would helpful to have the ability to automatically authenticate against a private JFrog registry when adding a custom type cluster in Rancher. At the moment, in airgap scenario with use of private registry such as JFrog Container Registry one would have to either configure credentials on each node of the custom cluster(or do docker login manually) prior to the sudo docker run..  command provided by Rancher UI. Without it it fails requesting authentication:
Trying to pull repository registry.example.com/rancher-example-test/rancher/rancher-agent ...
/usr/bin/docker-current: Get https://registry.example.com/v2/rancher-example-test/rancher/rancher-agent/manifests/v2.3.3: unknown: Authentication is required.
See '/usr/bin/docker-current run --help'.

One idea would be to include in the Rancher provided docker command a way to authenticate the registry user, rather than requiring manual effort as explained above. By doing so, the rancher-agent image would be then successfully downloaded and then the private registry information provided for that custom cluster would be used to fetch the required images and provision the cluster.

Is https://github.com/rancher/rancher/issues/20029 related?

Closing the issue as the idea of providing registry credentials in UI is not secure. Doing a docker login before running the docker run command is the most common path to follow.


Blocks and characters display should not get confused.

Expected Behavior
Related to #337
Blocks should not be shown as part of a character when dragging the character, and characters should not appear as blocks when the blocks are being dragged.
Actual Behavior
https://user-images.githubusercontent.com/399209/122299888-8da54180-cecc-11eb-8522-b834bf3698fc.mp4
https://user-images.githubusercontent.com/399209/122299897-9433b900-cecc-11eb-8780-4078107ae14b.mp4
Steps to Reproduce

Start from the Race Story starter
move some characters around
add the Peg character, and move it around
Add some blocks, and then move the blocks

Device and Operating System
Samsung Galaxy E

Right now we're not seeing these issues in the latest version. Closing and will reopen if we get new reports.


static late and definite initialization

As noted by @MikhailMalyutin, the typechecker accepts this:
class HazelcastExecutor {
    static late HazelcastExecutor _instance;

    shared new () {}

    shared HazelcastExecutor instance => HazelcastExecutor._instance;
}

It doesn't accept this:
class HazelcastExecutor {
    static late HazelcastExecutor _instance;

    shared HazelcastExecutor instance => HazelcastExecutor._instance;

    shared new () {}
}

I'm not sure, but perhaps it should accept both.

I'm not sure, but perhaps it should accept both.

If one, then I agree, definitely both.
I don't see how instance initialization is relevant to class initialization for this. The fact that the value's type is the same as the class's type just confuses the issue.

I have relaxed this check.


feat(wardend): burn 30% of the tx fee

This PR should be merged after https://github.com/warden-protocol/snapshots/pull/1

Did you consider implementing this feature as a BeginBlocker instead of an AnteHandler? Do you know if there are limitations to one or the other possible implementations?


<-:1> %fire-core -fire-span.{<1.abr {#t *} ...> {huge subject type}}

While trying to pretty-print void is certainly an error, and even one I am somewhat thankful to the typesystem for catching, "fire-core" is not the most helpful of messages to print there.

As opposed to, like, a special case in #>/#< expansion for %show-void.

Hm, |.((dec !!)) also fails to compile, with what is now a fire-span. Shouldn't that just short-circuit to an outer %void?

Could you give the reproduction in the initial comment instead of the title?  This is confusing.

Yes, fix this issue report please.  It might as well be an EKG core of
someone's brain while discovering this issue.  Whatever exactly the issue
is.
On Wed, Feb 8, 2017 at 2:40 PM, Galen Wolfe-Pauly<EMAIL_ADDRESS>wrote:

Could you give the reproduction in the initial comment instead of the
title? This is confusing.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/issues/98#issuecomment-278485869, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALyAYOM46BGKpmFPguHCugqjej35V5Yks5rakRMgaJpZM4H9FVa
.

The issue is that the hoon expression <-:1> prints a very verbose and confusing type error, when the core problem is that you're trying to pretty-print a void value.

Closing as I think this is too idiosyncratic to be useful more broadly.

"Too idiosyncratic" = "it does still reproduce"? Mildly disagree that "it takes multiple pages to print a 'trying to print a void type' error" is particularly an edge case(as opposed to the specific <-:1> minimal-example, which like, <[!!]> does the same thing I think), but won't insist on it

Like #115, this is a bug in the current prettty-printer, likely fixed in the new printer, but that is not fully integrated.

Can we reopen these until then, and put "fixed #98, #115" in the message of whichever full-integration commit ends up resolving them? :3

Too idiosyncratic" = "it does still reproduce"?

I think the title/OP/initial comments are too idiosyncratic to be useful as-is -- i.e., it's just hard to tell what the issue is supposed to be, even if it's somehow associated with problematic behaviour (as echoed by other comments prior to mine).


Setup semantic test infrastructure

I'm gonna go ahead and merge this @xeno-by as I suspect you are busy in the next few days.

Yes, please feel free to merge.


KAFKA-17848: Fixing NPE in delayed share fetch

The test shows that with 16 topic partitions reading 1 million messages with 10 Share Consumers, the share fetch stucks.
Though the code should execute tryComplete but in some scenario onComplete is called prior to the tryComplete which causes error. This PR fixes same.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@junrao For my understanding, what can trigger onComplete without invoking tryComplete? Is it the number of requests that can be in purgatory? I was doing 10 share consumers paralled read with 5Million records already produced over 16 partitions.

@junrao @adixitconfluent @AndrewJSchofield Can I please get a re-review.

@junrao Thanks for the suggestion, I have addressed the feedback.


Update spec for mul op

Work for #9, base on the existing working branch:

rebase to catch up with main
add 66bit (9 bytes) constraints for v0 / v1
fix the testing scripts

lgtm. created a PR to EF now.


Out of nowhere: SignatureError: Signature missing for response

Since a few days, we've had error messages on saml2 authentication. The IdP is Google apps, our side is Django 1.11 on Python 2.7. The login has been working for months and suddenly stopped. Therefore I'd think this is not a case of wrong configuration. I checked the metadata xml config, and it's not a case of expired validity.
The error we're seeing is:
Signature Error: Signature missing for response
XML parse error: Signature missing for response
Invalid or malformed SAML Assertion.
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/djangosaml2/views.py", line 271, in assertion_consumer_service
    response = client.parse_authn_request_response(xmlstr, BINDING_HTTP_POST, outstanding_queries)
  File "/usr/local/lib/python2.7/dist-packages/saml2/client_base.py", line 702, in parse_authn_request_response
    binding, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/saml2/entity.py", line 1138, in _parse_response
    response = response.loads(xmlstr, False, origxml=origxml)
  File "/usr/local/lib/python2.7/dist-packages/saml2/response.py", line 512, in loads
    self._loads(xmldata, decode, origxml)
  File "/usr/local/lib/python2.7/dist-packages/saml2/response.py", line 337, in _loads
    **args)
  File "/usr/local/lib/python2.7/dist-packages/saml2/sigver.py", line 1738, in correctly_signed_response
    raise SignatureError("Signature missing for response")
SignatureError: Signature missing for response

Our SAML_CONFIG contains the item "authn_requests_signed": "true" However, this has been working correctly up until now, so I don't get why this would suddenly pop up. I tried commenting out this settings, and changing it to "false" (also tried python booleans instead of string values), but to no avail. When looking at the xml structure & content of the saml message, the signature is present:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<saml2p:Response
    xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol" Destination="https://our_site/saml2/acs/" ID="some_id" InResponseTo="id-36dxayd46WoIHJnmc" IssueInstant="2017-10-15T10:14:58.964Z" Version="2.0">
    <saml2:Issuer
        xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion">https://accounts.google.com/o/saml2?idpid=our_google_idpid
    </saml2:Issuer>
    <saml2p:Status>
        <saml2p:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"/>
    </saml2p:Status>
    <saml2:Assertion
        xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" ID="session_id" IssueInstant="2017-10-15T10:14:58.964Z" Version="2.0">
        <saml2:Issuer>https://accounts.google.com/o/saml2?idpid=our_google_idpid</saml2:Issuer>
        <ds:Signature
            xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
            <ds:SignedInfo>
                <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
                <ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
                <ds:Reference URI="#session_id">
                    <ds:Transforms>
                        <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
                        <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
                    </ds:Transforms>
                    <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
                    <ds:DigestValue>Cb/UaHp9...VBQ=</ds:DigestValue>
                </ds:Reference>
            </ds:SignedInfo>
            <ds:SignatureValue>mi+t3nw...jJJOr3XVx6fJIcblXE3wK0LR2hw==</ds:SignatureValue>
            <ds:KeyInfo>
                <ds:X509Data>
                    <ds:X509SubjectName>ST=California,C=US,OU=Google For Work,CN=Google,L=Mountain View,O=Google Inc.</ds:X509SubjectName>
                    <ds:X509Certificate>MIIDdDCCAlygAwIBAgIGAVjyQ98LMA0GCSqGSIb3DQEBCwUAMHsxFDASBgNVBAoTC0dvb2dsZSBJ
...
n0f8fRAlU4xmQ6F7P6W0S7Cx56ZxqfWRyrpQRR6Nt5XV</ds:X509Certificate>
                </ds:X509Data>
            </ds:KeyInfo>
        </ds:Signature>
        <saml2:Subject>
            <saml2:NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">my_name_id</saml2:NameID>
            <saml2:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
                <saml2:SubjectConfirmationData InResponseTo="id-36dxayd46WoIHJnmc" NotOnOrAfter="2017-10-15T10:19:58.964Z" Recipient="https://our_site/saml2/acs/"/>
            </saml2:SubjectConfirmation>
        </saml2:Subject>
        <saml2:Conditions NotBefore="2017-10-15T10:09:58.964Z" NotOnOrAfter="2017-10-15T10:19:58.964Z">
            <saml2:AudienceRestriction>
                <saml2:Audience>https://our_site/saml2/metadata/</saml2:Audience>
            </saml2:AudienceRestriction>
        </saml2:Conditions>
        <saml2:AttributeStatement>
            <saml2:Attribute Name="first_name">
                <saml2:AttributeValue
                    xmlns:xs="http://www.w3.org/2001/XMLSchema"
                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:anyType">Mathieu
                </saml2:AttributeValue>
            </saml2:Attribute>
            <saml2:Attribute Name="email">
                <saml2:AttributeValue
                    xmlns:xs="http://www.w3.org/2001/XMLSchema"
                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:anyType">my_name_id
                </saml2:AttributeValue>
            </saml2:Attribute>
        </saml2:AttributeStatement>
        <saml2:AuthnStatement AuthnInstant="2017-10-15T10:02:38.000Z" SessionIndex="session_id">
            <saml2:AuthnContext>
                <saml2:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:unspecified</saml2:AuthnContextClassRef>
            </saml2:AuthnContext>
        </saml2:AuthnStatement>
    </saml2:Assertion>
</saml2p:Response>

We've been running pip version 0.16.1 , I tried switching to 0.16.10 but that failed due to the known issue with python2 which has been fixed on git, so I also tried installing from git master. Nothing works...
Any thoughts?

As reference for anyone who might run into the same issue; this comes from a change in PySaml2 default behaviour. We did not pin the requirement correctly (we used >=4.4.0) and the 4.5.0 version was released, which started blocking unsigned responses by default.

Thanks for your report. We were actually just considering to upgrade to pysaml2 4.5.0 also, so I'm interested to know if this can possibly break things.
You're saying:

4.5.0 version was released, which started blocking unsigned responses by default.

Your requests could have been signed (as configured with authn_requests_signed, but that does not say anything about the Response that comes from IdP to SP's ACS endpoint. If you want to accept unsigned responses, you should configure want_assertions_signed to False. What's your current setting for this? Or have you not defined it in your config? If not, would you please try it and let me know if it fixed your issue?
Thanks

In my config, under SAML_CONFIG['service']['sp'] I have the following config (relevant to this)
        "authn_requests_signed": True,
        "want_response_signed": False,

The setting want_assertions_signed is not configured and never has been (it defaults to True that way).
The authn_requests_signed was to align with the IdP settings.
The want_response_signed settings is new since the upgrade, as that default behaviour has been changed (see https://github.com/rohe/pysaml2/pull/439/files) - previously it defaulted to False.
This is still something else from the want_assertions_signed  which you mentioned; that one did I not set.
The issue was fixed by two ways (independantly):

One of our IdP's is Google App Saml2. There, we can enable the checkbox to sign responses (it's disabled by default)
Adding the "want_response_signed": False to our settings. This was necessary as one of our IdP's is external, and it's configuration is out of our control.

We now run with the following package versions on Django 1.11:
pysaml2==4.5.0
djangosaml2==0.16.1


Removed initialization check and added off to the event binds.

Removed initialization check and added off to the event binds. This would make it possible to change the chip dataset on fly by simply re-initializing the "material_chip" with new data. This solves following 2 issues:
https://github.com/Dogfalo/materialize/issues/3626
https://github.com/Dogfalo/materialize/issues/3458

Its the chips.js file in the js folder

Ohh. Will do that. Thanks for guiding
--
Anirudh Prabhu
Portfolio: www.behance.net/anirudh
Blog: http://anirudhprabhu.blogspot.com/
LinkedIn: http://www.linkedin.com/in/anirudhprabhu
Site: http://anirudhprabhu.branded.me/
Amazon Author: https://www.amazon.com/author/anirudhprabhu
Design - Develop - Train
Date: Sun, 25 Sep 2016 11:01:17 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [Dogfalo/materialize] Removed initialization check and added off to the event binds. (#3689)
Its the chips.js file in the js folder
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@acburst i made the changes but my git seems to have amended the changes to my previous pull request. will it work or what exactly do i need to do?

Hi @acburst I have made the changes and committed those. Kindly review and lemme know if they are fine.

@acburst / @Dogfalo Can you please review the pull request i created? I have made the changes suggested by Alan Chang.

Sorry for the delay, thanks for this


Update columnstore-indexes-query-performance.md

Correcting the list of datatypes supported by aggregate pushdown.

@kfarlee,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@kfarlee Thanks for fixing this.  Next time, be sure to fix it in the sql-docs-pr repo.  That's where MSFT employees do their fixes.


Railgun movement on events not working as intended

When clicking to move, the event is not processed until another move to click happens.

Events sent to server using RailGun don't appear to get raised past RailServer process commands for packet with events.

The issue was with how mobile party works with movement. A flag (DefaultBehaviorNeedsUpdate) needed to be set for pathfinding to process. Due to the latency, the movement was not changed until after pathfinding was processed.


Clean is an unknown argument

Brief bug description
Trying to run clean command. Returns with error "Unknown arguments: environmentId, apiKey, clean"
Repro steps
Run command as according to read me
npx @kontent-ai/data-ops clean --environmentId <target-environment-id> --apiKey <Management-API-key>
Test environment
<EMAIL_ADDRESS>

hello and thanks for your submission. minor version was not released following the merge to main. v1.1.0 is now released and includes the clean operation.


Ordering Multiple Volunteers Per Shift

Hello. We used to use Onebox phone system which was a great layout for our helpline schedule. We were able to enter helpline volunteers just once into the database. The we could go into a calendar view of the week and enter per shift which volunteers were scheduled and the order in which they are scheduled (very important because we have people specifically requesting 1st, 2nd and 3rd shift orders). We didn't have to manipulate a main volunteer list based on their shift schedule or have to enter volunteers in multiple times to get the correct order.
Is this a possibility for YAP?

You can only sequence the master list.  There is no per shift order sequencing.

You can change the sequence by dragging and dropping the volunteers.

Will this feature ever be available?

Do you have a screenshot from OneBox I can see?

Not anymore, we discontinued their service to switch to grasshopper.

Nothing is impossible, it really comes down to the demand of a feature/usability and priority compared to other feature requests/bugs that have been sitting in the hopper for a while.

Have you installed Yap and played around with it yet?

we basically have a sunday - monday schedule of midnight to 8am, 8am to noon, noon to 4pm, 4pm to 8pm, 8pm to midnight. I was able to enter a master list of volunteers and select one of the specific time slots and enter any amount of volunteers and change the order of which they are called.

I had Mat S set it up for us and I logged in and started to play around with it. It seems similar to grasshopper when it comes to what I'm trying to do. For grasshopper I had to enter all of the volunteers with a "1" after their name for first shifts and then re enter them in with "2" for second shifts, etc.

Mat wanted to make sure I told you that the AD from South Florida is an asshole

Time slots are set on the volunteers in which you can set any number of shifts times and days.  You can sequence the order in which they are called, but the ordering is not going to be unique per person per shift.

Yeah, I understand that it's the same with Grasshopper. We have about 20 volunteers and we have 3 shifts per time slot so it gets very complicated to arrange and organize the shifts. Is it possible to add this feature to YAP at some point?

Potentially, it's a rather large change to implement.  It requires decoupling scheduling from volunteers.  There are a number of other "in-demand" features that have been waiting a while to implement, and this is the first time that this request has been placed.

similar related issues #218 and #115

Alright, well in the meantime I will setup the volunteer list and schedule the same way I have it set up in the Grasshopper system. This way we can at least test out and play around with YAP. Is it possible to make my request into a formal request? Maybe at some point in the near future that option can be implemented?

This ticket serves as a formal request.

Ok cool. Thank you very much!

Can you share some screenshots from Onebox so that I can see it for inspiration?

Probably not going to implement this, since one person asked for it 4 years ago.


Behaviour on change in IP address no SYSTEM_EVENT_STA_LOST_IP

Environment

Core (if using chip or module): ESP-WROOM32
IDF version (git rev-parse --short HEAD to get the commit id.): absolute latest from master
Development Env:		Eclipse
Operating System:		Windows
Power Supply:         external 24V to 3.3V

Problem Description
When deploying devices in the field we go through a process where the device is allocated a DHCP address and, depending on the address allocated we might change the IP address to fit into a certain organisational structure.
We primarily use MikroTik APs managed by CAPSMan so this change is achieved by:
a) converting the dynamic lease into a pseudo "static" lease;
b) changing the assigned "static" IP address to the required address
c) Waiting for the lease time to expire for the IP address to change
Expected Behavior
We expect to see 2 events at this time being:
a) SYSTEM_EVENT_STA_LOST_IP
b) SYSTEM_EVENT_STA_GOT_IP
If both events are received our code will close all client & server sockets opened with the old address and reopen them with the new address.
Actual Behavior
All we see is SYSTEM_EVENT_STA_GOT_IP and the application either hangs or spews out a long string of Telnet, Syslog or MQTT error messages
Steps to reproduce
Just follow step a-c above
Code to reproduce this issue
Debug Logs
Other items if possible

SYSTEM_EVENT_STA_GOT_IP has an ip_changed property.  So you are saying it crashes on dhcp renew?

If my assumption is correct the ip_changed flag would indicate the following logic:
a) On first SYSTEM_EVENT_STA_GOT_IP when IP goes from 0/invalid to valid1 the flag should be false
b) On subsequent SYSTEM_EVENT_STA_GOT_IP when IP goes from validX to validY the flag should be true to indicate that it did effectively "change"
If the above assumption is correct then I think we should re-look the code because the flag currently ALWAYS is true.

That is something to consider whether the flag should be set when going from an invalid address to a valid one.  But I don't know if it should really disrupt application logic since your app should know it doesn't have any connections to tear down.

Have added the logic to check if my existing IP is non-zero, in which case the change is a new address as opposed to the first address.
Happy to close the issue, but think the exact reasoning should be clarified in documentation.


[Releases] Automate sanity/smoke testing

Each package release required manual testing and signoff from teams before shipping.

What steps were taken to verify that artifacts were ready for release?
Can these steps be automated and optimized to run in a few minutes?
Can automation runs be kicked off after successful artifact production for release builds?

For those things that can't be automated we should collect best practices so we're applying success criteria consistently across sanity checks.

This is possibly related to or a dupe of azure/azure-sdk-for-js#2783

@kurtzeborn is this related to Unified Pipelines? I'm trying to close that epic down ;)

I'm gonna take a risk and close this one ;)


Fix small typo: procesors -> processors

Coverage remained the same at 90.397% when pulling 77a9f30a705d01c6cc6226293b4a6b9ed23bc94a on skade:patch-1 into 9550c813fc1556bd85fec5834a3f8eba19f51cc3 on hackndev:master.

Coverage remained the same at 90.397% when pulling 77a9f30a705d01c6cc6226293b4a6b9ed23bc94a on skade:patch-1 into 9550c813fc1556bd85fec5834a3f8eba19f51cc3 on hackndev:master.

Thanks!