[BUG] Unable to Provision RKE2 Custom Cluster w/ Harvester Cloud Provider

Describe the bug
RKE2 Custom Cluster with Harvester Cloud Provider is unable to be provisioned.
To Reproduce
Steps to reproduce the behavior:

Have a Helm install of Rancher, v2.7.5-rc4
Import Harvester to Rancher
Create VLAN 1 for Harvester for VM Networks
Download supporting cloud image, choose your flavor (like OpenSuse Leap 15.4 nocloud)
Set Up Minio, with HTTPS, through certgen
Create RKE2 Custom Cluster, providing Minio S3 Backup enabled, selecting Harvester as Cloud Provider
Create two vms on Harvester, with your distro flavor
If using nip.io for Rancher helm install hostname/ipv4, changing ingress-wildcard in Rancher, if desired...
Use the "Registration" section from RKE2 Custom Cluster, to highlight, 2 roles: etcd & control-plane (check insecure), then copy & paste into first vm.
Use the "Registration" section from RKE2 Custom Cluster, to highlight, 1 role: worker (check insecure), then copy & paste into second vm.
The cluster will never provision, gets stuck at bootstrapping

Expected behavior
Harvester Cloud Provider selection in custom RKE2 Cluster provisioning to not adversely affect the cluster
Environment

Harvester ISO version:  Version: v1.2-0d1cf827-head
Rancher Version: v2.7.5-rc4
Underlying Infrastructur: Bare Metal, for both Rancher & Harvester
Helm install based Rancher w/ K3s: curl -sfL https://get.k3s.io/ | INSTALL_K3S_VERSION="v1.25.9+k3s1" sh -s - server --cluster-init
helm install rancher rancher-latest/rancher --devel --version v2.7.5-rc4 --namespace cattle-system --set bootstrapPassword=testtesttest --set hostname=your-ipv4-or-hostname-from-the-rancher-node.nip.io--set replicas=3

Additional context

Additionally, out of curiosity, I went through and added a cloud-credential and retried.
Also tested Harvester ISO version: Version: v1.2-0d1cf827-head with:

Rancher v2.7.4
Rancher v2.7.3
Rancher v2.7.2
Cleaning up the cluster utilizing https://github.com/rancher/rancher-cleanup before each Rancher version changeover.

Then tested as well with Harvester v1.2.0-rc2 & Rancher v2.7.5-rc5, that yielded the same results as above.
No cluster was able to provision within 25~ min on two nodes: 1 worker and 1 control-plane & etcd.

Watching journalctl -u rancher-system-agent.service --follow on the node that runs etcd & control-plane w/ 15.4 Leap Cloud Image usually yields similar logs to:

╭─mike at suse-workstation-team-harvester in ~/Projects/rancher-cleanup on main✔
╰─± ssh<EMAIL_ADDRESS>Last login: Thu Jun 15 23:43:04 2023 from <IP_ADDRESS>
openSUSE Leap 15.4 x86_64 (64-bit)

As "root" use the:
- zypper command for package management
- yast command for configuration management

Have a lot of fun...
opensuse@testrc2nodes-01:~> sudo su
testrc2nodes-01:/home/opensuse # journalctl -u rancher-system-agent.service --follow
Jun 15 23:43:54 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:54Z" level=error msg="error encountered during parsing of last run time: parsing time \"\" as \"Mon Jan _2 15:04:05 MST 2006\": cannot parse \"\" as \"Mon\""
Jun 15 23:43:54 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:54Z" level=error msg="error loading CA cert for probe (kube-scheduler) /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: open /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: no such file or directory"
Jun 15 23:43:54 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:54Z" level=error msg="error while appending ca cert to pool for probe kube-scheduler"
Jun 15 23:43:54 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:54Z" level=error msg="error loading CA cert for probe (kube-controller-manager) /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: open /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: no such file or directory"
Jun 15 23:43:54 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:54Z" level=error msg="error while appending ca cert to pool for probe kube-controller-manager"
Jun 15 23:43:59 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:59Z" level=error msg="error encountered during parsing of last run time: parsing time \"\" as \"Mon Jan _2 15:04:05 MST 2006\": cannot parse \"\" as \"Mon\""
Jun 15 23:43:59 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:59Z" level=error msg="error loading CA cert for probe (kube-scheduler) /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: open /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: no such file or directory"
Jun 15 23:43:59 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:59Z" level=error msg="error while appending ca cert to pool for probe kube-scheduler"
Jun 15 23:43:59 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:59Z" level=error msg="error loading CA cert for probe (kube-controller-manager) /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: open /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: no such file or directory"
Jun 15 23:43:59 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:43:59Z" level=error msg="error while appending ca cert to pool for probe kube-controller-manager"
Jun 15 23:44:04 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:04Z" level=error msg="error encountered during parsing of last run time: parsing time \"\" as \"Mon Jan _2 15:04:05 MST 2006\": cannot parse \"\" as \"Mon\""
Jun 15 23:44:04 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:04Z" level=error msg="error loading CA cert for probe (kube-scheduler) /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: open /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: no such file or directory"
Jun 15 23:44:04 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:04Z" level=error msg="error while appending ca cert to pool for probe kube-scheduler"
Jun 15 23:44:04 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:04Z" level=error msg="error loading CA cert for probe (kube-controller-manager) /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: open /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: no such file or directory"
Jun 15 23:44:04 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:04Z" level=error msg="error while appending ca cert to pool for probe kube-controller-manager"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error encountered during parsing of last run time: parsing time \"\" as \"Mon Jan _2 15:04:05 MST 2006\": cannot parse \"\" as \"Mon\""
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=info msg="[Applyinator] No image provided, creating empty working directory /var/lib/rancher/agent/work/20230615-234409/08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_0"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=info msg="[Applyinator] Running command: sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null]"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_0:stdout]: Name Location Size Created"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=info msg="[Applyinator] Command sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null] finished with err: <nil> and exit code: 0"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error loading CA cert for probe (kube-controller-manager) /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: open /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: no such file or directory"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error while appending ca cert to pool for probe kube-controller-manager"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error loading CA cert for probe (kube-scheduler) /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: open /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: no such file or directory"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error while appending ca cert to pool for probe kube-scheduler"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error loading CA cert for probe (kube-controller-manager) /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: open /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: no such file or directory"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error while appending ca cert to pool for probe kube-controller-manager"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error loading CA cert for probe (kube-scheduler) /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: open /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: no such file or directory"
Jun 15 23:44:09 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:09Z" level=error msg="error while appending ca cert to pool for probe kube-scheduler"
Jun 15 23:44:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:14Z" level=error msg="error loading CA cert for probe (kube-controller-manager) /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: open /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: no such file or directory"
Jun 15 23:44:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:14Z" level=error msg="error while appending ca cert to pool for probe kube-controller-manager"
Jun 15 23:44:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:14Z" level=error msg="error loading CA cert for probe (kube-scheduler) /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: open /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: no such file or directory"
Jun 15 23:44:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:14Z" level=error msg="error while appending ca cert to pool for probe kube-scheduler"
Jun 15 23:44:15 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:15Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 15 23:44:15 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:15Z" level=error msg="error loading CA cert for probe (kube-controller-manager) /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: open /var/lib/rancher/rke2/server/tls/kube-controller-manager/kube-controller-manager.crt: no such file or directory"
Jun 15 23:44:15 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:15Z" level=error msg="error while appending ca cert to pool for probe kube-controller-manager"
Jun 15 23:44:15 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:15Z" level=error msg="error loading CA cert for probe (kube-scheduler) /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: open /var/lib/rancher/rke2/server/tls/kube-scheduler/kube-scheduler.crt: no such file or directory"
Jun 15 23:44:15 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:15Z" level=error msg="error while appending ca cert to pool for probe kube-scheduler"
Jun 15 23:44:20 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:44:20Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 15 23:45:11 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:45:11Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[Applyinator] No image provided, creating empty working directory /var/lib/rancher/agent/work/20230615-235348/08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[Applyinator] Running command: sh [-c rke2 etcd-snapshot list --etcd-s3 2>/dev/null]"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: Name                                                Size     Created"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-vms-for-customtest-01-1686697449          15781920 2023-06-13T23:04:10Z"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: etcd-snapshot-anothertestnode-01-1686859202         8577056  2023-06-15T20:00:03Z"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: etcd-snapshot-replace-customtest-vm-1686700804      13017120 2023-06-14T00:00:05Z"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-onenode-pool1-fd34fdfb-9254c-1686688339   11595808 2023-06-13T20:32:19Z"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-onenode-pool1-fd34fdfb-rlrhc-1686686641   18681888 2023-06-13T20:04:01Z"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-rke2-embedded-clstr-test-vm-01-1686707885 16044064 2023-06-14T01:58:06Z"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-test-01-1686701756                        15835168 2023-06-14T00:15:56Z"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[Applyinator] Command sh [-c rke2 etcd-snapshot list --etcd-s3 2>/dev/null] finished with err: <nil> and exit code: 0"
Jun 15 23:53:48 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:53:48Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 15 23:54:13 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:54:13Z" level=info msg="[Applyinator] No image provided, creating empty working directory /var/lib/rancher/agent/work/20230615-235413/08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_0"
Jun 15 23:54:13 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:54:13Z" level=info msg="[Applyinator] Running command: sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null]"
Jun 15 23:54:13 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:54:13Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_0:stdout]: Name Location Size Created"
Jun 15 23:54:13 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:54:13Z" level=info msg="[Applyinator] Command sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null] finished with err: <nil> and exit code: 0"
Jun 15 23:54:13 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:54:13Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 15 23:55:13 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:55:13Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 15 23:55:13 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-15T23:55:13Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[Applyinator] No image provided, creating empty working directory /var/lib/rancher/agent/work/20230616-000349/08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[Applyinator] Running command: sh [-c rke2 etcd-snapshot list --etcd-s3 2>/dev/null]"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: Name                                                Size     Created"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-vms-for-customtest-01-1686697449          15781920 2023-06-13T23:04:10Z"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: etcd-snapshot-anothertestnode-01-1686859202         8577056  2023-06-15T20:00:03Z"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: etcd-snapshot-replace-customtest-vm-1686700804      13017120 2023-06-14T00:00:05Z"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: etcd-snapshot-testrc2nodes-01-1686873600            10801184 2023-06-16T00:00:01Z"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-onenode-pool1-fd34fdfb-9254c-1686688339   11595808 2023-06-13T20:32:19Z"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-onenode-pool1-fd34fdfb-rlrhc-1686686641   18681888 2023-06-13T20:04:01Z"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-rke2-embedded-clstr-test-vm-01-1686707885 16044064 2023-06-14T01:58:06Z"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_1:stdout]: on-demand-test-01-1686701756                        15835168 2023-06-14T00:15:56Z"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[Applyinator] Command sh [-c rke2 etcd-snapshot list --etcd-s3 2>/dev/null] finished with err: <nil> and exit code: 0"
Jun 16 00:03:49 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:03:49Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"
Jun 16 00:04:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:04:14Z" level=info msg="[Applyinator] No image provided, creating empty working directory /var/lib/rancher/agent/work/20230616-000414/08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_0"
Jun 16 00:04:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:04:14Z" level=info msg="[Applyinator] Running command: sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null]"
Jun 16 00:04:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:04:14Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_0:stdout]: Name                                     Location                                                                                Size     Created"
Jun 16 00:04:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:04:14Z" level=info msg="[08fddef0872b4a1b5b4d4210f62ef9869ee73a8ef5b2b634af02b7ab5fe440f0_0:stdout]: etcd-snapshot-testrc2nodes-01-1686873600 file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-testrc2nodes-01-1686873600 10801184 2023-06-16T00:00:01Z"
Jun 16 00:04:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:04:14Z" level=info msg="[Applyinator] Command sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null] finished with err: <nil> and exit code: 0"
Jun 16 00:04:14 testrc2nodes-01 rancher-system-agent[2142]: time="2023-06-16T00:04:14Z" level=info msg="[K8s] updated plan secret fleet-default/custom-f034dccaa650-machine-plan with feedback"

Should "Harvester" be an available option? :thinking:

Default - RKE2 Embedded will provision extremely fast and doesn't hang in Updating as a selected Cloud Provider.

Marking this as a regression, but not entirely sure it is a regression or not :thinking:

For RKE2 Custom Cluster, we have to generate and inject cloud config for harvester-cloud-provider by ourselves.

Hit similiar issue in v1.2.0-rc4 regression, provide rancher-system-agent.log and support bundle in https://github.com/harvester/tests/issues/900#issuecomment-1658569036

Hi @irishgordo, I use steps in this document and can't reproduce the issue. May you try again with it? Thanks.
https://github.com/harvester/docs/pull/525

We also encounter the issue of can't provision the custom RKE2 cluster on Harvester v1.4-head with Rancher v2.8.5
as stated in https://github.com/harvester/harvester/issues/6286

By using the correct manner to generate the Kubeconfig, I can provision the custom RKE2 cluster on Harvester v1.4-head with Rancher v2.8.5. Already close the issue #6286 link here.

@TachunLin thanks for that mention :smile: :+1:
I will also close this out as we now have a documented process for the custom RKE2 cluster & this did also seem related to environment configuration issues.
Thanks again for the doc @FrankYang0529 :+1: :smile: !


Missing Distribution Group

Hello. I have been invited to a team on AppCenter, but when I click on Distribution -> Group, I cannot see all the groups of project. I thought I must be invited into a group inside project too, but my leader said it needs not. Please help me!. Thanks

Thanks for filing this report & sorry that you haven't heard back from us. It sounds like this issue for technical support, but this repository isn't monitored by our support team.
If you need technical help, you can contact support by:

Going to https://appcenter.ms/apps
Selecting ? > Contact Support (in the upper right corner).
Reference this issue for context if needed.

If you've already resolved your issue/still want us to document this, give us an update of your current observations. We're catching up on our backlog here.


Disable Developer preview mode

Hello, how can we disable the option to use developer preview mode at the organizational level for managed mobile devices?

@cbarbier7 Disability the ability for the organisation to be able to enable Developer Preview is to return to Org Wide App settings within Permission Policies of Teams Apps in the Teams Admin Centre, swiping off Allow interaction with custom apps and Saving. This will remove the Developer preview option from all users desktop, web and mobile clients.


Tensor allocations and Tensorflow Session support added

This PR completes the entire prediction pipeline. If you have a graph you can now completely generate predictions. Tensor allocation functions have also been added which are used for holding output tensors which only obtain their values after a session is run successfully.
To exemplify the working of the entire prediction pipeline, I am going to use the simple toy graph created by the script in examples/ called graphdef_create.py . Upon running the script you should have a graph definition file called graphdef.pb. You can also download this file stored in my Dropbox here.
Then I would recommend going through the graphdef_create.py file to get an idea of what the operations are. The code basically works like a very simple matrix multiplication of some predefined weights with the input and then the addition of the biases. Ideally the weights should be ascertained through training but since this is a toy example they are predefined (look here in the code).
The more important thing to notice in the graphdef_create.py file are the operations where the input is fed and where the output is obtained. It is important to know the names of these operations as when we perform Inference the input will be fed to that named input operation and the output will be obtained similarly. The names of the operations are required to run sessions. In our toy example, the input operation is assigned the name "input" (look here in the code) and the output operation is assigned the name "output" (look here in the code).
Now in Tensorflex, the Inference would go something like this:

First load the graph and look to see all the operations are correct. You will see "input" and "output" somewhere as mentioned before.

iex(1)> {:ok, graph} = Tensorflex.read_graph "graphdef.pb"
2018-06-04 00:32:53.993446: I tensorflow/core/platform/cpu_feature_guard.cc:137] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
{:ok, #Reference<0.1321508712.421658628.225797>}

iex(2)> Tensorflex.get_graph_ops graph
["biases", "biases/read", "weights", "weights/read", "input", "MatMul", "add",
 "output"]

Then create the input tensors. First create matrices to house the tensor data as well as it's dimensions. As an example, let's say we set our input to be a 3x3 tensor with the first inputs all 1.0, second row to be 2.0, and third to be 3.0. The tensor is a float32 tensor created using the float32_tensor function.

iex(3)> in_vals = Tensorflex.create_matrix(3,3,[[1.0,1.0,1.0],[2.0,2.0,2.0],[3.0,3.0,3.0]])
#Reference<0.1321508712.421658628.225826>

iex(4)> in_dims = Tensorflex.create_matrix(1,2,[[3,3]])
#Reference<0.1321508712.421658628.225834>

iex(5)> {:ok, input_tensor} = Tensorflex.float32_tensor(in_vals, in_dims)
{:ok, #Reference<0.1321508712.421658628.225842>}

Now to create the output tensor, since we know the matrix operations, the output will be a 3x2 tensor. We set the dimensions appropriately. Moreover, since we do not yet have the output values (we can only get them after the session is run), we will use the float32_tensor_alloc function instead of float32_tensor.

iex(6)> out_dims = Tensorflex.create_matrix(1,2,[[3,2]])
#Reference<0.1321508712.421658628.225850>

iex(7)> {:ok, output_tensor} = Tensorflex.float32_tensor_alloc(out_dims)
{:ok, #Reference<0.1321508712.421658628.225858>}

Finally, we need to run a session to get the output answers from sending the input tensors through the graph. We can see that the answer we get is exactly what we get when we do the matrix multiplications of the inputs with the weights and the addition of the biases. Also, the run_session function takes 5 inputs: the graph definition, the input tensor, the output tensor, the name of the input operation and the output operation. This is why knowing the names of your input and output operations is important.

iex(8)> Tensorflex.run_session(graph, input_tensor, output_tensor, "input", "output")
[
  [56.349998474121094, 39.26000213623047],
  [109.69999694824219, 75.52000427246094],
  [163.04998779296875,<PHONE_NUMBER>7929688]
]

ping @josevalim


r2dbc-spi dependency not found

below dependency not found:
<r2dbc-spi.version>1.0.0.BUILD-SNAPSHOT</r2dbc-spi.version>,
where can I find this artifact?
official maven repo only keeps version of '1.0.0.M7' :(

Snapshots are available from https://repo.spring.io/snapshot/ and milestones from https://repo.spring.io/milestone/. Btw. 0.8.0 M8 is out, I filed #8.


chore(example): update podfile lock

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

v3.0.0
GitHub release

Your semantic-release bot :package::rocket:


Initially created token file is world readable on Unix

The token file is created without specifying a mask so it will usually be world readable on Unix systems.

Could this possibly be fixed by adding something along the lines of:
os.chmod(path, 0o600) 1 To prevent the file from being world readable or have I got the permissions incorrect?

No, chmod after creation is not sufficient.
Call os.umask(0o077) any time before opening it.

First of all, sorry for replying so late. The library was essential not supported since ~2017. I had some free time recently though and decided to give it some love and release v1.0.0
This should be fixed:
https://github.com/pawelad/pymonzo/blob/a3a609d07e1c07c06451ba551cd9ed5eda363f2b/src/pymonzo/settings.py#L49-L59


Provide a standard way to import a database to drupal

Builds upon #174 to provide standard ways of importing a database dump in line with the other framework images.
This includes the means to fetch that database dump via SSH if certain environment variables are configured and the do_drupal_sync_database function is called from a custom version of do_setup or do_drupal_install.
The PR also includes the ability to run drupal's composer plugin if required, via do_drupal_composer_install.

@kierenevans should we ask @rj-ikos & @andytson-inviqa to review again?

@rj-ikos, @andytson-inviqa: could you update your review on this PR?

Happy for this to be merged now.
Will leave this comment for approval and allow Kieren to merge when ready.


Fix build pipeline for x86 and x64 msix packages

Details of Changes
Due to some mistake done by the Powershell Team in the Microsoft.Management.Infrastructure nuget package, x64 and x86 compiles of the application when performed by the CI task do not produce expected binaries, leading to the app being non functional on these platforms.

The Microsoft.Management.Infrastructure.Runtime.Win package uses a mismatch of RIDs (Runtime Identifiers) with win10-x64/win10-x86 being used versus win-arm and win-arm64. Due to another issue with Windows Application Packaging projects, the files only get copied if the following RID scheme is used: win-XXX.
This PR therefore brings a workaround to this problem by bundling a local fixed version of the Microsoft.Management.Infrastructure.Runtime.Win nuget package, and adjusts the CI to restore said Nuget package.
Given MSBuild ability to restore nuget packages both from nuget.org and from local sources, the Nuget installer/Restore tasks were removed from the CI pipelines, and instead msbuild was instructed to restore packages by itself. This allows us to bring in the fixed package.
Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility (does not apply here)
[x] Test CI pipeline (non release) and sideloaded/ensured the built package was working on x64 Windows.

Screenshots

My Microsoft Store application is failing because if this problem. Please, fix this.

OK; I'm impacted with the MMI issue. Is there any way to get this sorted out in the official packages? Thanks!

@SuperJMN v2.1 will be released when it's ready, but it depends on a couple things that will take some time to implement.


chore: don't run system tests with grpc-js

@kinwa91 will enable system tests with grpc-js as a separate Kokoro task.
It's a little bit flaky now so will likely bring more harm than good.
But good news is that it works (#400)!

[x] Tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

@JustinBeckwith @kinwa91 Since #418 is on its way, can you approve&merge this one so that flaky system tests don't interfere with PRs? Thanks!


Compilation Error

Dear CACTUS-Community,
I cloned the repo and followed the compilation instructions. Unfortunately, I receive the following error when executing make:

Has someone suggestions on how to fix the problem? What additional information do you require to help me? I am a Mac user with intel compilers installed.
Thank you very much in advance
Nils

Hi Nils, can you verify that airfoil.f95 actually contains code? Also, please share the entirety of your cmake output.

Dear Phil,
thank you very much for the quick reply. Yes airfoil.f95 does contain code.
Here attached the CMakeOutput.log file.
CMakeOutput.log
Regards
Nils

I solved my problem by switching to the GNU compiler. It might be worth investigating whether the current Cmake configuration is still compatible with the newest intel Fortran compiler.

I solved my problem by switching to the GNU compiler. It might be worth investigating whether the current Cmake configuration is still compatible with the newest intel Fortran compiler.

Sorry @NilsBForze , just had time to look at this. I just tested and have the same problem with Intel Fortran. Re-opening this issue for tracking.

Should be fixed with https://github.com/SNL-WaterPower/CACTUS/pull/48, but that PR needs testing


Codecov coverage added

Testing Codecov coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@289e442). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #192   +/-   ##
=========================================
  Coverage          ?   22.06%
=========================================
  Files             ?       52
  Lines             ?     2470
  Branches          ?      257
=========================================
  Hits              ?      545
  Misses            ?     1888
  Partials          ?       37

Add the code coverage CodeCov badge.

Remove the coveralls dependency

Include the DockerFile in the PR just for completeness


Typescript error triggerCookieConsentBanner

Node/npm version(s): 8.3.1
Package(s) version(s):
<EMAIL_ADDRESS>
Browser(s) version(s): lastest Chrome
Description of the issue/feature: Getting an TS error: Module '"@porscheofficial/cookie-consent-banner-react"' has no exported member 'triggerCookieConsentBanner'.
Some example to reproduce the issue: based on demo code
Use cases:

Hi @zeitvertrieb !
Sorry for the inconvenience. The documentation already includes features of the upcoming release.
Takes a bit longer than anticipated. Will notify you, once this function is available.

Thank you for the update, @ppuritscher!
Ok, seems straight forward. I must be honest, I did just find this project and it seems like the best CC library out there and I have yet to study the implementation.
I will start with a custom method and look for your update later

Glad to hear that. Always open for feedback :)

Hi @zeitvertrieb  and @learsson!
I just released v3.0.0. triggerCookieConsentBanner is now available.
See: https://github.com/porscheofficial/cookie-consent-banner/tree/main/packages/cookie-consent-banner-react#-real-world-example-with-tag-manager-and-custom-error-tracking
Please reopen this issue or create a new one if the issue still persists.


Allow to search using dotted notation

Fantastic idea.
Search using the file path is useful, but being able to search by module would be great.
Something like:
pyq3 def[name=get] -m requests
pyq3 class[name=User] -m django.contrib.auth.models
pyq3 #foo -m * # search in all importable modules

This seems to be a good idea. Thanks!


Events

I've just read the documentation and love it! I wish I had always used viewmodel ..
Ok, look at this code:
Template.person.viewmodel
  events:
    'click #fancyButton': ->
      Template.instance().viewmodel.doSomething()

Having to use Template.instance().viewmodel here is ugly (just too long), so I'm wondering if the following is possible:
Template.person.viewmodel
  events:
    'click #fancyButton': (e, tmpl, vm) ->
      vm.doSomething()

The thing to remember is that adding events that way is a last resort kind of thing. It's what you would do when you have no way to put a bind in the markup.
Implementing your suggestion would require monkey patching Meteor code. I'm not a fan of it for something so minor and, as mentioned before, something that should seldom happen.
The normal way of doing things is:
<template name="person">
  <button data-bind="click: doSomething">Do Something</button>
</template>

Template.person.viewmodel
  doSomething: ->

btw, you can also write the following right now:
Template.person.viewmodel
  blaze_events:
    'click #fancyButton': (e, t) ->
      t.viewmodel.doSomething()

(a minor improvement)

I've just started converting my code to viewmodel, can say it has reduced my code by some hundred lines of code in about two hours. I actually opened this issue just at the beginning, but I didn't have to use events so far. So t.viewmodel.doSomething() should be nice enough :)

it has reduced my code by some hundred lines of code in about two hours
Oh man, you just made my day =)
People don't believe me when I tell them that you need a lot less code when you do things this way (with a view-model). They think "yeah, right, everyone says that..."


Bump changelog for 0.6.0-rc1

@docker/machine-maintainers
We haven't really done changelogs for RCs in the past so let me know if you want to go forward with this.  I don't think we've really defined a procedure around it yet.
One option is we could merge this now, then simply change the release version to "0.6.0" and add anything new if it comes up in the next RCs, but no new features should be added between now and then.
Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

Let's merge it now!
LGTM


[kserve] testing: config: update to RHOAI 2.8rc2

test passed in https://github.com/openshift-psap/topsail/pull/274, merging


[Solution] How to integrate Apache Dubbo with Nacos authentication

Introduction
Although Apache Dubbo 2.7.6 had been released, built-in artifact org.apache.dubbo:dubbo-registry-nacos could not cooperate with Nacos Server 1.2.0+ enabling authentication. This issue will help you how to integrate them.
Prerequisites

Nacos Server 1.2.0+ enabling authentication feature [Guide]
Apache Dubbo 2.7.5+

How to configure
Adding the Maven dependencies
Adding following dependencies into your pom.xml
        <!-- Dubbo Registry Nacos -->
        <dependency>
            <groupId>com.alibaba</groupId>
            <artifactId>dubbo-registry-nacos</artifactId>
            <version>2.7.6</version>
        </dependency>

        <dependency>
            <groupId>com.alibaba.nacos</groupId>
            <artifactId>nacos-client</artifactId>
            <version>1.2.1</version>
        </dependency>

Updating the externalized properties

Assuming that username and password are "nacos"

For Spring stack applications

Assuming that your application is using Spring Framework 3.1+, and current Properties file is like this :
## Nacos registry address
dubbo.registry.address = nacos://<IP_ADDRESS>:8848

You should append the Nacos authentication username and password as the parameters, as following
dubbo.registry.address = nacos://<IP_ADDRESS>:8848/?username=nacos&password=nacos

For Raw API  applications

Before:
    RegistryConfig registryConfig = ...
    registryConfig.setAddress("nacos://<IP_ADDRESS>:8848");

After:
    RegistryConfig registryConfig = ...
    registryConfig.setAddress("nacos://<IP_ADDRESS>:8848/?username=nacos&password=nacos");

More details
Bugfixs
com.alibaba:dubbo-registry-nacos:2.7.6 also fixes some known bugs in Dubbo 2.7.6, please see

PR : https://github.com/apache/dubbo/pull/5902
Issues : #5871 #5885 and #5899

Compatibility
Being compatible with Dubbo Nacos Registry 2.6+.
Documents
https://github.com/mercyblitz/dubbo-registry-nacos
Warning
com.alibaba:dubbo-registry-nacos:2.7.6 is not a long-term maintaining module, it will be replaced by Apache Dubbo 2.7.7.

Is this solution useful only for users who use Nacos 1.2+ and enable authentication? It seems can't resolve #5871

dubbo 2.7.5 目前不支持，需要修改源码


If a weighted ejector has a stack size set and an item on it, it won't split a full stack of items

Describe the Bug
If a weighted ejector has a stack size set and n items on it, it won't take part of a stack of 64 - n + 1 items that is thrown, belted, or tunneled onto it. For example, if there are two items on an ejector and you throw a stack of 63 items at it, the ejector won't take any of the items, but it works fine if you throw 62 items.
Reproduction Steps

Set the stack size on a weighted ejector to 2.
Throw one item onto the ejector.
Throw a full stack of items onto the ejector.

Expected Result
The ejector should take enough items to meet its stack size, as it does when you throw less than a full stack of items onto it.
Screenshots and Videos
Once the item on the ejector was removed, it started launching 2 items at a time as expected.

Crash Report or Log
No response
Operating System
Windows 11 Home 10.0.22000
Mod Version
0.5.0c
Minecraft Version
1.18.2
Other Mods
No response
Additional Context
No response

Since the ejector is holding an item already, it will ignore items that land on it.
This is the exact same behavior as on Forge.
Going to say this is not a bug. Maybe a bit of an oversight, but not on us to change.

Oops, my bad, should have tested it on Forge first before opening an issue here.


DNM experiment with error codes and messages

This doesn't work, but it shows some ideas I'm thinking about.
I'm saying "code" but it's a short string not a number.

FYI @hacbs-contract/devs

Superseded by #32 .


[Performance Issue] Pool Performance on UI FPS on iOS only with victory-native VictoryArea animating.

I made a animated VictoryArea like this:

Watch the UI FPS ,please .  The animation is bad. But it is much better on Android.
Anyone can help me?  Thank you in advance.
dependencies:
"react-native": "0.55.4",
"react-native-svg": "^6.5.2",
"victory-native": "^0.17.4"

@msand Thank you.
I have already done that as you say to resolve this issue in this case. But not work in some other case.
Thank you again.

Hi @ATShiTou, alternatively, you could create a clipping mask that reveals the chart underneath (so you don't have to animate the paths, just a rectangle that grows to the width of the device (or height, depending on the orientation)

Thank you for your advice, I will have a try.

I've done some more work on native animation: https://github.com/react-native-community/react-native-svg/pull/757
Any help in testing would be much appreciated 😄


Dose adminjs support default value for property?

Hello, I'm using adminjs with mongoose. Suppose my schema have a property with default value like this:
const MySchema = new Schema({
  key: { type: String, required: true },
  level: { type: Number, default: 1, required: true },
});

In adminjs resource page, there is no default value for 'level', only empty input box.
So dose adminjs support default value for property? Thanks.

Mongoose should set your level to 1 if you leave the form field empty, but the form is not autofilled with your ORM's/ODM's defaults.

Thanks. So it there any method which make resource admin webpage use the default value? or just set an initial value when resource creating page shown.

I don't think there's an easy way currently. We plan to make changes to new action so that it allows you to fetch some data from the backend, but currently I think you'd have to create a custom component for specific properties.

Bump 👊
I am also interested in setting up default values for certain properties in the new action. Too bad this doesn't work yet.

Could this be done using an action?

Currently the only way is to use search params in the url:
https://demo.adminjs.co/app/resources/Category/actions/new?name=example

I did it by adding a hook method to before property like so:
import { ActionContext, ActionRequest } from "adminjs";

const setDefaultValuesFromQueryParams = (queryParams: string[]) => async (request: ActionRequest, context: ActionContext): Promise<ActionRequest> => {

    const { query = {}, } = request
    // check if query params are present in the request and inject them in the context in edit or request payload in new
    queryParams.forEach((param) => {
        if (query[param] !== undefined) {
            switch (context.action.name) {
                case 'edit':
                    if (query.product !== undefined) {
                        context.record.params = {
                            ...context.record.params,
                            [param]: { id: query[param] },
                        };
                    }
                    break;
                default:

                    if (query.designStudySection !== undefined) {
                        request.payload = {
                            ...request.payload,
                            product: query.designStudySection,
                        };
                    }

            }
        }
    });

    return request;
}

export default setDefaultValuesFromQueryParams;

Then in resource options:
// resource options
options: {
    actions: {
            new: {
                before: [setDefaultValuesFromQueryParams(['product'])],
                after: [/* redirectToAction('Product', 'show') a hook for redirection also*/]
            },
            edit: {
                showInDrawer: false,
                before: [setDefaultValuesFromQueryParams(['product'])],
                after: [/* redirectToAction('Product', 'show')*/]
            },
    }
}


Upgrade solr example to docker-compose 2+

In docker-compose 2+ the preference is to used a named volume to persist data, rather than data containers. In schema v3+, volumes_from is removed.
This means replacing volumes_from with a normal volume statement:
      - search-data:/var/lib/solr

Next, the docker-compose manifest will need a simple volume declaration such as:
volumes:
  # This data volume persists Solr storage.
  # The search service is using a customized Docker image to facilitate write
  # access to this volume.
  # An empty value indicates all settings are default.
  search-data:

Lastly, since we are no longer using a data container, we need to instead customize our docker image to have a place to store the data. In examining the upstream solr image, it appears we could simply locate the data within /opt/solr. Since we are not, we will need a Dockerfile such as:
FROM solr:5.5.4-alpine

USER root

# Create and permission the data directory.
RUN mkdir -pv /var/lib/solr && chown $SOLR_USER:$SOLR_USER /var/lib/solr

# Restore use of the Solr user for container operations.
USER $SOLR_USER

Now, we could conceivably follow the existing data container configuration to add s6 and confd to the solr container, but when I tried that I got some errors so I stepped back to this simpler approach.
Note that our current example uses solr:5.5, but in my current project implementation I decided to specify a specific patch-level, and use the alpine variant because I'm optimizing for local development access to the Solr service. I believe those could be switched back without otherwise changing what I'm demonstrating.

@grayside
Could you elaborate further as to what these changes mean for someone with solr setup with the following containers? Maybe a more verbose example as to what actually needs to change.
solr:
    container_name: atmosphere_${DOCKER_ENV:-local}_solr
    image: solr:5.5.4
    network_mode: "bridge"
    labels:
      com.dnsdock.name: solr
      com.dnsdock.image: atmosphere
    # For each core you want automatically available add a solr
    # configuration directory mapped under /opt/solr/server/solr
    # The configurations should set the data area for their core
    # to a directory under /var/lib/solr.
    volumes:
      # We make this a unique path so that there are no conflicts with other
      # projects running solr in the container.
      - ./env/solr/core01:/opt/solr/server/solr/atm
    volumes_from:
      - solr_data

# This container exists to allow setting the data area of solr to
  # a persistent storage area and fixing permissions so that the solr
  # container can write to it. This does not need to be done per core.
  solr_data:
    container_name: atmosphere_${DOCKER_ENV:-local}_solr_data
    network_mode: "bridge"
    build: ./env/solr_data
    volumes:
      # We make this a unique path so that there are no conflicts with other
      # projects running solr in the container.
      - /data/solr/solr:/var/lib/solr/atmosphere

volumes_from is deprecated, so instead you would use a named volume. Docker Volumes are like containers in that they are constructs managed by the docker system, but they are specifically for persisting data and making it available at a particular path in one or more container filesystems.
Here's broader context on the volumes section of your docker-compose.yml:
    volumes:
      - ./env/search/cores/core01:/opt/solr/server/solr/core01
      - search-data:/var/lib/solr

This is in progress in #4


docs: Add some other quantco repos

~for glum and metalearners, the PR is still open. let's wait for them with merging~

you need to force merge because the rust ci isn't being picked up in only-docs prs


Fix: Enum unification bug

Fixes #125.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


FLOW CLI is incredibly vague on which contracts failed to deploy

Problem:
The FLOW CLI just outputs "Command Error: failed to deploy all contracts". It would be nicer if it summarized at the end which ones failed to deploy for what reason. A little bit of data clustering would make the error message more meaningful and less useless.
Steps to Reproduce:
Just do "flow project deploy --network testnet" in the root folder of any flow project.
Recommended Output:
"Command Error: Some contracts failed to deploy. 3 Passed and 2 Failed.
Reason for Failure:
ContractFour: The contract is already deployed
ContractFive: Syntax Error: Missing Parenthesis"
Or something like that.

@harshnambiar I think you have a very valid point and I believe the PR should fix it.


Added copysign fixes #152

Please look at the failed CI results, and let me know if you need help...

@peartt Hello, are you still interested in continuing this PR? 🙂 As I would be interested in seeing this merged so we can use it in a project, and would be willing to continue the work.


"An element's ID must be unique" is not an accessibility check

I don't think checking for unique IDs is a good fit for an accessibility audit. We use some SVG icons exported from Adobe Illustrator, which adds in some automatically generated IDs. If those icons occur in the document multiple times, this check fails.
It would certainly be better if we could remove them, but I don't see why this should fail the accessibility audit unless those IDs are referenced as part of an aria-* attribute (they are not).

@calebegg a11y is frequently highly impacted by duplicate ids, discussed in much more detail #141

@alice not sure how to handle duplicates but this is a duplicate of #141 - do we just close?

This one got me thinking... I'm actually surprised that the ids in the SVG are considered by the browser for the purpose of getElementById.
I don't think it changes anything but I guess theoretically it would be possible to ignore any elements that are not in an HTML namespace. Of course the browser doesn't do that so I'm not sure it would make sense.

When using polymer reusable web components to build our page, it received many element's ID  must be unique violations (100+). Polymer provides its shadow dom for its elements, even the element is reused multiple times in the same page, there should be no problem of duplicate ID. Is there anyway to avoid this violation? I have tried inserting aria-hidden="true", but failed.

@wgl85 I would recommend turning this rule off for the time being:

If you're using the extension, you can do this via the extension options.
If you're using the library, you can pass an AuditConfiguration object with auditRulesToIgnore = ['duplicateId']

I would imagine that if you're seeing this issue with Polymer, then you are probably testing it using the "shady dom" polyfill rather than native shadow DOM, since the test uses a query selector which would not select elements inside of true shadow DOM.
It seems like this test is very noisy, sadly. IDREFs in the same scope really should be unique, otherwise there is no point having them, but it is indeed the case that automatically generated code often generates non-unique IDREFs and it is harmless unless something attempts to refer to that ID. Since there is a finite number of situations in which IDREFs may be used, perhaps we should follow @dmazzoni-google's original suggestion of finding all the cases where an IDREF is specified and make sure that each one refers to exactly one element.

@RickSBrown Yeah, I don't think GH issues have an official mechanism, but I think commenting "dup of #" and closing is fine. I'll do that now, and copy my reasoning above into the other bug.

Duplicate of #141.


Cannot run "run_random_agent.py"

Hello.
I'm using m1 Mac and Android emulator version <IP_ADDRESS> and got error
E0305 21:37:52.800976<PHONE_NUMBER> base_simulator.py:71] unknown option: -adb-path
Maybe it's same with issue134 but emulator at https://developer.android.com/studio/emulator_archive was different with mine and couldn't use it. How can I update update emulator and resolve this issue?
Thank you.

Thank you! Now I could launch the emulator.
However, I have remaining issues. After the below message, the codes does not proceed to env.reset in my code.
Do you have any ideas?
I0306 01:04:18.539759<PHONE_NUMBER> emulator_simulator.py:405] See the full emulator logs at '/tmp/android_env/simulator/simulator_instance_zklfmxen/emulator_output'
def main(_):

  with loader.load(
      emulator_path=FLAGS.emulator_path,
      android_sdk_root=FLAGS.android_sdk_root,
      android_avd_home=FLAGS.android_avd_home,
      avd_name=FLAGS.avd_name,
      adb_path=FLAGS.adb_path,
      task_path=FLAGS.task_path,
      run_headless=FLAGS.run_headless) as env:

    action_spec = env.action_spec()

    def get_random_action() -> dict[str, np.ndarray]:
      """Returns a random AndroidEnv action."""
      action = {}
      for k, v in action_spec.items():
        if isinstance(v, specs.DiscreteArray):
          action[k] = np.random.randint(low=0, high=v.num_values, dtype=v.dtype)
        else:
          action[k] = np.random.random(size=v.shape).astype(v.dtype)
      return action

    _ = env.reset()

Can you paste the emulator logs? There's probably a problem booting it.

emulator_output.txt
Here it is.

Additionally, is there a way to downgrade android emulator in android studio to version 29.x.x? I could only find 34.1.18

Thanks for the info.
It seems that the emulator started successfully:
INFO    | Boot completed in 13676 ms

I'm not sure what the problem is, it looks like it is hanging after the emulator is up and running, maybe waiting on an adb command or something.
I don't have an ARM Apple to try this, but I'll see if I can reproduce this on Linux. I can update this bug once I find time to work on this.
I don't know how to downgrade the emulator, but it looks like it's not the culprit now since it seems to be starting well. You can run older Android APIs on recent versions of the Emulator. Do you have a particular reason to downgrade the Emulator?

Thank you, I'll try more to find the problem.
Maybe there are issues at coordinator in loader.py, while task_manager has returned but environment was not returned.
My coworker is using 29.x.x so I tried to reproduce the results.

This issue will be closed due to inactivity.


[SPARK-31197][CORE] Shutdown executor once we are done decommissioning

What changes were proposed in this pull request?
Exit the executor when it has been asked to decommission and there is nothing left for it to do.
This is a rebase of https://github.com/apache/spark/pull/28817
Why are the changes needed?
If we want to use decommissioning in Spark's own scale down we should terminate the executor once finished.
Furthermore, in graceful shutdown it makes sense to release resources we no longer need if we've been asked to shutdown by the cluster manager instead of always holding the resources as long as possible.
Does this PR introduce any user-facing change?
The decommissioned executors will exit and the end of decommissioning. This is sort of a user facing change, however decommissioning hasn't been in any releases yet.
How was this patch tested?
I changed the unit test to not send the executor exit message and still wait on the executor exited message.

Test build #126436 has started for PR 29211 at commit 525b335.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31050/
Test PASSed.

Test build #126437 has started for PR 29211 at commit ba51033.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31051/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126436/
Test FAILed.

test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31053/
Test PASSed.

Test build #126440 has started for PR 29211 at commit ba51033.

cc @attilapiros & @agrawaldevesh

Test build #126437 has finished for PR 29211 at commit ba51033.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126437/
Test PASSed.

Test build #126440 has finished for PR 29211 at commit ba51033.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126440/
Test PASSed.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31063/
Test PASSed.

Test build #126451 has started for PR 29211 at commit fea00dd.

Test build #126453 has started for PR 29211 at commit 12e9e23.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31067/
Test PASSed.

Test build #126456 has started for PR 29211 at commit 46fb2f7.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31070/
Test PASSed.

Test build #126457 has started for PR 29211 at commit 5678d28.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31071/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31074/
Test PASSed.

Test build #126460 has started for PR 29211 at commit 50b9cb2.

Test build #126457 has finished for PR 29211 at commit 5678d28.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126457/
Test FAILed.

Test build #126456 has finished for PR 29211 at commit 46fb2f7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126456/
Test FAILed.

Test build #126453 has finished for PR 29211 at commit 12e9e23.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126453/
Test FAILed.

Test build #126451 has finished for PR 29211 at commit fea00dd.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126451/
Test PASSed.

Test build #126460 has finished for PR 29211 at commit 50b9cb2.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  case class DecommissionWorker(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126460/
Test FAILed.

All of the github actions pass, if no one else wants more time to comment on this, I'll merge this today.

I would like to help here too but I am still busy with SPARK-32198.

Sure, I can hold off on this one then @attilapiros :)

Test build #126510 has started for PR 29211 at commit 484f8e2.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31129/
Test PASSed.

Test build #126510 has finished for PR 29211 at commit 484f8e2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  case class WorkerDecommission(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126510/
Test FAILed.

Test build #126664 has started for PR 29211 at commit 3debd73.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31285/
Test PASSed.

Test build #126664 has finished for PR 29211 at commit 3debd73.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126664/
Test FAILed.

Test build #126666 has started for PR 29211 at commit 63846f1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31287/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126666/
Test FAILed.

Test build #126735 has started for PR 29211 at commit 285600a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31359/
Test PASSed.

Test build #126739 has started for PR 29211 at commit 03a88ff.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31362/
Test PASSed.

Test build #126739 has finished for PR 29211 at commit 03a88ff.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126739/
Test FAILed.

Test build #126740 has started for PR 29211 at commit 0e023a0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31363/
Test PASSed.

So it seems without the thread start, we end up in the situation where there is an orphan worker (see https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/126735/console ) so I think that's covered. I'll double-check that this goes away once we put the thread start back in, otherwise I'll do some more poking.

Test build #126740 has finished for PR 29211 at commit 0e023a0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126740/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126735/
Test FAILed.

Test build #126791 has started for PR 29211 at commit eb3acd2.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31413/
Test PASSed.

Test build #126791 has finished for PR 29211 at commit eb3acd2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31437/
Test PASSed.

Test build #126816 has started for PR 29211 at commit 490b8a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31451/
Test PASSed.

Test build #126816 has finished for PR 29211 at commit 490b8a3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #126828 has started for PR 29211 at commit 0ee7c4b.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126816/
Test FAILed.

Test build #126828 has finished for PR 29211 at commit 0ee7c4b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126828/
Test PASSed.

So we don’t reject tasks sent to us and an executor can start
decommissioning without the driver knowing yet so it is possible (although
unlikely) to get a new task after we’ve started decommissioning.
On Fri, Jul 31, 2020 at 6:58 AM Attila Zsolt Piros<EMAIL_ADDRESS>wrote:

@attilapiros commented on this pull request.
In
core/src/main/scala/org/apache/spark/storage/BlockManagerDecommissioner.scala
https://github.com/apache/spark/pull/29211#discussion_r463627379:

@@ -327,4 +354,28 @@ private[storage] class BlockManagerDecommissioner(
}
logInfo("Stopped storage decommissioner")
}

/*

Returns the last migration time and a boolean for if all blocks have been migrated.

If there are any tasks running since that time the boolean may be incorrect.

*/
private[storage] def lastMigrationInfo(): (Long, Boolean) = {
if (stopped || (stoppedRDD && stoppedShuffle)) {

 (System.nanoTime(), true)

} else {

 // Chose the min of the running times.

 val lastMigrationTime = if (

   conf.get(config.STORAGE_DECOMMISSION_SHUFFLE_BLOCKS_ENABLED) &&

   conf.get(config.STORAGE_DECOMMISSION_RDD_BLOCKS_ENABLED)) {

   Math.min(lastRDDMigrationTime, lastShuffleMigrationTime)

Now I am starting to get this part. Can we try to simplify this? :)
On a decommissioned executor there will be no new tasks started, right?
(Theoretically one task could be started as the scheduler does not
processed the DecommissionExecutor message but let's take this corner
case out as we can have this first 1 sec sleep which more or less handles
this).
So when executor.numRunningTasks will be 0 it stays 0. As I remember
caching is part of task running so no new cached blocks will be created
when numRunningTasks=0.
So would it work if we first wait to reach numRunningTasks==0 in a sleep
check loop and then we would check for the migration finished flag without
using the time part of lastMigrationInfo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/29211#discussion_r463627379, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAOT5I4FIQYBIEAGKJPETTR6LEXXANCNFSM4PGENWSA
.

--
Cell :<PHONE_NUMBER>

Test build #126899 has started for PR 29211 at commit b9eb4f3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31524/
Test PASSed.

Test build #126899 has finished for PR 29211 at commit b9eb4f3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126899/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31623/
Test PASSed.

Test build #126999 has started for PR 29211 at commit 96049a0.

Test build #126999 has finished for PR 29211 at commit 96049a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126999/
Test PASSed.

I've added a bunch of tests around the timestamp stuff. I think it's got all of the cases folks were asking for covered, and in the discussion on the PR to this PR it seems like we're in agreement that while the timestamps are complex, it beats the alternative of maybe having a race condition and trying to mitigate with a thread sleep.
With that in mind, if there is no other active discussion I'll consider this to be a lazy consensus.

Test build #127061 has started for PR 29211 at commit 4d3252d.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31683/
Test PASSed.

Test build #127061 has finished for PR 29211 at commit 4d3252d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127061/
Test FAILed.

Test build #127067 has started for PR 29211 at commit 55a7f1f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31689/
Test PASSed.

Test build #127067 has finished for PR 29211 at commit 55a7f1f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127067/
Test PASSed.

Test build #127076 has started for PR 29211 at commit 477e77f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31698/
Test PASSed.

Test build #127076 has finished for PR 29211 at commit 477e77f.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127076/
Test FAILed.

The only outstanding point of discussion is a test timeout length, which I don't believe is critical to address. If CI passes I intend to merge this PR and rebase the next PR which brings the feature full circle.

Test build #127101 has started for PR 29211 at commit e81c3fc.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31724/
Test PASSed.

Test build #127101 has finished for PR 29211 at commit e81c3fc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127101/
Test PASSed.

Since it's approved and passing jenkins & GHA I'm going to merge this, but I'll add the comment about the time in the follow up I'll rebase on top of this after merge.

Merged to the dev branch :)

cc @tgravescs, @mridulm, @squito, @Ngone51, @jiangxb1987 as well FYI


[CARBONDATA-3175]Fix Testcase failures in complex deleimiters

Fix Testcase failures in complex deleimiters:
Changed the complex delimiter in testcases

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1759/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10018/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1970/

LGTM


DatimeTimePicker rendering issue

Hello
I am trying to use the DateTimePicker object in the latest version and it seems like if the component is part of a DMC drawer or a children of an Accordion component - it does not render properly.

This is how I am defining the DateTImePicker
dmc.DateTimePicker(label='Recording End Time', id=f'{cls.selected_test}_stop_time_datetime',
                                                                                value=datetime.now(),valueFormat="MM/DD/YYYY HH:mm:ss",
                                                                                withSeconds=True,popoverProps={'zindex': 10000})

where the drawer component has a zinder of 5000.
Am I doing something wrong?

Hi @sssaha
Be sure to include the additional stylesheets
See the getting started section for more info  - https://www.dash-mantine-components.com/getting-started
https://www.dash-mantine-components.com/getting-started

I did - but I think I found what is the issue. I use both the bootstrap and dmc styles, dmc styles.ALL is a list where everything else is just the stylesheet itself. So I had external stylesheet like this - external_stylesheets=[dbc.themes.BOOTSTRAP,dmc.styles.ALL] - which is wrong. It was an issue on my end.

Glad you solved the problem :tada:
It's noted in the Getting Started Section as well:

@AnnMarieW
So now the rendering is fine in terms of component. However see the screenshot - where the popover is behind the drawer - even through the drawer has a lower z index than the popover as I set via the popoverProps={'zindex': 1000000}

Hi @sssaha
Can you make a complete minimal example that reproduces the issue?

Please close this ticket. I found the issue. In the popovertargets parameter of the date time picker I had dict(zindex=300000), which should be dict(zIndex=300000)

Thanks for your help


Reorganize TS functions in catalog

Now we have 4 TS functions in the functions catalog repo. Per repo structure that we desire, these functions should be put into different directory and make each function self-contained.
Functions:

helm-inflator
istioctl-analyze
kubeval
sops

We should be able to easily build a single TS function. Currently we rely on kpt-functions-sdk to build all of the functions with the same tag. There is no way to build a specific TS function with a tag.
We can do that for golang functions. e.g. CURRENT_FUNCTION=set-namespace TAG=v1.2.3 make func-build.

We should be able to easily build a single TS function. Currently we rely on kpt-functions-sdk to build all of the functions with the same tag. There is no way to build a specific TS function with a tag.
We can do that for golang functions. e.g. CURRENT_FUNCTION=set-namespace TAG=v1.2.3 make func-build.

I think split the TS functions to separate directory may make building single function work.

I think split the TS functions to separate directory may make building single function work.


[BUG] ME Conduits use too much power

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The ME Conduit uses 0.5 AE/t (1 µI) and the Dense uses 2 AE/t (4 µI).
In AE2 the Dense Cables don't have a Passive Drain adding one increases the power drain by 0.02AE/t
Expected Behavior
The Conduits should not consume 100x as much as those of AE2
Steps To Reproduce
No response
Environment
- OS:
- Java version:
- Minecraft version:
- Version:

Anything else?
No response

this is intentional to not solely rely on me conduits to give , however the power usage wasn't changed alongside the recent energy rebalance we've done and 1FE/t and 4FE/t are probably a bit too much, bringing those numbers down to a reasonable, but not ignorable amount should probably be considered

I looked already in to the code and I am pretty sure it's because of this line AE2InWorldConduitNodeHost.java#L33. It was probably set that high while development and than forgotten

it was just forgotten to be updated with the energy rebalance, the cost shouldn't be that low that you can ignore it easily (early game) because I wanted to balance their compactness with energy cost, reducing them by 80% seems reasaonable though


Update license to remove Copyright year.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi Andrew, you can fix the ProofAlarm failure by updating the hash in .github/workflows/proof-alarm.yml from 9276b7251 to aaabab98c. We have a set of proofs for the epoll event loop, however they're maintained separately from the implementation. The proof alarm warns if the source file changes, which might mean the proofs need to be updated. In this case, the license change is not a concern for the correctness of the proofs so it's safe to update the alarm.

Ah the merge changed the hash to 84bfb96d so the alarm is still failing. I'll make a PR.


CAS4 upgrade

Still need to update the sample and test, but thought to open this up for review.

bump

I almost pushed that Merge button ;-)

We'll wait a few more days to allow everyone to review. At some point, we might merge on lazy consensus.

Have we got a client that actively wants it?

I'm confused by the versioning. Why is this a 1.0.0-SNAPSHOT when 1.0.0 is already a release?

I'm confused by the versioning. Why is this a 1.0.0-SNAPSHOT when 1.0.0 is already a release?

Looks like the cas-server-support-wsfederation/pom.xml got bumped, but not the parent one. I'd suspect this should get change to 1.1 or 1.0.1 before merging.

The versioning structure of the project is confusing.
You have:
a parent pom at 1.0.0-SNAPSHOT
the parent pom has 2 modules:
the wsfed module is at 1.0.1-SNAPSHOT
the sample site is at ${cas.version}
So I dont know.
Typically, all modules are children of a parent pom, who all share the same version number. If you manually update and manage pom versions and untangle a child from its own parent, then it gets confusing to update and manage releases. All modules should point to the same parent. If modules dont inherit from the same parent, then they should not belong to the project.
Suggestions?

To elaborate furthermore:
if you want a sample app that basically shows how the module can integrated with ADFS support, GREAT! It needs its own project.
If you want a sample overlay that is released alongside the same module structure which suggests to folks that they too can build overlays on top of it, then the sample becomes a child and is released alongside the same set.
Make sense, or am I off?

I never intended for there to be a parent pom... someone else added that. :)
With that said... They should be consistent...

if you want a sample app that basically shows how the module can integrated with ADFS support, GREAT! It needs its own project.

Define "own project"... Do you mean its own repo? Cause by definition a pom.xml is a project and that's what it has.

Cool. Lets get to fixing :) I'll update this.
As for an active enthusiasts who wants it, yes, I have to dig up their name. At the apereo conference I was asked if the module supports CAS4, and think do have an email from one gentleman who did ask.

By "own project" I mean its own repo, yes. If you want it to have an independent lifecycle from the rest of the application, then you dont really want it to be a children of the parent pom. It's a like stranger living in your house. He doesn't eat the same food, he doesn't use the same resources, he doesn't do laundry, guests come over and ask" who is this guy?" and we have to launch into a complicated explanation. He's just there waiting for a new apartment to be found, but it never is found :D

Oh man... :D
As we said in private chat a few days ago. I'm fine with it being a sub-project, but would like a comment saying "Implementers: comment out/remove this parent block to run this in a standalone mode...".
Does that still work? I'm guessing the enthusiast will appreciate it. ;)

:)
So you mean, if I clone it the module and decide to run the sample app? That depends.
As a typical deployer, if I clone the module, I'd simply run mvn package at the root of the app, grab the war and deploy that. No further changes should be required, I don't think. That's the shortest path to success. Removing the parent doesn't get me much, other than the fact it allows me to possibly run the sample site against a different version of the ws-fed module, (which means not only I should remove the parent, I also have to change the versions as well because those are no longer inherited right?) and I dont know why I would want to do that. When I clone snapshot code, I always accept the risk of "it may not work". So I would want it to run against the code I downloaded in same transaction.
That's a long way of saying, sure! A comment can be added, but offhand, I don't understand why someone would want to do something like that?

P.S: Apologies if some of this stuff is redundant or repetitive. This is evidence that I am losing brain cells :)

Typical use of the example module was "hey go grab the source (as a zip since most didn't get git), grab the example directory and that is your cas overlay source. Now. update the cas.properties and wsfed.xml, and figure out your services registry, then live long and prosper."
A newb could be running CAS and integrated with ADFS in less 30 minutes if they stuck with the wild card service entry.

Makes good sense, thanks. I updated the module to include additional comments on how the sample site can be detached from the parent and run independently.

Defaults are also removed for those that didnt make sense.

I think you may have clicked into the commit. On the latest changes in that branch, I cant find any iml files.

Couple of items of polish, then I think it is good to go.

Great, thank you @jtgasper3 for your review. Please merge when you find the chance. Pull is updated.

Thank you for taking this on.


user_path methods take required_fields keyword argument

This updates the user_path methods for all CRMs to take an optional required_fields keyword argument. Support for the deprecated phone_required argument is removed. For krautbuster, petition_id becomes a keyword argument.
Because this is a breaking change, the major version is increased.

Let's start URI escaping everything untrusted.


MAP fits Failing for BetaGeoModel

Should probably fix this before the Official Release:
from lifetimes.datasets import load_cdnow_summary
from pymc_marketing.clv import BetaGeoModel

df = load_cdnow_summary()

model = BetaGeoModel(customer_id=df['ID'],
                     frequency=df['frequency'],
                     recency=df['recency'],
                     T=df['T'],
                    )

model.fit(fit_method='map')

SamplingError: Initial evaluation of model at starting point failed!
Starting values:
{'a_log__': array(0.), 'b_log__': array(0.), 'alpha_log__': array(0.), 'r_log__': array(0.)}

Initial evaluation results:
{'a': 0.0, 'b': 0.0, 'alpha': 0.0, 'r': 0.0, 'likelihood': nan}

Can probably use a custom initial value for the priors if that's the problem.

This has caused a lot of confusion but the second dictionary contains the log-probabilities

This has caused a lot of confusion: the second dictionary contains the log-probabilities. We should write it explicitly in the error message

I can create a beginner friendly issue in the PyMC repo later today

This has caused a lot of confusion: the second dictionary contains the log-probabilities. We should write it explicitly in the error message

I can create a beginner friendly issue in the PyMC repo later today

That would be good!

For sorting the issue, we need to know why is a = b = alpha = r = 1 invalid, and what would be a safe default instead. This could also mean that simple positive priors may be incorrect for this model?

For sorting the issue, we need to know why is a = b = alpha = r = 1 invalid, and what would be a safe default instead. This could also mean that simple positive priors may be incorrect for this model?

Parameter values must be positive, but a and b are parameters of a beta distribution. Might work better to pool those priors. Here's some code I wrote in the past for this model:
https://github.com/ColtAllen/btyd/blob/main/btyd/models/beta_geo_model.py#L97

Regularizing the priors is certainly important, but the snippet above is failing already at the initial point. That means those values can't all be 1 for this dataset (or if they can, our log is too unstable)

In the logp expression:
c4 = a / (b + x - 1)

logp = d1 + d2 + pt.log(c3 + c4 * pt.switch(x_zero, 1, 0))

c4 will throw a DIV/0 if b=1 and x=0. Should it be placed inside pt.switch()?

In the logp expression:
c4 = a / (b + x - 1)

logp = d1 + d2 + pt.log(c3 + c4 * pt.switch(x_zero, 1, 0))

c4 will throw a DIV/0 if b=1 and x=0. Should it be placed inside pt.switch()?

That sounds right! Good catch

Cool, yeah sounds like that would solve it

I can spin a PR for this


lodash vulnerability

We're relying on this package in an open source project of ours which is monitored by snyk, which noticed that you're depending on a version of lodash < 4.17.5 (specifically 3.7.0). There is a vulnerability which 4.17.5 fixes:
https://snyk.io/vuln/npm:lodash:20180130
https://hackerone.com/reports/310443
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3721
I'm not clear on whether bumping the lodash dependency breaks anything (I'll admit I haven't tried) but maybe someone wants to see how much work would be involved in addressing this?

+1

Just FYI - I've just a published a new version of this module which is a complete rewrite using Google's V4 Sheets API (v3 is being deprecated on March 3, 2020).
Docs available here - https://theoephraim.github.io/node-google-spreadsheet
Thanks! 😄


sqlalchemy does not have a type called Double

see dtype.py:196:
DType.FLOAT64: sa.Double(),
Is this a problem that ruff should have picked up?

I have seen FLOAT(53)=double vs. FLOAT(24)=real/float but I am not sure this is reliable across all database targets. We can test with databases pipedag supports.
Random link about this topic: https://stackoverflow.com/questions/1056323/difference-between-numeric-float-and-decimal-in-sql-server


Changed a type  variable in an attempt to quelch shadow warnings.

This very well may be the wrong fix. Tests pass and the library compiles, but I wasn't sure if any of the a's from the first forall black were meant to some how carry over to the quantification specified in the second block.
Perhaps I need to revisit Purescript By Example for this one?
This is the last of warnings produced in purescript/purescript#1063 that shouldn't require a compiler change.

:+1: Looks good, thanks!


Fix typeahead ordering for user group mentions

Here's what you currently get when trying to autocomplete @mobile on chat.zulip.org with the typeahead:

We should definitely sort user group exact prefix matches ahead of users who don't have a prefix match.
@hamletcharacters is the test user group present in the dev environment by default.
It's possible the quick fix here is to just put user groups before everything else.

@zulipbot claim Maybe this recipients.concat(groups) is causing the problem, it needs some change in logic of sorting.

Yeah, let's try doing groups first.


Show something in the home page when user have no organization

When issue #4572 will be done, users will have option to leave an organization. Users can leave all of the current organizations. When this happens, the home page will be empty with a search bar to search application. See the attachment to get an idea of how it looks like now.
A new home page should be designed for this state. It may contain some messages to guide users about the state and where to go from here.

Not valid since users cannot leave their own personal organization and a very edge case so closing it till someone complains


Unable to delete deployment after upgrading from v219 to v246

We're running into some DB schema issues when trying to delete a deployment on a BOSH that we've upgraded from v219 to v246. The error being thrown is:
PG::Error: ERROR:  update or delete on table "deployments" violates foreign key constraint "vms_deployment_id_fkey" on table "vms" DETAIL:  Key (id)=(18) is still referenced from table "vms".
It's occurring on BOSH's hooked up to both AWS + vSphere. When we take a look at the VMs table, there are a bunch of VMs in there with cids who do not match any live instances. It looks like the data from the vms table was migrated into the instances table, somewhere between v219 and v246, but never cleaned up. Is the vms table no longer used for anything?
If so, can it be cleaned up via another schema migration?
Reproduction steps should be deploy BOSH v219.. deploy a boshrelease with VMs. Upgrade BOSH to v246. Try running a bosh delete deployment

yup. unfortunelty our integration testing didnt catch this migration breakage. next build will it.
Sent from my iPhone

On Jan 21, 2016, at 7:52 AM, Geoff Franks<EMAIL_ADDRESS>wrote:
We're running into some DB schema issues when trying to delete a deployment on a BOSH that we've upgraded from v219 to v246. The error being thrown is:
PG::Error: ERROR: update or delete on table "deployments" violates foreign key constraint "vms_deployment_id_fkey" on table "vms" DETAIL: Key (id)=(18) is still referenced from table "vms".
It's occurring on BOSH's hooked up to both AWS + vSphere. When we take a look at the VMs table, there are a bunch of VMs in there with cids who do not match any live instances. It looks like the data from the vms table was migrated into the instances table, somewhere between v219 and v246, but never cleaned up. Is the vms table no longer used for anything?
If so, can it be cleaned up via another schema migration?
Reproduction steps should be deploy BOSH v219.. deploy a boshrelease with VMs. Upgrade BOSH to v246. Try running a bosh delete deployment
—
Reply to this email directly or view it on GitHub.

I think this was fixed in v250 and can be closed.


mount empty dir for user containers in openshift environment

Why:
fix #3738
This change addresses the need by:
pod in openshift runs in unprivilege mode, for every pps worker, it
would create directory recursively in container, which leading to wrong
state.
@JoeyZwicker @gabrielgrant please review, thanks.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @jiangytcn We'll review asap and hopefully get this all sorted out for 1.9.2 which will be cut this week

LGTM, merging.


UTF8 in file names not supported

When i try to bag a set of files with unicode chars in it, pybagit fails.
I expected pybagit to include those filenames in the resulting bag.
Additionally I expect pybagit to crash on this error, but somehow this stacktrace is printed without crashing the app. I think it has to do with pybagit.py calling multichecksum.py with subprocess.popen.
When i try it without unicode filenames, no problems occur.
Example filenames:
/dir/Kopiâren.htm
/dir/tëst.gif
The stacktrace:
Traceback (most recent call last):
File "/srv/tu3/venv/lib/python2.7/site-packages/pybagit/multichecksum.py", line 111, in
write_manifest(args[0], ENCODING)
File "/srv/tu3/venv/lib/python2.7/site-packages/pybagit/multichecksum.py", line 54, in write_manifest
mfile.write("{0} {1}\n".format(csum, fl))
File "/srv/tu3/venv/lib/python2.7/codecs.py", line 691, in write
return self.writer.write(data)
File "/srv/tu3/venv/lib/python2.7/codecs.py", line 351, in write
data, consumed = self.encode(object, self.errors)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xcc in position 59: ordinal not in range(128)

I can confirm that this issue has been resolved. @RoelWKramer is actually an (ex-)colleague of mine so I know it works for the current codebase now :)

Ok, great. Thanks!