K8SPXC-1207 - Implement dynamic test execution

JUST A DRAFT, DO NOT MERGE
CHANGE DESCRIPTION
Problem:
Short explanation of the problem.
Cause:
Short explanation of the root cause of the issue if applicable.
Solution:
Short explanation of the solution we are providing with this PR.
CHECKLIST
Jira

[ ] Is the Jira ticket created and referenced properly?
[ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[ ] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Are E2E tests passing?
[ ] Are unit tests passing?
[ ] Are linting tests passing?
[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?
[ ] Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

[ ] Are all needed new/changed options added to default YAML files?
[ ] Are the manifests (crd/bundle) regenerated if needed?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PXC version?
[ ] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

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

haproxy-5-7
failed

haproxy-8-0
failed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 1

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/c8d12ba351bec08ae4ef8ec6a0ba024bfabb6bf2
image: perconalab/percona-xtradb-cluster-operator:PR-1346-c8d12ba3

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

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

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 1

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/8343e91a0732516fcf558cde6072b2c0507e9c09
image: perconalab/percona-xtradb-cluster-operator:PR-1346-8343e91a

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
failed

haproxy-8-0
failed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/0e6abf85a2fa13b023befae01f53cb9d7f2142c1
image: perconalab/percona-xtradb-cluster-operator:PR-1346-0e6abf85

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
failed

haproxy-8-0
failed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/0e6abf85a2fa13b023befae01f53cb9d7f2142c1
image: perconalab/percona-xtradb-cluster-operator:PR-1346-0e6abf85

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/92899df73809e4be134225a1d892e9e17a0e188f
image: perconalab/percona-xtradb-cluster-operator:PR-1346-92899df7

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
failed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
failed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/0e35334952948eab5ddb907deeaaaa7df64a7107
image: perconalab/percona-xtradb-cluster-operator:PR-1346-0e353349

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/0e35334952948eab5ddb907deeaaaa7df64a7107
image: perconalab/percona-xtradb-cluster-operator:PR-1346-0e353349

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/0e35334952948eab5ddb907deeaaaa7df64a7107
image: perconalab/percona-xtradb-cluster-operator:PR-1346-0e353349

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/3027db5d1c5f01ff703969e9e77d60432ac06fa9
image: perconalab/percona-xtradb-cluster-operator:PR-1346-3027db5d

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/078bb55e2eeabea278a6f7a1ef0e94fcac469007
image: perconalab/percona-xtradb-cluster-operator:PR-1346-078bb55e

Test name
Status

We run 0 out of 1

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/1f6a23d490c3c4c90ba84b324ddb6cc0ec736cf4
image: perconalab/percona-xtradb-cluster-operator:PR-1346-1f6a23d4

Test name
Status

affinity- 8-0
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/affinity- 8-0.log)

auto-tuning- 8-0
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/auto-tuning- 8-0.log)

cross-site- 8-0
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/cross-site- 8-0.log)

demand-backup-cloud- 8-0
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/demand-backup-cloud- 8-0.log)

demand-backup-encrypted-with-tls- 8-0
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/demand-backup-encrypted-with-tls- 8-0.log)

demand-backup- 8-0
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/demand-backup- 8-0.log)

haproxy- 5-7
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/haproxy- 5-7.log)

haproxy- 8-0
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/haproxy- 8-0.log)

init-deploy- 5-7
[failed](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/init-deploy- 5-7.log)

init-deploy- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/init-deploy- 8-0.log)

limits- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/limits- 8-0.log)

monitoring-2-0- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/monitoring-2-0- 8-0.log)

one-pod- 5-7
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/one-pod- 5-7.log)

one-pod- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/one-pod- 8-0.log)

pitr- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/pitr- 8-0.log)

proxy-protocol- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/proxy-protocol- 8-0.log)

proxysql-sidecar-res-limits- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/proxysql-sidecar-res-limits- 8-0.log)

recreate- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/recreate- 8-0.log)

restore-to-encrypted-cluster- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/restore-to-encrypted-cluster- 8-0.log)

scaling-proxysql- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/scaling-proxysql- 8-0.log)

scaling- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/scaling- 8-0.log)

scheduled-backup- 5-7
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/scheduled-backup- 5-7.log)

scheduled-backup- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/scheduled-backup- 8-0.log)

security-context- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/security-context- 8-0.log)

smart-update1- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/smart-update1- 8-0.log)

smart-update2- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/smart-update2- 8-0.log)

storage- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/storage- 8-0.log)

tls-issue-cert-manager-ref- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/tls-issue-cert-manager-ref- 8-0.log)

tls-issue-cert-manager- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/tls-issue-cert-manager- 8-0.log)

tls-issue-self- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/tls-issue-self- 8-0.log)

upgrade-consistency- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/upgrade-consistency- 8-0.log)

upgrade-haproxy- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/upgrade-haproxy- 8-0.log)

upgrade-proxysql- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/upgrade-proxysql- 8-0.log)

users- 5-7
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/users- 5-7.log)

users- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/users- 8-0.log)

validation-hook- 8-0
[NA](https://percona-jenkins-artifactory-public.s3.amazonaws.com/cloud-pxc-operator/PR-1346/e703982d/validation-hook- 8-0.log)

We run 9 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/e703982dc584600638abc804cb6c16440fb4345d
image: perconalab/percona-xtradb-cluster-operator:PR-1346-e703982d

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/a19bd32cfaffa8c8e5b4799b21522b10476027d6
image: perconalab/percona-xtradb-cluster-operator:PR-1346-a19bd32c

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/a19bd32cfaffa8c8e5b4799b21522b10476027d6
image: perconalab/percona-xtradb-cluster-operator:PR-1346-a19bd32c

Test name
Status

affinity-8-0
NA

auto-tuning-8-0
NA

cross-site-8-0
NA

demand-backup-cloud-8-0
NA

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

demand-backup-8-0
NA

haproxy-5-7
NA

haproxy-8-0
NA

init-deploy-5-7
NA

init-deploy-8-0
NA

limits-8-0
NA

monitoring-2-0-8-0
NA

one-pod-5-7
NA

one-pod-8-0
NA

pitr-8-0
NA

proxy-protocol-8-0
NA

proxysql-sidecar-res-limits-8-0
NA

recreate-8-0
NA

restore-to-encrypted-cluster-8-0
NA

scaling-proxysql-8-0
NA

scaling-8-0
NA

scheduled-backup-5-7
NA

scheduled-backup-8-0
NA

security-context-8-0
NA

smart-update1-8-0
NA

smart-update2-8-0
NA

storage-8-0
NA

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

tls-issue-cert-manager-8-0
NA

tls-issue-self-8-0
NA

upgrade-consistency-8-0
NA

upgrade-haproxy-8-0
NA

upgrade-proxysql-8-0
NA

users-5-7
NA

users-8-0
NA

validation-hook-8-0
NA

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/4708dbab9a82f2fb3fc383ed9a365242ed2cbff9
image: perconalab/percona-xtradb-cluster-operator:PR-1346-4708dbab

Test name
Status

affinity-8-0
NA

auto-tuning-8-0
NA

cross-site-8-0
NA

demand-backup-cloud-8-0
NA

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

demand-backup-8-0
NA

haproxy-5-7
NA

haproxy-8-0
NA

init-deploy-5-7
NA

init-deploy-8-0
NA

limits-8-0
NA

monitoring-2-0-8-0
NA

one-pod-5-7
NA

one-pod-8-0
NA

pitr-8-0
NA

proxy-protocol-8-0
NA

proxysql-sidecar-res-limits-8-0
NA

recreate-8-0
NA

restore-to-encrypted-cluster-8-0
NA

scaling-proxysql-8-0
NA

scaling-8-0
NA

scheduled-backup-5-7
NA

scheduled-backup-8-0
NA

security-context-8-0
NA

smart-update1-8-0
NA

smart-update2-8-0
NA

storage-8-0
NA

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

tls-issue-cert-manager-8-0
NA

tls-issue-self-8-0
NA

upgrade-consistency-8-0
NA

upgrade-haproxy-8-0
NA

upgrade-proxysql-8-0
NA

users-5-7
NA

users-8-0
NA

validation-hook-8-0
NA

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/d9d98d0b8131cfcb03c4bc2156f01f6735bc3d17
image: perconalab/percona-xtradb-cluster-operator:PR-1346-d9d98d0b

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failed

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

demand-backup-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
NA

limits-8-0
NA

monitoring-2-0-8-0
NA

one-pod-5-7
NA

one-pod-8-0
NA

pitr-8-0
NA

proxy-protocol-8-0
NA

proxysql-sidecar-res-limits-8-0
NA

recreate-8-0
NA

restore-to-encrypted-cluster-8-0
NA

scaling-proxysql-8-0
NA

scaling-8-0
NA

scheduled-backup-5-7
NA

scheduled-backup-8-0
NA

security-context-8-0
NA

smart-update1-8-0
NA

smart-update2-8-0
NA

storage-8-0
NA

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

tls-issue-cert-manager-8-0
NA

tls-issue-self-8-0
NA

upgrade-consistency-8-0
NA

upgrade-haproxy-8-0
NA

upgrade-proxysql-8-0
NA

users-5-7
NA

users-8-0
NA

validation-hook-8-0
NA

We run 9 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/5d10771137d2563c1e067abf84526d42e69fa4e4
image: perconalab/percona-xtradb-cluster-operator:PR-1346-5d107711

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failed

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

demand-backup-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
NA

recreate-8-0
NA

restore-to-encrypted-cluster-8-0
NA

scaling-proxysql-8-0
NA

scaling-8-0
NA

scheduled-backup-5-7
NA

scheduled-backup-8-0
NA

security-context-8-0
NA

smart-update1-8-0
NA

smart-update2-8-0
NA

storage-8-0
NA

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

tls-issue-cert-manager-8-0
NA

tls-issue-self-8-0
NA

upgrade-consistency-8-0
NA

upgrade-haproxy-8-0
NA

upgrade-proxysql-8-0
NA

users-5-7
NA

users-8-0
NA

validation-hook-8-0
NA

We run 16 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/5d10771137d2563c1e067abf84526d42e69fa4e4
image: perconalab/percona-xtradb-cluster-operator:PR-1346-5d107711

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/a19bd32cfaffa8c8e5b4799b21522b10476027d6
image: perconalab/percona-xtradb-cluster-operator:PR-1346-a19bd32c

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/1e078c4a5a77dce3c5966e944384e4cc02574c4d
image: perconalab/percona-xtradb-cluster-operator:PR-1346-1e078c4a

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/e3f42eb57118f18759b945412aa83426f58c96fa
image: perconalab/percona-xtradb-cluster-operator:PR-1346-e3f42eb5

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/e3f42eb57118f18759b945412aa83426f58c96fa
image: perconalab/percona-xtradb-cluster-operator:PR-1346-e3f42eb5

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
failed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
failed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
failed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
failed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1346/commits/b8c8201229b4757d58ef494b183b583f9d10c8bf
image: perconalab/percona-xtradb-cluster-operator:PR-1346-b8c82012


Init

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@8c9cb60). Click here to learn what that means.
 Consider uploading reports for the commit cb7e6d7 to get more accurate results

Additional details and impacted files
@@           Coverage Diff            @@
##             main       #17   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         3
  Lines           ?        13
  Branches        ?         0
========================================
  Hits            ?        13
  Misses          ?         0
  Partials        ?         0

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


Module build fails with empty binding.gyp

Hello, I'm trying to use audify (https://github.com/almoghamdani/audify) in an electron app with electron-forge.
When the electron-rebuild step runs it tries to rebuild audify build fails with the error at the end.
The module actually uses cmake-js to build and builds fine if build using npm run rebuild. It actually worked fine with electron-rebuild at some point but something updated and it doesn't work anymore. not sure if the issue is in electron-rebuild or node-gyp.
\ Building module: audify, Completed: 0gyp: Unable to find targets in build file binding.gyp while trying to load binding.gyp
Error: `gyp` failed with exit code: 1
    at ChildProcess.onCpExit (C:\code\wiservibe\electron\node_modules\@electron\rebuild\node_modules\node-gyp\lib\configure.js:325:16)
    at ChildProcess.emit (node:events:513:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)

× Rebuild Failed

An unhandled error occurred inside electron-rebuild
node-gyp failed to rebuild 'C:\code\wiservibe\electron\node_modules\audify'

Error: node-gyp failed to rebuild 'C:\code\wiservibe\electron\node_modules\audify'
    at ChildProcess.<anonymous> (C:\code\wiservibe\electron\node_modules\@electron\rebuild\lib\module-type\node-gyp\node-gyp.js:118:24)
    at ChildProcess.emit (node:events:513:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)

This is caused by the same issue as https://github.com/electron/rebuild/issues/1116.
See https://github.com/electron/rebuild/issues/1116#issuecomment-1973877557 for a workaround.

It doesn't seem like node-rebuild does anything at all when forced to run with<EMAIL_ADDRESS>It just hangs there claiming to be building but no compiler commands are actually running


imgui: Upgrade parking_lot to 0.12 with windows-rs bindings

parking_lot now uses windows-rs's windows-sys crate, officially developed and vetted by Microsoft - the bindings are autogenerated from metadata and faster to compile too.
See also https://github.com/Amanieu/parking_lot/pull/311.

Thanks! The CI failures all seem entirely unrelated to this change (and unrelated to any existing failures on the main branch), so merging

Thanks @dbr! Would you mind porting this to the 0.8.2 branch and doing a 0.8.3 release with it?


clean up istio policy proxy bootstrap file

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

integ-telemetry-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

integ-telemetry-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-telemetry-k8s-tests_istio

release-test_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

integ-telemetry-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-telemetry-k8s-tests_istio

release-test_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-test_istio

integ-distroless-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

integ-telemetry-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-telemetry-k8s-tests_istio

release-test_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-test_istio

integ-distroless-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

integ-telemetry-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-telemetry-k8s-tests_istio

release-test_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-test_istio

integ-distroless-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

integ-telemetry-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-telemetry-k8s-tests_istio

release-test_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-test_istio

integ-distroless-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

integ-telemetry-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-telemetry-k8s-tests_istio

release-test_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-test_istio

integ-distroless-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-notes_istio

integ-telemetry-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-telemetry-k8s-tests_istio

release-test_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test release-test_istio

integ-distroless-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
60666fc36a4f2bcb31ab01c2e539f068e0f17b24
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


deprecated  dependencies

Description
[-] build: + npm install
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
[-] build: npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
[-] build: npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Switch to @scure/base for audited version of the lib & updates
[-] build: npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
[-] build: npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Please update to the latest object-keys
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to v7.0.2+ of superagent.  We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing.  See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
[-] build: npm WARN deprecated<EMAIL_ADDRESS>Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410

@xmonader  the old weblets is deprecated, should resolve this still?

it's shouldn't be packaged indeed, it will be removed in the 3.11 deployment :)


Query:  Why ramda is used?

I have a doubt why ramda component is used in this library. why is it used and what is the use of it in other developments. Just a query to know, so that i can get use of this ramda components in my projects if i find it useful.

Ramda https://ramdajs.com/
Useful links - https://codeburst.io/currying-in-javascript-ba51eb9778dc
Specifically designed for functional programming
The primary distinguishing features of Ramda are:

Ramda emphasizes a purer functional style. Immutability and side-effect free functions are at the heart of its design philosophy. This can help you get the job done with simple, elegant code.
Ramda functions are automatically curried. This allows you to easily build up new functions from old ones simply by not supplying the final parameters.
The parameters to Ramda functions are arranged to make it convenient for currying. The data to be operated on is generally supplied last.

The last two points together make it very easy to build functions as sequences of simpler functions, each of which transforms the data and passes it along to the next. Ramda is designed to support this style of coding.

Ramda

pipe
http://randycoulman.com/blog/2016/05/31/thinking-in-ramda-combining-functions/

Ramda provides the pipe function, which takes a list of one or more functions and returns a new function.
The new function takes the same number of arguments as the first function it is given. It then “pipes” those arguments through each function in the list. It applies the first function to the arguments, passes its result to the second function and so on. The result of the last function is the result of the pipe call.
e.g.
function addition(a,b){
return a+b
}
function display(result){
console.log(result)
}
var myfun=R.pipe(addition,display);
myfun(11,2)

applySpec
const getMetrics = R.applySpec({
sum: R.add,
nested: { mul: R.multiply }
});
getMetrics(2, 4); // => { sum: 6, nested: { mul: 8 } }

props and propsOr
const alice = {
name: 'ALICE',
age: 101
};
const favorite = R.prop('favoriteLibrary');
const favoriteWithDefault = R.propOr('Ramda', 'age');

favorite(alice);  //=> undefined //there no key favoriteLibrary
favoriteWithDefault(alice);  //=> // 101

evolve
Creates a new object by recursively evolving a shallow copy of object, according to the transformation functions. All non-primitive properties are copied by reference.


Is this project abandoned?

If someone wanted to take over, are you open to that idea?

It sure seems like it is... Kind of a bummer because the functionality it is promising would be awesome!


Passing Props to Components in Stepper

Hi there, first of all thank you for sharing the project, I think this complements perfectly react-toolbox.
I would like to know if there is a way of passing prps to the components within the stepper:
<Stepper pages={[
  {
    component: PageOne,
  },
  {
    component: PageTwo,
  },
  {
    component: PageThree,
  },
]}>

In my case I would like to define "PageOne", "PageTwo" and "PageThree" also with props...
Thanks for the response and apologies if it is something very easy that should be known.

Hey! Glad that you like it.
You can use render over component:
<Stepper pages={[
  {
    render: () => <PageOne myProp='Hello' />,
  },
]}>

Thanks!! I forgot to answered you!


Update cloud-metrics-layer.md

Description & motivation

To-do before merge

Prerelease docs
If this change is related to functionality in a prerelease version of dbt (delete if not applicable):

[ ] I've added versioning components, as described in "Versioning Docs"
[ ] I've added a note to the prerelease version's Migration Guide

Checklist
If you added new pages (delete if not applicable):

[ ] The page has been added to website/sidebars.js
[ ] The new page has a unique filename

If you removed existing pages (delete if not applicable):

[ ] The page has been removed from website/sidebars.js
[ ] An entry has been added to _redirects
[ ] Run link testing to update the links that point to the deleted page

hey @azzam34 , this page has been deleted. are you ok with us closing this pr?

Yeah that's alright with me!


Per site social auth, unique for email AND SITE_ID?

I've got an application that hosts multiple sites, using dynamicsiteslite.  Each site needs to have its own unique users, so my user model is setup to be unique for email and site_id.  I've managed to reconcile each site having unique secrets and keys, so the correct Facebook app (for example) is being hit for authorization.  If I've not attempted to log into any sites using the given backend, a new account is created that correctly references the appropriate site_id.  My problem comes when the user already exists for another site - the auth backends don't check site id when retrieving an account so the account for the wrong website is returned.  Is there any way I can add this check without monkey patching the backends?

You don't need to monkey patch the backends, it's enough to define your own storage (you can inherit from the built-in one), and override the get_user method to take the current site_id into account, you might need to override other user related methods too.
The storage is defined in the utils.py module, and it can be overridden with the SOCIAL_AUTH_STORAGE setting.

Fantastic!  I had my eye on SOCIAL_AUTH_STORAGE but wasn't sure.  Thanks!  I've got most of a solution put together, but I'm running into an error.  Can you confirm I'm going about this the right way?  I've tried to override as little as possible...
import six

from django.contrib.sites.models import Site
from django.conf import settings

from social.apps.django_app.default.models import DjangoUserMixin as SocialAUth_DjangoUserMixin, DjangoStorage as SocialAuth_DjangoStorage

class SocialAuthUserMixinOverride(SocialAUth_DjangoUserMixin):
    """
    Override social auth storage class' user methods to be site specific
    """

    @classmethod
    def user_exists(cls, *args, **kwargs):
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        super(SocialAuthUserMixinOverride).user_exists(cls, *args, **kwargs)

    @classmethod
    def create_user(cls, *args, **kwargs):
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        super(SocialAuthUserMixinOverride).create_user(cls, *args, **kwargs)

    @classmethod
    def get_user(cls, pk=None, **kwargs):
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        super(SocialAuthUserMixinOverride).get_user(cls, pk=pk, **kwargs)

    @classmethod
    def get_users_by_email(cls, email):
        user_model = cls.user_model()
        email_field = getattr(user_model, 'EMAIL_FIELD', 'email')
        return user_model.objects.filter(**{email_field + '__iexact': email,
                                            # filter by site_id
                                            'site': Site.objects.get(pk=settings.SITE_ID)})

    @classmethod
    def get_social_auth(cls, provider, uid):
        if not isinstance(uid, six.string_types):
            uid = str(uid)
        try:
            return cls.objects.get(provider=provider, uid=uid,
                                    # filter by site_id
                                    user__site=Site.objects.get(pk=settings.SITE_ID))
        except cls.DoesNotExist:
            return None

class SocialAuthStorageOverride(SocialAuth_DjangoStorage):
    """
    Override social auth storage class' user methods to be site specific
    """
    user = SocialAuthUserMixinOverride

In settings.py:
SOCIAL_AUTH_STORAGE = 'realtors.apps.registration.models.SocialAuthStorageOverride'
When attempting to login I'm getting "type object 'SocialAuthUserMixinOverride' has no attribute 'DoesNotExist'", pointing to the line "except cls.DoesNotExist:" in the function "get_social_auth".  If you can point me in the right direction I'd really appreciate it.

Yeah, the trick is not going to be as simple as you thought, but you are in the correct path. What you need now is:

Define your own UserSocialAuth model, make it inherit from your custom mixin
Use that model in the configuration for SocialAuthStorageOverride

from django.db import models
from social.apps.django_app.default.models import Nonce, Association, Code, DjangoStorage

class UserSocialAuth(models.Model, SocialAuthUserMixinOverride):
    class Meta:
        db_table = 'social_auth_usersocialauth'

class SocialAuthStorageOverride(DjangoStorage):
    user = UserSocialAuth

You can avoid the mixin and directly define the overridden methods in the custom UserSocialAuth class.

Thanks again for all your help!  I tried what you wrote above, but it didn't have access to the field definitions.  Here's what I've got now:
from social.utils import setting_name
from social.apps.django_app.default.models import DjangoUserMixin as SocialAUth_DjangoUserMixin, DjangoStorage as SocialAuth_DjangoStorage, UserSocialAuth as SocialAuth_UserSocialAuth
from social.apps.django_app.default.fields import JSONField

USER_MODEL = getattr(settings, setting_name('USER_MODEL'), None) or \
             getattr(settings, 'AUTH_USER_MODEL', None) or \
             'auth.User'
UID_LENGTH = getattr(settings, setting_name('UID_LENGTH'), 255)
NONCE_SERVER_URL_LENGTH = getattr(
    settings, setting_name('NONCE_SERVER_URL_LENGTH'), 255)
ASSOCIATION_SERVER_URL_LENGTH = getattr(
    settings, setting_name('ASSOCIATION_SERVER_URL_LENGTH'), 255)
ASSOCIATION_HANDLE_LENGTH = getattr(
    settings, setting_name('ASSOCIATION_HANDLE_LENGTH'), 255)

class SocialAuthUserMixinOverride(SocialAUth_DjangoUserMixin):
    """
    Override social auth storage class' user methods to be site specific
    """

    @classmethod
    def user_exists(cls, *args, **kwargs):
        """
        Return True/False if a User instance exists with the given arguments.
        Arguments are directly passed to filter() manager method.
        """
        logger.info('Customer user_exists method triggered.')
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        if 'username' in kwargs:
            kwargs[cls.username_field()] = kwargs.pop('username')
        return cls.user_model().objects.filter(*args, **kwargs).count() > 0

    @classmethod
    def create_user(cls, *args, **kwargs):
        logger.info('Customer create_user method triggered.')
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        username_field = cls.username_field()
        if 'username' in kwargs and username_field not in kwargs:
            kwargs[username_field] = kwargs.pop('username')
        return cls.user_model().objects.create_user(*args, **kwargs)

    @classmethod
    def get_user(cls, pk=None, **kwargs):
        logger.info('Customer get_user method triggered.')
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        if pk:
            kwargs = {'pk': pk}
        try:
            return cls.user_model().objects.get(**kwargs)
        except cls.user_model().DoesNotExist:
            return None

    @classmethod
    def get_users_by_email(cls, email):
        logger.info('Customer get_users_by_email method triggered.')
        user_model = cls.user_model()
        email_field = getattr(user_model, 'EMAIL_FIELD', 'email')
        return user_model.objects.filter(**{email_field + '__iexact': email,
                                            # filter by site_id
                                            'site': Site.objects.get(pk=settings.SITE_ID)})

    @classmethod
    def get_social_auth(cls, provider, uid):
        logger.info('Customer get_social_auth method triggered.  cls = %s' % cls)
        if not isinstance(uid, six.string_types):
            uid = str(uid)
        try:
            return cls.objects.get(provider=provider, uid=uid,
                                    # filter by site_id
                                    user__site=Site.objects.get(pk=settings.SITE_ID))
        except cls.DoesNotExist:
            return None

class UserSocialAuth(models.Model, SocialAuthUserMixinOverride):
    """Social Auth association model"""
    user = models.ForeignKey(USER_MODEL, related_name='social_auth_user')
    provider = models.CharField(max_length=32)
    uid = models.CharField(max_length=UID_LENGTH)
    extra_data = JSONField()

    def __str__(self):
        return str(self.user)

    class Meta:
        """Meta data"""
        unique_together = ('provider', 'uid', 'user')
        db_table = 'social_auth_usersocialauth'

    @classmethod
    def get_social_auth(cls, provider, uid):
        try:
            return cls.objects.select_related('user').get(provider=provider,
                                                        uid=uid,
                                                        # filter by site_id
                                                        user__site=Site.objects.get(pk=settings.SITE_ID))
        except UserSocialAuth.DoesNotExist:
            return None

    @classmethod
    def username_max_length(cls):
        username_field = cls.username_field()
        field = UserSocialAuth.user_model()._meta.get_field(username_field)
        return field.max_length

    @classmethod
    def user_model(cls):
        user_model = UserSocialAuth._meta.get_field('user').rel.to
        if isinstance(user_model, six.string_types):
            app_label, model_name = user_model.split('.')
            return models.get_model(app_label, model_name)
        return user_model

class SocialAuthStorageOverride(SocialAuth_DjangoStorage):
    """
    Override social auth storage class' user methods to be site specific
    """
    user = UserSocialAuth

This seems to work okay for accounts that already exist, but if I attempt to create a new social auth account the request just spins, while cpu and memory usage climbs steadily to max on the server.
In a spirit of overriding as little as possible, I also tried inheriting from the mixin and creating a proxy model for UserSocialAuth, only overriding what I absolutely had to, like this:
class SocialAuthUserMixinOverride(SocialAUth_DjangoUserMixin):
    """
    Override social auth storage class' user methods to be site specific
    """

    @classmethod
    def user_exists(cls, *args, **kwargs):
        logger.info('Customer user_exists method triggered.')
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        super(SocialAuthUserMixinOverride).user_exists(cls, *args, **kwargs)

    @classmethod
    def create_user(cls, *args, **kwargs):
        logger.info('Customer create_user method triggered.')
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        super(SocialAuthUserMixinOverride).create_user(cls, *args, **kwargs)

    @classmethod
    def get_user(cls, pk=None, **kwargs):
        logger.info('Customer get_user method triggered.')
        # filter by site_id
        kwargs.update({'site': Site.objects.get(pk=settings.SITE_ID)})
        super(SocialAuthUserMixinOverride).get_user(cls, pk=pk, **kwargs)

    @classmethod
    def get_users_by_email(cls, email):
        logger.info('Customer get_users_by_email method triggered.')
        user_model = cls.user_model()
        email_field = getattr(user_model, 'EMAIL_FIELD', 'email')
        return user_model.objects.filter(**{email_field + '__iexact': email,
                                            # filter by site_id
                                            'site': Site.objects.get(pk=settings.SITE_ID)})

    @classmethod
    def get_social_auth(cls, provider, uid):
        logger.info('Customer get_social_auth method triggered.  cls = %s' % cls)
        if not isinstance(uid, six.string_types):
            uid = str(uid)
        try:
            return cls.objects.get(provider=provider, uid=uid,
                                    # filter by site_id
                                    user__site=Site.objects.get(pk=settings.SITE_ID))
        except cls.DoesNotExist:
            return None

class UserSocialAuth(SocialAuth_UserSocialAuth):
    """Social Auth association model"""

    class Meta:
        """Meta data"""
        proxy = True
        unique_together = ('provider', 'uid', 'user')
        db_table = 'social_auth_usersocialauth'

    @classmethod
    def get_social_auth(cls, provider, uid):
        try:
            return cls.objects.select_related('user').get(provider=provider,
                                                        uid=uid,
                                                        # filter by site_id
                                                        user__site=Site.objects.get(pk=settings.SITE_ID))
        except UserSocialAuth.DoesNotExist:
            return None

class SocialAuthStorageOverride(SocialAuth_DjangoStorage):
    """
    Override social auth storage class' user methods to be site specific
    """
    user = UserSocialAuth

The UserSocialAuth definition seems to work just as well, but I get " 'super' object has no attribute 'get_user' " when it tries to use the get_user method.
Thanks again for your help... gotta be getting close. :)


st-flash failed writing flash, but could succeed with --debug.

[x] Programmer/board type:  Stlink/v2
[x] Operating system: Arch Linux
[X] Stlink tools version and/or git commit hash: stlink 1.3.1
[X] Stlink commandline tool name: st-flash
[X] Target chip (and optional board): STM32F030F4p6. SSOP20, single chip with SSOP20_to_DIP breadbord.

st-flash write main.bin 0x8000000
Output:
st-flash 1.3.1
2017-05-07T19:47:42 INFO src/common.c: Loading device parameters....
2017-05-07T19:47:42 INFO src/common.c: Device connected is: F0 small device, id 0x10006444
2017-05-07T19:47:42 INFO src/common.c: SRAM size: 0x1000 bytes (4 KiB), Flash: 0x4000 bytes (16 KiB) in pages of 1024 bytes
2017-05-07T19:47:42 INFO src/common.c: Attempting to write 4772 (0x12a4) bytes to stm32 address: 134217728 (0x8000000)
Flash page at addr: 0x08001000 erased
2017-05-07T19:47:42 INFO src/common.c: Finished erasing 5 pages of 1024 (0x400) bytes
2017-05-07T19:47:42 INFO src/common.c: Starting Flash write for VL/F0/F3 core id
2017-05-07T19:47:42 INFO src/flash_loader.c: Successfully loaded flash loader in sram
  0/4 pages written2017-05-07T19:47:46 ERROR src/flash_loader.c: flash loader run error
2017-05-07T19:47:46 ERROR src/common.c: stlink_flash_loader_run(0x8000400) failed! == -1
stlink_fwrite_flash() == -1

run 10 times may succeeded once.
but when use --debug:
st-flash --debug write main.bin 0x8000000
It almost succeeded every time(99%).
st-info and st-utils worked well.
Bye the way, openocd would connected and supported debug, but could not flash either.
OpenOCD complained:
Error erasing flash with vFlashErase packet

Now only stm32loader.py with uart succeeded 100%.

After adding a 47uF capacitor between VDD and VSS, st-flash works very well.
Don't know why. Without the capacitor, STM32F030F4P6 still runs very well.

It is my falt.
Supplying the mcu with independent power source, and no problems at all.
please close this.

You could close yourself. But thanks for reporting. Good luck!


preprocess of input frame is different from original implementation.

Hi, @hassony2
Thank you for sharing the pytorch-i3d implementation.
I find the preprocess of input frame is different from the original implementaion.
In I3D-tensorflow version, they state  that "For RGB, ..... . Pixel values are then rescaled between -1 and 1. "
However, in i3d_pt_profiling.py,  I only see process like
    dataset = datasets.ImageFolder(dataset_path,                                    transforms.Compose([                                        transforms.CenterCrop(args.im_size),                                        transforms.ToTensor(),                                        normalize,                                    ]))
But in the other implementations (https://github.com/piergiaj/pytorch-i3d), they use
img = (img/255.)*2 - 1
I am wondering whether this inconsistent will lead to a drop of performance.
Thanks

Hi @hzhang57,
The profiling code from i3d_pt_profiling was just meant for profiling purposes :). Therefore I feed in dummy data and don't worry about the output values.
If you want the proper demo you should look at i3d_pt_demo where you can verify that indeed the input is scaled between [-1, 1].
For proper results you should indeed rescale the inputs.
Hope this helps!
All the best,
Yana

Hi, @hassony2 ,
Thank you so much for your post.
I ran the pt_demo code.
I try to parse the rgb.npy file in data/ provided by you. I assume that you are preprocessing each frame with
img = (img/255.)*2 - 1
right?
However, I can not recover the images from such rgb.npy.
But I can recover the images in flow.npy.
Could you please tell me how to get the rgb input data for your code?
Regards,
Xiaobin


transaction type question

I'm here to see the API documentation: https://github.com/OmniLayer/omnicore/blob/master/src/omnicore/doc/rpc-api.md#omni_listtransactions, but not to document

"Type_int" : n, // (number) the transaction type as number
"Type" : "type", // (string) the transaction type as string

These two attributes explain, what values are there, and how can I tell if a transaction is a roll-in or a roll-out.
thanks

Hi @hero-zhanghao,
the transaction type and transaction type description show which Omni Layer transaction you are handling. For an overview, check out the specification:
https://github.com/OmniLayer/spec/
Please note, the specification is not up-to-date, but it describes the most common type: 1 - Simple Send, which is a standard transfer of tokens.


ci: release new version '0.4.0' -> '0.4.1'

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Release new version '0.4.0' -> '0.4.1'
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

current blocker:

[ ] https://github.com/GreptimeTeam/greptimedb/pull/2557
[ ] https://github.com/GreptimeTeam/greptimedb/pull/2576


Add typescript typings

Hi,
The typings on DefinitlyTyped repo are not updated, and it's much better and easy to maintain to have your typing file on your repo.
It's why I've updated it with some bugfix I've seen, and added it to the repo.
Thanks for your work.
Matt'

Thanks @mathieutu!


Fix typos (quiting -> quitting)

Pull Request Test Coverage Report for Build 5391

1 of 3 (33.33%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.006%) to 41.858%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunner.java
0
1
0.0%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
1
2
50.0%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/jmx/JmxJobMBeanManager.java
1
72.73%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
1
76.83%

Totals

Change from base Build 5388:
-0.006%

Covered Lines:
13921

Relevant Lines:
33258

💛  - Coveralls


Multiple firehose providers for firehose metrics when only one Firehose provider is supplied as config

Do you want to request a feature or report a bug?
A bug, I think
What is the current behavior?
When I have a single Firehose provider and then curl the metrics from graph node I see output like the following:
deployment_firehose_blockstream_connect_duration{deployment="QmNntE5hyzhTCoW51UYMvmKHBdFNgXMEYs6hVg5VqFC1gS",provider="firehose-3"} 1.924322659
deployment_firehose_blockstream_connect_duration{deployment="QmNntE5hyzhTCoW51UYMvmKHBdFNgXMEYs6hVg5VqFC1gS",provider="firehose-5"} 1.825530799
deployment_firehose_blockstream_connect_duration{deployment="QmNntE5hyzhTCoW51UYMvmKHBdFNgXMEYs6hVg5VqFC1gS",provider="firehose-8"} 3.675308704
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-10"} 3.126101749
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-11"} 3.41320891
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-13"} 2.987674525
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-15"} 2.091415605
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-16"} 2.140956528
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-3"} 0.816994415
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-4"} 1.938940324
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-5"} 1.812108187
deployment_firehose_blockstream_connect_duration{deployment="QmPwuMJJLzdPfZ6NXX1JNXhFcJyTCVX4Y3uixGp9zSGAwh",provider="firehose-8"} 2.500762376
deployment_firehose_blockstream_connect_duration{deployment="QmQ9fGL2DKBYWgFbNVQicw1ADSdq9kR3MYrFRsKVBsYEmu",provider="firehose-1"} 1.657005793
deployment_firehose_blockstream_connect_duration{deployment="QmR2qvm2Vhhjfd65g16CQYbYgLdNHfuSokW7FePj8j7bWq",provider="firehose-14"} 2.163223028
deployment_firehose_blockstream_connect_duration{deployment="QmR2qvm2Vhhjfd65g16CQYbYgLdNHfuSokW7FePj8j7bWq",provider="firehose-15"} 3.48737248
deployment_firehose_blockstream_connect_duration{deployment="QmR2qvm2Vhhjfd65g16CQYbYgLdNHfuSokW7FePj8j7bWq",provider="firehose-17"} 2.954491939
deployment_firehose_blockstream_connect_duration{deployment="QmR2qvm2Vhhjfd65g16CQYbYgLdNHfuSokW7FePj8j7bWq",provider="firehose-3"} 3.078251135
deployment_firehose_blockstream_connect_duration{deployment="QmR2qvm2Vhhjfd65g16CQYbYgLdNHfuSokW7FePj8j7bWq",provider="firehose-4"} 1.7710952180000001
deployment_firehose_blockstream_connect_duration{deployment="QmR2qvm2Vhhjfd65g16CQYbYgLdNHfuSokW7FePj8j7bWq",provider="firehose-8"} 1.9191417720000001
deployment_firehose_blockstream_connect_duration{deployment="QmRzkv1vWnxWaqEZzo5rNr2nTput4mx5y3QqKxWQz7cSGR",provider="firehose-10"} 1.766222365
deployment_firehose_blockstream_connect_duration{deployment="QmRzkv1vWnxWaqEZzo5rNr2nTput4mx5y3QqKxWQz7cSGR",provider="firehose-11"} 2.069972008
deployment_firehose_blockstream_connect_duration{deployment="QmRzkv1vWnxWaqEZzo5rNr2nTput4mx5y3QqKxWQz7cSGR",provider="firehose-16"} 2.951801974
deployment_firehose_blockstream_connect_duration{deployment="QmRzkv1vWnxWaqEZzo5rNr2nTput4mx5y3QqKxWQz7cSGR",provider="firehose-18"} 2.151872044

Note that the same deployment ID appears with many different firehose providers even though I only have a single provider. Why is that?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

Launch a graph node with a single firehose provider
deploy a subgraph against this provider
wait a bit
curl the metrics endpoint

What is the expected behavior?
I expect the firehose related metrics to have only a single provider value when the graph node config only has 1 firehose provider.

Likely will be resolved by #4778. Is that true @mangas?

you want to disable the behaviour you can set conn_pool_size of the provide to 1

that would be problematic if there were more than 100 subgraphs deployed into graph node, right?
I personally don't find the numerically suffixed provider tag useful. There's no way for me to act on a misbehaving connection in the pool. I'm not sure how others feel but I personally would find it more useful if the provider tag removed the numeric suffix and just had the name of the provider.


Cherry-pick asset editor fixes, small UI updates to stable6.8

Add border to help distinguish selected/unselected asset tab (#7833)
Compress tilemap sidebar for smaller screen sizes (#7835)
Fix tilemap upgrade path in compiler (#7839)
Be stricter when parsing image literals (#7849)
Clean up temporary asset when exiting field editor (#7848)
Unite asset emitting code paths and fix tile parsing (#7489) <- @abchatra this is the one richard was talking about in standup
Expose more informative skillmap parsing error (#7863)

@riknoll let me know if i missed any!

Worth noting we don't have the gh actions on this branch currently so no tests running on this pr, I added that to my release cherry pick pr https://github.com/microsoft/pxt/pull/7865 so should be fine


Superset Roles Assignment For New Users

We have configured Superset with our LDAP server, i was wondering if it's feasible to assign Roles dynamically based on LDAP data. Currently i am seeing only this env variable
AUTH_USER_REGISTRATION_ROLE= 'Gamma'
Can't figure it out how to use this for assigning role dynamically ?

@som2014 There is another configuration option (in your superset_config.py) that can be used according to flask appbuilder documentation. But its not working for me :-(
# e.g
AUTH_USER_REGISTRATION_ROLE_JMESPATH="ends_with(email<EMAIL_ADDRESS>&& 'Admin' || 'Gamma'"

This should ideally grant all users from yourcompany.com admin roles

Okay I was able to figure it out. The flask-appbuilder version of the superset I'm using does not have jmespath support. I had to manually add it

you could override the FAB SecurityManager addUser method to customize how you add new users by adding them multiple roles

https://github.com/dpgaspar/Flask-AppBuilder/pull/1374 has been merged, and is now part of Flask-AppBuilder 3.2.0, meaning the AUTH_ROLES_MAPPING feature is now available.
@amitmiran137 I'm not sure if Superset needs to do anything to update Flask-AppBuilder to 3.2.0
See the Flask-AppBuilder docs here:
https://flask-appbuilder.readthedocs.io/en/latest/security.html#authentication-ldap

can we assign multiple roles to a registering user?
I have my expression working but it only assigns the last role
e.g
(ends_with(email<EMAIL_ADDRESS>&& 'Gamma' && 'CustomCreatedRole') || 'Gamma'
but only  CustomCreatedRole is being assigned and not Gamma to  the new user

@usamaB the AUTH_ROLES_MAPPING feature is a dictionary from string --> list, so it supports multiple roles:
# a mapping from LDAP DN to a list of FAB roles
AUTH_ROLES_MAPPING = {
    "cn=fab_users,ou=groups,dc=example,dc=com": ["User", "User_role2"],
    "cn=fab_admins,ou=groups,dc=example,dc=com": ["Admin"],
}

(Similarly for OAUTH)

@usamaB You can see the docs for my airflow helm chart (airflow also uses Flask-Appbilder, so the configs are the same):
https://github.com/airflow-helm/charts/tree/main/charts/airflow#how-to-authenticate-airflow-users-with-ldapoauth
See "Option 2 - use OAUTH"

Hi Everyone.
I checked if our LDAP is created in the below ways the dynamic role mapping is working perfectly fine when integrating with superset.
AUTH_ROLES_MAPPING = {
"cn=fab_users,ou=groups,dc=example,dc=com": ["User"],
"cn=fab_admins,ou=groups,dc=example,dc=com": ["Admin"],
}
AUTH_LDAP_GROUP_FIELD = "memberOf"
AUTH_ROLES_SYNC_AT_LOGIN = True
But in my case, I have two OUs say, OU=OU_A and OU=OU_B in LDAP and inside OUs members are there. I want to assign all users in OU_A to Admin role and OU_B to Gamma role respectively. I used AUTH_LDAP_GROUP_FIELD ='ou'. But it is not working. Please help me to resolve this issue.


Mock lambda with body > 6Mb does not respond with 6Mb limit error

The sample lambda function should try to return a response that is too large:
def lambda_handler(event, context):
    import sys

    x = ["xxx" for x in range(10 ** 6)]
    assert sys.getsizeof(x) > 6291556
    return {"statusCode": 200, "body": x}

When this is called in a moto lambda mock, it returns successfully.  It should return an error that the response exceeds the 6MB limit.
https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html notes that synchronous functions have limits:

6Mb for synchronous invoke payload and response
the bytes value of 6291556 is from a live AWS Lambda error message

The error message is
'{\n "errorMessage": "Response payload size exceeded maximum allowed payload size (6291556 bytes).",\n "errorType": "Function.ResponseSizeTooLarge"\n}'

Or
{
    "errorMessage": "Response payload size exceeded maximum allowed payload size (6291556 bytes).",
    "errorType": "Function.ResponseSizeTooLarge",
}

hacked the system)


2018-12-06 REX-413 Fix Lightspeed throttling error

Lightspeed logs were showing repeated 429 throttling errors
- Examination of logs showed throttler was not waiting the correct length of time before trying again
- Refactored ThrottlerAsync to await in milliseconds, not seconds
Also did minor refactoring in ThrottlerAsync to clarify workflow within methods to make it more apparent what exceptions would be thrown under what conditions.

The changes look good to me.  I had a few questions I asked Laura in person.  Some of the removed code was moved to the top to help make the code easier to read.  The formatting looks a bit off, but in VS it looks good. Not sure why the formatting is off here in GitHub.

There is still an issue with the changes in this PR you are using ?. which won't work because c# 5.0 does not have this feature


Operating system support list is very misleading

The Operating system support list is very misleading and potentially costing small business thousands of dollars that they don't need to spend on a standard license. There needs to be an asterisk next to the Windows Server 2022 Standard explaining that this also covers the OEM Essentials version, most people (including the sales team at Dell) don't understand that the essentials version is no longer a separate version from the standard version.

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

ID: c5dbbe35-6dd7-6ca7-3966-ee9416304d99
Version Independent ID: c5dbbe35-6dd7-6ca7-3966-ee9416304d99
Content: SQL Server 2019: Hardware & software requirements - SQL Server
Content Source: docs/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019.md
Service: sql
Sub-service: release-landing
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@paranoidloyd -- thank you for your feedback.
@MikeRayMSFT -- please look into this issue.

@paranoidloyd - note that we added essentials to this table in the noted PR.
Thank you for submitting the request.


Moved forecasting to official folder

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist: a

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[ ] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[x] This notebook has been added to the CODEOWNERS file under # Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

TODO: Fix the problem with no forecasted data being shown in the Data Studio link.

@kweinmeister I'll keep tweaking this and merge this over the next week or so. It's 99% there so I might as well wrap it up.

@kweinmeister Per last review, it appears we need these 3 last changes:

remove reference to online prediction
Rephrase as just 'AutoML forecasting model'
Changed the amount of time to wait for training to at least one hour.

@kweinmeister I made the remaining 3 changes in Ivan's branch. Will merge when test completes.

Karl Weinmeister, 3:13 PM
Also, I reviewed the build log of the Forecast PR ... after 20 hours !! it failed. it looks like it was a timeout on an unrelated notebook.
so i think we can also merge that


[aufs] No longer exclude ".wh..wh.*" files in Diff

The exclusion of AUFS special files beginning with ".wh..wh." were made about
a year ago in an effort to reduce the differences in filesystem layer diffs
produced by the various storage drivers. While the exclusion of most of these
special files made no difference in behavior of the mounted filesytem, the
loss of ".wh..wh..opq" files did affect behavior of some directories.
A directory which contains a ".wh..wh..opq" file is considered to be "Opaque"
meaning that ReadDir() calls should not include the content of the directory
in any lower layers. An opaque directory is created when you have an AUFS
layer which deletes a directory (which may contain other files and directories)
and then recreate the directory with no contents:
rm -rf /dir && mkdir /dir

By excluding the ".wh..wh..opq" file from filesystem layer diffs, images made
on a system using the AUFS storage driver which created an opaque directory
would result in that directory no longer being opaque, exposing content of the
old/deleted directory that it replaced.
This patch fixes this bug by removing the now-outdated exclusion of ".wh..wh.*"
files when producing a diff of an AUFS layer. The original problem that this
exclusion addressed was never fully resolved by this exclusion and Docker 1.8
now addresses the problem by storing a manifest of layer tar archive entries to
reliably recreate the contents of a rootfs diff when pushing/pulling to a
docker registry.

@jlhawn should be in 1.8.2?

@LK4D4 It could be included in 1.8.2 if you want, however I'm not 100% sure if this still does not lead to some problems related to the tar-split changes added by @vbatts. The other storage drivers perform special processing of the ".wh..wh.*" files as seen here: https://github.com/docker/docker/blob/3111aa7293f49f550b56652c622b0f4d194aae6f/pkg/archive/diff.go#L85 So I wonder if that would end up breaking an expectation that the tar-split changes have. @vbatts do you think that your changes still work given these AUFS special files?

what changed to make this an issue now?

@crosbymichael It's been an issue (see #9093) introduced by #8813, and with @vbatts changes in #14067 this should probably be okay to revert.

I'm not sure if this fixes #15643

I actually think that this patch would make the issue in #15643 worse: That issue seems to only manifest itself when you pull an image that contains ".wh..wh." files (i.e., images created from an AUFS storage driver  before the changes in #8813). The error occurs when @vbatts's changes in #14067 attempt to recreate the tar archive as it was pulled and it does this by mounting the image rootfs and grabbing each of the files from the original archive, HOWEVER using AUFS these ".wh..wh." files will not be visible in the mounted directory. AND if your storage driver was not AUFS then these files would also not be extracted per the conditions in pkg/archive/diff.go and so you would still not be able to grab these files to recreate the original archive.
The easiest fix would probably be for @vbatts's tar-split library to special-case files/dirs which begin with ".wh..wh."? Maybe use empty files in their place? But that seams really hacky, but it must be handling whiteout files currently as a similar special case, right?

There is no issue with these whiteout files laying around, besides clutter, is there?

@vbatts I think most of them are just clutter but .wh..wh..opq is actually important.

Important to stay or not stay?
On Sep 1, 2015 19:27, "Josh Hawn"<EMAIL_ADDRESS>wrote:

@vbatts https://github.com/vbatts I think most of them are just clutter
but .wh..wh..opq is actually important.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15996#issuecomment-136890715.

important to stay ;-)

oh good. then this seems fine to me.

@jlhawn what happens when you want to migrate containers (with their layers) to another driver (cf #15299) ?

I am not sure about how this works exactly, but including these files essentially makes them a part of the layer file format. For this to happen, it must be driver agnostic.
A few small questions:

Is the whiteout (or wh..wh..opq) file format documented anywhere?
Does docker make any effort to unify these formats across drivers? Should we?

I am sorry if I'm way off base here, but I am trying to understand the issues with #15643.

As @stevvooe mentions, the problem with this is that the opaque directory format is not consistent across different filesystems. Removing this exclusion means that people will find weird wh..wh..opq if they create an image with AUFS and then run it on Overlay.
Maybe a better fix is what you describe in:

The easiest fix would probably be for @vbatts's tar-split library to special-case files/dirs which begin with ".wh..wh."? Maybe use empty files in their place? But that seams really hacky, but it must be handling whiteout files currently as a similar special case, right?

For reference, the docs explaining how overlay creates opaque and whiteout directories:
https://github.com/torvalds/linux/blob/master/Documentation/filesystems/overlayfs.txt#L84-L99

@calavera The docs for Overlay are really good, but I've found it difficult to find docs for how AUFS does things. I really prefer how Overlay does whiteouts and opaque directories with xattrs over how AUFS has separate opaque-specifier files.
@stevvooe there is logic in Docker for handling AUFS special files when extracting and generating rootfs layer diffs, but I'm not sure if they take the .wh..wh..opq files into account. I know they don't generate them (it's impossible to know if a directory is opaque or if everything in it was just deleted, so the generic rootfs differ just generates whiteouts for each removed directory entry), but they should be able to see the opaque dir whiteout file and know to remove all of the existing content of the directory.

The xattr approach is nice. It's a shame that AUFS never supported xattrs.
:-(
On Sep 17, 2015 1:55 PM, "Josh Hawn"<EMAIL_ADDRESS>wrote:

@calavera https://github.com/calavera The docs for Overlay are really
good, but I've found it difficult to find docs for how AUFS does things. I
really prefer how Overlay does whiteouts and opaque directories with xattrs
over how AUFS has separate opaque-specifier files.
@stevvooe https://github.com/stevvooe there is logic in Docker for
handling AUFS special files when extracting and generating rootfs layer
diffs, but I'm not sure if they take the .wh..wh..opq files into account.
I know they don't generate them (it's impossible to know if a directory is
opaque or if everything in it was just deleted, so the generic rootfs
differ just generates whiteouts for each removed directory entry), but they
should be able to see the opaque dir whiteout file and know to remove all
of the existing content of the directory.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/15996#issuecomment-141166512.

Just to reiterate, Docker's "layer file format" has always been equal to what AUFS does. It was designed from the beginning with AUFS being the only supported storage driver (back before storage drivers were even a thing - in the pre Docker 0.7 days). When support for devicemapper was added, the pkg/archive package was expanded to handle creating and extracting directory diffs to match AUFS's format.

@calavera Thank you for the great link. That clarifies things a bit but it looks like we use the aufs approach.
@jlhawn Thanks for the clarification.

@jlhawn be careful, I've recently switched to overlay and I have the same kind of whiteout files thant AUFS (see https://github.com/docker/docker/issues/15643#issuecomment-142224626)

Ping @tonistiigi!

This was resolved by #16470