K8SPXC-630 add mysql 5.7 for tests

Test name
Status

haproxy-8-0
failed

upgrade-haproxy-8-0
failed

cross-site-8-0
failed

recreate-8-0
failed

big-data-8-0
failed

scheduled-backup-8-0
failed

storage-8-0
failed

scaling-8-0
failed

users-5-7
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
passed

restore-to-encrypted-cluster-8-0
passed

security-context-8-0
passed

one-pod-5-7
failed

upgrade-proxysql-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
passed

init-deploy-8-0
failed

scheduled-backup-5-7
passed

demand-backup-8-0
passed

smart-update-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
passed

limits-8-0
passed

pitr-8-0
failed

demand-backup-encrypted-with-tls-8-0
failed

monitoring-2-0-8-0
failed

init-deploy-5-7
passed

haproxy-5-7
passed

affinity-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 40 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/5e9cedb94d6d67bc8c1fb375024d78c0c7d02cb1
image: perconalab/percona-xtradb-cluster-operator:PR-1194-5e9cedb9

Test name
Status

scheduled-backup-8-0
failed

recreate-8-0
failed

scaling-8-0
failed

haproxy-8-0
failed

storage-8-0
failed

upgrade-haproxy-8-0
failed

big-data-8-0
failed

users-5-7
passed

cross-site-8-0
failed

one-pod-5-7
passed

scaling-proxysql-8-0
passed

security-context-8-0
passed

scheduled-backup-5-7
passed

init-deploy-5-7
passed

haproxy-5-7
passed

self-healing-8-0
passed

self-healing-chaos-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
passed

restore-to-encrypted-cluster-8-0
passed

demand-backup-8-0
passed

pitr-8-0
passed

upgrade-proxysql-8-0
passed

demand-backup-encrypted-with-tls-8-0
failed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failed

affinity-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/5e9cedb94d6d67bc8c1fb375024d78c0c7d02cb1
image: perconalab/percona-xtradb-cluster-operator:PR-1194-5e9cedb9

Test name
Status

big-data-8-0
failed

scheduled-backup-8-0
failed

haproxy-8-0
failed

cross-site-8-0
failed

scaling-8-0
failed

upgrade-haproxy-8-0
failed

recreate-8-0
failed

storage-8-0
failed

users-5-7
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
passed

restore-to-encrypted-cluster-8-0
passed

init-deploy-8-0
passed

security-context-8-0
failed

upgrade-proxysql-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
passed

demand-backup-8-0
passed

smart-update-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
passed

one-pod-5-7
passed

limits-8-0
passed

pitr-8-0
passed

scheduled-backup-5-7
passed

upgrade-consistency-8-0
failed

monitoring-2-0-8-0
failed

demand-backup-encrypted-with-tls-8-0
failed

affinity-8-0
failed

init-deploy-5-7
passed

one-pod-8-0
passed

haproxy-5-7
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/bd93a495eb902c823f42d535a832530ee70d21c6
image: perconalab/percona-xtradb-cluster-operator:PR-1194-bd93a495

Test name
Status

upgrade-haproxy-8-0
passed

cross-site-8-0
passed

scaling-8-0
passed

storage-8-0
passed

users-5-7
passed

scheduled-backup-8-0
failed

big-data-8-0
passed

haproxy-8-0
failed

recreate-8-0
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
passed

restore-to-encrypted-cluster-8-0
passed

one-pod-5-7
passed

init-deploy-8-0
passed

8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
passed

security-context-8-0
passed

scheduled-backup-5-7
failed

demand-backup-8-0
passed

upgrade-proxysql-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
passed

pitr-8-0
failed

limits-8-0
failed

upgrade-consistency-8-0
passed

init-deploy-5-7
passed

demand-backup-encrypted-with-tls-8-0
passed

monitoring-2-0-8-0
failed

affinity-8-0
passed

haproxy-5-7
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/00988bcbcc46f22c21becda3f4c7cfd0b6112aa4
image: perconalab/percona-xtradb-cluster-operator:PR-1194-00988bcb

Test name
Status

users-5-7
passed

big-data-8-0
passed

cross-site-8-0
passed

scheduled-backup-8-0
failed

haproxy-8-0
failed

recreate-8-0
passed

scaling-8-0
passed

upgrade-haproxy-8-0
passed

storage-8-0
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
failed

restore-to-encrypted-cluster-8-0
passed

security-context-8-0
passed

init-deploy-8-0
passed

demand-backup-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

limits-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

monitoring-2-0-8-0
failed

one-pod-5-7
passed

pitr-8-0
failed

affinity-8-0
passed

scheduled-backup-5-7
failed

one-pod-8-0
failed

We run 27 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/8c2501d207a9c7b5b30cd51f5ec56e982c17ab42
image: perconalab/percona-xtradb-cluster-operator:PR-1194-8c2501d2

Test name
Status

big-data-8-0
passed

haproxy-8-0
failed

scaling-8-0
passed

recreate-8-0
passed

scheduled-backup-8-0
failed

users-5-7
passed

storage-8-0
passed

upgrade-haproxy-8-0
passed

cross-site-8-0
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
failed

restore-to-encrypted-cluster-8-0
passed

security-context-8-0
passed

upgrade-proxysql-8-0
passed

init-deploy-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

demand-backup-8-0
passed

limits-8-0
passed

smart-update-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

monitoring-2-0-8-0
failed

one-pod-5-7
passed

scheduled-backup-5-7
failed

pitr-8-0
failed

affinity-8-0
passed

upgrade-consistency-8-0
passed

one-pod-8-0
failed

demand-backup-encrypted-with-tls-8-0
passed

init-deploy-5-7
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

haproxy-5-7
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/88edc1750d9a660ecab2e98300d05f3fece6ca3e
image: perconalab/percona-xtradb-cluster-operator:PR-1194-88edc175

Test name
Status

scheduled-backup-8-0
failed

storage-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
failed

haproxy-8-0
passed

scaling-8-0
passed

cross-site-8-0
passed

recreate-8-0
passed

big-data-8-0
passed

users-5-7
passed

upgrade-haproxy-8-0
passed

scaling-proxysql-8-0
passed

restore-to-encrypted-cluster-8-0
passed

one-pod-5-7
passed

security-context-8-0
passed

demand-backup-8-0
passed

scheduled-backup-5-7
passed

pitr-8-0
failed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

affinity-8-0
passed

one-pod-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

operator-self-healing-8-0
passed

tls-issue-cert-manager-8-0
passed

operator-self-healing-chaos-8-0
failed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

init-deploy-5-7
passed

haproxy-5-7
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/88edc1750d9a660ecab2e98300d05f3fece6ca3e
image: perconalab/percona-xtradb-cluster-operator:PR-1194-88edc175

Test name
Status

haproxy-8-0
failed

scheduled-backup-8-0
failed

big-data-8-0
passed

storage-8-0
passed

cross-site-8-0
passed

users-5-7
passed

scaling-8-0
passed

upgrade-haproxy-8-0
passed

recreate-8-0
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
failed

restore-to-encrypted-cluster-8-0
passed

security-context-8-0
passed

one-pod-5-7
passed

upgrade-proxysql-8-0
passed

init-deploy-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

scheduled-backup-5-7
passed

demand-backup-8-0
passed

limits-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

smart-update-8-0
failed

monitoring-2-0-8-0
passed

init-deploy-5-7
passed

affinity-8-0
passed

pitr-8-0
failed

one-pod-8-0
passed

auto-tuning-8-0
failed

haproxy-5-7
failed

demand-backup-encrypted-with-tls-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

upgrade-consistency-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
failed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/802a44813ba118810335a224e23ee4336cfa30cf
image: perconalab/percona-xtradb-cluster-operator:PR-1194-802a4481

Test name
Status

upgrade-haproxy-8-0
passed

cross-site-8-0
passed

storage-8-0
passed

recreate-8-0
passed

self-healing-8-0
passed

restore-to-encrypted-cluster-8-0
passed

big-data-8-0
passed

scaling-8-0
passed

haproxy-8-0
passed

self-healing-chaos-8-0
failed

demand-backup-8-0
passed

scaling-proxysql-8-0
passed

pitr-8-0
failed

security-context-8-0
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

affinity-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

demand-backup-encrypted-with-tls-8-0
passed

upgrade-consistency-8-0
passed

We run 35 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/802a44813ba118810335a224e23ee4336cfa30cf
image: perconalab/percona-xtradb-cluster-operator:PR-1194-802a4481

Test name
Status

upgrade-haproxy-8-0
passed

cross-site-8-0
passed

storage-8-0
passed

self-healing-8-0
passed

scaling-8-0
passed

haproxy-8-0
passed

recreate-8-0
passed

scheduled-backup-8-0
failed

users-5-7
passed

big-data-8-0
passed

self-healing-chaos-8-0
failed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

init-deploy-8-0
passed

one-pod-5-7
passed

demand-backup-8-0
passed

limits-8-0
passed

security-context-8-0
passed

scheduled-backup-5-7
passed

monitoring-2-0-8-0
passed

pitr-8-0
failed

init-deploy-5-7
passed

affinity-8-0
passed

haproxy-5-7
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

demand-backup-encrypted-with-tls-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/802a44813ba118810335a224e23ee4336cfa30cf
image: perconalab/percona-xtradb-cluster-operator:PR-1194-802a4481

Test name
Status

scaling-8-0
passed

scaling-proxysql-8-0
passed

security-context-8-0
passed

We run 3 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/8e3cba161f6939a3d71a8c94aa9d3a233f590c37
image: perconalab/percona-xtradb-cluster-operator:PR-1194-8e3cba16

Test name
Status

upgrade-haproxy-8-0
failed

scaling-8-0
passed

haproxy-8-0
failed

users-5-7
failed

storage-8-0
passed

scheduled-backup-8-0
failed

big-data-8-0
passed

cross-site-8-0
failed

recreate-8-0
passed

scaling-proxysql-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
passed

restore-to-encrypted-cluster-8-0
passed

security-context-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
passed

demand-backup-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
passed

pitr-8-0
failed

init-deploy-8-0
passed

one-pod-5-7
passed

demand-backup-encrypted-with-tls-8-0
passed

scheduled-backup-5-7
passed

limits-8-0
passed

monitoring-2-0-8-0
failed

init-deploy-5-7
passed

affinity-8-0
passed

haproxy-5-7
failed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
failed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
failed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
failed

We run 38 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/f6da5e4ab66395ac378839510a19dfc7b9abd49e
image: perconalab/percona-xtradb-cluster-operator:PR-1194-f6da5e4a

Test name
Status

haproxy-8-0
passed

cross-site-8-0
passed

scheduled-backup-8-0
passed

storage-8-0
passed

users-5-7
passed

recreate-8-0
passed

self-healing-8-0
passed

upgrade-haproxy-8-0
passed

big-data-8-0
passed

restore-to-encrypted-cluster-8-0
passed

self-healing-chaos-8-0
passed

demand-backup-8-0
passed

self-healing-advanced-8-0
passed

scaling-8-0
passed

pitr-8-0
failed

self-healing-advanced-chaos-8-0
passed

scaling-proxysql-8-0
passed

operator-self-healing-8-0
passed

security-context-8-0
passed

operator-self-healing-chaos-8-0
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

affinity-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

upgrade-proxysql-8-0
passed

one-pod-5-7
passed

scheduled-backup-5-7
passed

init-deploy-5-7
passed

haproxy-5-7
passed

demand-backup-encrypted-with-tls-8-0
passed

smart-update-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

upgrade-consistency-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/f6da5e4ab66395ac378839510a19dfc7b9abd49e
image: perconalab/percona-xtradb-cluster-operator:PR-1194-f6da5e4a

Test name
Status

big-data-8-0
passed

haproxy-8-0
passed

scheduled-backup-8-0
passed

upgrade-haproxy-8-0
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

storage-8-0
passed

affinity-8-0
passed

scaling-8-0
passed

self-healing-8-0
passed

one-pod-8-0
passed

scaling-proxysql-8-0
passed

self-healing-chaos-8-0
passed

auto-tuning-8-0
passed

security-context-8-0
passed

self-healing-advanced-8-0
passed

cross-site-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

self-healing-advanced-chaos-8-0
passed

users-8-0
passed

restore-to-encrypted-cluster-8-0
passed

operator-self-healing-8-0
passed

tls-issue-self-8-0
passed

demand-backup-8-0
passed

operator-self-healing-chaos-8-0
passed

tls-issue-cert-manager-8-0
passed

pitr-8-0
passed

users-5-7
passed

tls-issue-cert-manager-ref-8-0
passed

one-pod-5-7
passed

validation-hook-8-0
passed

scheduled-backup-5-7
passed

proxy-protocol-8-0
passed

init-deploy-5-7
passed

haproxy-5-7
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/f6da5e4ab66395ac378839510a19dfc7b9abd49e
image: perconalab/percona-xtradb-cluster-operator:PR-1194-f6da5e4a

Test name
Status

scaling-8-0
passed

scaling-proxysql-8-0
passed

security-context-8-0
passed

We run 3 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/34f33d7ea2121ef197161a6b3c7889a72301ed0d
image: perconalab/percona-xtradb-cluster-operator:PR-1194-34f33d7e

Test name
Status

users-5-7
passed

big-data-8-0
passed

haproxy-8-0
passed

upgrade-haproxy-8-0
passed

storage-8-0
passed

recreate-8-0
passed

cross-site-8-0
passed

scheduled-backup-8-0
passed

scaling-8-0
passed

self-healing-8-0
passed

scaling-proxysql-8-0
passed

self-healing-chaos-8-0
failed

restore-to-encrypted-cluster-8-0
passed

security-context-8-0
passed

one-pod-5-7
passed

upgrade-proxysql-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

init-deploy-8-0
passed

scheduled-backup-5-7
passed

demand-backup-8-0
failed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

smart-update-8-0
passed

init-deploy-5-7
passed

haproxy-5-7
passed

limits-8-0
passed

upgrade-consistency-8-0
passed

monitoring-2-0-8-0
passed

affinity-8-0
passed

one-pod-8-0
failed

We run 31 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/995440a50d12902b47e0d8a3cc5ad4a8bcd236ff
image: perconalab/percona-xtradb-cluster-operator:PR-1194-995440a5

Test name
Status

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

demand-backup-8-0
passed

scaling-8-0
passed

scheduled-backup-8-0
passed

scaling-proxysql-8-0
passed

security-context-8-0
passed

users-5-7
passed

big-data-8-0
passed

one-pod-5-7
passed

scheduled-backup-5-7
passed

init-deploy-5-7
passed

haproxy-8-0
passed

storage-8-0
passed

upgrade-haproxy-8-0
passed

haproxy-5-7
passed

init-deploy-8-0
passed

self-healing-8-0
passed

limits-8-0
passed

self-healing-chaos-8-0
failed

monitoring-2-0-8-0
passed

cross-site-8-0
passed

affinity-8-0
passed

one-pod-8-0
passed

upgrade-proxysql-8-0
passed

auto-tuning-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

pitr-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/995440a50d12902b47e0d8a3cc5ad4a8bcd236ff
image: perconalab/percona-xtradb-cluster-operator:PR-1194-995440a5

Test name
Status

scaling-8-0
passed

scheduled-backup-8-0
passed

users-5-7
passed

cross-site-8-0
passed

scaling-proxysql-8-0
passed

one-pod-5-7
passed

security-context-8-0
passed

scheduled-backup-5-7
passed

upgrade-haproxy-8-0
passed

recreate-8-0
passed

haproxy-8-0
passed

storage-8-0
passed

init-deploy-5-7
passed

restore-to-encrypted-cluster-8-0
passed

init-deploy-8-0
passed

big-data-8-0
passed

self-healing-8-0
passed

haproxy-5-7
passed

limits-8-0
passed

demand-backup-8-0
passed

self-healing-chaos-8-0
failed

monitoring-2-0-8-0
passed

pitr-8-0
passed

affinity-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/995440a50d12902b47e0d8a3cc5ad4a8bcd236ff
image: perconalab/percona-xtradb-cluster-operator:PR-1194-995440a5

Test name
Status

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scheduled-backup-8-0
passed

demand-backup-8-0
passed

cross-site-8-0
passed

pitr-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

upgrade-haproxy-8-0
passed

storage-8-0
passed

users-5-7
passed

haproxy-8-0
passed

self-healing-8-0
passed

scaling-8-0
passed

one-pod-5-7
passed

big-data-8-0
passed

init-deploy-8-0
passed

scaling-proxysql-8-0
passed

self-healing-chaos-8-0
failed

scheduled-backup-5-7
passed

limits-8-0
passed

security-context-8-0
passed

init-deploy-5-7
passed

monitoring-2-0-8-0
passed

haproxy-5-7
passed

affinity-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/995440a50d12902b47e0d8a3cc5ad4a8bcd236ff
image: perconalab/percona-xtradb-cluster-operator:PR-1194-995440a5

Test name
Status

scheduled-backup-8-0
passed

storage-8-0
passed

cross-site-8-0
passed

upgrade-haproxy-8-0
passed

self-healing-8-0
passed

self-healing-chaos-8-0
failed

scaling-8-0
passed

recreate-8-0
passed

users-5-7
passed

scaling-proxysql-8-0
passed

restore-to-encrypted-cluster-8-0
passed

one-pod-5-7
passed

security-context-8-0
passed

demand-backup-8-0
passed

scheduled-backup-5-7
passed

pitr-8-0
passed

big-data-8-0
passed

init-deploy-5-7
passed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

affinity-8-0
passed

one-pod-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/995440a50d12902b47e0d8a3cc5ad4a8bcd236ff
image: perconalab/percona-xtradb-cluster-operator:PR-1194-995440a5

Test name
Status

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

demand-backup-8-0
passed

pitr-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

cross-site-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

security-context-8-0
passed

upgrade-haproxy-8-0
passed

haproxy-8-0
passed

storage-8-0
passed

big-data-8-0
passed

init-deploy-8-0
passed

self-healing-8-0
passed

limits-8-0
passed

self-healing-chaos-8-0
failed

monitoring-2-0-8-0
passed

scheduled-backup-8-0
passed

users-5-7
passed

affinity-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

scheduled-backup-5-7
passed

auto-tuning-8-0
passed

init-deploy-5-7
passed

proxysql-sidecar-res-limits-8-0
passed

haproxy-5-7
passed

users-8-0
passed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/995440a50d12902b47e0d8a3cc5ad4a8bcd236ff
image: perconalab/percona-xtradb-cluster-operator:PR-1194-995440a5

Test name
Status

haproxy-8-0
passed

init-deploy-8-0
passed

limits-8-0
passed

scheduled-backup-8-0
passed

upgrade-haproxy-8-0
passed

monitoring-2-0-8-0
passed

cross-site-8-0
passed

affinity-8-0
passed

one-pod-8-0
passed

scaling-8-0
passed

auto-tuning-8-0
passed

storage-8-0
passed

scaling-proxysql-8-0
passed

recreate-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

self-healing-8-0
passed

big-data-8-0
passed

security-context-8-0
passed

restore-to-encrypted-cluster-8-0
passed

users-8-0
passed

self-healing-chaos-8-0
failed

demand-backup-8-0
passed

tls-issue-self-8-0
passed

pitr-8-0
passed

tls-issue-cert-manager-8-0
passed

users-5-7
passed

demand-backup-encrypted-with-tls-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

one-pod-5-7
passed

validation-hook-8-0
passed

scheduled-backup-5-7
passed

proxy-protocol-8-0
passed

init-deploy-5-7
passed

haproxy-5-7
passed

upgrade-proxysql-8-0
passed

smart-update-8-0
passed

upgrade-consistency-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
failed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
failed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1194/commits/995440a50d12902b47e0d8a3cc5ad4a8bcd236ff
image: perconalab/percona-xtradb-cluster-operator:PR-1194-995440a5


Add GridFS as backed storage mechanism

https://docs.mongodb.com/manual/core/gridfs/

Interesting. Out of curiosity, what's the use case? Trying to take advantage of an existing MongoDb instance?


Update README.md

Added a new app in the Applications section of the README

Hi! Just wanted to add an app built using RxSwift and RxCocoa, I think it could be another nice example to include in the list.

Great, thanks! 👊


Clarification on goals/pros/cons/differences to prometheus-net

Hello,
I couldn't find any information on how this project is different to prometheus-net except for the brief mention that it's a fork.
Would be great if you could elaborate the goals/pros/cons/differences of this project compared to "prometheus-net" in the README. Given there's not much info there currently, the alternative is to read the code and/or try both APIs.
I expect most users would simply compare the projects based on the number of Github stars/Nuget downloads/Commit activity and choose in favour of the original "prometheus-net". The clarification would help promote the project!

I wrote some information in Readme.
I created a fork for my own projects. Now I think about its development. Write more issues.


Fastcdr CI cleanup, ros rolling API changes

This is a temp PR meant to clean up CI. Resolves https://github.com/RobotLocomotion/drake-ros/issues/274

This change is

Green CI !


Option changes in class definitions do not result in anything in the changes display

I added #instancesNotPersistent to a number of classes, but when I browsed changes in the project none of them were reported.
I had also removed the GemToGemAnnouncement class, so its artefacts were shown, including its class definition showing as removed. But, none of the other class definitions showed as changes.

Note that it's instancesNonPersistent; and yes, while changes in class definitions instance variables do show up in the Changes Browser in 3.2.12, options are ignored.  I see that the changes browser doesn't even print any information on the options.

For v3 I plan to remove the Cypress classes (that are there only because the changes browser expects Monticello style definitions) when this change is made (replace with Modifications) the changes browser will have access to all of the detailed changes ...


pull request for e2e test at 01/01/2017 23:45:07

:white_check_mark: Validation status: passed
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.

:white_check_mark: Validation status: passed
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.


Complete current listed RPi manager functions

What is this PR for?
Finish currently listed RPi manager functions, except for functions with LED and EL.
What type of PR is it?
[Feature]
Todos
EL, LED_strip
What is the Github issue?
https://github.com/NTUEELightDance/LightDance-RPi/issues/41
How should this be tested?
None
Screenshots (if appropriate)
None
Questions:

Do the license files need updating? No
Are there breaking changes for older versions? Yes
Does this need new documentation? No

@Kenchu123 There are no significant changes compared to the older version, I'll finish ELs and LEDs after discussing with the hardware department.


start.ps1 - The system cannot find the file specified

If there is some documentation I am missing, I am all for starting over......I am new to docker......
This is what I have done so far

Set up Windows 2016 VM and current on Windows updates
Installed Container role from Server Manager
Install-Module DockerMsftProvider -Force
Install-Package Docker -ProviderName DockerMsftProvider -Force
Install-Package ContainerImage -Force
Created strong SA password in C:\ProgramData\Docker\secrets\sa-password
Copy\paste contents https://github.com/Microsoft/mssql-docker/blob/master/windows/mssql-server-windows-express/dockerfile to c:\sql\dockerfile
Copy\paste contents https://github.com/Microsoft/mssql-docker/blob/master/windows/mssql-server-windows-express/start.ps1 to c:\sql\start.ps1

c:\sql> docker build - < dockerfile
Sending build context to Docker daemon  3.584kB
Step 1/10 : FROM microsoft/windowsservercore
---> ea9f7aa13d03
Step 2/10 : LABEL maintainer "Perry Skountrianos"
---> Using cache
---> 1b0f4f033900
Step 3/10 : ENV sql_express_download_url "https://go.microsoft.com/fwlink/?linkid=829176"
---> Using cache
---> 2cab396c57b9
Step 4/10 : ENV sa_password=""     attach_dbs="[]"     ACCEPT_EULA=""     sa_password_path="C:\ProgramData\Docker\secrets\sa-password"
---> Using cache
---> bf7e7861e6db
Step 5/10 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
---> Using cache
---> 30b552183943
Step 6/10 : COPY start.ps1 /
COPY failed: CreateFile \?\C:\ProgramData\docker\tmp\docker-builder075099570\start.ps1: The system cannot find the file specified.

Hi mvalpreda,

COPY failed: CreateFile ?\C:\ProgramData\docker\tmp\docker-builder075099570\start.ps1: The system cannot find the file specified.

Please check if the file present in the directory that you're building from. Also check if there is a .dockerignore file in your build directory. Here is a similar thread. See if it can help.
COPY / The system cannot find the file specified. #34893


Fix: Typing feedback text under composer is not being displayed

Fix: Typing feedback text under composer is not being displayed

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/22426
PROPOSAL: https://github.com/Expensify/App/issues/22426#issuecomment-1625466771
Tests

1- Open a tab where account A is signed in
2- Open an existing chat with account B
3- Start typing in composer

Account B should be able to see account A is typing feedback under composer

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

same as tests above.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/77965000/680d4f2f-863e-4eab-8e56-ada72f7eff59

Mobile Web - Chrome

https://github.com/Expensify/App/assets/77965000/140ac055-f78c-401b-b6c5-be774f7166e5

Mobile Web - Safari

https://github.com/Expensify/App/assets/77965000/dfc3d033-9a73-495d-822e-5a00e4b48bbb

Desktop

https://github.com/Expensify/App/assets/77965000/843d264e-30f3-438c-9e66-1c1fab52bee6

iOS

https://github.com/Expensify/App/assets/77965000/f6a0ef7a-aaec-4091-84ce-41d662cdec7d

Android

https://github.com/Expensify/App/assets/77965000/cc5f36d1-c0a0-4e3c-b696-ec3724b65e04

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web & Desktop
https://github.com/Expensify/App/assets/85645967/246bbd05-b937-45ed-b507-b81e2bf0a9a0

Mobile Web - Chrome & Mobile Web - Safari
https://github.com/Expensify/App/assets/85645967/c53dc8e7-1b88-4043-81c9-e815a1a8dc7f

 iOS & Android
https://github.com/Expensify/App/assets/85645967/b34c6ef8-3e14-463c-8ef8-602e22c6e8f3

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/srikarparsi in version: 1.3.38-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@srikarparsi Assign me issue for tracking Review payment thanks!

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.38-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@srikarparsi Bump https://github.com/Expensify/App/pull/22501#issuecomment-1629578893

Hi @Santhosh-Sellavel! I believe this is something the contributor manager takes care of? Let me take a look.

Hey @Santhosh-Sellavel! Flavia is coming back from OOO on Thursday so I believe she will assign the tracking issue as soon as she is back.

Thanks @srikarparsi!
@flaviadefaria Please assign me the issue for tracking review payment!


D3 integration, master refactoring, and new Graph input components

This includes the following:

D3 integration in to Entity Detail component as "At a Glance"
Src Path updates and refactoring
SzRelationshipNetworkInputComponent
SzRelationshipNetworkLookupComponent component
SzRelationshipNetworkUploadComponent component

@timadair this contains your graph input components as well, but with the paths adjusted to the new layout. Ignore the docs updates. lemme know if you have any questions.

Issue number: #40


Move Fahrenheit Variable Below Comment Line

Convert Celsius to Fahrenheit
https://www.freecodecamp.org/challenges/convert-celsius-to-fahrenheit
Issue Description
There's an inconsistency between the forum solution to this module and the needed solution. In order to get the tests to pass, you need to modify the Fahrenheit variable, but it's above the comment that says to only modify code below that comment.
My proposed solution is to update the content on the exercise so the variable is below the comment, so it would appear like this:
function convertToF(celsius) {
  // Only change code below this line

  var fahrenheit

  // Only change code above this line
  return fahrenheit;
}

// Change the inputs below to test your code
convertToF(30);
function convertToF(celsius) {
  var fahrenheit = (celsius * 9/5) + 32;
  // Only change code below this line

  // Only change code above this line
  return fahrenheit;
}

// Change the inputs below to test your code
convertToF(30);

Here's a link to the solution in the forum so you can see the discrepency: https://forum.freecodecamp.org/t/freecodecamp-challenge-guide-convert-celsius-to-fahrenheit/16806
Browser Information

Browser Name, Version: Chrome
Operating System: Mac OS Sierra
Mobile, Desktop, or Tablet: Desktop

Your Code
This is what I used to get the tests to pass. I had to modify var fahrenheit which is above the comment line. My sense is this is where a lot of the confusion from this exercise is coming from.
function convertToF(celsius) {
  var fahrenheit = (celsius * 9/5) + 32;
  // Only change code below this line

  // Only change code above this line
  return fahrenheit;
}

// Change the inputs below to test your code
convertToF(30);

Screenshot

Notice how the comments between the exercise and the solution are not in the same place. This is what's creating the confusion because in order to solve the problem you need to modify the var that's above the comment in the exercise.

I guess that the variable declaration at the top was placed there either to ease the testing or to help campers have a structure to start working with.
What probably many new coders don't consider is that the solution can simply be achieved by a basic value assign:
var fahrenheit;
 // Only change code below this line
 fahrenheit = // my expression
 // Only change code above this line
 return fahrenheit;

Then again I've seen this confusion happening before so I guess we could consider re-write the seed code as you proposed to lead to less confusion.

note this challenge is not tested in strict mode so the following code pass:
function convertToF(celsius) {
 fahrenheit =  //expression
 return fahrenheit;
}

maybe while we are at it we want to tackle it for better consistency?

@andreagoulet thanks for the issue and feedback.
I'm able to pass the challenge with all variations on how the equation is placed (with the initial var fahrenheit, with a fahrenheit = ... on another line, etc), so I'm not sure what bug there is from the challenge not working correctly.
I agree that the forum wiki and the challenge itself should be consistent :+1:
We can make it cleaner on what the "Instructions" are for the challenge.

To test your learning, you will create a solution "from scratch". Place your code between the indicated lines and it will be tested against multiple test cases.
The algorithm to convert from Celsius to Fahrenheit is the temperature in Celsius times 9/5, plus 32.
Instructions
You are given a variable celsius representing a temperature in Celsius. Use the variable fahrenheit already defined and assign it the Fahrenheit temperature equivalent to the given Celsius temperature. Use the algorithm mentioned above to help convert the Celsius temperature to Fahrenheit.
Note
Don't worry too much about the function and return statements as they will be covered in future challenges. For now, only use operators that you have already learned.

I agree with @erictleung .
I would like to have a chance to work on this.
I am working on this and will submit a PR soon.


Production Build: Cannot Convert BigInt to Number (Create React App)

While serving a production build of create-react-app with multiple different servers (Netlify, locally using serve) I ran into this error.
Uncaught TypeError: can't convert BigInt to number

I solved this issue by modifying the production list of supported browsers to this.
  "browserslist": {
    "production": [
      "chrome >= 67",
      "edge >= 79",
      "firefox >= 68",
      "opera >= 54",
      "safari >= 14"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },

It was related to this Issue in another project having to do with browser support for older browsers in a production build. Hope this helps someone else!

Asked an answered my own question to pass along more good karma.


WIP: Rearrange / GetItem / stack / clone

WIP API for shape operations.

rearrange(pattern, **axes_lengths)
with an enhanced pattern type
... | ... -> (...) | (...)
-> will reshape to one other dim, all in k0. keep coil.
'|' is the delimter between other-like batch dimensions and k-dimensions. For kdata.data this is the 'coil' dimension.
if no | is present, interpret left-to-right, i.e. only apply to other dimensions
always return other coil k2 k1 k0, set to 1 if required.

clone()
creates a new copy of data, header, trajectory

getitem
Returns a view into the dataset.
So kdata[0].traj.kz will return the kz values of the first other and is equivalent to kdata.traj.kz[0].
This supports boolean mask indexing and is used in the next function. .clone() can be used to transform it into a new data
object

stack(other, dim)
stacks another data object in a certain dimension

split(dim, size, step)
Splits one data object along other dimension into multiple, potentially overlapping, views.

select_idx_subset(iabel, idx)
This is a convenience function, implementing
mask= torch.isin( getattr(kdata.header.acq_info.idx, label), idx)
return self[mask]

reshape_idx_to_dim(label, dim):
reshapes a based on a label into a new other dim

arange_idx_(label, dim)
Another convenience function, filling in the acqidx with consecutive integers along a dimension.

while implementing the rearrange parser for einops, I was started to wonder if
a) allowing the rearrange k0 is useful
b) allowing ellipses on the k dims is useful
c) automatically adjusting such that we always have 3 kdim is useful (or if an error should be thrown)
a-c) I think the answer is NO
d) if we should support coil-> other reshapes as part of rearrange. I think not... not sure yet.
e) if we enforce coil, k2, k1 names -> I think not.
f ) if we allow ... | ..., i.e. an ellipsis on all k dim. -> I think yes if e) is no
g) If we allow  to leave out "| ..." and default to rearrange only on the batch dims. -> maybe.


Incident Response Playbook / Toolkit

Background
In the even of an incident, we should have a playbook of general actions that should be taken to mitigate problems and come to an eventual solution.
In addition to this, a "toolkit" should be created that make diagnosing issues across system simpler. An example of this would be some tool that could be run on any system that can extract basic information such as module hashes / s3cmd config pre configured to upload snapshots to our DO s3 buckets / etc.
Suggested Design

Basic outline for incident response

Could potentially use the most recent incident (hash mismatch) as the starting playbook
Can extend this to previous issues (gamm exploits)
Eventually once all previous incidents are covered, create playbooks for incidents that have not happened to us but have happened on other chains
Finally create playbooks for incidents that have not happened for us or other chains but is still possible

Create a toolkit that can be deployed on incident that makes some of these manual tasks more automated and in turn quicker

As explained above, this is stuff like creating a node off a snapshot (node to node transfer in same data center to make it faster), snapshot upload, export module hashes, export block events in a clean format, etc

Acceptance Criteria

All above points are addressed

Another part of this toolkit could be a google sheet that gets automatically generated with validator addresses / power. This is currently manually generated during every incident.

I think we should:

Make a list of all incidents we've ran into
Make an outline for how the playbook / toolkit should work (and layout some of our decision trees)
Get started trying out an incident or two, ratify a plan, and iterate on format :)


[Bug report] The header anchor should stay outside of the heading tag

Description
The header anchors # are placed inside the heading tags (h1, h2, h3...).
This behaviour is not actually correct, since the heading tag should explicitly indicate the nature of the content as a title, and # shouldn't be part of it.

Apart from the semantic issue, there is also a more problematic issue: crawlers, some social media crawlers may take the title from the h1 heading tag to create a post preview. This means that the preview title of the post will contain the "#" character.
This is an example of a VuePress post preview on LinkedIn

To reproduce I have a live link
https://www.mida.org/posts/reactive-programming-in-financial-markets/
The website above is built with VuePress 1 but the issue persists also on VuePress 2.
Thank you,
Vasile
Reproduction
https://www.mida.org/posts/reactive-programming-in-financial-markets/
Used Package Manager
npm
System Info
Not relevant

Yep, markdown-it-anchor has provided multiple solutions for that since v8.0.
We didn't update to use other methods to get better a11y yet. Contribution welcome


Maximum error

It would be great to support a maximum error parameter. Ideally we can say, “decimate this mesh to n faces, but don’t remove any faces then produce error greater than x threshold.”
This would allow a more aggressive face target, while maintaining a particular level of quality.

Hey. This is a great feature. Due to the application of my implementation, I was focussing on the node reduction, only ;).


Omegaconf & hydra-core missing dependencies

🐛 Bug
After installing torch, trying to load a model will fail due to two missing dependencies: omegaconf and hydra-core.
To Reproduce
Running the following code block doesn't work:
import torch
roberta = torch.hub.load("pytorch/fairseq", "roberta.large")
roberta.eval()
device = "cuda" if torch.cuda.is_available() else "cpu"
print(f"using device: {device}")
roberta.to(device)

The traceback I get is:
Traceback (most recent call last):
  File "/src/cortex/lib/type/predictor.py", line 111, in initialize_impl
    return class_impl(**args)
  File "/mnt/project/predictor.py", line 10, in __init__
    roberta = torch.hub.load("pytorch/fairseq", "roberta.large")
  File "/opt/conda/envs/env/lib/python3.6/site-packages/torch/hub.py", line 349, in load
    hub_module = import_module(MODULE_HUBCONF, repo_dir + '/' + MODULE_HUBCONF)
  File "/opt/conda/envs/env/lib/python3.6/site-packages/torch/hub.py", line 71, in import_module
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/root/.cache/torch/hub/pytorch_fairseq_master/hubconf.py", line 8, in <module>
    from fairseq.hub_utils import BPEHubInterface as bpe  # noqa
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/__init__.py", line 17, in <module>
    import fairseq.criterions  # noqa
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/criterions/__init__.py", line 26, in <module>
    importlib.import_module('fairseq.criterions.' + module)
  File "/opt/conda/envs/env/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/criterions/adaptive_loss.py", line 12, in <module>
    from fairseq.dataclass.data_class import DDP_BACKEND_CHOICES
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/dataclass/data_class.py", line 12, in <module>
    from fairseq.tasks import TASK_DATACLASS_REGISTRY
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/tasks/__init__.py", line 73, in <module>
    importlib.import_module('fairseq.tasks.' + task_name)
  File "/opt/conda/envs/env/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/tasks/language_modeling.py", line 36, in <module>
    from omegaconf import II
ModuleNotFoundError: No module named 'omegaconf'

Then, if I add omegaconf to the requirements.txt file, the next error I get is:
Traceback (most recent call last):
  File "/src/cortex/lib/type/predictor.py", line 111, in initialize_impl
    return class_impl(**args)
  File "/mnt/project/predictor.py", line 10, in __init__
    roberta = torch.hub.load("pytorch/fairseq", "roberta.large")
  File "/opt/conda/envs/env/lib/python3.6/site-packages/torch/hub.py", line 349, in load
    hub_module = import_module(MODULE_HUBCONF, repo_dir + '/' + MODULE_HUBCONF)
  File "/opt/conda/envs/env/lib/python3.6/site-packages/torch/hub.py", line 71, in import_module
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/root/.cache/torch/hub/pytorch_fairseq_master/hubconf.py", line 8, in <module>
    from fairseq.hub_utils import BPEHubInterface as bpe  # noqa
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/__init__.py", line 17, in <module>
    import fairseq.criterions  # noqa
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/criterions/__init__.py", line 26, in <module>
    importlib.import_module('fairseq.criterions.' + module)
  File "/opt/conda/envs/env/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/criterions/adaptive_loss.py", line 12, in <module>
    from fairseq.dataclass.data_class import DDP_BACKEND_CHOICES
  File "/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/dataclass/data_class.py", line 18, in <module>
    from hydra.core.config_store import ConfigStore
ModuleNotFoundError: No module named 'hydra'

Adding hydra-core to the requirementst.txt fixes the issue. With both of them in, torch works as expected - one thing I've noticed is that when installing them, they go through a complex-looking stage of compiling stuff with g++ (takes some time).
Expected behavior
Expected it to work without having to install omegaconf and hydra-core. The provided example worked without these a couple of months ago - maybe something did change in torch?
Environment
Installed torch the following way:
pip install --no-cache-dir --find-links https://download.pytorch.org/whl/torch_stable.html torch==1.6.0+cu101 torchvision==0.7.0+cu101

OS (e.g., Linux): Linux.
Python version: 3.6.9.
CUDA/cuDNN version: 10.1
GPU models and configuration: A single T4 GPU.

Additional context
As fixed in https://github.com/cortexlabs/cortex/pull/1402. Suggested by @omry to post here.

@RobertLucian, the stack trace suggests that you do have version of fairseq installed that depends on Hydra.
Can you show a complete repro including how you create the environment?
(say, a clean conda environment).

Thanks for flagging, torch.hub uses its own mechanism for specifying dependencies, and we need to add hydra there: https://github.com/pytorch/fairseq/blob/master/hubconf.py#L13-L18

Thanks @myleott, I spotted that at the repo root and I thought it might be the case.

@myleott thanks a lot for your quick resolution on this!
@omry in this case, is a complete repro including the process of creating the environment still necessary?

@RobertLucian, that that we are clearing the unneeded dependency in cortex for Hydra - I recommend that you take a look anyway and consider using it.
https://hydra.cc

Thanks @omry, I'll have a look at it.

This should be fixed by f902a363abc578906f29239f995cacce5e93a807

@myleott thanks for the fix.
Any idea when this is gonna land (or is it just a patch and is already available)?
Also, is there an ETA of when this will make it in torch (as a dependency)?

Actually that didn't totally fix it :/

Any idea when this is gonna land (or is it just a patch and is already available)?
Also, is there an ETA of when this will make it in torch (as a dependency)?

When it lands it will take effect immediately, you'll just need to do torch.hub.load(..., force_reload=True). But for now it's still broken.

This should be fixed. Please use torch.hub.load(..., force_reload=True). Note that dataclasses and hydra-core are now required dependencies, so you'll need to pip install them if you haven't already.

Hey I am still running through this error even after installing hyrda-core using pip.
Traceback I am getting is
`Downloading: "https://github.com/pytorch/fairseq/archive/master.zip" to /root/.cache/torch/hub/master.zip
ModuleNotFoundError                       Traceback (most recent call last)
 in ()
----> 1 roberta = torch.hub.load('pytorch/fairseq', 'roberta.large',force_reload=True)
2 roberta.eval()
7 frames
/root/.cache/torch/hub/pytorch_fairseq_master/fairseq/dataclass/initialize.py in ()
7 import logging
8 from typing import Dict, Any
----> 9 from hydra.core.config_store import ConfigStore
10 from fairseq.dataclass.configs import FairseqConfig
11
ModuleNotFoundError: No module named 'hydra.core'; 'hydra' is not a package`


improve failure modes of ChromeConnection.getTabs

Have ChromeConnection.getTabs return better exceptions where there's a failure setting up the Chrome connection (#85).
Introduce a new, optional retryFor parameter to ChromeConnection.getTabs. This will re-try failed connections for a period of time; it can be useful to mitigate some intermittent connection issues very early in Chrome's startup.
fix https://github.com/google/webkit_inspection_protocol.dart/issues/85

@annagrin - flutter tools would have to opt-into the retry in order to get the benefit of that work. But even w/o that, they should see a better exception message - it'll print more of the <html... response that's confusing the json decoder.

@devoncarew thanks, this is really helpful! I'll propagate the change to dwds and flutter after the version with the change is published.


feat(matic.ts): add amWETH to matic list

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature Request: clasp diff

Great work. So very appreciative for this.
Wondering if you're entertaining a clasp diff functionality. I often wonder which code base is most current. And a clasp diff that brings the last updated at the header would help me know when i last pushed or pulled.
Thanks again!
Expected Behavior
Actual Behavior
Steps to Reproduce the Problem

Specifications

Node version (node -v)
Version (npm list -g | grep clasp):
OS (Mac/Linux/Windows)

@namelus Good idea, I've wondered if this would be useful too.
However, I think once TypeScript development production-ready, I don't think there's a need to use the script editor.
It comes down to this: git diff will always be better than anything we can build.
We might want to add a section on working with git to the README. What do you think?

As stated above, git diff will always be better anything in clasp. Closing, but feel free to add to the discussion here though.

Moving to typescript doesn't stop you from using the online script editor and messing up the whole thing unless you have a clasp diff.


Added the submodules initialization step

/cc @JunTaoLuo for an expert review

@aspnet/brt this has failed with some unrelated error, as my change is to a MD file only.

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=142524&view=results

This comment was made automatically. If there is a problem contact ryanbrandenburg.
I've triaged the above build.

@mkArtakMSFT when this kind of thing happens speak the above incantation and RaaS will arrive to triage. After it's been triaged you can retry the build.


[Docs] Update README to include Twitter

What
I added the dependency for twitter.
Before

After

@guelate thanks for submitting a PR, a member of the core team is reviewing our readme for some future updates and this is a great suggestion.
Note that we do list Twitter on the main website though

@lb- Okay no problem.


feature: add stopEarly option

Add new stopEarly boolean property to the configuration options. If true, the operands array _ will be populated with all the arguments after the first non-option.
getopts(["-w9", "alpha", "--turbo", "beta"], {
  stopEarly: true
}) //=> { _:["alpha", "--turbo", "beta"], w:9 }

This property is useful when implementing sub-commands in a CLI as described by @julien-f in #40.

Codecov Report

Merging #41 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #41   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          92     94    +2
=====================================
+ Hits           92     94    +2

Impacted Files
Coverage Δ

index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d94fccd...0296de8. Read the comment docs.

@julien-f What do you think about the example I added to the docs? Could it be improved?

Looks fine to me :slightly_smiling_face:


Update user responses to match parsing format

Codecov Report

Merging #124 (37bbaaf) into master (0eeb183) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #124      +/-   ##
============================================
- Coverage     50.88%   50.85%   -0.03%
  Complexity      560      560
============================================
  Files           113      113
  Lines          2443     2444       +1
  Branches        292      292
============================================
  Hits           1243     1243
- Misses         1119     1120       +1
  Partials         81       81

Impacted Files
Coverage Δ

...du/address/logic/commands/meeting/MeetCommand.java
0.00% <ø> (ø)

...main/java/seedu/address/model/meeting/Meeting.java
0.00% <0.00%> (ø)

.../java/seedu/address/model/meeting/MeetingTime.java
0.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0eeb183...37bbaaf. Read the comment docs.


Cleanup "Hudson" references in the Jenkinsfile Runner codebase

Contributes to #375

@darkphoenix17 if you are interested, a similar patch could be applied to the Jenkins Test harness codebase: https://github.com/jenkinsci/jenkins-test-harness which was originator of the code. Note that there Binary compatibility should be retained, so it is not possible to just rename classes and methods

@oleg-nenashev can this PR be eligible for hacktoberfest? If so, Can you add the hacktoberfest label?

@darkphoenix17 if you are interested, a similar patch could be applied to the Jenkins Test harness codebase: https://github.com/jenkinsci/jenkins-test-harness which was originator of the code. Note that there Binary compatibility should be retained, so it is not possible to just rename classes and methods

Yeah, I am very much interested. Looking forward to the issue.

@darkphoenix17 if you are interested, a similar patch could be applied to the Jenkins Test harness codebase: https://github.com/jenkinsci/jenkins-test-harness which was originator of the code. Note that there Binary compatibility should be retained, so it is not possible to just rename classes and methods

Hello @oleg-nenashev , I looked through the code base and tried to understand the workflow so that I can make the necessary changes of the name.
The code of that repo is more than the current repo which I was working on.... could you provide me some initial steps to start working on in some form of bullets task.


HTML synthax highlighting not displaying correclty

This request is about the synthax highlighting of source code on Stackoverflow.
When HTML attributes contains characters such as >, it creates an issue in the synthax highlighting.
Here is a sample of Angular code from this answer that generates the problem:

As you can see, there are severals problems. For example, the > operator in ng-if is understanded as the end of the <div>.

Can we ignore characters such as > between " and ' in HTML synthax highlighting?

It's a good idea to escape special characters like <, >, and & in HTML using the equivalent entity references.
Here is a live demo: https://jsfiddle.net/amroamroamro/0rwouzg8/

this is sort of similar to #339, although technically it is valid in HTML standard unlike XML.

As @amroamroamro mentioned, angle brackets are allowed in HTML attribute values, so this bug should be addressed. I came here because I also encountered the bug -- click "view source" below the "With prefix/suffix" example.


Fix IfStatementAssignment violation message

Fix #655

@ravage84 it did not worry me, I do not see how my change could have broken anything ^^

@Jir4 my comment was just informative  for other maintainers


Make HttpMessage.SetHeader replace any existing header value

Fixes #12
Ensure the "Signature" value is not added multiple times when a retry happens

Takker! v3.2.1 is up on NuGet 😄


Make it possible to give a keyDecodingStrategy for the decoder

Or better yet, just the possibility to give a custom encoder / decoder?

It should be possible, as the Endpoint type stores the function that transforms the raw response into a typed response. I will give it a try as soon as I can.


Any form of automation causes Wood Rack to delete Cured Hide

Problem is as title states: If you attempt to automate the placement of Cured Hide onto a Wood Rack (with either a Dropper, or a "Basic Inventory Hopper" from "Tom's Simple Storage Mod"), the Cured Hide appears on the Wood Rack for a moment, then gets deleted.
This makes any form of automation impossible currently.

Thanks for the report, fixed hopper interaction with https://github.com/Globox1997/FleshZ/commit/f092f02050e80c29563def44aa9cc46b0e559e10


Remove registration of link tooltip component

Summary
The link tooltip feature is having some issues as noted in the ticket below. The feature is pretty complex, so it will take some time to fix the issue. This PR temporarily removes the feature so we unblock the v4.1.0 release.
Ticket Link
Temporarily fixes https://github.com/mattermost/mattermost-plugin-jira/issues/1015

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

Comparison is base (249614e) 33.32% compared to head (2ed51dd) 33.29%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1016      +/-   ##
==========================================
- Coverage   33.32%   33.29%   -0.03%
==========================================
  Files          53       53
  Lines        7944     7944
==========================================
- Hits         2647     2645       -2
- Misses       5070     5072       +2
  Partials      227      227

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

Closing in favor of https://github.com/mattermost/mattermost-plugin-jira/pull/1017


ompl: fix compilation error

The issue is here #522
For the ompl fix:
This time I submitted the issue to ompl and they do a fix. I generated the git format-patch from the commit they made. The format should be good this time.
As for the cv-bridge, I am not able to fix as I am working on morty environment only, can't test it on other environment. For now I just keep a patch in my repository.
Please have a look for those changes, thank you.

@yangjiel The upstream has released the version 1.1.1 with the patch already included. Could you please upgrade the ompl recipe from v1.1.0 to v1.1.1?
This way there's no need to have the patch in the meta layer.

Seems ompl haven't address the gcc6 problem fully yet, there is still gcc6 problem at the branch 1.1.1. I have talked to them. As soon as they response, I will upgrade the ompl version to 1.1.1.

I have upgraded the ompl from version 1.1.0 to 1.1.1.

I successfully built core-image-ros-world with
Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "fedora-25"
TARGET_SYS        = "i586-oe-linux"
MACHINE           = "qemux86"
DISTRO            = "nodistro"
DISTRO_VERSION    = "nodistro.0"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              = "master:ef68005a8c527e9b1d05b7769f0ec8ebe9ec3f91"
meta-oe
meta-python
meta-multimedia   = "master:1cbd1bc195017312ba8cf670b340f61a2ac6207b"
meta-ros          = "yangjiel-master-v1:f25474fdf3fb576e832426e7f40836eb33a8b821"

and a patch for https://github.com/bmwcarit/meta-ros/issues/532 applied manually.
Thanks @yangjiel ! That looks great


Errorof type "CrashLoopBackOff" when executing the "get pods" on the Go memcached operator example

Bug Report
What did you do?
A clear and concise description of the steps you took (or insert a code snippet).
Followed the guideline here:
https://github.com/operator-framework/operator-sdk/blob/master/doc/user-guide.md
What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).
What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).
when I arrive at the point:
"Verify that the memcached-operator is up and running:
$ kubectl get deployment"
I see the following:
NAME                      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
memcached-operator-long   1         1         1            0           15h
The main big difference here is that I have renamed the operator to "memcached-operator-long"
moreover, when from command line I execute, i get the following output:
"kubectl get pods
NAME                                       READY     STATUS             RESTARTS   AGE
memcached-operator-long-6b45cc5d84-dhtr2   0/1       CrashLoopBackOff   30         15h"
Environment

operator-sdk version:

operator-sdk version v0.3.0+git

Kubernetes version information:
Insert output of kubectl version here
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0+b81c8f8", GitCommit:"b81c8f8", GitTreeState:"clean", BuildDate:"2019-01-13T08:18:56Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
"I'm using minishift"

Are you writing your operator in ansible, helm, or go?
Go

Possible Solution

Additional context
Add any other context about the problem here.

@spanichella can you provide details on how you built the operator. The problem seems to be at least judging by the logs the binary is missing from the container.
https://github.com/operator-framework/operator-sdk/blob/master/doc/ansible/user-guide.md#build-and-run-the-operator

Dear @LiliC , Attached you find a pdf of the process followed to build the operator.
It is very detailed
Ansible operator.pdf
so that you can get how I did build it.
Cheers,
Sebastiano

@spanichella
The problem appears that you update the tasks/main.yml to use the command memcachedansible with is not the correct command, if you change this to memchached then this works.
Closing as I was able to reproduce locally and also fix the problem with this change. Please re-open if this is still a bug


✏ Fix typos in configuration.md

Thank you for the typo corrections. It may take a while to affect the web site, since it is only updated when I do a release to make sure that it is in sync with the code


Chapter 2 - Error while trying to run the ingest app on App Engine: first service must be 'default' service

ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: The first service (module) you upload to a new application must be the 'default' service (module). Please upload a version of the 'default' service (module) before uploading a version for the 'flights' service (module). See the documentation for more information. Python: (https://developers.google.com/appengine/docs/python/modules/#Python_Uploading% modules) Java: (https://developers.google.com/appengine/docs/java/modules/#Java_Uploading% modules)

Shall I change the service name to default?

I think you missed the step to initialize app engine:

Initialize a default AppEngine application in your project by running ./init_appengine.sh.


UI: Update pin/unpin icons

Update the pin/unpin icons to newer ones provided by UX.

This is a bad cherry-pick. Will try to manually backport the changes.


How to set environment variables?

Hi,
Noob question, but how do I set environment variables for the program?

It's a fair question. This is going to vary a bit between OS (I'll note I only built this on Linux, so I've no idea how well it works on Windows). I'm afraid StackOverflow might give some better advice than I can for each OS (Windows example, Linux example).

Thanks. Was using Linux, and the export KEY=value commands worked!


Is it possible: text wrap / break on specific place in word

Is it possible?
Say I got a translation going "pineapple". But the component the text is being translated in isn't big enough to fit "pineapple" on one line.
It shows as:
pineap
 ple

Can I specify where the word should break, so it would show like this:
pine-       or    pine
apple             apple

thanks for an otherwise nicely working library!

I have no idea myself :P
But this does seem an issue of the library itself though...

Hehe that's okay, I found a way. For HTML you can use  elements and add css property of display: inline-block (see stackoverflow answer).
Now, to be honoust, the reason I made this issue here is because I was having this problem in React Native. Since there's an I18n plugin which is based on this library I thought it would be best to come straight to this repository and ask my issue here.
But I also have a solution for the issue in React Native (just in case of future people with a similar problem read this):
In react native you can do this to solve this problem:
    <View style={ [{ flexDirection: 'column'}] }>
       <Text>
         pine
       </Text>
       <Text>
         apple
       </Text>
     </View>

It will still write "pineapple" if there's enough place in the parent component, and break on pine/apple if there isn't enough.
Can be closed!

Well the solution is also language specific
If there is a language which require the word representing "pineapple" as one word (no line break)
Then that solution doesn't work :P
Well let's hope we will never encounter that language :D

that's true. I believe that, even with my solutions I found and presented above, I saw that simply finding synonyms for the words in the other languages (if possible), or fiddling with the width/padding/margin... when I couldn't fit it completely was also necessary.
I'll just blame it as 'one of those hoops you have to jump through' if you so desperately want multi-language support for your app/website/...
Cheers Pika


Use development version of distributed in gpuCI build

This ensures that our gpuCI build is using the latest main branch of distributed (similar to our other CI builds). I think we need to do this here instead of over in https://github.com/rapidsai/dask-build-environment since the images there are built nightly and may not contain the latest commits to distributed (though my knowledge of how docker pull works may not be correct)
xref https://github.com/dask/dask/issues/7975
cc @charlesbluca @quasiben

It looks like we're getting some test failures on main now (xref https://github.com/dask/dask/pull/7978). I'll suggest we put this PR on hold and focus on resolving those failures first


Hi, how many hours needed for one pretrain process using 10 Nvidia A5000?

See title.

Hi @Ruiyuan-Zhang
Base: approximately 87 hours
Medium: around 32 hours
Small:  8.7 hours

Thx,  (～￣▽￣)～


[HITNET] How can I train my own models?

I'm interested in training my own models using a dataset I've created myself. I currently have pretrained models from here hitnet, but I'm unsure about the training process they underwent. Specifically, I'm curious about which files and parameters were used. Can anyone provide guidance on how I can train my own models using TensorFlow?

Why can't I find the pre-trained models on the official website? Would you be able to upload a copy for me? I would be very grateful. Thank you.

What do you mean you can't find them? They are available here: hitnet. You can manually download the .pb file if you want. Just open the predict_middlebury.sh file, and you'll find a link. Copy this link into your browser and add the model name at the end. For the Middlebury pretrained model, it would be: https://storage.googleapis.com/tensorflow-graphics/models/hitnet/default_models/middlebury_d400.pb.
I hope this is what you meant :)


add GPT-4o Advanced Voice Mode prompt

for both of your PRs, I ask you two things please:

make sure you attribute it to the proper author if you are not the one who figured it out. for instance, I attribute elder_plinius in various places
make sure you also update the corresponding table of contents file (README.md) and in the proper folder

Finally, how did you verify the work if you are the one who did it?


Parametrize

Fixes #1
/cc @ionelmc

Current coverage is 100.00%

Merging #8 into master will not affect coverage as of e7e4ab0

@@            master      #8   diff @@
======================================
  Files            6       8     +2
  Stmts          250     307    +57
  Branches        29      40    +11
  Methods          0       0
======================================
+ Hit            250     307    +57
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of e7e4ab0

Powered by Codecov. Updated on successful CI builds.

Awesome stuff :D

@ionelmc before I merge, can I validate that this satisfies your use case?

It mostly does. I miss a "skip" option tho - eg: you can't run django 1.9 on python 2.6. That could be added later right?
For reference, you can "skip a parameter" in pytest: http://pytest.org/latest/skipping.html?highlight=parametrize#skip-xfail-with-parametrize

@ionelmc yeah. You're welcome to file another bug for that.
In the meantime, that one isn't hard to do within the session itself:
def session_blah(session, foo):
    if foo in ('bad', 'worse'):
        print('Not running with arg {}.format(foo)
        return


Automated cherry pick of #4155: ctyun sync bugfix

Cherry pick of #4155 on release/2.13.
#4155: ctyun sync bugfix

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.13@0dbf305). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.13   #4156   +/-   ##
==============================================
  Coverage                ?   6.89%
==============================================
  Files                   ?     519
  Lines                   ?   87733
  Branches                ?       0
==============================================
  Hits                    ?    6049
  Misses                  ?   81185
  Partials                ?     499

Flag
Coverage Δ

#aFlag
6.89% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/guests.go
0.56% <ø> (ø)

pkg/compute/models/disks.go
0.58% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0dbf305...1fb48cd. Read the comment docs.

/lgtm

/approve


Email appears good in gmail, web outlook, but not in desktop outlook

Hello,
I am new to mjml, using it to prepare a newsletter campaign in mailjet.
The email appears right in gmail and web outlook, however in desktop outlook, it takes the full screen width, and the photos at the bottom of the email aren't one next to the other, but above (eventhough I use GROUP).
In the code below I removed the photos and the weblinks
MJML code Used
https://mjml.io/try-it-live/HkPmkpMFD
MJML version:
mailjet version - 4.6.3
Email clients the bug is seen on:
Outlook - office 365 ProPlus - version 1902
Thank you for the help

How did you send your test email, can you share some screenshot of the issue ? As it looks fine on Email On Acid and with default templates :

Thanks for the reply.
The email was sent using the TEST email in mailjet campaign (envoyer un email de test)
below screenshot1 of the bottom of the email in outlook. (screenshot2 is gmail)
As you can see the wrapper borders have the same width as the screen
and the social media icons aren't aligned

GMAIL

It's weird that your container goes to full width here, can you try with a minimal template like https://mjml.io/try-it-live/templates/racoon, I doubt Mailjet is altering the HTML here ?

same result with Raccon mail.
I copied the model in my mailjet and sent a test mail to outlook.
the email has the screen width, and all the photos are one above the other

Can you try with https://putsmail.com/ to send the racoon mail ?

UPDATE
indeed, my email code is good.
The issue is with my outlook.
My mailjet emails go to a folder named "Newsletter".
When they go to the inbox, the format is good.
I guess that outlook messes with the format when moving the email from inbox to newsletter.
Sorry for the inconvenience and that you for the support.

Ugh, the fact that Outlook would mess with the HTML of the email when placing it into a folder really mesmerizes me (luckily it's nothing new from Outlook). Thanks for sharing @georgesbc.


Avoid crashing due to malformed paths creating URLs

In some cases, file manager APIs may be called with malformed string paths. We correctly throw an error in those cases, but when throwing an error we try to initialize a URL from the path. In certain FOUNDATION_FRAMEWORK scenarios this leads to calling into an NSURL initializer which crashes. This code works around that crash by creating an internal failable path we can take instead when we know we're in a scenario where we may have malformed paths.

@swift-ci please test


Voigtdiagnostic

Adds the voigt eta parameter to the diagnostic tool.

Ok, approving this one because of split code between here and pull #127
The above comment will be fixed in that pull request.


Link to or explain the Microsoft Teams admin center

Hello - These docs keep talking about the Microsoft Teams admin center but I don't know what that is and Googling for it returns SERPs that just point back to these docs.
My story is: I'm looking around Teams as a new user to see if I can use it to talk to other people on Teams, especially make video and voice calls, i.e. to replace Skype since none of my friends use it anymore and WhatsApp desktop has no voice calling. Zoom is too conference-call-y, I don't use Facetime/Apple and I don't want to use my phone given that I have a webcam and condenser mic.
So I've setup Teams to check it out. I've always used and recommended Slack for my clients, since it was first to market. I work alone, so I am on the free tier; I don't want to pay monthly to explore, or to make occasional calls (given alternatives).
I want to search for someone (ironically today, an MS sales exec!) and add him and be able to video call him, ad-hoc. It seems I can't. Searching for him in various search boxes, yields no results.
It feels like Skype was thrown under a bus and no product was there to replace it, or at least the UX/docs aren't guiding me into the pit of success with Teams as a noob.
What am I missing? Should this be simple? Is this a paid feature? Do I need to enable something in the admin center?
Anyway, sorry I've turned this into a product support issue: my main point is that I've clicked around in Teams and searched the web and I don't know where the "admin center" is that you're talking about. Thanks.

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

ID: 59900927-5e5f-77a4-04be-e05a91330fca
Version Independent ID: 1e4d6b87-f57c-fa45-1630-3c32b821d93c
Content: Manage external access (federation) - Microsoft Teams
Content Source: Teams/manage-external-access.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

@lukepuplett Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@lukepuplett Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

@scanum Thanks but...
"You must be an admin for a business subscription to use these support methods"
(at least these docs are clear that I need to be a paid subscriber)
I did say above that I work alone and I'm on the free-tier so I don't have a business subscription; I'm just looking around with my personal account. So perhaps the docs aren't explaining that chatting or calling external users is not allowed for free-tier users.
Perhaps I'm missing something but it really looks to me that Microsoft bought leading web video calling app Skype and all its users at great expense, then effectively obsoleted that app for a whole class of business workers, but forgot to build Skype's primary feature in the replacement Teams app, clearing the way for competitors to fill the space.


A bug about C#

First, I wrote some code like this.
using System;

namespace FirstApp
{
    class HelloWorld
    {
        static void Main()
        {
            Console.WriteLine("Hello world !");
        }
    }

    class Hello
    {
        static void Main()
        {
            Console.Write("Hello world! 2");
        }
    }
}

Clearly,it's wrong.

but if I delete the class above ,the error will disappear.
Suddenly, although we can compile it correctly ,but we could still see that the error was still there.

We can know there was no errors in the window below

I need concrete steps to reproduce issue 100% of the time.


Decouple voting

At the moment there is an integrated version of gmod-mapvote with fixed parameters.
It would be nice if it is possible to decouple the voting to allow own voting scripts or make the existing one more configurable.

I would love to have this work done


Let UriEndpoint ToString return the Uri

Summary of the changes (Less than 80 chars)

Overriding the ToString Method of UriEndpoint to return the ToString Result if the Uri Property

Addresses #12656

@ste1nstone think you might need to update ref assemblies. Could you rin the instructions provided in https://github.com/aspnet/AspNetCore/blob/master/docs/ReferenceAssemblies.md#when-changing-public-api in the  src/Servers/Connections.Abstractions/src directory?

/azp run AspNetCore-ci

/azp run AspNetCore-ci

/azp run AspNetCore-ci

Hi @ste1nstone. Sorry for the delay merging your PR. There's still one more reference assembly that needs to be updated before we can merge the PR. You can either rerun .\eng\scripts\GenerateReferenceAssemblies.ps1 yourself, or you can cherry-pick https://github.com/aspnet/AspNetCore/commit/4baa717811a9c396060fe337e75bd056198d4347. Thanks!

Hi @halter73 no problem.
Hope that no everything is OK.

Thanks @ste1nstone!


Make sure jnind4j.dll links with psapi.dll, as now required by JavaCPP on Windows

Refer to this link for build results (access rights to CI server needed):
/job/nd4j_PR/77/


make ex_machina dep for test only

This was causing unnecessary dependency conflicts

Good catch! Thanks for the PR!

better make a new release for that :+1:

@princemaple Yep :) Just been a bit busy haha

It's up! https://hex.pm/packages/bamboo


Coin change solution fails simple test cases

It is working as expected.
If you look at code its pretty clear if solution is not possible it returns Integer.MAX_VALUE which is<PHONE_NUMBER> . I never said it will return -1 if solution is not possible.
Second for cases like [186, 419, 83, 408]for amount:6249 . It is returning 20. I dunno what code you are running. I ran it right now and it returns 20 without any problem.
https://github.com/mission-peace/interview/blob/master/src/com/interview/dynamic/CoinChangingMinimumCoin.java Are you talking about this code??
Bottom up also returns Integer.MAX_VaLUE if solution is not possible. I have updated the docs to say that.
https://github.com/mission-peace/interview/commit/73384e088a5a21625c3430970807893fb19b892a

Thanks for the response, yes I am referring to the code you pointed.
Yes, I agree for the case of -1, we can change it.
I just tried the code for the topdown approach, it failed for the following cases, where the expected return is not -1:
coins:[1, 2, 5]...for amount:11..expected return coins:3...got:2147483647
coins:[186, 419, 83, 408]...for amount:6249..expected return coins:20...got:2147483647
coins:[1, 2, 3]...for amount:5..expected return coins:2...got:2147483647

These are the just few test cases that I tried.

[186, 419, 83, 408]...for amount:6249 Got 20
[1, 2, 5]...for amount:11 Got 3
[1, 2, 3]...for amount:5 Got 2
Code is running as expected. Are you sure you have exact same code as on github?

Used this code https://github.com/mission-peace/interview/blob/master/src/com/interview/dynamic/CoinChangingMinimumCoin.java
The bottomup approach is good for me. No worries about the other approaches for now.