Installing Rancher by run docker image on RHEL 8.5

Greetings All,
I’m have a new VM based on RHEL 8.5 and tried to install Rancher using the below simple command from formal rancher page here (Getting Started with Kubernetes | Rancher Quick Start)
sudo docker run --privileged -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher
but after the container start it keep restarting & the below errors appears.
Any Idea?
[root@redhat-vm-01 ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NA MES
e8fbd2a4d67e rancher/rancher “entrypoint.sh” 5 minutes ago Up 12 seconds <IP_ADDRESS>:80->80/tcp, :::80->80/tcp, <IP_ADDRESS>:443->443/tcp, :::443->443/tcp tr usting_shockley
[root@redhat-vm-01 ~]# docker logs -f e8fbd2a4d67e
2022/01/05 20:42:24 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:42:24 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:42:24 [INFO] Listening on /tmp/log.sock
2022/01/05 20:42:24 [INFO] Waiting for k3s to start
time=“2022-01-05T20:42:24Z” level=info msg=“Acquiring lock file /var/lib/rancher /k3s/data/.lock”
time=“2022-01-05T20:42:24Z” level=info msg=“Preparing data dir /var/lib/rancher/ k3s/data/e61cd97f31a54dbcd9893f8325b7133cfdfd0229ff3bfae5a4f845780a93e84c”
2022/01/05 20:42:25 [INFO] Waiting for k3s to start
2022/01/05 20:42:26 [INFO] Waiting for k3s to start
2022/01/05 20:42:28 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:42:30 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:42:32 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:42:34 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:42:36 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:42:48 [INFO] Running in single server mode, will not peer connecti ons
2022/01/05 20:42:48 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD navlinks.ui.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD clusters.management.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD apiservices.management.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD clusterregistrationtokens.management.cat tle.io
2022/01/05 20:42:50 [INFO] Applying CRD settings.management.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD preferences.management.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD clusterrepos.catalog.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD operations.catalog.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD apps.catalog.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD fleetworkspaces.management.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD bundles.fleet.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD clusters.fleet.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD managedcharts.management.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD clusters.provisioning.cattle.io
2022/01/05 20:42:50 [INFO] Applying CRD clusters.provisioning.cattle.io
2022/01/05 20:42:51 [INFO] Applying CRD rkeclusters.rke.cattle.io
2022/01/05 20:42:51 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2022/01/05 20:42:51 [INFO] Applying CRD rkebootstraps.rke.cattle.io
2022/01/05 20:42:51 [INFO] Applying CRD rkebootstraptemplates.rke.cattle.io
2022/01/05 20:42:51 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2022/01/05 20:42:51 [INFO] Applying CRD custommachines.rke.cattle.io
2022/01/05 20:42:51 [INFO] Applying CRD clusters.cluster.x-k8s.io
2022/01/05 20:42:51 [INFO] Applying CRD machinedeployments.cluster.x-k8s.io
2022/01/05 20:42:51 [INFO] Applying CRD machinehealthchecks.cluster.x-k8s.io
2022/01/05 20:42:51 [INFO] Applying CRD machines.cluster.x-k8s.io
2022/01/05 20:42:51 [INFO] Applying CRD machinesets.cluster.x-k8s.io
2022/01/05 20:42:51 [INFO] Waiting for CRD machinesets.cluster.x-k8s.io to becom e available
2022/01/05 20:42:52 [INFO] Done waiting for CRD machinesets.cluster.x-k8s.io to become available
2022/01/05 20:42:52 [INFO] Creating CRD authconfigs.management.cattle.io
2022/01/05 20:42:52 [INFO] Creating CRD groupmembers.management.cattle.io
2022/01/05 20:42:52 [INFO] Creating CRD groups.management.cattle.io
2022/01/05 20:42:52 [INFO] Creating CRD tokens.management.cattle.io
2022/01/05 20:42:52 [INFO] Creating CRD userattributes.management.cattle.io
2022/01/05 20:42:52 [INFO] Creating CRD users.management.cattle.io
2022/01/05 20:42:52 [INFO] Waiting for CRD users.management.cattle.io to become available
2022/01/05 20:42:53 [INFO] Done waiting for CRD users.management.cattle.io to be come available
2022/01/05 20:42:54 [INFO] Creating CRD clusterroletemplatebindings.management.c attle.io
2022/01/05 20:42:54 [INFO] Creating CRD catalogs.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD catalogtemplates.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD apps.project.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD dynamicschemas.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD apprevisions.project.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD etcdbackups.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD catalogtemplateversions.management.cattl e.io
2022/01/05 20:42:54 [INFO] Creating CRD globalrolebindings.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clusteralerts.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD pipelineexecutions.project.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD globalroles.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clusteralertgroups.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD pipelinesettings.project.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD kontainerdrivers.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clustercatalogs.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD pipelines.project.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD sourcecodecredentials.project.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD nodedrivers.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clusterloggings.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clusteralertrules.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD sourcecodeproviderconfigs.project.cattle .io
2022/01/05 20:42:54 [INFO] Creating CRD nodepools.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD nodetemplates.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clustermonitorgraphs.management.cattle.i o
2022/01/05 20:42:54 [INFO] Creating CRD sourcecoderepositories.project.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clusterscans.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD nodes.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD composeconfigs.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD podsecuritypolicytemplateprojectbindings .management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD podsecuritypolicytemplates.management.ca ttle.io
2022/01/05 20:42:54 [INFO] Waiting for CRD pipelinesettings.project.cattle.io to become available
2022/01/05 20:42:54 [INFO] Creating CRD multiclusterapps.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD projectnetworkpolicies.management.cattle .io
2022/01/05 20:42:54 [INFO] Creating CRD multiclusterapprevisions.management.catt le.io
2022/01/05 20:42:54 [INFO] Creating CRD projectroletemplatebindings.management.c attle.io
2022/01/05 20:42:54 [INFO] Creating CRD monitormetrics.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD projects.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD notifiers.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD rkek8ssystemimages.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD rkek8sserviceoptions.management.cattle.i o
2022/01/05 20:42:54 [INFO] Creating CRD projectalerts.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD rkeaddons.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD projectalertgroups.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD roletemplates.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD projectcatalogs.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD projectloggings.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD samltokens.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clustertemplates.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD projectalertrules.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD clustertemplaterevisions.management.catt le.io
2022/01/05 20:42:54 [INFO] Creating CRD projectmonitorgraphs.management.cattle.i o
2022/01/05 20:42:54 [INFO] Creating CRD cisconfigs.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD cisbenchmarkversions.management.cattle.i o
2022/01/05 20:42:54 [INFO] Creating CRD templates.management.cattle.io
2022/01/05 20:42:54 [INFO] Waiting for CRD nodepools.management.cattle.io to bec ome available
2022/01/05 20:42:54 [INFO] Creating CRD templateversions.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD templatecontents.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD globaldnses.management.cattle.io
2022/01/05 20:42:54 [INFO] Creating CRD globaldnsproviders.management.cattle.io
2022/01/05 20:42:54 [INFO] Done waiting for CRD pipelinesettings.project.cattle. io to become available
2022/01/05 20:42:54 [INFO] Waiting for CRD pipelines.project.cattle.io to become available
2022/01/05 20:42:55 [INFO] Waiting for CRD clusterscans.management.cattle.io to become available
2022/01/05 20:42:55 [INFO] Done waiting for CRD nodepools.management.cattle.io t o become available
2022/01/05 20:42:55 [INFO] Waiting for CRD nodetemplates.management.cattle.io to become available
2022/01/05 20:42:55 [INFO] Done waiting for CRD pipelines.project.cattle.io to b ecome available
2022/01/05 20:42:55 [INFO] Waiting for CRD sourcecodecredentials.project.cattle. io to become available
2022/01/05 20:42:55 [INFO] Done waiting for CRD clusterscans.management.cattle.i o to become available
2022/01/05 20:42:55 [INFO] Waiting for CRD composeconfigs.management.cattle.io t o become available
2022/01/05 20:42:55 [INFO] Done waiting for CRD nodetemplates.management.cattle. io to become available
2022/01/05 20:42:55 [INFO] Waiting for CRD nodes.management.cattle.io to become available
2022/01/05 20:42:56 [INFO] Done waiting for CRD sourcecodecredentials.project.ca ttle.io to become available
2022/01/05 20:42:56 [INFO] Waiting for CRD sourcecodeproviderconfigs.project.cat tle.io to become available
2022/01/05 20:42:56 [INFO] Done waiting for CRD composeconfigs.management.cattle .io to become available
2022/01/05 20:42:56 [INFO] Waiting for CRD projectcatalogs.management.cattle.io to become available
2022/01/05 20:42:56 [INFO] Done waiting for CRD nodes.management.cattle.io to be come available
2022/01/05 20:42:56 [INFO] Waiting for CRD roletemplates.management.cattle.io to become available
2022/01/05 20:42:56 [INFO] Done waiting for CRD sourcecodeproviderconfigs.projec t.cattle.io to become available
2022/01/05 20:42:56 [INFO] Waiting for CRD sourcecoderepositories.project.cattle .io to become available
2022/01/05 20:42:56 [INFO] Done waiting for CRD projectcatalogs.management.cattl e.io to become available
2022/01/05 20:42:56 [INFO] Waiting for CRD cisconfigs.management.cattle.io to be come available
2022/01/05 20:42:56 [INFO] Done waiting for CRD roletemplates.management.cattle. io to become available
2022/01/05 20:42:56 [INFO] Waiting for CRD clustertemplates.management.cattle.io to become available
2022/01/05 20:42:57 [INFO] Done waiting for CRD sourcecoderepositories.project.c attle.io to become available
2022/01/05 20:42:57 [INFO] Waiting for CRD pipelineexecutions.project.cattle.io to become available
2022/01/05 20:42:57 [INFO] Done waiting for CRD cisconfigs.management.cattle.io to become available
2022/01/05 20:42:57 [INFO] Waiting for CRD templates.management.cattle.io to bec ome available
2022/01/05 20:42:57 [INFO] Done waiting for CRD clustertemplates.management.catt le.io to become available
2022/01/05 20:42:57 [INFO] Waiting for CRD podsecuritypolicytemplateprojectbindi ngs.management.cattle.io to become available
2022/01/05 20:42:57 [INFO] Done waiting for CRD pipelineexecutions.project.cattl e.io to become available
2022/01/05 20:42:57 [INFO] Done waiting for CRD templates.management.cattle.io t o become available
2022/01/05 20:42:57 [INFO] Waiting for CRD templateversions.management.cattle.io to become available
2022/01/05 20:42:57 [INFO] Done waiting for CRD podsecuritypolicytemplateproject bindings.management.cattle.io to become available
2022/01/05 20:42:57 [INFO] Waiting for CRD samltokens.management.cattle.io to be come available
2022/01/05 20:42:58 [INFO] Done waiting for CRD templateversions.management.catt le.io to become available
2022/01/05 20:42:58 [INFO] Waiting for CRD globaldnsproviders.management.cattle. io to become available
2022/01/05 20:42:58 [INFO] Done waiting for CRD samltokens.management.cattle.io to become available
2022/01/05 20:42:58 [INFO] Waiting for CRD podsecuritypolicytemplates.management .cattle.io to become available
2022/01/05 20:42:58 [INFO] Done waiting for CRD globaldnsproviders.management.ca ttle.io to become available
2022/01/05 20:42:58 [INFO] Waiting for CRD projectalerts.management.cattle.io to become available
2022/01/05 20:42:58 [INFO] Done waiting for CRD podsecuritypolicytemplates.manag ement.cattle.io to become available
2022/01/05 20:42:58 [INFO] Waiting for CRD projectnetworkpolicies.management.cat tle.io to become available
2022/01/05 20:42:59 [INFO] Done waiting for CRD projectalerts.management.cattle. io to become available
2022/01/05 20:42:59 [INFO] Waiting for CRD projectalertrules.management.cattle.i o to become available
2022/01/05 20:42:59 [FATAL] k3s exited with: exit status 255
2022/01/05 20:43:17 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:43:17 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:43:17 [INFO] Listening on /tmp/log.sock
2022/01/05 20:43:17 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:43:19 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:43:21 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:43:23 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:43:25 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:43:27 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:43:29 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:43:35 [FATAL] k3s exited with: exit status 255
2022/01/05 20:43:53 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:43:53 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:43:53 [INFO] Listening on /tmp/log.sock
2022/01/05 20:43:53 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:43:55 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:43:57 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:43:59 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:44:01 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:44:03 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:44:05 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:44:07 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:44:09 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:44:15 [FATAL] k3s exited with: exit status 255
2022/01/05 20:44:31 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:44:31 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:44:31 [INFO] Listening on /tmp/log.sock
2022/01/05 20:44:31 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:44:33 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:44:35 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:44:37 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:44:39 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:44:41 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:44:43 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:44:45 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:44:50 [FATAL] k3s exited with: exit status 255
2022/01/05 20:45:08 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:45:08 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:45:08 [INFO] Listening on /tmp/log.sock
2022/01/05 20:45:08 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:10 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:12 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:14 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:16 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:18 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:45:20 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:45:22 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:45:24 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:45:26 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:45:28 [INFO] Running in single server mode, will not peer connecti ons
2022/01/05 20:45:28 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:45:29 [INFO] Applying CRD navlinks.ui.cattle.io
2022/01/05 20:45:29 [INFO] Applying CRD clusters.management.cattle.io
2022/01/05 20:45:29 [INFO] Applying CRD apiservices.management.cattle.io
2022/01/05 20:45:29 [INFO] Applying CRD clusterregistrationtokens.management.cat tle.io
2022/01/05 20:45:29 [INFO] Applying CRD settings.management.cattle.io
2022/01/05 20:45:29 [INFO] Applying CRD preferences.management.cattle.io
2022/01/05 20:45:30 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:45:30 [INFO] Applying CRD clusterrepos.catalog.cattle.io
2022/01/05 20:45:30 [INFO] Applying CRD operations.catalog.cattle.io
2022/01/05 20:45:30 [INFO] Applying CRD apps.catalog.cattle.io
2022/01/05 20:45:30 [INFO] Applying CRD fleetworkspaces.management.cattle.io
2022/01/05 20:45:30 [INFO] Applying CRD managedcharts.management.cattle.io
2022/01/05 20:45:31 [FATAL] failed to update managedcharts.management.cattle.io apiextensions.k8s.io/v1, Kind=CustomResourceDefinition for managedcharts.manage ment.cattle.io: Patch “https://<IP_ADDRESS>:6443/apis/apiextensions.k8s.io/v1/custo mresourcedefinitions/managedcharts.management.cattle.io?timeout=15m0s”: EOF
2022/01/05 20:45:47 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:45:47 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:45:47 [INFO] Listening on /tmp/log.sock
2022/01/05 20:45:47 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:49 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:51 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:53 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:45:55 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:45:57 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:45:59 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:46:01 [INFO] Running in single server mode, will not peer connecti ons
2022/01/05 20:46:01 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:46:03 [INFO] Applying CRD navlinks.ui.cattle.io
2022/01/05 20:46:03 [INFO] Applying CRD clusters.management.cattle.io
2022/01/05 20:46:03 [FATAL] failed to update clusters.management.cattle.io apiex tensions.k8s.io/v1, Kind=CustomResourceDefinition for clusters.management.cattl e.io: Patch “https://<IP_ADDRESS>:6443/apis/apiextensions.k8s.io/v1/customresourced efinitions/clusters.management.cattle.io?timeout=15m0s”: EOF
2022/01/05 20:46:22 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:46:22 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:46:22 [INFO] Listening on /tmp/log.sock
2022/01/05 20:46:22 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:46:24 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:46:26 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:46:28 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:46:30 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:46:32 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:46:34 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:46:36 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:46:38 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:46:40 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:46:46 [FATAL] k3s exited with: exit status 255
2022/01/05 20:47:03 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:47:03 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:47:03 [INFO] Listening on /tmp/log.sock
2022/01/05 20:47:03 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:05 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:07 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:09 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:11 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:13 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:15 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:47:17 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:47:19 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:47:21 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:47:23 [INFO] Running in single server mode, will not peer connecti ons
2022/01/05 20:47:23 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:47:24 [INFO] Applying CRD navlinks.ui.cattle.io
2022/01/05 20:47:24 [INFO] Applying CRD clusters.management.cattle.io
2022/01/05 20:47:24 [INFO] Applying CRD apiservices.management.cattle.io
2022/01/05 20:47:24 [INFO] Applying CRD clusterregistrationtokens.management.cat tle.io
2022/01/05 20:47:24 [INFO] Applying CRD settings.management.cattle.io
2022/01/05 20:47:24 [INFO] Applying CRD preferences.management.cattle.io
2022/01/05 20:47:24 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD clusterrepos.catalog.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD operations.catalog.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD apps.catalog.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD fleetworkspaces.management.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD managedcharts.management.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD clusters.provisioning.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD clusters.provisioning.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD rkeclusters.rke.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD rkebootstraps.rke.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD rkebootstraptemplates.rke.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD custommachines.rke.cattle.io
2022/01/05 20:47:25 [INFO] Applying CRD clusters.cluster.x-k8s.io
2022/01/05 20:47:26 [INFO] Applying CRD machinedeployments.cluster.x-k8s.io
2022/01/05 20:47:26 [INFO] Applying CRD machinehealthchecks.cluster.x-k8s.io
2022/01/05 20:47:26 [FATAL] failed to list apiextensions.k8s.io/v1, Kind=CustomR esourceDefinition for machinehealthchecks.cluster.x-k8s.io: Get “https://127.0. 0.1:6443/apis/apiextensions.k8s.io/v1/customresourcedefinitions?labelSelector=ob jectset.rio.cattle.io%!F(MISSING)hash%!D(MISSING)7372e5228a5d4df32e62db137ea6bf4 69c35d4c4&timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connection refused
2022/01/05 20:47:44 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:47:44 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:47:44 [INFO] Listening on /tmp/log.sock
2022/01/05 20:47:44 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:46 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:48 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:50 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:47:52 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:47:54 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:47:56 [INFO] Waiting for server to become available: an error on t he server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:48:02 [FATAL] k3s exited with: exit status 255
2022/01/05 20:48:20 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/05 20:48:20 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embed ded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:fal se Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit. log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Feat ures: ClusterRegistry:}
2022/01/05 20:48:20 [INFO] Listening on /tmp/log.sock
2022/01/05 20:48:21 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:48:23 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:48:25 [INFO] Waiting for server to become available: Get “https:// <IP_ADDRESS>:6443/version?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connect ion refused
2022/01/05 20:48:27 [INFO] Waiting for server to become available: an error on the server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:48:29 [INFO] Waiting for server to become available: an error on the server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:48:31 [INFO] Waiting for server to become available: an error on the server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:48:33 [INFO] Waiting for server to become available: an error on the server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:48:35 [INFO] Waiting for server to become available: an error on the server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:48:37 [INFO] Waiting for server to become available: an error on the server (“apiserver not ready”) has prevented the request from succeeding
2022/01/05 20:48:39 [INFO] Running in single server mode, will not peer connections
2022/01/05 20:48:39 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:48:39 [INFO] Applying CRD navlinks.ui.cattle.io
2022/01/05 20:48:40 [INFO] Applying CRD clusters.management.cattle.io
2022/01/05 20:48:40 [INFO] Applying CRD apiservices.management.cattle.io
2022/01/05 20:48:40 [INFO] Applying CRD clusterregistrationtokens.management.cattle.io
2022/01/05 20:48:40 [INFO] Applying CRD settings.management.cattle.io
2022/01/05 20:48:40 [INFO] Applying CRD preferences.management.cattle.io
2022/01/05 20:48:40 [INFO] Applying CRD features.management.cattle.io
2022/01/05 20:48:40 [INFO] Applying CRD clusterrepos.catalog.cattle.io
2022/01/05 20:48:41 [FATAL] Get “https://<IP_ADDRESS>:6443/apis/apiextensions.k8s.io/v1/customresourcedefinitions/clusterrepos.catalog.cattle.io?timeout=15m0s”: dial tcp <IP_ADDRESS>:6443: connect: connection refused

Possibly this is related to issue 35892. I am not a Rancher developer, but I've been trying to find the source of this problem by differentially updating from 8.4 to 8.5.  I am fairly sure that the problem is in one of the new systemd packages in 8.5.  I get a working Rancher first boot login screen if I upgrade everything on an 8.4 test box to 8.5, but exclude systemd* from the upgrade.  This leaves behind only the following in their last 8.4 versions, and everything else in their 8.5 versions.
systemd-pam-239-45.0.2.el8_4.3.x86_64
systemd-udev-239-45.0.2.el8_4.3.x86_64
systemd-libs-239-45.0.2.el8_4.3.x86_64
systemd-239-45.0.2.el8_4.3.x86_64
Hopefully this helps someone diagnose the actual problem. Keep in mind that this is not a permanent solution since eventually a security vulnerability will be found and fixed only in the 8.5 version of systemd. I tested on Oracle Linux 8 using the "docker on a single system" Rancher install method.

Same for me. Switching to linux-lts arch (5.15.15-1-lts) doesnt help.

Our team is seeing this behavior as well with single-node Rancher v2.6.3-patch1 running on AlmaLinux 8.5 (one of the Enterprise Linux distros).
For the Rancher devs -- this is basically the same behavior reported in #35892 and #36238, which my team is also seeing -- the error messages we get alternate between the ones reported here and the ones in those tickets.

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.

The related issues all seem to still be active. Not clear whether this was fixed with the release of the latest Rancher version or any patch version, since it really seems like a K3s issue.

This issue and the related issues still appear to be valid.

@themowski, I am unable to reproduce the original issue. Are you? If so, could you provide additional steps? Various problems with your host machine can cause this issue, such as having limited system resources. I will be closing this issue if there isn't a problem with the rancher image running on RHEL 8.5.

I am closing this issue due to the inability to reproduce the original problem.

Same problem here.
How to reproduce:
Install new Ubuntu Server 22
Install Docker.IO
Run
sudo docker run --privileged -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher


Hyperlink in Email notice does not work

Affected module
UI/backend
Describe the bug
The hyperlink generated by the email notice does not work when click it.
To Reproduce
Please see this attach GIF

The email setting is here

Expected behavior
Click on the hyperlink in the email should jump into the BOT.
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: [1.1]
OpenMetadata Ingestion package version: []

Additional context
N/A

this is fixed here https://github.com/open-metadata/OpenMetadata/pull/14674 , we need to make sure openmetadataUrl or ENV OPENMETADATA_SERVER_URL points to the proxy or url where UI is hosted, for example if backend is started directly without proxy then http://localhost should be used , else http://localhost:8585 or other port should be used


is it possible to deploy data lake locally

not s3

You can use local absolute path like "/home/yourname/data/table_name" as path option to save/load LakeSoul table.


Passing an incorrect certificate in the Harbor installation corrupts the install

Hello,
We tried installing Harbor Bosh release in Enterprise PKS and provided an incorrect certificate.
The timeout for the pre-start script in the Bosh release was set to the default of 60 minutes.
The prestart script fails at this line:  https://github.com/vmware/harbor-boshrelease/blob/master/jobs/harbor/templates/bin/pre-start.erb.sh#L309
You can see that, if the certificate is incorrect, it will continue to return something other than HTTP 200 OK which means this script will stall the process for 60 minutes, without much feedback, even in the logs, there's nothing there except the echo statement. Also, since the problem is in the pre-start script, monit will not boot up properly.
Possible solutions:

avoid doing lots of logic in a pre-start script, these are run directly by Bosh
give better error logging on why harbor is not coming up (even the HTTP code would help a lot)

The current purpose of this repo is primarily to serve as a dependency for Harbor Tile as part of the BOSH release. Due to resource limits, we do not support the Bosh release.


fix typo

Codecov Report

Merging #1512 (aaed4b0) into master (ef58fde) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1512      +/-   ##
==========================================
- Coverage   39.52%   39.52%   -0.01%
==========================================
  Files         598      598
  Lines       35068    35068
==========================================
- Hits        13861    13859       -2
+ Misses      19680    19673       -7
- Partials     1527     1536       +9

Impacted Files
Coverage Δ

app/dispatcher/fakednssniffer.go
0.00% <ø> (ø)

app/dns/dnscommon.go
86.36% <ø> (ø)

app/dns/fakedns/fake.go
61.36% <ø> (ø)

app/observatory/burst/healthping.go
0.00% <ø> (ø)

common/antireplay/replayfilter.go
69.56% <ø> (ø)

common/buf/multi_buffer.go
84.11% <ø> (ø)

common/cache/lru.go
100.00% <ø> (ø)

common/crypto/io.go
17.39% <0.00%> (-21.74%)
:arrow_down:

common/crypto/aes.go
75.00% <0.00%> (-12.50%)
:arrow_down:

proxy/vmess/account.go
61.53% <0.00%> (-7.70%)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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


Peer Sharing & Eclipse Evasion Design

The documents are still internal:

Peer Discovery and Eclipse Resistance: google doc summary
Peer Sharing and Eclipse: presentation
Evading Eclipse with Peer Sharing and State-Driven Peer Discovery: early latex document
Peer Sharing Planning: high level design of peer sharing

Merged into #3884.


error on building with exoplayer video and audio in 1 project

i am getting error while building with exoplayer audio and exoplayer video both in one project
exoplayer audio version : ^0.6.1
exoplayer video version: ^2.1.10
flutter verison: 2.2.2
error message:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkDebugDuplicateClasses'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
   > Duplicate class com.google.android.exoplayer2.ui.package-info found in modules jetified-exoplayer-common-2.14.1-runtime (com.google.android.exoplayer:exoplayer-common:2.14.1) and jetified-exoplayer-ui-2.11.1-runtime (com.google.android.exoplayer:exoplayer-ui:2.11.1)

     Go to the documentation to learn how to Fix dependency resolution errors.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 19s
The build failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetifier to solve the incompatibility.
Building plugin flutter_exoplayer...
Exception: The plugin flutter_exoplayer could not be built due to the issue above.

I fixed the error by specifying the exoplayer version to be used.
add to /android/app/build.gradle
dependencies {
    ...
    implementation('com.google.android.exoplayer:exoplayer:2.14.1')
}

Thanks bro your trick worked👍👍


🍒 Cherry pick PR #17697 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/17697 to staging 🍒

🚀 Cherry-picked to staging by https://github.com/OSBotify in version: 1.3.2-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.2-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 1.3.28-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Include explicit OSV- prefix in id field.

Old UI links and API requests will still work.

(This needs to wait on some internal clients to migrate before committing).


Update exportChart options

The version of Billboard js' Chart.export used by this repo (3.0.0) as well as latest (3.7.2) expects it's arguments in an object with some optional parameters.  This is a change from some older versions where the only argument was an optional mimeType parameter.
I've updated the repo to take this into account, fixing the usage in the readme and the BarChart example.  I've also renamed the parameter from mimeType to options to hopefully be more clear to callers what its purpose is

Appreciate this, definitely a good change. Would you mind updating the unit tests here and here relating to exportChart? I realize the value is still passed through transparently, but the tests still reflect the string values.

This should be included in the 3.0.4 release. Thanks for the contribution!


Global var set before evaluating function declaration in non-strict block

For the following test case:
function getF() { return f; }
{
  if (getF() === f) {
    print('Global var set before evaluating function declaration');
  }
  function f() { return "bar"; }
}

I see:
#### ch
Global var set before evaluating function declaration

#### sm

#### v8

#### jsc
Global var set before evaluating function declaration

According to B3.3.2, the global "var" binding should be initialized to undefined, and only set to the block-level value of f when the function declaration is evaluated.

Annex B3.3 is crazy stuff.
It says that if there's a function in a block scope in non-strict code, then when we begin executing the script we initialize a global var with that identifier to undefined. When we enter the block, we create a block-scoped, hoisted binding for the function. When we reach the function definition, we set the outer (global) var binding to the current value of the inner shadowing block scope binding.
I don't think there is a test262 test for this particular edge case.

Ah; so the bug in this case is that we aren't distinguishing between the block-scoped binding of f and the global binding of f, we are just directly setting the global binding of f when we enter the block scope?

We set both the global and the block-scoped bindings at the same time. We almost certainly have the same issue with non-global code. It should be a pretty simple thing to fix. Does anyone actually implement the spec today?

Based on the test results above it appears that both SpiderMonkey and V8 implement this properly.

I feel it's worth noting that the reason Annex B exists at all is simply for the sake of legacy Web compatibility; not implementing it properly WILL break a lot of existing code (in fact it's my understanding that implementing Annex B is only required if you're writing a browser).  In this particular case, block-scoped functions are specified the way they are because many devs in the past would conditionally define functions like this:
if (someCondition) {
    function doSomethingAwesome() {
        // do stuff
    }
}

If that function is hoisted onto the global object too early (as we appear to be doing now) then such code no longer does what the programmer intended.

You're right, the annex is crucial for backward compat. Our divergence from the spec is pretty subtle, though. We're doing the important thing correctly, which is to instantiate the function only if awesomenessIsAvailable is true and to let people call it later, from outside the block, by referring to the global. The fact that we're assigning the right value to the global on entry to the if block doesn't seem likely to break legacy code. We should certainly fix it, but @zenparsing 's assessment of severity 3 seems appropriate to me.


Stopped posting to Blue Sky after DNS verification

My bridged web account has stopped posting to Blue Sky since around the time I did the DNS validation (added a txt dns record). Apologies if I've done or not done something! Domain is atpgeo.com could you have a look please?

Hey, sorry for the trouble! Bridged accounts in Bluesky occasionally get "stuck" like this. Bridgy Fed is happily committing your new posts to its ATProto repo, and emitting them to the Bluesky relay, but they're not making it all the way into the appview. We don't know why yet. Ugh.

Thanks for coming back to me. Is there anything I can do at this end to unblock it? Eg change the way my posts are tagged or remove the txt record from the domain dns, would this revert the username? Could either of these help?

Afaik this is completely unrelated to your domain handle. You can test that by changing your handle bak and forth if you want though!
Otherwise, no, I don't know of an easy fix yet, sorry. I talk with the Bluesky team about it on and off, hopefully we'll figure something out soon.

Howdy, I just did this myself (username set to my domain from Mastodon to Bluesky) and also noticed this issue. Bluesky appears to be pulling my website instead of my Mastodon account. (If you want to see what I mean, the domain is thenewoil.org)

Any chance you could update the documentation to warn about this issue for people who might be considering it? Or are you hoping to have it resolved so fast that it's not worth mentioning?

How can I roll back to the default way of doing things until this is resolved?

Thanks!

@tnonate hmm, sorry for the trouble! https://bsky.app/profile/thenewoil.org looks like it's correctly bridging https://mastodon.thenewoil.org/@thenewoil to me...?
(I do see https://bsky.app/profile/thenewoil.org.web.brid.gy for your web site too, but that's separate.)

@snarfed Well, disregard, I guess I just didn't give it enough time.
I was bridging from Mastodon to Bluesky, I followed the instructions here and after a while the existing link (https://bsky.app/profile/thenewoil.mastodon.thenewoil.org.ap.brid.gy) stopped working but the new profile was nowhere to be found. When I checked GitHub I saw this issue and thought it described my issue the same, but I guess it just took longer than expected to populate.
Sorry for the confusion and noise.

https://bsky.app/profile/sockpuppet.band and https://bsky.app/profile/beesbuzz.biz seem to have also fallen prey to this.


Crash after receive read status from Android device.

Help avoid duplicate issue reports, check existing issues
Environment details
iOS version, Quickblox iOS SDK version, QMServices version
iPhone 5s.
iOS 7.1.1.
QuickBlox SDK: 2.7.2
QMServices version: 0.4
Did this work before?
No.
Expected behavior
Does not crash.
Actual behavior
It's crash after receiving read status from Android device because of dialogID = nil
Logs
Attach full logs that will describe your problem (please, use github gist)
- (void)chatDidReadMessageWithID:(NSString *)messageID dialogID:(NSString *)dialogID readerID:(NSUInteger)readerID
{
    *NSParameterAssert(dialogID != nil);*

Steps to reproduce the behavior

iOS device send a message to Android device.
Android device open dialog to view message.
iOS device received message was read and crash because of missing dialogID.

Any others comments?

@tranngoclinh88  I'll ask Android team to help you.

Hi,
Seems this is the issue on Android side.
Can you please let us know your IOS/ Android q-municate version?

Android SDK version is 2.5.2.

This is what iOS send to Android after received message:
<message<EMAIL_ADDRESS>type="chat" id="5732ab9c545a484e2e0041c0">
  <received xmlns="urn:xmpp:chat-markers:0" id="5732ab9a06ef8353eba0d308"/>
  <extraParams xmlns="jabber:client">
    <dialog_id>56e4f39388eaf454ae000d97</dialog_id>
  </extraParams>
</message>

And this is what Android sent to iOS:
<message xmlns="jabber:client"<EMAIL_ADDRESS><EMAIL_ADDRESS>id="5732abef06ef8353eba0d30a" type="chat">
  <received xmlns="urn:xmpp:chat-markers:0" id="5732abf1545a484e2e0041c8"/>
  <extraParams xmlns="jabber:client">
    <dialog_id>56e4f39388eaf454ae000d97</dialog_id>
  </extraParams>
</message>

Delete ticket because of security.


Swarmmode hybrid clusters with Windows agents

What this PR does / why we need it: Adds a swarmmode-hybrid.json cluster definition, with documentation for a hybrid Swarm Mode cluster with Linux masters and Linux and Windows agents.
Release note:

Swarmmode with Windows agents

Will eventually windows based managers be allowed as well, completely removing neccessity to have anything UNIX related in setup?


Installation warning from Microsoft Defender

I searched through the issues and haven't found anything about it, am I the only one getting this warning when I run the demo installer?

And just to clarify, I'm talking about versions 2.2.2 and 2.2.3:
Video Hub App 2 Setup 2.2.2-demo.exe

Thank you for opening the issue.
This is a standard warning from Windows about an "unrecognized app" 🤷♂
👌  On Windows 10 there's a question about whether you want to run the app. In your screenshot it seems like you don't have an easy "run anyway" button to click (is this Windows 8?). Perhaps if you click "More info" you'll be able to proceed.
I think the only way I can avoid this with my app is to pay Microsoft something like $100/year (if not more) to register the app with them 🤔
If someone knows better about this, please let me know 🤝

Hello, and thank you for a great app! 😄 👍
Indeed, I can get over it by clicking on the "More info" link, but I think this might deter a lot of non-technical users from using it, which is a pity. Maybe you can create a different type of installer? I am sure lots of developers out there don't need to pay that amount of money to Microsoft to get their apps installed.

I'll keep the issue open with a help wanted tag -- in case someone who knows a bit more could comment / contribute 👍
My understanding is I need a Code Signing Certificate and there are no free solutions, even if the project is open source 👎


the hotjar feedback button is too cool

what i mean is that it totally distracts me from the articles...
also, can we control when it appears? we don't want it to appear before the user has used the app for a while.

Made it less cool, how about now?


Warning in the Server Console

Server version: Paper 1.16.4-345

mv version -p`: 4.2.2

Server log: [03:17:59] [Server thread/WARN]: [Multiverse-Core] "Multiverse-Core v4.2.2-b812" has registered a listener for org.bukkit.event.entity.EntityCreatePortalEvent on method "public void com.onarandombox.MultiverseCore.listeners.MVPortalListener.entityPortalCreate(org.bukkit.event.entity.EntityCreatePortalEvent)", but the event is Deprecated. "Server performance will be affected"; please notify the authors [dumptruckman, Rigby, fernferret, lithium3141, main--].

Problem
This is Coming in the Console when i starting the server

See #2000

See #2000


The pretrained model for evalutaion error

After download pretrained model for evalution,but the tar file cannot be unzip

Hi, thanks for your interest!
The pretrained model can be directly loaded without unzipping. See the last line in config/train_main.yaml.


fix: add connection pool to MySQL plugin

Description

This PR adds connection pool mechanism to MySQL plugin. So far, we used to create one connection per datasource instance and all the queries used to run on this one connection. This PR introduces a change to create a connection pool instead of a single connection for each datasource instance. The following configuration is used with the connection pool:

max pool size = 5
max idle time for a connection = 10 min

Minor code refactor to move some of the functions into helper utility classes.

Fixes #17481 #8419
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual
All Existing JUnit TCs pass

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Closing in favour of https://github.com/appsmithorg/appsmith/pull/17873 due to some rebasing issues.


Handle different 2fa response codes

This PR introduces custom exceptions that are thrown when an incorrect 2fa login attempt is made.  Usage guidelines follow below:
package pro.beam.api;

import pro.beam.api.exceptions.BeamException;
import pro.beam.api.exceptions.user.TwoFactorWrongCodeException;
import pro.beam.api.exceptions.user.TwoFactorWrongPasswordException;
import pro.beam.api.services.impl.UsersService;

import java.util.concurrent.ExecutionException;

public class Application {
    public static void main(String[] args) throws ExecutionException, InterruptedException {
        BeamAPI beam = new BeamAPI();

        try {
            beam.use(UsersService.class).login("username", "password", "2facode").checkedGet();
        } catch(TwoFactorWrongCodeException e) {
            // wrong code
        } catch(TwoFactorWrongPasswordException e) {
            // wrong password
        } catch (BeamException e) {
            // something went horribly wrong
        }
    }
}

/to @connor4312 @MCProhosting-Matt

LGTM

Is this on Maven? @ttaylorr @MCProhosting-Matt

Publishing now!

Published.


Possible Typo in page 44

however, it does not make the original data set normally distributed

standardization does make the data set normally distributed.

no that's not true. The dataset will have the parameters of a standard normal distribution, i.e., zero mean and unit variance, but it cannot transform the data into a normal distribution. For that you'd need some power transformation like box-cox transformation.


Cannot build musikcube 0.98 under macOS with PulseAudio installed

I could not build musikcube 0.98 under macOS 12.4 on x86_64 using Homebrew.
[  4%] Building CXX object src/plugins/gmedecoder/CMakeFiles/gmedecoder.dir/GmeDataStream.cpp.o
In file included from /tmp/musikcube-20220707-20832-77eqsa/musikcube-0.98.0/src/plugins/pulseout/pulseout_plugin.cpp:35:
/tmp/musikcube-20220707-20832-77eqsa/musikcube-0.98.0/src/plugins/pulseout/pch.h:41:10: fatal error: 'alsa/asoundlib.h' file not found
#include <alsa/asoundlib.h>
         ^~~~~~~~~~~~~~~~~~
1 error generated.

Complete log: homebrew-logs.zip
I noticed that the pluseout plugin had been enabled. So I removed PulseAudio. After that, it was compiled fine.
I'm using PulseAudio to communicate to a server, and it's not related to musikcube. So, I'm OK with disabling pulseout on macOS. Just note that PulseAudio can be installed without ALSA, especially in non-Linux OSs.

Yep, looks like the ALSA header file was being erroneously included in the PulseAudio output plugin. I just pushed a fix to master. Please re-open if you still have issues.


Database recipe causing error if run a second time

I'm using Chef with Vagrant. If I run vagrant reload --provision having previously provisioned the machine I get an error:
ERROR: link[/var/run/mysqld/mysqld.sock] (wordpress::database line 56) had an error: Errno::ENOENT:
No such file or directory @ sys_fail2 - (/var/run/mysql-default/mysqld.sock, /var/run/mysqld/mysqld.sock)

wordpress::database line 56

Running on Ubuntu 14.04. Only other Chef packages running are locale and apt.

Same issue with Ubuntu 14.04 LTS (GNU/Linux 3.13.0-24-generic x86_64)
The problems seems to be a non-existent target directory when trying to symlink mysqld.sock (i.e., /var/run/mysqld doesn't exist)
Temporary workaround:
a) Explicitly create this directory before including the wordpress recipe:
directory '/var/run/mysqld' do
  owner 'ubuntu'
  group 'ubuntu'
  mode '0755'
  action :create
end
include_recipe 'wordpress::default'

b) Manually create this directory and the symlink:
sudo mkdir -p /var/run/mysqld && sudo ln -s /var/run/mysql-default/mysqld.sock /var/run/mysqld/mysqld.sock

@joe4dev thanks that worked


Solve CLI parse order bug

Close #557

We have smoke tests for the basic lurk invocation (tests/lurkrs-smoke-test.rs) and the same for clutch (clutch/tests/clutch-smoke-test.rs). Would it be possible to take this occasion to write a couple more to test the arguably not always intuitive passthrough semantics between CLI & REPL?

I will write an issue for it

@huitseeker I've added test_repl_command for this PR (to validate the fix).
But I'll write an issue with the proper scope for the full blown task


SEC-3.1: Authentication : Adding hostname configuration and encoding type JSON_IETF

SEC-3.1: Authentication :
Adding hostname configuration
motd-banner configuration required encoding type for JSON_IETF Added encoding type JSON_IETF for gnmi GET

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 46.888%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
580

Relevant Lines:
1237

💛  - Coveralls

@avaneesh90, sorry for the delay on this. We had a gap internally in terms of our ability to run KNE-based tests in a continuous build -- bigger than I realized. I've been busy creating that, but I don't think that needs to be perfect before you get a proper review. I have assigned myself https://github.com/openconfig/featureprofiles/pull/1057 to review


install from pip package fails on Ubuntu 15.10

Environment info
Operating System: Ubuntu 15.10

pip package: tensorflow-0.7.1-cp27-none-linux_x86_64.whl

The screen output:
Downloading tensorflow-0.7.1-cp27-none-linux_x86_64.whl (13.8MB): 13.8MB downloaded
Cleaning up...
Exception:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in main
status = self.run(options, args)
File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 304, in run
requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle)
File "/usr/lib/python2.7/dist-packages/pip/req.py", line 1271, in prepare_files
req_to_install)
File "/usr/lib/python2.7/dist-packages/pip/req.py", line 109, in init
self.prereleases = any([is_prerelease(x[1]) and x[0] != "!=" for x in self.req.specs])
File "/usr/lib/python2.7/dist-packages/pip/util.py", line 739, in is_prerelease
return any([any([y in set(["a", "b", "c", "rc", "dev"]) for y in x]) for x in parsed])
TypeError: 'int' object is not iterable

Storing debug log for failure in /home/osboxes/.pip/pip.log
Steps to reproduce

sudo apt-get install python-pip python-dev
2.sudo pip install --upgrade https://storage.googleapis.com/tensorflow/linux/cpu/tensorflow-0.7.1-cp27-none-linux_x86_64.whl

Can you upgrade pip or tell me which version of pip is installed?

Closing due to lack of information.  I'm happy to reopen if more information arises.


Update encryption and signature encoding to base64

Signature will remain as hex since this appears to be the standard for schnorr sigs. Updated encryption strings to base64.


tidy: Smartlead objectNames, URL building

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1006  👈
#923 : 2 other dependent PRs (#925 , #933 )
#1005
#1004
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Cobalt0s and the rest of your teammates on  Graphite


False positive on post unavailable

When i try on this reel i have in the embed a message telling me it's not available but i can open it
https://www.instagram.com/reel/CxbCygXoxzv/

It seems that reel is posted by restricted profile (18+), instafix cant access it

hi @Wikidepia, how do you check if it's restricted ? cause if have this one too now https://www.instagram.com/p/Cx5J7uyL6f6/


Novomatic garage door with x3d card : (Module TYDOM 1.0 - NFF13694) not working

I have 2 garage doors.  Motor is from novoferm. ( novomatic ) and there is an embedded x3d card : (Module TYDOM 1.0 - NFF13694).
It is detected as a switch but open/close state is not received and it cannot be opened/closed.
Here is the discovery info with the latest installed version 3.1.2
Topic: homeassistant/switch/tydom/1662041571_1662041571/config
Payload
name: Garage  RDC
unique_id: '1662041571_1662041571'
command_topic: switch/tydom/1662041571_1662041571/set_levelCmdGate
state_topic: switch/tydom/1662041571_1662041571/state
json_attributes_topic: switch/tydom/1662041571_1662041571/attributes
payload_on: TOGGLE
payload_off: TOGGLE
retain: 'false'
device:
manufacturer: Delta Dore
model: Porte
name: Garage  RDC
identifiers: '1662041571_1662041571'
platform: mqtt
If I replace payload_on: TOGGLE and payload_off: TOGGLE with payload_on: ON and payload_off: OFF , I can open/close it.
Moreover, the payload OFF stops the opening , so a partial opening like in the tydom app should be possible.
Opening/closing state is not updated or received. I haven't the knowledge to find why.

Bonjour merci pour le développement de Tydom sur Home assistant
J'ai un petit souci pour contrôler ma porte de garage la commande qui est envoyer TOGGLE ne fonctionne pas et après avoir regarder dans MQTT les donnée qui remontait j'ai OPEN et CLOSE
Voici mes données
2023-07-09 16:08:42,233 - mqtt.MqttClient - INFO - set_levelCmd message received (topic=switch/tydom/xxxxxxxxxx_xxxxxxxxxx/set_levelCmdGate, message=CLOSE)
2023-07-09 16:08:42,233 - sensors.Light - INFO - xxxxxxxxxx levelCmd CLOSE
2023-07-09 16:08:52,242 - mqtt.MqttClient - INFO - set_levelCmd message received (topic=switch/tydom/xxxxxxxxxxx_xxxxxxxxxxx/set_levelCmdGate, message=OPEN)
2023-07-09 16:08:52,242 - sensors.Light - INFO - xxxxxxxxxx levelCmd OPEN
Merci d'avance

Hello

so I've add a zigbee sensor to get the state.

I think it's the best way to make it reliable because, even on the Tydom app, the state is hazardous.
Shame for a card at this price vs a device on dry contact...
By the way, it'll be interesting to get state from tydom2mqtt to spy out total or partial (ventilation) opening.
It's always in my plan to take a look at this device but I need to find time...


Who should own the Copyright of new code?

We should update this, probably:
https://github.com/ko-build/ko/blob/main/hack/boilerplate/boilerplate.go.txt#L1

will update that
/assign


Wjiang/feature/check restart dims

Check the dimension of variables in restart file.
Description

Related Issue

Motivation and Context

If given a wrong restart file( higher resolution), the program would just read and move on. The checking makes sure the restart file is consistent with the original setup
How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Trivial change (affects only documentation or cleanup)

Checklist:

[x] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

#655 has addressed this issue.

#655 has addressed this issue.


Fix LDAP in frontend and update env and docs

Describe the bug
Hardcoded variables in LDAP config, lines 13 and 14 here:
https://github.com/FORTH-ICS-INSPIRE/artemis-web/blob/d005e931de866d47800355d69d6f0bea353cb2e4/apps/artemis-web/libs/passport-strategies/ldap-strategy.ts
Affected Component(s)

[x ] Back-End (Database, Microservices, Containers, etc)
[ ] Front-End (Flask, API, etc)
[ ] Docs
[ ] Build System

Expected behavior
no hardcoded entries in .env LDAP variables

child frontend-specific issue created in the correct repo: https://github.com/FORTH-ICS-INSPIRE/artemis-web/issues/101
Any other conf changes that may be required will also take place in master ARTEMIS repo.

TODO:
[ ] New .env vars
LDAP_GROUP_SEARCH_BASE="ou=people,dc=planetexpress,dc=com"
LDAP_GROUP_SEARCH_FILTER="(member={{dn}})"
LDAP_GROUP_SEARCH_ATTRIBUTES="mail,uid"
[ ] Remove .env. var LDAP_USER_GROUP
[ ] Update LDAP-related docs (ldapconf.md)
[ ] Update docker-compose (also in vagrant) and k8s (values, configmap,  frontend-deployment) vars


how to use ollama with open-interpreter?

I noticed that open-interpreter utilizes litellm to communicate with llms. While litellm can utilise ollama as a backend to respond to prompts, I have been unable to find a way to utilise ollama within open-interpreter. Does anyone have any experience or knowledge regarding this?

update:
run :
interpreter --model openai/codellama --api_base http://<IP_ADDRESS>:8000/
now the connection is fine.

hey @wuyongyi  openinterpreter uses litellm, so you could just use it as ollama/codellama in the interpreter call

hey @wuyongyi openinterpreter uses litellm, so you could just use it as ollama/codellama in the interpreter call

How did you do it? I tried with interpreter --model ollama/codellama --api_base http://<IP_ADDRESS>:11434/ but I get this error:
▌ Model set to ollama/codellama

Open Interpreter will require approval before running code.

Use interpreter -y to bypass this.

Press CTRL-C to exit.

> Hello there!

We were unable to determine the context window of this model. Defaulting to 3000.
If your model can handle more, run interpreter --context_window {token limit} or interpreter.context_window = {token limit}.
Also, please set max_tokens: interpreter --max_tokens {max tokens per response} or interpreter.max_tokens = {max tokens per response}

Traceback (most recent call last):
  File "/home/adriano/.local/pipx/venvs/open-interpreter/lib/python3.11/site-packages/litellm/llms/ollama.py", line 133, in get_ollama_response_stream
    j = json.loads(chunk)
        ^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/json/decoder.py", line 340, in decode
    raise JSONDecodeError("Extra data", s, end)
json.decoder.JSONDecodeError: Extra data: line 1 column 5 (char 4)

@Axenide
I encountered the same error you did.
[GIN] 2023/11/22 - 21:03:44 | 404 |       2.256µs |       <IP_ADDRESS> | POST     "//api/generate"

There was an extra slash in the request URL.
I removed the trailing slash from the api_base argument URL and the error went away.
> interpreter --model ollama/llama2 --api_base http://localhost:11434

> hi

We were unable to determine the context window of this model. Defaulting to 3000.
If your model can handle more, run interpreter --context_window {token limit} or interpreter.context_window = {token limit}.
Also, please set max_tokens: interpreter --max_tokens {max tokens per response} or interpreter.max_tokens = {max tokens per
response}

b'{"model":"llama2","created_at":"2023-11-22T12:11:27.893947Z","response":"Hello","done":false}'

@Axenide
I encountered the same error you did.
[GIN] 2023/11/22 - 21:03:44 | 404 |       2.256µs |       <IP_ADDRESS> | POST     "//api/generate"

There was an extra slash in the request URL.
I removed the trailing slash from the api_base argument URL and the error went away.
> interpreter --model ollama/llama2 --api_base http://localhost:11434

> hi

We were unable to determine the context window of this model. Defaulting to 3000.
If your model can handle more, run interpreter --context_window {token limit} or interpreter.context_window = {token limit}.
Also, please set max_tokens: interpreter --max_tokens {max tokens per response} or interpreter.max_tokens = {max tokens per
response}

b'{"model":"llama2","created_at":"2023-11-22T12:11:27.893947Z","response":"Hello","done":false}'

Actually, the solution was to specify the version of the model. :)
ollama/codellama:latest

@Axenide
I'm still getting the same errors previously described despite specifying the model version (as displayed in 'Ollama list' cmd). I'm on intel-mac, running mistral, and here is what I used:
interpreter --model ollama/mistral:latest --api_base http://<IP_ADDRESS>:11434/
but I then get the following from open interpreter:
▌ Model set to openai/ollama/mistral:latest

Open Interpreter will require approval before running code.
Use interpreter -y to bypass this.
Press CTRL-C to exit.

Any ideas on how to correct this?

@phrane
Try without ollama/, it used to work when specifying it as openai, so I guess it should work if you just use mistral:latest.

@phrane that looks wrong. I think openinterpreter is automatically assuming this is an openai compatible endpoint,
LiteLLM (which openinterpreter uses to make api calls) supports ollama/mistral and that should work fine - https://docs.litellm.ai/docs/providers/ollama.
But it seems like open-interpreter hasn't added support yet - https://docs.openinterpreter.com/language-model-setup/hosted-models/openai
Would recommend filing an issue on their github - https://github.com/KillianLucas/open-interpreter

@phrane that looks wrong. I think openinterpreter is automatically assuming this is an openai compatible endpoint,
LiteLLM (which openinterpreter uses to make api calls) supports ollama/mistral and that should work fine - https://docs.litellm.ai/docs/providers/ollama.
But it seems like open-interpreter hasn't added support yet - https://docs.openinterpreter.com/language-model-setup/hosted-models/openai
Would recommend filing an issue on their github - https://github.com/KillianLucas/open-interpreter

@hidek84 this works, thanks!! I still get  ```
We were unable to determine the context window of this model. Defaulting to 3000.
If your model can handle more, run interpreter --context_window {token limit} or interpreter.llm.context_window = {token limit}.
Also, please set max_tokens: interpreter --max_tokens {max tokens per response} or interpreter.llm.max_tokens = {max tokens per response}
but guessing this is due to a config I need to update somewhere.

@phrane that looks wrong. I think openinterpreter is automatically assuming this is an openai compatible endpoint (see the appended openai/),
LiteLLM (which openinterpreter uses to make api calls) supports ollama/mistral and that should work fine - https://docs.litellm.ai/docs/providers/ollama.
But it seems like open-interpreter hasn't added support yet - https://docs.openinterpreter.com/language-model-setup/hosted-models/openai
Would recommend filing an issue on their github - https://github.com/KillianLucas/open-interpreter

@krrishdholakia thanks for your input bro, my thinking was in line with yours regarding open default assumption. Was about to log an issue, but for @hidek84 . Thanks alll round!!


Clean up thread context map implementations

We bring some order in the current variety of ThreadContextMap implementations by:

replacing DefaultThreadContextMap with the more performant StringArrayThreadContextMap introduced in #2330,
removing the CopyOnWriteSortedArrayThreadContextMap, since it has no advantages over the default one. It doesn't even guarantee garbage-free logging.
moving the GarbageFreeSortedArrayThreadContextMap to log4j-core, since no other logging implementation can profit from it.

The documentation has been updated to include the fact that the configuration options for ThreadContext actually depend on the underlying implementation:

Log4j Core users have access to all the ThreadContext configuration options,
Simple Logger users have a more restricted list of config options (they can not use the garbage free map any more). We could even restrict this further by allowing only the log4j2.simplelogShowContextMap and log4j2.isThreadContextMapInheritable options,
Logback users have no configuration options, since the thread context map is hardcoded to use MDC,
JUL users have no configuration options, since the thread context map is hardcoded to no-op.

This PR deprecates #2593.

Before merging this please ensure you look into the issues I had with the performance tests and StringArrayThreadContextMap.

@rgoers,
I can not reproduce the issues in this branch. I suspect that they were due to the changes in the ThreadContextDataInjector (which I reverted).
The performance is similar to the GcFreeSortedArrayThreadContextMap, which seems reasonable:
Benchmark                            (count)  (threadContextMapAlias)  Mode  Cnt     Score    Error  Units
ThreadContextBenchmark.putAndRemove        5                  Default  avgt   25    40,337 ±  2,409  ns/op
ThreadContextBenchmark.putAndRemove        5             NoGcOpenHash  avgt   25    10,500 ±  0,446  ns/op
ThreadContextBenchmark.putAndRemove        5          NoGcSortedArray  avgt   25    46,233 ±  0,484  ns/op
ThreadContextBenchmark.putAndRemove       50                  Default  avgt   25   129,873 ±  2,131  ns/op
ThreadContextBenchmark.putAndRemove       50             NoGcOpenHash  avgt   25    12,334 ±  3,297  ns/op
ThreadContextBenchmark.putAndRemove       50          NoGcSortedArray  avgt   25    65,971 ±  0,742  ns/op
ThreadContextBenchmark.putAndRemove      500                  Default  avgt   25  1192,296 ± 21,985  ns/op
ThreadContextBenchmark.putAndRemove      500             NoGcOpenHash  avgt   25    15,351 ±  2,341  ns/op
ThreadContextBenchmark.putAndRemove      500          NoGcSortedArray  avgt   25   117,499 ±  1,333  ns/op

The poor performance when the context map has 50 or more entries is due to the remove operation, since the array is not sorted and the element was added at the end.
Large context maps and the remove operation itself are rather rare, but I can optimize it by reverting the order of the search.

After reversing the lookup order in remove() the benchmark improves slightly:
Benchmark                            (count)  (threadContextMapAlias)  Mode  Cnt    Score    Error  Units
ThreadContextBenchmark.putAndRemove        5                  Default  avgt   25   37,141 ±  2,795  ns/op
ThreadContextBenchmark.putAndRemove        5             NoGcOpenHash  avgt   25   12,097 ±  2,007  ns/op
ThreadContextBenchmark.putAndRemove        5          NoGcSortedArray  avgt   25   46,352 ±  0,285  ns/op
ThreadContextBenchmark.putAndRemove       50                  Default  avgt   25   82,210 ±  1,496  ns/op
ThreadContextBenchmark.putAndRemove       50             NoGcOpenHash  avgt   25   15,974 ±  2,184  ns/op
ThreadContextBenchmark.putAndRemove       50          NoGcSortedArray  avgt   25   67,429 ±  1,369  ns/op
ThreadContextBenchmark.putAndRemove      500                  Default  avgt   25  731,671 ± 13,308  ns/op
ThreadContextBenchmark.putAndRemove      500             NoGcOpenHash  avgt   25   18,260 ±  5,095  ns/op
ThreadContextBenchmark.putAndRemove      500          NoGcSortedArray  avgt   25  117,670 ±  1,649  ns/op

@rgoers,
Unless we find some problems, I will merge this PR next week.

I've only reviewed functional and documentation changes, they LGTM. (Did not have time to check the tests.)

Thanks, I am merging it.


Running multiple test files crashes when canvas is installed (Error: Module did not self-register: '.../canvas/build/Release/canvas.node'.)

Describe the bug
I’ve started exprimenting with Vitest and got all tests to pass individually; however, running npx vitest run . (or any set of test files together like npx vitest run src/*.test.js) crashes with the following error:
 RUN  /home/phil/dev/packages/vue-accessible-color-picker

node:internal/process/promises:265
            triggerUncaughtException(err, true /* fromPromise */);
            ^

Error: Module did not self-register: '/home/phil/dev/packages/vue-accessible-color-picker/node_modules/canvas/build/Release/canvas.node'.
    at Object.Module._extensions..node (node:internal/modules/cjs/loader:1185:18)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/phil/dev/packages/vue-accessible-color-picker/node_modules/canvas/lib/bindings.js:3:18)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)

I’ve removed the node_modules directory contents several times, re-installed the dependencies, and the issue still happens. I’m writing this only because that’s the only tangible workaround I found for this problem.
Reproduction
git clone https://github.com/kleinfreund/vue-accessible-color-picker.git
cd vue-accessible-color-picker
npm install

npm test
# or
npx vitest run .

Expected behavior:
Test suite runs with all tests passing.
Actual behavior:
Vitest crashes and no tests are run.
Workaround: turn off threads
In https://github.com/vitest-dev/vitest/issues/740#issuecomment-1042648373, a workaround was presented. Turning off threads stops the issue from happening. Using the following configuration, the tests start working:
/// <reference types="vitest" />

import { defineConfig } from 'vite'
import Vue from '@vitejs/plugin-vue'

export default defineConfig({
  plugins: [
    Vue(),
  ],
  test: {
    threads: false,
    environment: 'jsdom',
  },
})

System Info
System:
    OS: Linux 5.13 Ubuntu 20.04.3 LTS (Focal Fossa)
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 16.14.0 - /usr/bin/node
    Yarn: 1.22.5 - ~/.yarn/bin/yarn
    npm: 8.5.0 - ~/dev/packages/vue-accessible-color-picker/node_modules/.bin/npm
  npmPackages:
    @vitejs/plugin-vue: ^2.2.0 => 2.2.0
    vite: ^2.8.1 => 2.8.1
    vitest: ^0.3.4 => 0.3.4

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is caused by the package canvas being installed in my dependencies and used in my tests. JSDom automatically detects the package being present (see https://github.com/jsdom/jsdom#canvas-support) and allows me to test code that relies on document.createElement('canvas').getContext('2d').
Removing it allows me to run multiple tests at once (e.g npm test -- src/utilities/color-conversions/* works), but naturally, the tests relying on the canvas integration into JSDom fail now.
Interestingly, if ran individually, the tests relying on canvas work fine with Vitest (e.g. npm t -- src/ColorPicker.test.js passes). Just running them collectively results in the error reported originally.

We are having the same issue. Furthermore, once I get a singel test to compile (and run), re-running the test will choke and cause a segmentation fault or (erratically) some nice native binding errors. OS and versions same as OP.

I have a feeling this might be caused by https://github.com/Automattic/node-canvas/issues/1394.

workaround: in your config set threads: false

Is there any way to use threads: true while mocking or disabling jsdom? Disabling threads means losing many of vitest's benefits.
Apparently, npm 7+ always installs canvas since it's a peer dependency of jsdom. So this code in jsdom require()s canvas even if it is not mentioned in my package.json dependencies.
I'm using vite-plugin-svelte and run into the "Module did not self-register" error if a test just includes a "Hello world" Svelte Component, without using the canvas API at all.
I‘ve tried vi.mock('canvas', () => ({}));. But this does not work, I guess because Vitest cannot mock what jsdom require()s. Any other ideas? Thanks.

Is there any way to use threads: true while mocking or disabling jsdom? Disabling threads means losing many of vitest's benefits.

What kind of benefits?

Apparently, npm 7+ always installs canvas since it's a peer dependency of jsdom. So this code in jsdom require()s canvas even if it is not mentioned in my package.json dependencies.

As a workaround, maybe there is an old version of this module that doesn't throw? And you can pin it in your package.json.
Also, you can try using heppy-dom :)

threads: false makes things even worse. I'm using @testing-library/react and somehow setting threads: false breaks down all the screen usages while keeping threads: true breaks canvas  😅 so far the only solution I've found is this configuration:
{
       //...
        minThreads: 0,
        maxThreads: 1,
}

in the above example canvas seems to be happy and all the tests run without any changes. Nevertheless in this configuration everything is extremely slow.
I also tried older versions of canvas, all with the same result.

threads: false makes things even worse

If you are running --no-threads, don't forget to call cleanup from @testing-library in your setupFile. Currently Vitest doesn't retain global hooks between tests, if --no-threads is called

This bug is currently preventing me from switching over to Vitest.

Happy-dom is not an option for me because it still lacks features I need
jsdom package also installs canvas, and so rm node_modules/canvas only works temporarily only until the next npm install
threads: false is too slow (I have many tests)

Just want to add that because I am also using setup files, having threads turned off has additional performance hits.

TIP
Note, that if you are running --no-threads, this setup file will be run in the same global scope multiple times. Meaning, that you are accessing the same global object before each test, so make sure you are not doing the same thing more than you need.

https://vitest.dev/config/#setupfiles

Seeing a similar issue with sharp
Error:
Something went wrong installing the "sharp" module

Module did not self-register: '...../node_modules/sharp/build/Release/sharp-linux-x64.node'.

Possible solutions:
- Using worker threads? See https://sharp.pixelplumbing.com/install#worker-threads
- Install with verbose logging and look for errors: "npm install --ignore-scripts=false --foreground-scripts --verbose sharp"
- Install for the current linux-x64 runtime: "npm install --platform=linux --arch=x64 sharp"
- Consult the installation documentation: https://sharp.pixelplumbing.com/install

@MichaelFBA try calling require('sharp') in config file. Or in globalSetup. These are the only places user can call code outside of worker thread.

@MichaelFBA try calling require('sharp') in config file. Or in globalSetup. These are the only places user can call code outside of a worker thread.

Yes I tried adding it to our global setup file for vitest. The issue seems to occur when running watch and only when you change a test does it break

Since canvas is an optional peer dependency, we're considering a workaround to just not install peer dependencies locally and in our build agent. This only works for us because we don't have any other optional peer dependencies that we need to use locally or during testing. Though, if you did find yourself in that situation, you could list your optional peer dependencies as explicit dependencies.
npm ci --no-optional

@MichaelFBA try calling require('sharp') in config file. Or in globalSetup. These are the only places user can call code outside of a worker thread.

Yes I tried adding it to our global setup file for vitest. The issue seems to occur when running watch and only when you change a test does it break

Found any solution?

Had the same problem with pdfjs-dist including canvas as optional, npm i --no-optional did the work for me

I ran into this when I had the wrong path for include in my vite.config.ts file

@SebCorbin Did you manage to find the issue? I'm also dealing with the same issue with pdfjs-dist

I tried all the suggestions, and while disabling threading worked it broke ci. The thing that finally worked for me was blowing away my node_modules deleting the package-lock and clearing the npm cache. Then finally reinstalling everything.

I'm also still having issues with this. This is not completely fixed.

jsdom:

threads: true ❌ ("Error: Not implemented: HTMLCanvasElement.prototype.getContext (without installing the canvas npm package)")
threads: false ✅
singleThread: true ✅

happy-dom:

threads: true ❌ ("TypeError: document.createElement(...).getContext is not a function")
threads: false ❌ ("TypeError: document.createElement(...).getContext is not a function")
singleThread: true ❌ ("TypeError: document.createElement(...).getContext is not a function")

I'm also still having issues with this. This is not completely fixed.

jsdom:

threads: true ❌ "Error: Not implemented: HTMLCanvasElement.prototype.getContext (without installing the canvas npm package)" (note, canvas is installed)
threads: false ✅
singleThread: true ✅

happy-dom:

threads: true ❌ "TypeError: document.createElement(...).getContext is not a function"
threads: false ❌ "TypeError: document.createElement(...).getContext is not a function"
singleThread: true ❌ "TypeError: document.createElement(...).getContext is not a function"

This is package's limitation, not Vitest. threads: true is not supported when using canvas package.


eject-all not working

➜  ~ mac eject-all
53:63: execution error: The variable executable is not defined. (-2753)

OS:
macOS Sierra
Version 10.12.3 (16D32)

It looks like the osascript command is wrong. It currently is "osascript -e 'tell application 'Finder' to eject (every disk whose executable is true)' but it should be osascript -e 'tell application "Finder" to eject (every disk whose ejectable is true)'. I'm going to see if I can fix and submit pull request.


Handle SIGCHLD

watchexec waits for a filesystem event to collect zombie processes, instead of collecting them on SIGCHLD.

I agree it is suboptimal.
However, I've yet to find a solution to this that doesn't make the resulting code way more complicated.

The zombie process doesn't use resources and is collected at the next round, so it's low priority.

Fixed in b2c809c87a9332ea6666ab5d6e441fac03213d2e.
Needs more testing in day-to-day use and development, but it will be in 1.7.

Cool!


git-gone: 1.1.0 -> 1.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/swsnr/git-gone/releases.
meta.description for git-gone is: Cleanup stale Git branches of merge requests
meta.homepage for git-gone is: https://github.com/swsnr/git-gone
meta.changelog for git-gone is: https://github.com/swsnr/git-gone/raw/v1.1.1/CHANGELOG.md
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.1 with grep in /nix/store/3wsbk5k8hd3r42900vhh8s1abk5qxc96-git-gone-1.1.1
found 1.1.1 in filename of file in /nix/store/3wsbk5k8hd3r42900vhh8s1abk5qxc96-git-gone-1.1.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

git-gone

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3wsbk5k8hd3r42900vhh8s1abk5qxc96-git-gone-1.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A git-gone https://github.com/r-ryantm/nixpkgs/archive/b7a5e872cbf69fea1f66fe500014857d71de353c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b7a5e872cbf69fea1f66fe500014857d71de353c#git-gone

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3wsbk5k8hd3r42900vhh8s1abk5qxc96-git-gone-1.1.1
ls -la /nix/store/3wsbk5k8hd3r42900vhh8s1abk5qxc96-git-gone-1.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

git-gone

Maintainer pings
cc @cafkafk for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 343163 run on x86_64-linux 1

1 package built:

git-gone


Bug: UI for Patient list not listing person

https://github.com/user-attachments/assets/50beb8b1-c9fe-442d-b4a8-d2f1f181cf4f
UI not showing anyone even though there are people present in the contact list.

Issue is due to a null-pointer Exception.

More specifically,

We have an FXML annotation pointing to a Label with id status, but it does not exist in the PersonListCard.fxml file:

The fix is to just add a Label element with id status.


[feature request] bump controller-runtime vendor version to k8s 1.20

What would you like to be added:
In k8s >=1.20, align with controller-runtime >=0.8.x, list/watch transport protocol of built-in resources(pods, services...)  has upgraded from json to protobuf, which brings considerable performance improvement in large scale clusters.
Why is this needed:

@SimonCqk is this finished ?


Add Django Cheat sheets

Add Django cheat sheets. Here are some good ones I found:
A good overview:
https://dev.to/ericchapman/my-beloved-django-cheat-sheet-2056
About models and databases:
https://www.codecademy.com/learn/data-in-django/modules/django-models-and-databases/cheatsheet

Hey, I want to work on this, can you assign me for this?

Hello Contributors,
I have been learning django for a while now and therefore i feel i can potentially contribute to this issue.


'Align to columns' removes leading whitespace

The 'Align to columns' function removes leading whitespace from all the lines it operates on.  This makes it less useful to me, since usually when I want to use this feature, it is in source code where I want to preserve existing indentation.   I think this feature would be more useful if it preserved leading whitespace on lines, or at least had the option to do so.
For example, say I have this python function:
def some_function():
    var1 = 'foo'
    another_variable = 'bar'
    variable3 = 'bla'

If I select the 3 variable assignment lines and invoke 'Align to columns', what I'd like to see is:
def some_function():
    var1             = 'foo'
    another_variable = 'bar'
    variable3        = 'bla'

But instead what I get is:
def some_function():
var1             = 'foo'
another_variable = 'bar'
variable3        = 'bla'

I'm using PyCharm 2017.1.5.   Thanks.

Done.


Move NameGenerator into utils

NameGenerator is duplicated in many tests. It would be better to move it into util and reuse in every test.

Also name generator can be very simple:
  [](auto const& info) { return info.param.testName; }