Redis cluster with TLS encryption have replication broken.

I have issues
I'm submitting a bug report
What is the current behavior?
Obviously, clustering is not working. Neither a slave catch up new key, nor another master.
Verify Redis clustering configured with TLS/SSL
$ kubectl exec -it redis-cluster-shard0-0 -n kubedb-demo -c redis -- sh
/data # ls /certs/
ca.crt      client.crt  client.key  server.crt  server.key
redis-cli --tls --cert /certs/client.crt --key /certs/client.key --cacert /certs/ca.crt
<IP_ADDRESS>:6379> cluster nodes
1dddc8fe591bbafc6324a6e90d7cbe4ce9b171e7 <IP_ADDRESS>:6379@16379 myself,master - 0<PHONE_NUMBER>000 1 connected 0-5460
f5a7c80c1c5e77c578c789700923a7aa1aa4e4b4 <IP_ADDRESS>:6379@16379 slave 1dddc8fe591bbafc6324a6e90d7cbe4ce9b171e7 0<PHONE_NUMBER>000 1 connected
838e36ecfa7720ba8b1883899ff2d5e764a9b36a <IP_ADDRESS>:6379@16379 slave eed0040e1b8052a6dbc2387d2309a45c9936801c 0<PHONE_NUMBER>655 2 connected
d0468e8bbffc73bd089924912493f00cbac5abbc <IP_ADDRESS>:6379@16379 slave 24f06616b89bb35e0932e61e8cbad823324aa1cb 0<PHONE_NUMBER>000 3 connected
eed0040e1b8052a6dbc2387d2309a45c9936801c <IP_ADDRESS>:6379@16379 master - 0<PHONE_NUMBER>553 2 connected 5461-10922
24f06616b89bb35e0932e61e8cbad823324aa1cb <IP_ADDRESS>:6379@16379 master - 0<PHONE_NUMBER>653 3 connected 10923-16383

<IP_ADDRESS>:6379> set hello world
OK
<IP_ADDRESS>:6379> get hello
"world"
<IP_ADDRESS>:6379>
/data # redis-cli --tls --cert /certs/client.crt --key /certs/client.key --cacert /certs/ca.crt -h <IP_ADDRESS>
<IP_ADDRESS>:6379> get hello
(error) MOVED 866 <IP_ADDRESS>:6379
/data # redis-cli --tls --cert /certs/client.crt --key /certs/client.key --cacert /certs/ca.crt -h <IP_ADDRESS>
<IP_ADDRESS>:6379> get hello
(error) MOVED 866 <IP_ADDRESS>:6379

Logs from pods of 3 masters and slave of 0:
denis@L560:~/huma/hpaas-operator$ kubectl -n kubedb-demo logs redis-cluster-shard0-0
1:C 16 Aug 2021 09:39:03.853 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 16 Aug 2021 09:39:03.853 # Redis version=6.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 16 Aug 2021 09:39:03.853 # Configuration loaded
1:M 16 Aug 2021 09:39:03.855 * No cluster configuration found, I'm 1dddc8fe591bbafc6324a6e90d7cbe4ce9b171e7
1:M 16 Aug 2021 09:39:03.858 * Running mode=cluster, port=6379.
1:M 16 Aug 2021 09:39:03.858 # Server initialized
1:M 16 Aug 2021 09:39:03.858 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 16 Aug 2021 09:39:03.858 * Ready to accept connections
1:M 16 Aug 2021 09:39:15.185 # configEpoch set to 1 via CLUSTER SET-CONFIG-EPOCH
1:M 16 Aug 2021 09:39:15.195 # IP address for this node updated to <IP_ADDRESS>
1:M 16 Aug 2021 09:39:20.105 # Cluster state changed: ok
1:M 16 Aug 2021 09:39:35.340 * Replica <IP_ADDRESS>:6379 asks for synchronization
1:M 16 Aug 2021 09:39:35.341 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'dfd89dbfe30eaea9e865e796184dc20bfd838966', my replication IDs are '88a8bab04984f75d2b3cee29ca0a9dfc6fab97b7' and '0000000000000000000000000000000000000000')
1:M 16 Aug 2021 09:39:35.341 * Replication backlog created, my new replication IDs are '3a41d91880d4d884f1441e0b83754b6d97cad647' and '0000000000000000000000000000000000000000'
1:M 16 Aug 2021 09:39:35.341 * Starting BGSAVE for SYNC with target: disk
1:M 16 Aug 2021 09:39:35.342 * Background saving started by pid 66
66:C 16 Aug 2021 09:39:35.346 * DB saved on disk
66:C 16 Aug 2021 09:39:35.347 * RDB: 0 MB of memory used by copy-on-write
1:M 16 Aug 2021 09:39:35.439 * Background saving terminated with success
1:M 16 Aug 2021 09:39:35.440 * Synchronization with replica <IP_ADDRESS>:6379 succeeded
1:M 16 Aug 2021 09:42:03.396 # Error accepting a client connection: error:1408F10B:SSL routines:ssl3_get_record:wrong version number (conn: fd=23)
denis@L560:~/huma/hpaas-operator$ kubectl -n kubedb-demo logs redis-cluster-shard0-1
1:C 16 Aug 2021 09:39:05.248 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 16 Aug 2021 09:39:05.248 # Redis version=6.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 16 Aug 2021 09:39:05.248 # Configuration loaded
1:M 16 Aug 2021 09:39:05.252 * No cluster configuration found, I'm f5a7c80c1c5e77c578c789700923a7aa1aa4e4b4
1:M 16 Aug 2021 09:39:05.255 * Running mode=cluster, port=6379.
1:M 16 Aug 2021 09:39:05.256 # Server initialized
1:M 16 Aug 2021 09:39:05.256 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 16 Aug 2021 09:39:05.256 * Ready to accept connections
1:M 16 Aug 2021 09:39:33.442 # IP address for this node updated to <IP_ADDRESS>
1:S 16 Aug 2021 09:39:34.365 * Before turning into a replica, using my own master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
1:S 16 Aug 2021 09:39:34.366 # Cluster state changed: ok
1:S 16 Aug 2021 09:39:35.330 * Connecting to MASTER <IP_ADDRESS>:6379
1:S 16 Aug 2021 09:39:35.330 * MASTER <-> REPLICA sync started
1:S 16 Aug 2021 09:39:35.335 * Non blocking connect for SYNC fired the event.
1:S 16 Aug 2021 09:39:35.337 * Master replied to PING, replication can continue...
1:S 16 Aug 2021 09:39:35.339 * Trying a partial resynchronization (request dfd89dbfe30eaea9e865e796184dc20bfd838966:1).
1:S 16 Aug 2021 09:39:35.343 * Full resync from master: 3a41d91880d4d884f1441e0b83754b6d97cad647:0
1:S 16 Aug 2021 09:39:35.343 * Discarding previously cached master state.
1:S 16 Aug 2021 09:39:35.441 * MASTER <-> REPLICA sync: receiving 175 bytes from master to disk
1:S 16 Aug 2021 09:39:35.441 * MASTER <-> REPLICA sync: Flushing old data
1:S 16 Aug 2021 09:39:35.441 * MASTER <-> REPLICA sync: Loading DB in memory
1:S 16 Aug 2021 09:39:35.441 * Loading RDB produced by version 6.0.6
1:S 16 Aug 2021 09:39:35.441 * RDB age 0 seconds
1:S 16 Aug 2021 09:39:35.441 * RDB memory usage when created 2.52 Mb
1:S 16 Aug 2021 09:39:35.441 * MASTER <-> REPLICA sync: Finished with success
1:S 16 Aug 2021 09:39:35.442 * Background append only file rewriting started by pid 22
1:S 16 Aug 2021 09:39:35.466 * AOF rewrite child asks to stop sending diffs.
22:C 16 Aug 2021 09:39:35.467 * Parent agreed to stop sending diffs. Finalizing AOF...
22:C 16 Aug 2021 09:39:35.467 * Concatenating 0.00 MB of AOF diff received from parent.
22:C 16 Aug 2021 09:39:35.467 * SYNC append only file rewrite performed
22:C 16 Aug 2021 09:39:35.467 * AOF rewrite: 0 MB of memory used by copy-on-write
1:S 16 Aug 2021 09:39:35.530 * Background AOF rewrite terminated with success
1:S 16 Aug 2021 09:39:35.530 * Residual parent diff successfully flushed to the rewritten AOF (0.00 MB)
1:S 16 Aug 2021 09:39:35.530 * Background AOF rewrite finished successfully
denis@L560:~/huma/hpaas-operator$ kubectl -n kubedb-demo logs redis-cluster-shard2-0
1:C 16 Aug 2021 09:39:10.009 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 16 Aug 2021 09:39:10.009 # Redis version=6.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 16 Aug 2021 09:39:10.009 # Configuration loaded
1:M 16 Aug 2021 09:39:10.013 * No cluster configuration found, I'm 24f06616b89bb35e0932e61e8cbad823324aa1cb
1:M 16 Aug 2021 09:39:10.018 * Running mode=cluster, port=6379.
1:M 16 Aug 2021 09:39:10.018 # Server initialized
1:M 16 Aug 2021 09:39:10.018 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 16 Aug 2021 09:39:10.019 * Ready to accept connections
1:M 16 Aug 2021 09:39:15.186 # configEpoch set to 3 via CLUSTER SET-CONFIG-EPOCH
1:M 16 Aug 2021 09:39:15.301 # IP address for this node updated to <IP_ADDRESS>
1:M 16 Aug 2021 09:39:20.180 # Cluster state changed: ok
1:M 16 Aug 2021 09:39:37.299 * Replica <IP_ADDRESS>:6379 asks for synchronization
1:M 16 Aug 2021 09:39:37.299 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'b5c7f4d3733a7a656b0e65ba40710b721e2d735e', my replication IDs are '73af330c9140f0d7800aee294fd6f95d3d831c8d' and '0000000000000000000000000000000000000000')
1:M 16 Aug 2021 09:39:37.299 * Replication backlog created, my new replication IDs are 'edfb5b04ea4f071989d3b72707f2b49f452e6071' and '0000000000000000000000000000000000000000'
1:M 16 Aug 2021 09:39:37.299 * Starting BGSAVE for SYNC with target: disk
1:M 16 Aug 2021 09:39:37.299 * Background saving started by pid 20
20:C 16 Aug 2021 09:39:37.304 * DB saved on disk
20:C 16 Aug 2021 09:39:37.305 * RDB: 0 MB of memory used by copy-on-write
1:M 16 Aug 2021 09:39:37.354 * Background saving terminated with success
1:M 16 Aug 2021 09:39:37.355 * Synchronization with replica <IP_ADDRESS>:6379 succeeded
denis@L560:~/huma/hpaas-operator$ kubectl -n kubedb-demo logs redis-cluster-shard1-0
1:C 16 Aug 2021 09:39:06.567 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 16 Aug 2021 09:39:06.567 # Redis version=6.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 16 Aug 2021 09:39:06.567 # Configuration loaded
1:M 16 Aug 2021 09:39:06.570 * No cluster configuration found, I'm eed0040e1b8052a6dbc2387d2309a45c9936801c
1:M 16 Aug 2021 09:39:06.573 * Running mode=cluster, port=6379.
1:M 16 Aug 2021 09:39:06.573 # Server initialized
1:M 16 Aug 2021 09:39:06.573 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 16 Aug 2021 09:39:06.573 * Ready to accept connections
1:M 16 Aug 2021 09:39:15.186 # configEpoch set to 2 via CLUSTER SET-CONFIG-EPOCH
1:M 16 Aug 2021 09:39:15.200 # IP address for this node updated to <IP_ADDRESS>
1:M 16 Aug 2021 09:39:20.105 # Cluster state changed: ok
1:M 16 Aug 2021 09:39:36.163 * Replica <IP_ADDRESS>:6379 asks for synchronization
1:M 16 Aug 2021 09:39:36.163 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'bb0f82a8be0af656c166a1c61ec6895fab3157a0', my replication IDs are '5b64f77048f5fa64466b82b703e1ac959d9a9b32' and '0000000000000000000000000000000000000000')
1:M 16 Aug 2021 09:39:36.163 * Replication backlog created, my new replication IDs are '80c4dda3c393349a523f92082d74525cd7ffd08f' and '0000000000000000000000000000000000000000'
1:M 16 Aug 2021 09:39:36.163 * Starting BGSAVE for SYNC with target: disk
1:M 16 Aug 2021 09:39:36.164 * Background saving started by pid 20
20:C 16 Aug 2021 09:39:36.167 * DB saved on disk
20:C 16 Aug 2021 09:39:36.167 * RDB: 0 MB of memory used by copy-on-write
1:M 16 Aug 2021 09:39:36.238 * Background saving terminated with success
1:M 16 Aug 2021 09:39:36.238 * Synchronization with replica <IP_ADDRESS>:6379 succeeded

If this is a bug, how to reproduce it? Please include a code sample if relevant
Use KubeDB Enterprise Edition to provision a Redis cluster with TLS/SSL encryption

Install KubeDB Enterprise Edition

obtain a KubeDB Enterprise Edition license

MySQL TLS/SSL Encryption

$ openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout ./ca.key -out ./ca.crt -subj "/CN=redis/O=kubedb"
Generating a RSA private key
.........................................+++++
.......+++++
writing new private key to './ca.key'
-----
$ kubectl create secret tls my-ca \
     --cert=ca.crt \
     --key=ca.key \
     --namespace=kubedb-demo
secret/my-ca created

$ kubectl apply -f issuer.yaml --namespace=kubedb-demo
issuer.cert-manager.io/redis-issuer created

$ kubectl apply -f demo-tls.yaml --namespace=kubedb-demo
redis.kubedb.com/redis-cluster created

apiVersion: cert-manager.io/v1beta1
kind: Issuer
metadata:
  name: redis-issuer
spec:
  ca:
    secretName: my-ca
---
apiVersion: kubedb.com/v1alpha2
kind: Redis
metadata:
  name: redis-cluster
spec:
  version: 6.0.6
  mode: Cluster
  cluster:
    master: 3
    replicas: 1
  storageType: Ephemeral
  storage:
    resources:
      requests:
        storage: 1Gi
    storageClassName: "standard"
    accessModes:
      - ReadWriteOnce
  terminationPolicy: WipeOut
  tls:
    issuerRef:
      apiGroup: cert-manager.io
      kind: Issuer
      name: redis-issuer

What's the expected behavior?
I should get "hello" from each of 3 masters and slaves
Are you able to fix this problem and submit a PR? Link here if you have already
Environment details

KubeDB v2021.06.23
kubedb/operator:v0.19.0
Kubernetes version: v1.19.10-gke.1700
redis-cli 6.0.6
jetstack/cert-manager version: "1.3.1"

Any other relevant info
Installed Community Edition, Migrated to Enterprise Edition KubeDB v2021.06.23. Helm 3.
denis@L560:~/huma/hpaas-operator/demos/redis-cluster-management/kubedb$ helm ls -n kube-system
NAME                    NAMESPACE       REVISION        UPDATED                                         STATUS          CHART                                   APP VERSION
kubedb                  kube-system     2               2021-08-13 13:09:33.079450565 +0300 MSK         deployed        kubedb-v2021.06.23                      v2021.06.23

Operator's log
I0816 09:38:07.539690       1 redis.go:78] Patching Redis kubedb-demo/redis-cluster with {"metadata":{"finalizers":null}}.
I0816 09:39:00.542536       1 redis.go:78] Patching Redis kubedb-demo/redis-cluster with {"metadata":{"finalizers":["kubedb.com"]}}.
I0816 09:39:00.662609       1 service.go:37] Creating Service kubedb-demo/redis-cluster-pods.
I0816 09:39:00.771215       1 secret.go:39] Creating Secret kubedb-demo/redis-cluster.
I0816 09:39:00.783007       1 redis.go:78] Patching Redis kubedb-demo/redis-cluster with {"spec":{"configSecret":{"name":"redis-cluster"}}}.
I0816 09:39:00.843155       1 serviceaccount.go:37] Creating ServiceAccount kubedb-demo/redis-cluster.
I0816 09:39:00.876654       1 role.go:37] Creating Role kubedb-demo/redis-cluster.
I0816 09:39:00.935130       1 rolebinding.go:37] Creating RoleBinding kubedb-demo/redis-cluster.
I0816 09:39:00.996681       1 service.go:37] Creating Service kubedb-demo/redis-cluster.
I0816 09:39:01.050806       1 redis.go:86] wait for all certificate secrets for Redis kubedb-demo/redis-cluster
I0816 09:39:01.123988       1 service.go:77] Patching Service kubedb-demo/redis-cluster with {"metadata":{"annotations":null}}.
I0816 09:39:01.155298       1 redis.go:86] wait for all certificate secrets for Redis kubedb-demo/redis-cluster
I0816 09:39:02.582619       1 redis.go:86] wait for all certificate secrets for Redis kubedb-demo/redis-cluster
I0816 09:39:02.704281       1 statefulset.go:41] Creating StatefulSet kubedb-demo/redis-cluster-shard0.
I0816 09:39:02.722714       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard0
I0816 09:39:02.729475       1 pdb.go:40] Creating PodDisruptionBudget kubedb-demo/redis-cluster-shard0.
I0816 09:39:02.811460       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard0
I0816 09:39:02.916229       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:03.033228       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:04.078098       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard0
I0816 09:39:04.219184       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
E0816 09:39:04.948363       1 health.go:121] Failed to ping the database: kubedb-demo/redis-cluster error: dial tcp <IP_ADDRESS>:6379: connect: connection refused
I0816 09:39:05.041236       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:05.386198       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard0
I0816 09:39:05.489975       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:05.525726       1 statefulset.go:41] Creating StatefulSet kubedb-demo/redis-cluster-shard1.
I0816 09:39:05.542982       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard1
I0816 09:39:05.562015       1 pdb.go:40] Creating PodDisruptionBudget kubedb-demo/redis-cluster-shard1.
I0816 09:39:05.675775       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard1
I0816 09:39:05.761234       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:05.813122       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard1 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:07.104605       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard1
I0816 09:39:08.463605       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard1
I0816 09:39:08.605800       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:08.633625       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard1 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:08.659560       1 statefulset.go:41] Creating StatefulSet kubedb-demo/redis-cluster-shard2.
I0816 09:39:08.671876       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard2
I0816 09:39:08.676374       1 pdb.go:40] Creating PodDisruptionBudget kubedb-demo/redis-cluster-shard2.
I0816 09:39:08.731587       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard2
I0816 09:39:08.853826       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:08.890739       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard1 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:08.923265       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard2 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:11.132276       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard2
I0816 09:39:11.326239       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:11.375281       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard1 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:11.424290       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard2 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:13.107857       1 controller.go:113] Started processing, key: kubedb-demo/redis-cluster-shard2
I0816 09:39:13.298688       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:13.345391       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard1 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:13.383848       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard2 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:39:14.402487       1 cluster.go:82] All redis servers are ready
I0816 09:39:14.402554       1 cluster.go:658] Ensuring new cluster...
I0816 09:39:14.402780       1 cluster.go:169] Ensuring 1st pod as master in each statefulSet...
I0816 09:39:51.750203       1 cluster.go:308] Ensuring extra slaves be removed...
I0816 09:39:51.750228       1 cluster.go:169] Ensuring 1st pod as master in each statefulSet...
I0816 09:39:56.432939       1 cluster.go:353] Ensuring extra masters be removed...
I0816 09:39:56.432960       1 cluster.go:169] Ensuring 1st pod as master in each statefulSet...
I0816 09:40:01.421271       1 cluster.go:474] Ensuring new masters be added...
I0816 09:40:01.421294       1 cluster.go:169] Ensuring 1st pod as master in each statefulSet...
I0816 09:40:06.102178       1 cluster.go:525] Ensuring slots are rebalanced...
I0816 09:40:06.102266       1 cluster.go:169] Ensuring 1st pod as master in each statefulSet...
I0816 09:40:11.051881       1 cluster.go:608] Ensuring new slaves be added...
I0816 09:40:11.051931       1 cluster.go:169] Ensuring 1st pod as master in each statefulSet...
I0816 09:40:16.063165       1 cluster.go:169] Ensuring 1st pod as master in each statefulSet...
I0816 09:40:20.892729       1 statefulset.go:135] Cluster configured
I0816 09:40:20.894189       1 statefulset.go:136] Checking for removing master(s)...
I0816 09:40:20.900946       1 statefulset.go:159] Checking for removing slave(s)...
I0816 09:40:20.936778       1 appbinding.go:38] Creating AppBinding kubedb-demo/redis-cluster.
I0816 09:40:20.961279       1 service.go:140] spec.monitor.agent is not provided by prometheus.io
I0816 09:40:21.077405       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard0 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:40:21.134686       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard1 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:40:21.166340       1 statefulset.go:81] Patching StatefulSet kubedb-demo/redis-cluster-shard2 with {"spec":{"template":{"spec":{"$setElementOrder/containers":[{"name":"redis"}],"$setElementOrder/volumes":[{"name":"data"},{"name":"custom-config"},{"name":"tls-volume"},{"name":"exporter-tls-volume"}],"containers":[{"$setElementOrder/env":[{"name":"POD_IP"}],"env":[{"name":"POD_IP","valueFrom":{"fieldRef":{"apiVersion":null}}}],"name":"redis"}],"securityContext":null,"volumes":[{"$retainKeys":["name","projected"],"name":"tls-volume","projected":{"defaultMode":null}},{"$retainKeys":["name","projected"],"name":"exporter-tls-volume","projected":{"defaultMode":null}}]}}}}.
I0816 09:40:22.114746       1 cluster.go:82] All redis servers are ready

Hello @denist-huma,
For connecting as a client with Redis Cluster you need to add flag like -c in your redis-cli command. you can find out it in the official doc Ref.
From Doc,

The redis-cli utility implements basic cluster support when started with the -c switch.

This one should work:
redis-cli -c --tls --cert /certs/client.crt --key /certs/client.key --cacert /certs/ca.crt -h <IP_ADDRESS>

Then try the get hello query from a different master or a slave server.
If you still face the issue, Please let us know.

Exactly! My fault: missed "-c". Same as here https://serverfault.com/questions/812156/redis-cluster-error-moved.
My cluster is operational :tada:
Thank you @Emon46 for your support. I was breaking my head for the wrong reason :sweat:


HMR for main process in @electron-forge/plugin-webpack

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description
Webpack HMR is not implemented for the main process when using @electron-forge/plugin-webpack. The docs currently state that "It is unfortunately impossible to do hot module reloading inside a renderer preload script, WebWorkers, and the main process itself". This is however does not seem to hold for the main process at least, for example electron-webpack is capable of hot reloading the main process.
Proposed Solution
Implement HMR for the main process similarly to electron-webpack. I tried to look at exactly how it works but I'm not comfortable enough yet with HMR internals to implement this by myself.
Alternatives Considered
--
Additional Information
In #682, the idea of reloading the main process was dismissed because of the administrative burden of killing, making sure it's stopped, and restarting electron would mean for electron-forge. Implementing HMR would both improve upon that idea from a DX point of view, while eliminating the problem of restarting the process.
As I see, the only difficulty with HMR in the main process would be that users need to be aware that they need to clean up and reconfigure IPC listeners on updates, however this doesn't interfere with any current behavior, and in fact if users don't module.hot.accept updates, the fallback behavior would be exactly the same as now.

This is unlikely to be worked on by the maintainers unless it's sponsored. However, we'd be happy to review a pull request implementing this feature.

As a side-note I migrated from electron-webpack to electron-forge a while back and although it technically supports hot reloading it has a host of issues with it and I found the experience quite buggy.

@b-zurg thank you for your insight. Could you please clarify whether the issues are with electron-webpack or with electron-forge? It was a little ambiguously worded. ;) To be honest I’m at the early stages of a new project and haven’t worked much with either tool yet.

Sorry, I had many issues with electron-webpack.  I have a windows machine,  which may have exacerbated some of the issues, but some examples I remember is zombie node processes existing after the end of a dev session or if it crashed, to very large webpack logs clogging up vscode and making it unusable and no real way to change the webpack settings, to the old version of webpack that the project was on and its configuration with happypack actually being extremely resource intensive and such.
This project is much better maintained, gives more flexibility, is on the latest version of webpack (which makes a huge difference) and everything I've needed to I've been able to configure.  If you want to use electron-builder and not the publishers that's also totally possible by simply using the compiled code.

Thanks for the info @b-zurg!

HMR in the main process is not possible from a technical standpoint, we do watch via webpack and will update the compiled code in the fly so you can use the rs signal to quickly restart the app but live reloading main process code is not something that is technically possible


Migration from Java to Kotlin in the Litewallet Codebase

A long term issue that summarizes the progress

Closing ticket  vague


Use default device in examples

Fix #427
@diptorupd @reazulhoque @1e-to
If you like it, someone can extend this to all examples.

@PokhodenkoSA Can we close this as #430 supersedes this?

Can we close this as #430 supersedes this?

As I understand the approach is accepted. I will do update in #430.

Reopened for collecting only device contxt changes. @reazulhoque It is ready for review.

Ready for review.


Add installation instructions for MacOS

This PR adds instructions for building and installing dali-core at macOS.

I\ve opened it on https://review.tizen.org/gerrit/c/platform/core/uifw/dali-core/+/245917, so closing this.


Fix getting started instructions for dart

Some exercise README templates contain links to pages which no longer exist in v2 Exercism.
For example, C++'s README template had a link to /languages/cpp for instructions on running tests. The correct URLs to use can be found in the 'Still stuck?' sidebar of exercise pages on the live site. You'll need to join the track and go to the first exercise to see them.
Please update any broken links in the 'config/exercise_readme.go.tmpl' file, and run 'configlet generate .' to generate new exercise READMEs with the fixes.
Instructions for generating READMEs with configlet can be found at:
https://github.com/exercism/docs/blob/master/language-tracks/exercises/anatomy/readmes.md#generating-a-readme
Instructions for installing configlet can be found at:
https://github.com/exercism/docs/blob/bc29a1884da6c401de6f3f211d03aabe53894318/language-tracks/launch/first-exercise.md#the-configlet-tool
Tracking exercism/exercism.io#4102

@jackhughesweb How did you determine which links were broken. So far all the links take me to a website. Though one website is a blank page. I'd like to specifically find the ones that were 'broken".

@Stargator Sorry for any confusion - this was an automatically created issue to keep track of which languages have/haven’t been checked yet. We found some README templates had internal links which were broken in v2 of the website, however this doesn’t apply to all languages - please close this issue if everything is ok 😊

I’ve just checked the template file for Dart - it does seem to have a broken link (to exercism.io/languages/dart) (I’m on mobile now, but will fix the link later unless someone sends a PR first).


fix(scss): reinforced link-list pattern styling selectors

Related Ticket(s)
#1733
Description
I've updated the selectors for LinkList and TableOfComponents so they are more specific to the patterns.
Changelog
Changed

SCSS Selectors

Im actually kind of confused by how the styles are being overwritten...
Isn't .bx--link-list .bx--card__copy p and .bx--tableofcontents .bx--tableofcontents__content p specific to the linked list and table of contents respectively? How is it that those styles are affecting link list?

Im actually kind of confused by how the styles are being overwritten...
Isn't .bx--link-list .bx--card__copy p and .bx--tableofcontents .bx--tableofcontents__content p specific to the linked list and table of contents respectively? How is it that TOC styles are affecting link list?
@jeffchew @kennylam

I think it's because in this scenario, the LinkList is nested under the TableOfContents so those p styles were messing with the LinkList p styles...
cc: @RaphaelAmadeu

Im actually kind of confused by how the styles are being overwritten...
Isn't .bx--link-list .bx--card__copy p and .bx--tableofcontents .bx--tableofcontents__content p specific to the linked list and table of contents respectively? How is it that TOC styles are affecting link list?
@jeffchew @kennylam

I think it's because in this scenario, the LinkList is nested under the TableOfContents so those p styles were messing with the LinkList p styles...
cc: @RaphaelAmadeu

Exactly, TableOfContents were overwriting the intended color

Going to merge this, looks like CircleCI completed successfully but never reported back:
https://app.circleci.com/pipelines/github/RaphaelAmadeu/ibm-dotcom-library/412/workflows/2834a627-4fc7-4b38-8ac8-1c708aa065cf/jobs/566


Bump to 0.6.13

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

:warning: Warning :warning:

Pull requests are usually filed against the master branch for this repo, but this one is against v0.6.x. Please double check that you specified the right target!

Published


MGMT-15387: Refactor pkg/executer - Make it simpler to use

@jhernand can you please have a quick look? just to make sure it won't conflict too much with your executer change: https://github.com/openshift/appliance/pull/93


FEAT: deregister ship instruction

Changes
Checklist

[ ] UAT
[ ] Passes final QA checks

Task linked: CU-1tdgqt6 SCORE: Deregister ship instruction


Support for Xiaomi 3C

Is Xiaomi 3C Air purifier supported? If so, then it could be added to readme file in supported device list

Well not entirely. Looks like you can't set speed of the fan via percentage but you need to use rpm instead. That means the round slider is not showing any value and you cannot control the purifier with it.
At least I have managed to get the shortcuts from readme to work:
shortcuts:
  - name: 25%
    icon: mdi:circle-slice-2
    preset_mode: Favorite
    service: number.set_value
    service_data:
      entity_id: number.mi_air_purifier_3c_favorite_motor_speed
      value: '780'
  - name: 50%
    icon: mdi:circle-slice-4
    preset_mode: Favorite
    service: number.set_value
    service_data:
      entity_id: number.mi_air_purifier_3c_favorite_motor_speed
      value: '1250'
  - name: 75%
    icon: mdi:circle-slice-6
    preset_mode: Favorite
    service: number.set_value
    service_data:
      entity_id: number.mi_air_purifier_3c_favorite_motor_speed
      value: '1730'
  - name: 100%
    icon: mdi:circle-slice-8
    preset_mode: Favorite
    service: number.set_value
    service_data:
      entity_id: number.mi_air_purifier_3c_favorite_motor_speed
      value: '2200'

I'll try to get the slider working as well.

I was able to get it working with the following code.
`type: custom:purifier-card
entity: fan.zhimi_airpurifier_mb4
aqi:
entity_id: sensor.zhimi_airpurifier_mb4_pm2_5
stats:

entity_id: sensor.zhimi_airpurifier_mb4_filter_life_remaining
unit: '%'
subtitle: Filter Life
entity_id: sensor.zhimi_airpurifier_mb4_motor_speed
attribute: motor_speed
unit: RPM
subtitle: Motor Speed
shortcuts:
name: 25%
icon: mdi:circle-slice-2
preset_mode: Favorite
service: number.set_value
service_data:
entity_id: number.mi_air_purifier_3c_favorite_motor_speed
value: '780'
name: 50%
icon: mdi:circle-slice-4
preset_mode: Favorite
service: number.set_value
service_data:
entity_id: number.mi_air_purifier_3c_favorite_motor_speed
value: '1250'
name: 75%
icon: mdi:circle-slice-6
preset_mode: Favorite
service: number.set_value
service_data:
entity_id: number.mi_air_purifier_3c_favorite_motor_speed
value: '1730'
name: 100%
icon: mdi:circle-slice-8
preset_mode: Favorite
service: number.set_value
service_data:
entity_id: number.mi_air_purifier_3c_favorite_motor_speed
value: '2200'
show_name: true
show_state: true
show_toolbar: true
compact_view: false
card_mod:
style: |
ha-card > div.preview > div.controls > div >div {
visibility: hidden
}`

Here is the configuration I needed to use to get this card working with the Xiaomi 3C.
entity: fan.zhimi_airpurifier_mb4
aqi:
  entity_id: sensor.zhimi_airpurifier_mb4_pm2_5
stats:
  - entity_id: sensor.zhimi_airpurifier_mb4_filter_life_remaining
    unit: '%'
    subtitle: Filter Life
  - entity_id: sensor.zhimi_airpurifier_mb4_motor_speed
    attribute: motor_speed
    unit: RPM
    subtitle: Motor Speed
shortcuts:
  - name: 25%
    icon: mdi:circle-slice-2
    preset_mode: Favorite
    service: number.set_value
    service_data:
      entity_id: number.mi_air_purifier_3c_favorite_motor_speed
      value: '780'
  - name: 50%
    icon: mdi:circle-slice-4
    preset_mode: Favorite
    service: number.set_value
    service_data:
      entity_id: number.mi_air_purifier_3c_favorite_motor_speed
      value: '1250'
  - name: 75%
    icon: mdi:circle-slice-6
    preset_mode: Favorite
    service: number.set_value
    service_data:
      entity_id: number.mi_air_purifier_3c_favorite_motor_speed
      value: '1730'
  - name: 100%
    icon: mdi:circle-slice-8
    preset_mode: Favorite
    service: number.set_value
    service_data:
      entity_id: number.mi_air_purifier_3c_favorite_motor_speed
      value: '2200'
show_name: true
show_state: true
show_toolbar: true
compact_view: false

where did you use this config? Im getting invalid configuration, trying also with a 3C

Anyway to get rid of the slider?

Anyway to get rid of the slider?

I also have a 3C and would like to remove the slider since it doesn't work. Adding a show_slider option we could set to false would be good enough for me.

You can allways hide it by Styling via theme or Styling via card-mod like says in the Purifier Card Read Me file says.
I'm using card-mod and this worked nice for me:
type: custom:purifier-card style: |   ha-card {   --pc-background: none;   --pc-slider-bar-color: none;   --pc-slider-path-color: none;   --pc-toolbar-background: none;   }


how to overide command-line args?

i usually use yacs with config file as below:
python3 run.py --cfg /home/plask/seoha/kubeflow/metrabs/configs/aist_only_hrnet_new_aug_all.yaml
eg.
TRAIN:
AUGMENT : true
OPTIM: "ranger"
LR: 0.0001
BACKBONE_TRAIN: true
BATCH_SIZE : 16
OCCLUDE_AUGMENT : false
NUM_STEPS_START_ABS : 10000000
but i wand to override some args like
python3 run.py --cfg /home/plask/seoha/kubeflow/metrabs/configs/aist_only_hrnet_new_aug_all.yaml --train-optim "adam" --train-lr 1e-4
i have to override with command-line(not modifying yaml file)
how can i do this?

Hi, I have the same request as U. Have U solved this issue？


Public container registry, dockerhub or quay?

Any chance we could get releases available as a docker image on a public container registry like Dockerhub or Quay? Appreciate we can build it ourselves or use the binary, would just be nicer to have official docker releases.

There are docker containers on GitHub - https://github.com/cloudflare/pint/pkgs/container/pint


crashes on SBS URLs

SBS started including the plus operator (+) in their JSON to concatenate strings, which makes it invalid JSON, which makes youtube-dl crash. I found that adding this line to the SBS extractor fixes that crash:
release_urls_json = release_urls_json.replace('"+ "', '').replace('" +"','')

$ youtube-dl --verbose http://www.sbs.com.au/ondemand/video/351437891659/Apocalypto
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', 'http://www.sbs.com.au/ondemand/video/351437891659/Apocalypto']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.02.28
[debug] Python version 2.7.9 - Linux-4.0.0-1-amd64-x86_64-with-debian-stretch-sid
[debug] exe versions: avconv 11.3-6, avprobe 11.3-6, rtmpdump 2.4
[debug] Proxy map: {}
[SBS]<PHONE_NUMBER>59: Downloading webpage
{
    "progressive": "",
    "html": "http://link.theplatform.com/s/Bgtm9B/bdlbKcELrGUX?feed=Video%20-%20Single&mbr=true&manifest=m3u&ord=2358717&policy=22428&d1=video.film.sbs.com.au&d2=sec30htmlweb&d3=preroll&dm1=video.film.sbs.com.au&dm2=sec30midrollhtmlweb&dm3=midroll",
    "standard": "http://link.theplatform.com/s/Bgtm9B/bdlbKcELrGUX?feed=Video%20-%20Single&manifest=f4m&mbr=true&ord=9866337&policy=11929623&dfptag=sz%3D530x298%26iu%3D%2F4117%2Fvideo.film.sbs.com.au%2Fsec30%26ciu_szs%26impl%3Ds%26gdfp_req%3D1%26env%3Dvp%26output%3Dxml_vast3%26unviewed_position_start%3D1%26url%3Dwww.sbs.com.au%26description_url%3DSBS%26cust_params%3Dtype%253Dpreroll%26ad_rule%3D1%26cmsid%3D531%26url%3Dhttp%253A%252F%252Fwww.sbs.com.au%252Fondemand%252Fvideo%252F351437891659%252FApocalypto%26description_url%3DSBS%26correlator%3D"+ "ord" +"%26vid%3D351437891659"
}
Traceback (most recent call last):
  File "/usr/bin/youtube-dl", line 9, in <module>
    load_entry_point('youtube-dl==2015.02.28', 'console_scripts', 'youtube-dl')()
  File "/usr/lib/python2.7/dist-packages/youtube_dl/__init__.py", line 397, in main
    _real_main(argv)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/__init__.py", line 387, in _real_main
    retcode = ydl.download(all_urls)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 1442, in download
    res = self.extract_info(url)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 643, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 275, in extract
    return self._real_extract(url)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/sbs.py", line 45, in _real_extract
    release_urls = json.loads(release_urls_json)
  File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
    obj, end = self.scan_once(s, idx)
ValueError: Expecting ',' delimiter: line 4 column 552 (char 826)

Will be fixed in the next version. Thanks for the report.


make headers case insensitive

New Pull Request Checklist

[X] I have read the Documentation
[x] I have searched for a similar pull request in the project and found none
[x] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)
[x] I have added the required tests to prove the fix/feature I am adding
[x] I have updated the documentation (if necessary)
[x] I have run the tests and they pass

This merge request fixes / refers to the following issues:
TarekkMA/gql_dio_link#4
Pull Request Description
The current implementation of the headers do allow multiple header with different letter case.
for example the following header are considered as unique.
Content-type: xxxxxx
content-type: xxxxxx
CoNtEnT-TyPe: xxxxx
The current solution I have used is the same used in http package
https://github.com/dart-lang/http/blob/master/lib/src/base_request.dart#L89
...

.


fix(php): add PHPStan for static code analysis

🧭 What and Why
Closes https://github.com/algolia/algoliasearch-client-php/issues/709
With PHPStan we could have detected this bug much earlier, and maybe other bugs.
For now its mostly types.


Rewrite the Central Dashboard in Angular

/kind feature
Currently, most of our web apps use Angular (CRUD Jupyter/Volumes/Tensorboards), however the Central Dashboard is written in Polymer.
In the interest of consistency and maintainability, we should rewrite the Central Dashboard in Angular.
cc @kubeflow/wg-notebooks-leads

@thesuperzapper Regarding the remainder of the tasks in the last comment I have the following questions:

What is the prioritization around these tasks?
Do we have Github issues to track each of these individual tasks?

I was also wondering what the plan would be to test out the completed Angular rewrite in parallel with the Polymer version of the dashboard and how the Angular rewrite would eventually be planned to be rolled out.


Restructure project internally

I think I finally got it.

There is a library in c, that python and - if needed - c code can call. It will have the unsharing and so on
the plash entrypoint will also be in the libexec folder, /usr/local/bin/plash will in the end be a symbolic link to that executable.
everything in libexec must be standalone. the "plash" in libexec is just a thin wrapper.
reexecing happens with runpy.run_path when the subcommand is implemented in python
there is a new command: eval-macro this will take one macro and it's argument and print it's result to stdout. the eval command will use that. the macros library will be entirely eval-macro in a very simple way (if else...)
after that it's trivial to rewrite command by command to c or another langauge in an incremental way, since each command is standalone. But that I don't have to do. Only if for example I can't get the python implementation fast enough.

implicit build arguments will be removed and handled differently (very breaking change)

plash run -A
will be:
plash b run -A
otherwise -A will just be interpreted as a container number, nothing more
The magic plash -A will still work
that is a breaking change, but it has do be done


[qt5-base] Build failure due to 404 URL

Package: qt5-base[core,latest]:arm64-osx -> 5.12.8
Host Environment

Host: arm64-osx
Compiler: AppleClang <IP_ADDRESS>30022
vcpkg-tool version: 2023-04-07-bedcba5172f5e4b91caac660ab7afe92c27a9895
vcpkg-scripts version: 2c5c43325 2023-06-02 (2 hours ago)

To Reproduce
cmake -DCMAKE_TOOLCHAIN_FILE=~/Work/git/vcpkg/scripts/buildsystems/vcpkg.cmake ..
Failure logs
-- Figuring out qt target mkspec. Target arch arm64
-- Target mkspec set to: macx-clang
-- Host mkspec not set. Qt's own buildsystem will try to figure out the host system
-- Downloading http://download.qt.io/official_releases/qt/5.14/5.14.2/submodules/qtbase-everywhere-src-5.14.2.tar.xz;http://mirrors.ocf.berkeley.edu/qt/official_releases/qt/5.14/5.14.2/submodules/qtbase-everywhere-src-5.14.2.tar.xz -> qtbase-everywhere-src-5.14.2.tar.xz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Disabling metrics because vcpkg.disable-metrics exists
[DEBUG] Trying to load bundleconfig from /Users/koconnor/Work/git/vcpkg/vcpkg-bundle.json
[DEBUG] Failed to open: /Users/koconnor/Work/git/vcpkg/vcpkg-bundle.json
[DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] 1000: popen( curl --fail -L http://download.qt.io/official_releases/qt/5.14/5.14.2/submodules/qtbase-everywhere-src-5.14.2.tar.xz --create-dirs --output /Users/koconnor/Work/git/vcpkg/downloads/qtbase-everywhere-src-5.14.2.tar.xz.86303.part 2>&1)
[DEBUG] 1000: cmd_execute_and_stream_data() returned 22 after   814460 us
[DEBUG] 1001: popen( curl --fail -L http://mirrors.ocf.berkeley.edu/qt/official_releases/qt/5.14/5.14.2/submodules/qtbase-everywhere-src-5.14.2.tar.xz --create-dirs --output /Users/koconnor/Work/git/vcpkg/downloads/qtbase-everywhere-src-5.14.2.tar.xz.86303.part 2>&1)
[DEBUG] 1001: cmd_execute_and_stream_data() returned 22 after   304893 us
error: Failed to download from mirror set
error: http://download.qt.io/official_releases/qt/5.14/5.14.2/submodules/qtbase-everywhere-src-5.14.2.tar.xz: curl failed to download with exit code 22
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

curl: (22) The requested URL returned error: 404

error: http://mirrors.ocf.berkeley.edu/qt/official_releases/qt/5.14/5.14.2/submodules/qtbase-everywhere-src-5.14.2.tar.xz: curl failed to download with exit code 22
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

curl: (22) The requested URL returned error: 404

[DEBUG] /Users/runner/work/1/s/src/vcpkg/base/downloads.cpp(961):
[DEBUG] Time in subprocesses: 1119353us
[DEBUG] Time in parsing JSON: 4us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 8us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 1.1 s (1120049us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):

      Failed to download file with error: 1
      If you are using a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
         set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
         The value set by your proxy might be wrong, or have same `https://` prefix issue.

      3. Your proxy's remote server is out of service.

      If you've tried directly download the link, and believe this is not a temporary
      download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
      to report this upstream download server failure.

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
  /Users/koconnor/.cache/vcpkg/registries/git-trees/d5eb924065c565f6e15ea0bd9694fa819356d685/cmake/qt_download_submodule.cmake:21 (vcpkg_download_distfile)
  /Users/koconnor/.cache/vcpkg/registries/git-trees/d5eb924065c565f6e15ea0bd9694fa819356d685/portfile.cmake:47 (qt_download_submodule)
  scripts/ports.cmake:147 (include)

Additional context
vcpkg.json
{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "dependencies": [
    {
      "name": "opencv4",
      "default-features": false,
      "features": [
        "jpeg",
        "png",
        "tiff",
        "webp"
      ]
    },
    {
      "name": "qt5-base",
      "features": [
        "latest"
      ]
    }
  ],
  "vcpkg-configuration": {
    "registries": [
      {
        "kind": "git",
        "baseline": "2c5c4332524bb894d9f35756b52f937661da2fb9",
        "repository": "https://github.com/KOConchobhair/vcpkg",
        "packages": [
          "qt5-base"
        ]
      }
    ]
  },
  "builtin-baseline": "662dbb50e63af15baa2909b7eac5b1b87e86a0aa",
  "overrides": [
    {
      "name": "opencv4",
      "version": "4.5.1"
    },
    {
      "name": "protobuf",
      "version": "3.5.1"
    },
    {
      "name": "qt5-base",
      "version": "5.12.8"
    }
  ]
}

Using https://download.qt.io/archive/qt/ will provide a more stable URL for past releases


Query with non-existent column with 'undefined' value returns all data.

This code returns all data in a collection.
Model.find({not_exist_column_name: undefined, function(err, docs){
    //err is null, and docs have all data
    console.log(err, docs)
})

In mongo console, if value is undefined we get:
error: { "$err" : "can't have undefined in a query expression", "code" : 13629 }

And if column doesn't exist, we simply get nothing.

mongoose casts everything, so undefined becomes null - in which case the results are valid.

Hi, aheckmann.
Thanks for your comment.

In case querying on a existed column with "undefined"
In case querying on a non-existent column with "undefined"

I see mongoose casts undefined into null.
So in the first situation, some records return.
I think this may be reasonable.
But in the second,
it should not return any records to query against a non-existent column with casted 'null' value.
Should it?
What I want to say here is difference between mongo cli and mongoose.
Thanks.

from mongo shell:
> db.users.count({ idontexist: null })
79617

These are also from mongo shell:
> db.users.count({idontexist:null})
0

>db.users.find({})
> (nothing returned)

with MongoDB 2.0.0
on Ubuntu 11.10 32bit
Maybe MongoDB 2.0 is not supported by mongoose?

@craftgear i just ran the same query in the shell of mongodb 2.0 and it still behaves the as I posted above. It looks to me that your db is empty.

As for mongodb 2.0 I've been running mongoose on it for a couple weeks and its been fine.

Yeah, you are right.
I am wrong.
Deelply sorry for taking your time.

cool np


Getting Started Section

First impressions matter!
We need bullet-proof installation instructions for getting started on any major development platform (ie: Windows, Mac, Linux).
The instructions should be:

Engaging - The installation process should be as painless as possible. The adjective we should strive for is "fun".
Comprehensive - No corners cut here. Screenshots, exact commands to type, in-line troubleshooting tips, etc. Our "conversion rate" for new installs should be 100%.
Explanatory - What are you installing on my machine? Why? How will this be used? No black boxes; just thorough explanations of what is happening and why.

This is such a critical piece for a new CLJS dev interested in getting his toes wet. First impressions matter!

Seems like this will be composed of:

Installation instructions
Compiling first project
Where from here? (links to other things)

Some getting-started references:

Dart
TypeScript
PureScript
CoffeeScript
LiveScript
Elm
Haxe

http://www.mrspeaker.net/2015/02/18/nearly-getting-started-with-clojurescript/

@NPrescott this is a good reference for getting started. @oakmac @shaunlebron add additional getting started ideas as necessary.


Compute readableByte on read and write operations to avoid additional…

… iterations
Motivation:
ByteBufDecoderInput accumulates the readable bytes by iterating underlying ByteBufs.
It should be more efficient to internally manage the size than compute the number.
Modifications:

Increase and decrease readable bytes depending on read and write operations.

Result:
Optimized computation

Sounds reasonable to me.


Fix example npm start and  migrate from easyrtc@1 to open-easyrtc@2

Again this fix more than  487 vulnerabilities  and improve easyrtc WebRTC support.
Full EasyRTC to OpenEasyRTC ChangeLogs: open-easyrtc/open-easyrtc#6

@haydenjameslee this fix the basic errors of missing socket.io, missing easyrtc loading in example, missing dist staticServe.
This make this naf-easyrtc-adapter works where before it was not functional.

after this fixes the module works properly

npm i
npm start

Cc @haydenjameslee please consider my PR to fix this project issues.
Thank you.

@hthetiot What do you think about making a new repo for open-easyrtc, so that people who require the old easyrtc for any reason can use it. This makes sense to me because they are different libraries (even though they have the same API).

@haydenjameslee ok but why not simply merging this ? It take one click no ?

Note: the old easyRTC is dead Priologic removed it from GitHub, also ok easyRTC is full of security issues. Letting user use the old easyRTC is putting user at risk, also this PR fix more than easyRTC it fix basically this repository to work out of the box.

Conclusion there only one easyRTC now it's Open-EasyRTC therefore you should merge this PR and we can just move on.

This is a shame.... Why not fixing all the issues that make that repository works and update to open-easyrtc at the same time....

Up.

So, just fixing this doesn't give any testable demo, because the example in this repo uses aframe 0.7 and NAF 0.3 (on top of that, some custom iteration where hayden seems to have first tested the idea of 'NAF.adapter.register()', which later became standard). So, combing the changes in this pull request, with updates in the basic audio in the latest NAF, and bumping up versions of things, I came up with this glitch: https://glitch.com/edit/#!/join/ee19387d-eaad-4ff3-8353-be62ac4945b0
Sadly, the result is still not functional.
Locally, it seems fine. I open two tabs, I get feedback. Logs show connections seem to be going through, supposedly.
However, when I have someone at a distance log in, it fails to get any audio going through.
This is also true if I revert to 0.6.1 in the demo, basically, though things can be worse.
When I try to use the original easyrtc demo glitch out there, here, it gives me very weird results and frequent glitches where only some players can see others players some of the time.
I can't seem to find any permutation of NAF that ever worked consistently with webrtc audio, and am starting to suspect it has always been broken. I'm not sure where to look, but I'm starting to think the adapter isn't the right place, it's NAF itself. Makes it tempting to just use NAF for networked objects and orientation, and just try to do webrtc audio/video from scratch using peer.js for example.

I've gone ahead and made a fork with my version here: https://github.com/kylebakerio/naf-easyrtc-adapter/blob/master/README.md

@kylebakerio Thank you I merged your PR into open-easyrtc branch of open-easyrtc naf-easyrtc-adapter fork.
Your changes are now included in this PR.

Please @haydenjameslee make me and @kylebakerio maintainers on this repository so we can help your project continue to be secure and works with easyrtc.

The easyrtc adapter moved again to the networked-aframe repository. I'm closing all issues in this repository.


Add Anchore go dependency security scanning

What would you like to be added:
Scanning for known vulnerabilities in the container images we publish, and a feedback loop from that scanning to highlight the problem and encourage a fix. Some scanning already happens on Quay, but we don't do anything with that information.
For example: https://github.com/marketplace/actions/anchore-container-scan.
As a different type of scanning, we may also want to look into: https://github.com/octarinesec/kube-scan
Why is this needed:
More security more better.

Here’s a test of the Anchore container scan: https://github.com/submariner-io/submariner/pull/797
Uploading the SCARIF results involves participating in the security scanning beta, I’m in the queue for my fork of Submariner.

Additional thoughts: our containers are designed to be as up-to-date as possible based on their base image, except for non-packaged dependencies. The only image which could have undiagnosed, actionable security problems is our base Dapper image; our production images are all based on software which is already tracked by the security teams of the distributions we use.
So ultimately, as long as we regularly rebuild our container images, it’s all about our Go dependencies, and dependencybot is already supposed to track that.
If we ever start supporting multiple streams, with long-term releases, this will become harder to deal with, but until we’re there, we’re in pretty good shape.

Collecting a few more maybe-useful tool options:
https://github.blog/2020-09-30-code-scanning-is-now-available/
https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository
https://lgtm.com/

This is still relevant.

bump

bump

The CNCF has some partnerships we might be able to leverage here.

@Jaanki mentioned there's a tool Polaris that might be useful here. Something like: https://github.com/devsecops-test/polaris-action

Looking at this more, it seems like this would have caught the current Lighthouse text lib CVE before downstream scanning caught it, which would be much lower cost to fix than waiting for it to be in a release downstream.
Also discussed on the scrub, re-opening and will handle as a part of that fix.

This also looks interesting, but we'd need a Snyk account.
https://marketplace.visualstudio.com/items?itemName=redhat.fabric8-analytics

I did this for Lighthouse with:

https://github.com/submariner-io/lighthouse/pull/798
https://github.com/submariner-io/lighthouse/pull/819
https://github.com/submariner-io/lighthouse/pull/820

It would be interesting to check if CodeQL identifies anything not found by other tools.
https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql
https://codeql.github.com/

For the main repo:

https://github.com/submariner-io/submariner/pull/1961
https://github.com/submariner-io/submariner/pull/1968

And the rest of them:

https://github.com/submariner-io/submariner-operator/pull/2181
https://github.com/submariner-io/subctl/pull/217
https://github.com/submariner-io/admiral/pull/400
https://github.com/submariner-io/cloud-prepare/pull/357
https://github.com/submariner-io/coastguard/pull/73
https://github.com/submariner-io/shipyard/pull/920

It would be interesting to check if CodeQL identifies anything not found by other tools.
https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql https://codeql.github.com/

Evaluating CodeQL vuln variant analysis here:
https://github.com/dfarrell07/lighthouse/pull/6
The Go security rules are here (I don't see better docs):
https://github.com/github/codeql/tree/main/go/ql/src/Security

I used LGTM.com to run CodeQL against all the submariner-io repos. The test I did in Lighthouse was just unlucky to not see any new issues, there are other (minor from what I see so far) issues in other repos.

This is done. :heavy_check_mark:


feat: Add Fig completions to Mise

Requires a manual accept of fig's CLA by the mise-en-place account (see here)
Re-used the release-plz workflow, let me know if that secret shouldn't be used for this.

Will reopen with correct base commit


bump node-fetch version

and expose FetchError

I started on new fetch which uses node-fetch 2.x https://github.com/codler/fetch-register

Can this be merged? V2 is more spec compliant as it will not convert text with iconv by default.

This has been resolved in master … sorry for the huge delay. I will release as a major version soon, please test against your applications.


Unified inbox not updated anymore

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.000
Where did you get the app from?
Google Play
Android version
12
Device model
Samsung S10e
Steps to reproduce
None.
Just open K9 when a new mail notification appears
Expected behavior
All account inboxes as well as the Unified Inbox should be properly updated with new incoming mails
Actual behavior
Until a few days ago everything worked fine.
New mails are still correctly shown in the account inboxes.
However the Unified inbox view remains unchanged and is NOT updated anymore!
Logs
k9mail-logs.txt

It doesn't look like you've enabled debug logging in K-9 Mail. Please see https://github.com/k9mail/k-9/wiki/LoggingErrors

k9mail-logs.txt


chore: clean up bib documentation

Metanorma PR checklist

[ ] Breaking changes (list related PRs)
[ ] Documentation update required (create task for this)
[ ] External dependency introduced (documentation update need)
[ ] Gem with native library introduced

Thank you @reeseplews for reporting!


[Contributions welcomed] Create a glossary for Unit 3

temporal information - how things change through time

Hey there 👋 , can you open a PR to put the definitions so that then we will be able to merge and people can iterate on it 🤗
Thanks

A glossary has been created in #168 I'm closing this issue then. Thanks 🤗


macOS DNS not resolving own hostname

Describe the bug
Same as https://github.com/actions/virtual-environments/issues/1042.
In https://github.com/PowerShell/PowerShell/pull/13324 we're seeing a test failure in PowerShell code that looks like this:
$hostName = [System.Net.Dns]::GetHostName()
[System.Net.Dns]::GetHostEntry($hostName)

Last time we were able to work around this by using the gateway address for our Test-Connection tests, but those started failing (see https://github.com/PowerShell/PowerShell/issues/13309, I'll try to get a repro in the same PR). Migrating back to our DNS lookup, I hit this issue.
Area for Triage:
Apple
Question, Bug, or Feature?:
Bug
Virtual environments affected

[x] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Ubuntu 20.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
The [System.Net.Dns]::GetHostEntry() call should resolve a DNS entry based on the hostname.
Actual behavior
  Describing Test-Connection
    [-] Error occurred in Describe block 0ms
      ExtendedSocketException: nodename nor servname provided, or not known
      MethodInvocationException: Exception calling "GetHostEntry" with "1" argument(s): "nodename nor servname provided, or not known"
      at <ScriptBlock>, /Users/runner/work/1/s/test/powershell/Modules/Microsoft.PowerShell.Management/Test-Connection.Tests.ps1: line 49
      at Invoke-Blocks, /Users/runner/work/1/a/bins/publish/Modules/Pester/4.10.1/Functions/SetupTeardown.ps1: line 135
      at Invoke-TestGroupSetupBlocks, /Users/runner/work/1/a/bins/publish/Modules/Pester/4.10.1/Functions/SetupTeardown.ps1: line 121
      at DescribeImpl, /Users/runner/work/1/a/bins/publish/Modules/Pester/4.10.1/Functions/Describe.ps1: line 209

As seen here.

Hello, @rjmholt
Sorry for the trouble. We are planning to fix the issue in the next image roll-out.
jobs:
  build:
    runs-on: macos-latest

    steps:
    - name: change name
      run: |
        name="mac-$(python -c 'from time import time; print int(round(time() * 1000))')"
        sudo scutil --set HostName "${name}.local"
        sudo scutil --set LocalHostName $name
        sudo scutil --set ComputerName "${name}.local"
    - name: resolve
      shell: pwsh
      run: |
        $hostName = [System.Net.Dns]::GetHostName()
        [System.Net.Dns]::GetHostEntry($hostName)

Hello, @rjmholt
The fix has been deployed. The [System.Net.Dns]::GetHostEntry()  is working now.

Hi i update the mac to Big Sur and try the same code
var hostName = Dns.GetHostName();
var ipHostEntry = Dns.GetHostEntry(hostName);
and it fails but works if i add ".local"
var hostName = Dns.GetHostName();
var ipHostEntry = Dns.GetHostEntry(hostName + ".local");
has any solution in order to avoid ".local"???

I still see this problem on macos-13:
+ hostname
Mac-1720605937776.local
...
+ ping -c 4 Mac-1720605937776.local
ping: cannot resolve Mac-1720605937776.local: Unknown host


[nn/parallel/data_parallel.py]: Rename "_pre_bacward" method of ZeroDDP to "_pre_backward"

📌 Checklist before creating the PR

[ ] I have created an issue for this PR for traceability
[x] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[ ] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
e.g. fixed #1234, closed #1234, resolved #1234

📝 What does this PR do?
Rename "_pre_bacward" method of ZeroDDP to "_pre_backward".
💥 Checklist before requesting a review

[ ] I have linked my PR to an issue (instruction)
[ ] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[ ] I have performed a self-review of my code
[ ] I have added thorough tests.
[ ] I have added docstrings for all the functions/methods I implemented

⭐ Do you enjoy contributing to Colossal-AI?

[x]  🌝 Yes, I do.
[ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.

LGTM. Will merge when checks are passed.

Hi, seems some Github updates broke our CI checks. I have fixed the CI and can you rebase your code with the latest code so that the correct CI can be triggered?


generator: Convert #define generation from vkxml to vk-parse

For upcoming vk.xml features (the new api attribute) some of our codegen has to be converted to work on vk-parse types to make this ergonomic (and there's a longstanding plan of factoring out vkxml regardless).  Start with converting the #define code and showcasing that it does not affect the output (beyond removing the unneeded edgecase for VK_HEADER_VERSION resulting in a doc link).

Start with converting the #define code and showcasing that it does not affect the output (beyond removing the unneeded edgecase for VK_HEADER_VERSION resulting in a doc link).

Unfortunately this is not entirely true anymore. The other big requirement for conversion is structs, and vkmxl (the conversion in vk-parse, really) provides all the necessary boilerplate that I do not feel like whipping up in Ash just now, with a rewrite in mind.


mathversion and bold symbols

Description
Now ExtraBold, Heavy, Ultra in Fira Math do not have bold symbols (U+1D400 etc).
If using several weights containing the above ones, for example, Thin+Ultra, then when set \mathversion for them, the bold symbols of the normal weights (Thin in the example) will disappear.
Check/indicate

[x] Relevant for XeTeX
[x] Relevant for LuaTeX
[ ] Issue tracker has been searched for similar issues?
[ ] Links to <tex.stackexchange.com> discussion if appropriate

Minimal example demonstrating the issue
\documentclass{article}
\usepackage{amsmath,unicode-math}
\setmathfont{FiraMath-Thin.otf}[version=Thin]
\setmathfont{FiraMath-Regular.otf}[version=Regular]
% \setmathfont{FiraMath-Ultra.otf}[version=Ultra]

\begin{document}
\mathversion{Thin}    $ ABC abc \symbf{abc} $ \par
\mathversion{Regular} $ ABC abc \symbf{abc} $ \par
% \mathversion{Ultra}   $ ABC abc \symbf{abc} $ \par
\end{document}

If uncomment the Ultra lines, then the bold symbols of Thin and Regular disappear:

Further details
The only other math font that contains multiple weights is (as far as I know) is XITS Math Bold. But it uses the same glyphs as normal weights for the bold weights (U+1D400 is the same as U+0041). So should I create the mapping in Fira Math Ultra etc as in XITS Math Bold?

Interesting (albeit problematic!). Thanks for the nice test case.
The math version implementation has always had its problems; I think the \symXX commands need a lot more work to hook in correctly with the math versions.
Unfortunately I can’t promise a timely fix at the moment, it’s a busy time of year...


Domain iType Tidbit create date

Domain iType tidbit for creation date should also look for key name createdDate in direct Whois results to display if creationDate is not present in results.

fixed in #2228


Suggestion: Modified Fighter Types

Subtype Archer: I think the same Proficiencies like the Spear Fighter would fit. Maybe + Precision Shot
Subtype Aldori-Defender: Own Proficienses by removing out of Fighter Tower Shield, Medium and Heavy Armor, adding Duellsword and Dodge

No sorry, I am following the tabletop rules as close as possible when adding tabletop features.
If you want extra feats for free, you can add them using toybox.


Iterating through QueryRef

I have the following:
public posts: QueryRef<PostsInterface>;
this.posts = this._postService.get(); //in ngOnInit
And in the corresponding HTML:
<mat-card *ngFor="let post of posts | async">
And then am able to display each post's fields in html using {{post.name}}, etc.
My question is, how can I achieve the same iteration through the posts QueryRef inside typescript? When I try the following:
for (let post of this.posts) {
      console.log("Post name is: " + post.name);
    }

I get the error "Type 'QueryRef<PostsInterface, Record<string, any>>' is not an array type or a string type."
If ngFor is able to iterate through the QueryRef, there must be some way to do it in the typescript itself?
Ultimately I want to display the data in a table with a paginator. Having trouble achieving this with mat-table. Are there any examples of displaying data grabbed with apollographql in a mat-table?

QueryRef is not an Observable or even an iterable object so it cannot by used with AsyncPipe.
What you're looking for is valueChanges prop of QueryRef.

If QueryRef is not Observable or Iterable, how is ngFor able to iterate through it with no issues?

Impossibru. QuerRef is just an object, it's impossible to iterate an object so it means you're doing something wrong or you're returning an Observable in a service but you're defining it as QueryRef in a component. No other options.

Thanks, I realize now the problem is I incorrectly migrated to Apollo 2.0


add option for fixed vs. full-width rendering

I don't know if the markdown renderer you're using supports this, but it would be nice to be able to allow the preview to fill the tab rather than being stuck inside that fixed-width box.
Thanks for developing this alongside the Markdown plugin (and offering an option to replace its preview tab)!

:+1: Works perfectly! Thanks for tackling this one so quickly.


chore: Cleanup MS Links

Remove locales
Use HTTPS

Docs Build status updates of commit 20a30d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

README.md
:white_check_mark:Succeeded

ThirdPartyNotices.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thanks @nschonni! :)


Why is this app trying to access youtube, maps and videos apps ?

Every hour, I noticed these warnings in logcat:
2024-06-02 12:58:15.155  1823-2396  AppsFilter              pid-1823                             I  interaction: PackageSetting{ab6cbdf varzan.extraKeyboardLayouts/10436} -> PackageSetting{8ffafde com.google.android.youtube/10260} BLOCKED
2024-06-02 12:58:15.156  1823-2396  AppsFilter              pid-1823                             I  interaction: PackageSetting{ab6cbdf varzan.extraKeyboardLayouts/10436} -> PackageSetting{1704938 com.google.android.apps.maps/10262} BLOCKED
2024-06-02 12:58:15.156  1823-2396  AppsFilter              pid-1823                             I  interaction: PackageSetting{ab6cbdf varzan.extraKeyboardLayouts/10436} -> PackageSetting{27b5bf com.google.android.videos/10295} BLOCKED
This happened with my fork but this fork does not modify any code, so there is something odd or even fishy.

This is really a three-file project.
Compare the manifest
https://github.com/calin-darie/extra-keyboard-layouts/blob/master/app/src/main/AndroidManifest.xml
Against the Android docs
https://developer.android.com/reference/android/hardware/input/InputManager#META_DATA_KEYBOARD_LAYOUTS
I don't have time to investigate for a better explanation of the messages. I honestly think the messages are misleading. But if you do find a way to supress them, please reopen.


Add Solr 8.x, update to 7.7.3, deprecate 5.x and 6.x

Solr 8.x
I was wondering if we could also support Solr 8.x. The current stable version is 8.6.3.
https://www.drupal.org/project/search_api_solr supports 8.x with the 4.x version of the Drupal module too.
Looks like there are openjdk images on Alpine now https://github.com/docker-library/openjdk/blob/master/16/jdk/alpine3.12/Dockerfile
Solr 7.7.x
We are running 7.7.1 to which has security issues associated with it, we should default to 7.7.3. (to which is still in support).
Solr < 7.7
All older versions (<7.7) are End Of Life (EOL), and we should indicate this just like we do for PHP and drop support for them.
Task List

[x] Deprecate Solr 5.5 & 6.6 #281
[x] Add Solr 7.7.3 image #128 - uselagoon/solr-7 and uselagoon/solr-7-drupal
[ ] Add Solr 8 image

So, this is pretty involved (some backstory at https://github.com/amazeeio/lagoon/issues/1324#issuecomment-601902121).

The last upstream alpine-based image (docker/Solr) published was 7.7.1
The upstream of the upstream (OpenJDK), stopped supporting alpine in v8
The upstream (docker/Solr) has outlined a preference for using JRE (instead of JDK) to reduce size.

We're pretty much going to have to either:

roll our own alpine-based Solr images :scream:
change the base to Debian-slim for Solr (which means also remaking the commons image for Debian)

Either way, this is a largish piece of work, and not without possible complications...

work underway in https://github.com/uselagoon/lagoon-images/pull/97
One thing to note is that Lagoon prebackuppods are hardcoded to use busybox tar - which won't work on debian-slim based images.

Solr 7.7 does not get all the security updates that Solr 8 does. Somehow resolving this issue has to become a priority because we get more and more security reports about using "outdated" Solr version.

Solr 8 plan:

Introduce new script lagoon-recreate-solr or similar to wrap around https://github.com/docker-solr/docker-solr/blob/master/8.10/scripts/solr-precreate
This can then be called as the CMD in the solr and solr-drupal dockerfiles

Solr 8 images were added in 22.2.0, all tasks complete.


TeeBuildListener incompatible with OutputStreamTaskListener

Jenkins and plugins versions report

Environment

Jenkins: 2.414.3
OS: Linux - 6.2.0-36-generic
Java: <IP_ADDRESS> - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
---
Office-365-Connector:4.20.0
SquishPlugin:8.6
active-directory:2.34
analysis-model-api:11.11.0
ant:497.v94e7d9fffa_b_9
antisamy-markup-formatter:162.v0e6ec0fcfcf6
apache-httpcomponents-client-4-api:4.5.14-208.v438351942757
authentication-tokens:1.53.v1c90fd9191a_b_
blueocean:1.27.8
blueocean-bitbucket-pipeline:1.27.8
blueocean-commons:1.27.8
blueocean-config:1.27.8
blueocean-core-js:1.27.8
blueocean-dashboard:1.27.8
blueocean-display-url:2.4.2
blueocean-events:1.27.8
blueocean-git-pipeline:1.27.8
blueocean-github-pipeline:1.27.8
blueocean-i18n:1.27.8
blueocean-jwt:1.27.8
blueocean-personalization:1.27.8
blueocean-pipeline-api-impl:1.27.8
blueocean-pipeline-editor:1.27.8
blueocean-pipeline-scm-api:1.27.8
blueocean-rest:1.27.8
blueocean-rest-impl:1.27.8
blueocean-web:1.27.8
bootstrap5-api:5.3.2-2
bouncycastle-api:2.29
branch-api:2.1128.v717130d4f816
build-blocker-plugin:1.7.9
build-monitor-plugin:1.14-745.ve2023a_305f40
build-timeout:1.31
build-timestamp:1.0.3
caffeine-api:3.1.8-133.v17b_1ff2e0599
checks-api:2.0.2
clone-workspace-scm:84.v147686859e1c
cloudbees-bitbucket-branch-source:848.v42c6a_317eda_e
cloudbees-disk-usage-simple:187.v6378d330d1d4
cloudbees-folder:6.858.v898218f3609d
cobertura:1.17
code-coverage-api:4.99.0
command-launcher:100.v2f6722292ee8
commons-httpclient3-api:3.1-3
commons-lang3-api:3.13.0-62.v7d18e55f51e2
commons-text-api:1.10.0-78.v3e7b_ea_d5a_fe1
configuration-as-code:1714.v09593e830cfa
coverage:1.2.0
credentials:1307.v3757c78f17c3
credentials-binding:642.v737c34dea_6c2
dashboard-view:2.495.v07e81500c3f2
data-tables-api:1.13.6-5
description-setter:1.10
display-url-api:2.200.vb_9327d658781
docker-commons:439.va_3cb_0a_6a_fb_29
docker-workflow:572.v950f58993843
downstream-ext:73.vdda_16e6eb_0da
dtkit-api:3.0.2
durable-task:523.va_a_22cf15d5e0
echarts-api:5.4.0-7
email-ext:2.102
favorite:2.4.3
file-parameters:316.va_83a_1221db_a_7
font-awesome-api:6.4.2-1
forensics-api:2.3.0
git:5.2.0
git-client:4.5.0
github:<IP_ADDRESS>
github-api:1.316-451.v15738eef3414
github-branch-source:1741.va_3028eb_9fd21
handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953
htmlpublisher:1.32
http_request:1.18
instance-identity:173.va_37c494ec4e5
ionicons-api:56.v1b_1c8c49374e
jackson2-api:2.15.3-366.vfe8d1fa_f8c87
jakarta-activation-api:2.0.1-3
jakarta-mail-api:2.0.1-3
javax-activation-api:1.2.0-6
javax-mail-api:1.6.2-9
jaxb:2.3.9-1
jdk-tool:66.vd8fa_64ee91b_d
jenkins-design-language:1.27.8
jjwt-api:0.11.5-77.v646c772fddb_0
jobConfigHistory:1229.v3039470161a_d
jquery3-api:3.7.1-1
junit:1240.vf9529b_881428
ldap:711.vb_d1a_491714dc
lockable-resources:1185.v0c528656ce04
mailer:463.vedf8358e006b_
mapdb-api:1.0.9-28.vf251ce40855d
matrix-auth:3.2.1
matrix-project:818.v7eb_e657db_924
metrics:4.2.18-442.v02e107157925
mina-sshd-api-common:2.11.0-86.v836f585d47fa_
mina-sshd-api-core:2.11.0-86.v836f585d47fa_
monitoring:1.95.0
nodelabelparameter:1.12.0
okhttp-api:4.11.0-157.v6852a_a_fa_ec11
opentelemetry:2.18.0
pam-auth:1.10
parameterized-scheduler:255.v73827fcdf618
pipeline-build-step:516.v8ee60a_81c5b_9
pipeline-github-lib:42.v0739460cda_c4
pipeline-graph-analysis:202.va_d268e64deb_3
pipeline-groovy-lib:689.veec561a_dee13
pipeline-input-step:477.v339683a_8d55e
pipeline-milestone-step:111.v449306f708b_7
pipeline-model-api:2.2150.v4cfd8916915c
pipeline-model-definition:2.2150.v4cfd8916915c
pipeline-model-extensions:2.2150.v4cfd8916915c
pipeline-rest-api:2.33
pipeline-stage-step:305.ve96d0205c1c6
pipeline-stage-tags-metadata:2.2150.v4cfd8916915c
pipeline-stage-view:2.33
pipeline-utility-steps:2.16.0
plain-credentials:143.v1b_df8b_d3b_e48
plugin-util-api:3.6.0
prism-api:1.29.0-8
prometheus:2.3.3
pubsub-light:1.18
scm-api:676.v886669a_199a_a_
script-security:1275.v23895f409fb_d
snakeyaml-api:2.2-111.vc6598e30cc65
sse-gateway:1.26
ssh-agent:333.v878b_53c89511
ssh-credentials:308.ve4497b_ccd8f4
ssh-slaves:2.916.vd17b_43357ce4
sshd:3.303.vefc7119b_ec23
startup-trigger-plugin:2.9.4
stash-pullrequest-builder:1.17
stashNotifier:1.439.v202358346a_7d
structs:325.vcb_307d2a_2782
subversion:2.17.3
support-core:1362.vf5fe14238165
timestamper:1.26
token-macro:384.vf35b_f26814ec
translation:1.16
trilead-api:2.84.v72119de229b_7
update-sites-manager:2.0.0
variant:60.v7290fc0eb_b_cd
warnings-ng:10.5.1
windows-slaves:1.8.1
workflow-aggregator:596.v8c21c963d92d
workflow-api:1283.v99c10937efcb_
workflow-basic-steps:1042.ve7b_140c4a_e0c
workflow-cps:3806.va_3a_6988277b_2
workflow-durable-task-step:1289.v4d3e7b_01546b_
workflow-job:1360.vc6700e3136f5
workflow-multibranch:756.v891d88f2cd46
workflow-scm-step:415.v434365564324
workflow-step-api:639.v6eca_cd8c04a_a_
workflow-support:865.v43e78cc44e0d
xunit:3.1.3
xvnc:1.28

Configuration of otel Plugin
otel.exporter.otlp.protocol=grpc
otel.instrumentation.jenkins.web.enabled=false
otel.logs.exporter=otlp
otel.logs.mirror_to_disk=true
otel.metrics.exporter=none

What Operating System are you using (both controller, and any agents involved in the problem)?
Docker with Linux - 6.2.0-36-generic
Reproduction steps

Configure Logging in OTel
Run Job
See System logs on Warn level

Expected Results
No Warning should be emitted
Actual Results
System Log contains:
[...] WARNING org.jenkinsci.plugins.workflow.log.OutputStreamTaskListener getOutputStream
Unexpected PrintStream subclass io.jenkins.plugins.opentelemetry.job.log.util.TeePrintStream which might override write(…); error handling is degraded unless OutputStreamTaskListener is used: io.jenkins.plugins.opentelemetry.job.log.util.TeeBuildListener

Anything else?
No response

We are aware of this warning message. Unfortunately, it's not easy to tacklee it at the moment as we are still compatible with older versions of Jenkins Core that didn't have this warning message so we didn't explore the problem.

We don't face critical problems. Due to the high amount of messages and the way the OTel Plugin (as far as I know it ships logs of default logger) and the Jenkins logging works (default logger cannot be configured to set the level of the OutputStreamTaskListener logger to ERROR), we had to deactivate WARN messages for Jenkins completely to save bandwidth and disk space. Of course, this is a workaround that we don't want to keep.
If there is anything I can do to solve the problem in the plugin or to create a temporary workaround, I would gladly assist.

Warning message was

added in https://github.com/jenkinsci/workflow-api-plugin/commit/c57af92ba2781a2f25cae6673070bc0428ce2b7a#diff-1578c5b4297e08aa9ad0adedd3e8d23769daa4de82f2b0520803d9f0bfc5deda
released on July 28th 2023 in https://github.com/jenkinsci/workflow-api-plugin/releases/tag/1248.v4b_91043341d2

Then warning was supposed to be removed in  July 30th 2023 in https://github.com/jenkinsci/workflow-api-plugin/releases/tag/1251.vd4889a_b_0a_065

@kuisathaverat I propose we bump our dependency on Jenkins Core from 2.387.x to the following LTS, 2.401.x to be able to work on this problem of TeeBuildListener vs OutputStreamTaskListener

Sure, 2.401.x is fine. I have to fix a couple of bugs first and enable the logs test again.

FYI I'll open a PR, the fix is almost implemented.

thanks :)


Adding release notes for Version 0.17 SDK

Adding release notes for Version 0.17 SDK

Hi @AlexBulankou, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


⚠ Thumbnails API Endpoint has degraded performance

In 1199f0a, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1207 ms

Resolved: Thumbnails API Endpoint performance has improved in 35db046 after 12 minutes.


aggregations: fix missing index

When you do an optimized query against a non-existent index,
the Elastic response doesn't have an aggregations key, so we
crash when we call .hasOwnProperty on response.aggregations. We
already calculate the empty_result thing we're supposed to return
in this case, so let's actually use it.
Fixes https://github.com/juttle/juttle-elastic-adapter/issues/120
@demmer @VladVega

Looks good... seems like the travis failures are perhaps unrelated?

The logic was in fact wildly wrong, please have a look at the new approach.

Hmm. I'm not actually seeing the problem with the earlier one but tests don't like and I believe you. So this looks good.


Refactor "cache-hooks" implementation

Summary
As the forthcoming notifications will be dispatched according to hook events, there should ideally be a distinction between cache- and notification-related hook logic, e.g. the notification logic not be implemented within the "cache-hooks".
This refactors the route "cache-hooks" to be a more generic, "hooks" implementation with a generic HooksService that can be extended (and is for hooks) for later hook event based-logic. It also adds distinction between Transaction Service and Config. Service events.
Changes

Create HooksService and extend it for cache-clearing logic
Rename cache-hooks to hook and the associated controller, service(s) and module accordingly
Separate EventType into TransactionEventType and ConfigEventType and propagate changes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

65 of 68 (95.59%)  changed or added relevant lines in 22 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 48.461%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/hooks/hooks.service.ts
11
12
91.67%

src/routes/hooks/hooks.controller.ts
7
9
77.78%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
4318

Relevant Lines:
7182

💛  - Coveralls