[BUG] Rancher stuck on Waiting for cluster agent to connect after all control-plane VMs restarted

Rancher Server Setup

Rancher version: v2.7.2-rc7
Installation option (Docker install/Helm Chart): K3s install on a single VM
Proxy/Cert Details: N/A

Information about the Cluster

Kubernetes version: v1.24.10+k3s1
Cluster Type (Local/Downstream): RKE2 cluster with the Harvester provisioner

User Information

What is the role of the user logged in? Admin

Describe the bug
I had to reboot the underlying Harvester node which is running all the VMs which Rancher is maintaining. When all provisioned VMs got rebooted, Rancher is unable to get back to a working control plane:

Its stuck on:
configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect

Whenever this happens, I'm forced to completely delete the cluster and start fresh since I'm unable to get into the control plane :(
I noticed this error in the rancher-system-agent errors:
error syncing 'fleet-default/home-bootstrap-template-vfssj-machine-plan': handler secret-watch: the server could not find the requested resource (put secrets.meta.k8s.io home-bootstrap-template-vfssj-machine-plan), requeuing"
```

Logs on `home-control-panel-64fb95f768-vrlxf`:
```
May 10 12:01:38 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:38Z" level=info msg="[Applyinator] Command sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null] finished with err: <nil> and exit code: 0"
May 10 12:01:43 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:43Z" level=error msg="error syncing 'fleet-default/home-bootstrap-template-vfssj-machine-plan': handler secret-watch: the server could not find the requested resource (put secrets.meta.k8s.io home-bootstrap-template-vfssj-machine-plan), requeuing"
May 10 12:01:48 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:48Z" level=info msg="[Applyinator] No image provided, creating empty working directory /var/lib/rancher/agent/work/20230510-120148/8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0"
May 10 12:01:48 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:48Z" level=info msg="[Applyinator] Running command: sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null]"
May 10 12:01:49 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:49Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: Name                                                            Location                                                                                Size     Created"
May 10 12:01:49 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:49Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683608403      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683608403      98250784 2023-05-09T05:00:04Z"
May 10 12:01:49 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:49Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683626400      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683626400      98250784 2023-05-09T10:00:01Z"
May 10 12:01:49 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:49Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683644404      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683644404      98250784 2023-05-09T15:00:05Z"
May 10 12:01:49 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:49Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683662401.part file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683662401.part 13926400 2023-05-09T20:00:22Z"
May 10 12:01:49 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:49Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot--1683676800.part                                  file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot--1683676800.part                                  0        2023-05-10T00:00:00Z"
May 10 12:01:49 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:49Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683576000      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683576000      98250784 2023-05-08T20:00:01Z"
May 10 12:01:49 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:49Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683590402      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683590402      98250784 2023-05-09T00:00:03Z"
May 10 12:01:50 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:50Z" level=info msg="[Applyinator] Command sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null] finished with err: <nil> and exit code: 0"
May 10 12:01:55 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:01:55Z" level=error msg="error syncing 'fleet-default/home-bootstrap-template-vfssj-machine-plan': handler secret-watch: the server could not find the requested resource (put secrets.meta.k8s.io home-bootstrap-template-vfssj-machine-plan), requeuing"
May 10 12:02:00 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:00Z" level=info msg="[Applyinator] No image provided, creating empty working directory /var/lib/rancher/agent/work/20230510-120200/8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0"
May 10 12:02:00 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:00Z" level=info msg="[Applyinator] Running command: sh [-c rke2 etcd-snapshot list --etcd-s3=false 2>/dev/null]"
May 10 12:02:02 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:02Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: Name                                                            Location                                                                                Size     Created"
May 10 12:02:02 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:02Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683590402      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683590402      98250784 2023-05-09T00:00:03Z"
May 10 12:02:02 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:02Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683608403      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683608403      98250784 2023-05-09T05:00:04Z"
May 10 12:02:02 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:02Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683626400      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683626400      98250784 2023-05-09T10:00:01Z"
May 10 12:02:02 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:02Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683644404      file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683644404      98250784 2023-05-09T15:00:05Z"
May 10 12:02:02 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:02Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683662401.part file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot-home-control-panel-d5c1ddc9-8q5tf-1683662401.part 13926400 2023-05-09T20:00:22Z"
May 10 12:02:02 home-control-panel-d5c1ddc9-8q5tf rancher-system-agent[63918]: time="2023-05-10T12:02:02Z" level=info msg="[8d15054ffe8e5b367f1c42484faa83c3dbd756c78e981a70f99a00967f2a308d_0:stdout]: etcd-snapshot--1683676800.part                                  file:///var/lib/rancher/rke2/server/db/snapshots/etcd-snapshot--1683676800.part                                  0        2023-05-10T00:00:00Z"
```

Rancher logs:
```
│ 2023/05/13 01:33:35 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:35 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:36 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already                                                                                │
│ 2023/05/13 01:33:36 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already                                                                                │
│ 2023/05/13 01:33:36 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already                                                                                │
│ 2023/05/13 01:33:40 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: error creating dynamic rest mapper for remote cluster "fleet-default/home": Get "https://<IP_ADDRESS>/k8s/clusters/c-m-v9k6nzr4/api?timeout=10s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)                                          │
│ 2023/05/13 01:33:40 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:40 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:45 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:45 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:50 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:50 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:51 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already                                                                                │
│ 2023/05/13 01:33:51 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already                                                                                │
│ 2023/05/13 01:33:51 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already                                                                                │
│ 2023/05/13 01:33:51 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:51 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:55 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already                                                                                │
│ 2023/05/13 01:33:56 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:56 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:33:58 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: error creating dynamic rest mapper for remote cluster "fleet-default/home": Get "https://<IP_ADDRESS>/k8s/clusters/c-m-v9k6nzr4/api?timeout=10s": context deadline exceeded                                                                                │
│ 2023/05/13 01:34:01 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:34:01 [INFO] [planner] rkecluster fleet-default/home: waiting: configuring bootstrap node(s) home-control-panel-64fb95f768-vrlxf: waiting for cluster agent to connect                                                                                │
│ 2023/05/13 01:34:06 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already                                                                                │
│ 2023/05/13 01:34:06 [ERROR] [CAPI] Unable to retrieve Node status: failed to create cluster accessor: failed to get lock for cluster: cluster is locked already
```

Upgraded to 2.7.3 but its still stuck in pending. Last time this happened, I tried to manually scale down the broken node but that also got stuck and I was forced to recreate the entire cluster

The MachineDeployment has the following status:
status:
  availableReplicas: 0
  conditions:
    - lastTransitionTime: '2023-05-13T00:55:57Z'
      message: Minimum availability requires 3 replicas, current 0 available
      reason: WaitingForAvailableMachines
      severity: Warning
      status: 'False'
      type: Ready
    - lastTransitionTime: '2023-05-13T00:55:57Z'
      message: Minimum availability requires 3 replicas, current 0 available
      reason: WaitingForAvailableMachines
      severity: Warning
      status: 'False'
      type: Available
  observedGeneration: 1
  phase: ScalingUp
  readyReplicas: 0
  replicas: 3
  selector: >-
    cluster.x-k8s.io/cluster-name=home,cluster.x-k8s.io/deployment-name=home-control-panel
  unavailableReplicas: 3
  updatedReplicas: 3

When I manually deleted that particular Machine resource Its finalizer was stuck as well. After manually removing the finalizer it successfully created a new control panel node but it's again stuck on Pending. And the other control-plane node is now stuck in "waiting for cluster agent to connect"

restarting rancher / redeploying rancher pods did not help to fix the issue with the cluster agent.

@sarahhenkens, as a workaround

had to remove VM ( in my case it was cp+etcd node) manually from underlying infrastructure
delete respective node pool, designed to be 1 node pool for each node role ( by removing finalizer )
then deploy / add node to the rke2 cluster again
I think it has something to do with rancher v2.7.2 & cluster dynamicSchemaSpec

Assigning @jakefhyde to (eventually) investigate.

@sarahhenkens @rmammadli Are you able to reproduce this issue on newer version of rancher?

@jakefhyde thank you for taking the time to look into this issue.
I am not observing the same issue on rancher v2.7.[4-6]

@sarahhenkens Please let me know if you are still encountering this issue, otherwise I will be closing it. @rmammadli Glad to hear you are no longer affected. I do think it was related to the changes around dynamic schemas which have since been fixed.

I haven’t experienced the issue anymore
On Wed, Sep 6, 2023 at 2:12 PM Jake Hyde @.***> wrote:

@sarahhenkens https://github.com/sarahhenkens Please let me know if you
are still encountering this issue, otherwise I will be closing it.
@rmammadli https://github.com/rmammadli Glad to hear you are no longer
affected. I do think it was related to the changes around dynamic schemas
which have since been fixed.
—
Reply to this email directly, view it on GitHub
https://github.com/rancher/rancher/issues/41552#issuecomment-1709124631,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABDL5U2RX3JBUSFVFTFPWTXZDRKJANCNFSM6AAAAAAYAFLMKY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Closing as no longer reproducible

I have this exact same issue on my primary demo system.  I had a nasty power failure yesterday and I have not recovered from it.    Running Rancher 2.7.8.

And after the 4th reboot, everything seems to be cleared now.  Sigh.

I am facing similar issue with RKE2 cluster version - rke2 v1.25.15+rke2r2.
Post the install and reboot it takes 10-15 mins for cluster to come up as active.
[INFO ] waiting for at least one control plane, etcd, and worker node to be registered
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for agent to check in and apply initial plan
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for cluster agent to connect
[INFO ] non-ready bootstrap machine(s) custom-d88d623de839 and join url to be available on bootstrap node
[INFO ] waiting for join url to be available on bootstrap node
[INFO ] provisioning done
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for cluster agent to connect
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, kube-apiserver, kube-controller-manager
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, kube-controller-manager
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for cluster agent to connect
[INFO ] provisioning done
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for cluster agent to connect
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, kube-apiserver, kube-controller-manager
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: calico, kube-controller-manager
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for cluster agent to connect
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for probes: kube-apiserver
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for cluster agent to connect
[INFO ] custom-d88d623de839
[INFO ] provisioning done
[INFO ] configuring bootstrap node(s) custom-d88d623de839: waiting for cluster agent to connect
[INFO ] provisioning done

Also having this issue  v1.28.8+rke2r1

Same issue on v1.28.9+rke2r1

Same issue here on v1.28.9+rke2r1
Investigating this as well. Will comment if I find a solution, that does not involve rebuilding the cluster....

same issue here Rancher 2.8.3, k8s 1.28.9
using kubectl directly on the nodes, all shows good.
the cluster agent pod will not connect though, keeps crashing says unable to resolve DNS:
ERROR: https://xxxxxxxxxx/ping is not accessible (Could not resolve host: xxxxxxxxxx)

hahha - one person above says rebooted serveral times and it started working.  Tried that as i had nothing to lose.  And it did start working on the 4th reboot.  Amazing

same issue on Rancher 2.8.3 k8s 1.26.12+rke2r1 and Ubuntu 22.04. After rebooting node 4 times it worked again

Same issue after upgrading from Rancher 2.7.9 to 2.8.3. I would like to know the root cause.
I did discover that restarting rancher-system-agent.service fixes the issue tho.

I have the same issue on clean Rancher 2.8.5 installation and restarting rancher-system-agent.service multiple times helps too after many other fixes I've tried.
I'm writing this for all other that might come across this issue and to say that this is really big bug on Rancher side which should be fixed a.s.a.p.

@jakefhyde would it be possible to reopen this ticket due to the several comments above?

I have the same issue on clean Rancher 2.9.1

I have the same issue on clean Rancher 2.9.1

Same issue same version as well for me. Any workaround?

I have the same issue on clean Rancher 2.8.5 installation and restarting rancher-system-agent.service multiple times helps too after many other fixes I've tried. I'm writing this for all other that might come across this issue and to say that this is really big bug on Rancher side which should be fixed a.s.a.p.

Hi @madzid, What did you do to resolve ?
I too have a clean rancher 2.8.5 install and my hosted cluster in it has the issue with one of the node,
I dont see any issue on the node but the cluster  says "waiting for cluster-agent"
please advice any help is appreciated.

Hi @shqnayaz ,
Just execute "systemctl status rancher-system-agent" on node machine and wait till it's connected to Rancher. Sometimes it takes couple of times to get it done.
P.S.
Watch for logs on Rancher cattle pod in order to give it enough time before you retry in case you need to do it.

My issue was certs.

experienced the issue anymore
…

How did you solved it ? can you explain ?

I face the same issue:

Rancher 2.9.1
RKE v1.27.16+rke2r2
Cluster itself is healthy, node is Ready
All systemd services are green, also agent-service

I'm a first time user on Rancher and I spend a week on this already and cant figure out whats going on. Using Racher 2.9.2 (also tried 2.9.1). Creating a new rke2 cluster v1.30.4+rke2r1 and installing the agent on a Ubuntu 24.04 instance. Everything seems fine except Rancher keeps waiting
[Waiting] non-ready bootstrap machine(s) custom-a119461b26b7 and join url to be available on bootstrap node

The only error I can find is on the rancher-system-agent.service
Oct 22 09:28:41 edge-node-1 rancher-system-agent[2422]: W1022 09:28:41.356634    2422 reflector.go:462] pkg/mod/github.com/rancher/client-go@v1.29.3-rancher1/tools/cache/reflector.go:229: watch of *v1.Secret ended with: an error on the server ("unable to decode an event from the watch stream: stream error: stream ID 137; INTERNAL_ERROR; received from peer") has prevented the request from succeeding

@LuisAArce You say its certs, which certs? As well as what did you do to resolve.

I'm a first time user on Rancher and I spend a week on this already and cant figure out whats going on. Using Racher 2.9.2 (also tried 2.9.1). Creating a new rke2 cluster v1.30.4+rke2r1 and installing the agent on a Ubuntu 24.04 instance. Everything seems fine except Rancher keeps waiting
[Waiting] non-ready bootstrap machine(s) custom-a119461b26b7 and join url to be available on bootstrap node

The only error I can find is on the rancher-system-agent.service
Oct 22 09:28:41 edge-node-1 rancher-system-agent[2422]: W1022 09:28:41.356634    2422 reflector.go:462] pkg/mod/github.com/rancher/client-go@v1.29.3-rancher1/tools/cache/reflector.go:229: watch of *v1.Secret ended with: an error on the server ("unable to decode an event from the watch stream: stream error: stream ID 137; INTERNAL_ERROR; received from peer") has prevented the request from succeeding

@LuisAArce You say its certs, which certs? As well as what did you do to resolve.

Hey maartenschalekamp!
I am on Rancher 2.8.5 on Ubuntu at the moment so results may vary!
Does your DNS server have the CNAME of the Rancher UI ( for example rancher-burger.net)? The pods check /etc/resolve.conf for their DNS so if the CNAME does not exist they will fail. Putting it on the VMs /etc/hosts file will not work (I tried 😄 )
Also, on the Ubuntu VM I had to install IPTables prior to installing Rancher or else rke2-ingress-nginx-controller would not come up.  You can check if all the pods are running the below (assuming you have not changed the default location).
/var/lib/rancher/rke2/bin/kubectl  --kubeconfig /etc/rancher/rke2/rke2.yaml get pods --all-namespaces
After fixing the above Rancher finally came up.
My next issue was the .crt cert from Digicert was not being recognized as a full chain when creating my dev cluster. I had to export all 3 pieces of the cert and them remake the .crt file and then recreate the secret in Rancher. Once I did that my dev cluster came up.
Below was the error being seen:
`time="2024-10-09T18:29:34Z" level=fatal msg="Certificate chain is not complete, please check if all needed intermediate certificates are included in the server certificate (in the correct order) and if the cacerts setting in Rancher either contains the correct CA certificate (in the case of using self signed certificates) or is empty (in the case of using a certificate signed by a recognized CA). Certificate information is displayed above. error: Get "https://RANCHERURL": tls: failed to verify certificate: x509: certificate signed by unknown authority"
https://support.tools/post/how-to-change-rancher-2.x-server-cert/
https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/update-rancher-certificate

Thank you @LuisAArce. I thought I might have some bogus cert or secret around so I used this tool https://github.com/rancher/rancher-cleanup which I then reinstalled rancher, and I still had the same issues.
So I reached out to the slack channels for Rancher and there were someone who helped me to troubleshoot my issue. I created an ALB to my ingress, with source ip restrictions. And found that the fleet manager wasnt able to connect to the ingress due to the restrictions. So only needed to allow the fleet manager public ip access to the ingress.
Took them a few minutes to guide me on what to troubleshoot and managed to get it working within 30 min where I spend the last week not able to figure out whats wrong. So glad I managed to get it working.


Expand the "Language specific style guide and glossary" section

Fixes https://github.com/kubernetes/website/issues/36786

Retitled "Language specific style guide and glossary" section to "Language-specific localization guide" and updated its contents.
Made minor revisions for style and grammar throughout.
Reflowed the line breaks throughout. They were inconsistent and caused "jagged-looking" content.

/lgtm


[🐛] LaunchCamera not working on One Plus devices

Description
Explain the bug in as much detail as possible
It is working on Samsung, Mi but not working on all "One Plus" devices.
How to repeat issue and example

step to reproduce the issue
...

Solution
What needs to be done to address this issue?
Additional Information

Image Picker version: [FILL THIS OUT: Be specific, filling out "latest" here is not enough.]
React Native version: [FILL THIS OUT: Be specific, filling out "latest" here is not enough.]
Platform: [FILL THIS OUT: iOS, Android, or both?]
Development Operating System: [FILL THIS OUT: Are you developing on MacOS, Linux, or Windows?]
Dev tools: [FILL THIS OUT: Xcode or Android Studio version, iOS or Android SDK version, if applicable] navigation crash for Android

you can find the resolution  with issue #1587

you can find the resolution  with issue #1587

@hardikmehta88999 provide more details about the issue.

@hardikmehta88999 provide more details about the issue.

As already mentioned @hardikmehta88999.
react-native-image-picker: 2.3.3 is not supported. So closing this.

As already mentioned @hardikmehta88999.
react-native-image-picker: 2.3.3 is not supported. So closing this.


⚠ Bofrost.at has degraded performance

In 6f53d7e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1159 ms

Resolved: Bofrost.at performance has improved in 0cc2066 after 1 hour, 3 minutes.


(#11) - use up-to-date pouchdb-ajax

This ought to fix #11 because we're not using the old version of PouchDB's ajax anymore.

Related to https://github.com/pouchdb/pouchdb/pull/3559

@vpease let me know if this fixes the issue for you

released in 1.3.1

ugh, forgot to build. released in 1.3.2

Tested on iOS
same status:500, name: unknown_error i used to have before doing the modification to line 188 in 1.3.0


K8SPXC-1334: Add support for container lifecycle hooks

Problem:
There are cases where a graceful termination of the pxc (and proxysql/haproxy) pods is required by the app. For that we need to have a way to signal the pod to stop accepting new tasks but allow the running connections to terminate without dropping them.
Cause:
The operator has no option to set lifecycle hooks where we can specify a preStop script that can put a PXC node in maintenance mode or pause a proxysql pod
Solution:
This PR allows to specify lifecycle hooks (postStart and preStop) that can be used to terminate pods in a more graceful way.
This PR updates and fixes https://github.com/percona/percona-xtradb-cluster-operator/pull/1435 PR.

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

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

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

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

recreate-8-0
passed

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

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

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

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

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1568/commits/f0c461f20757cc11120be7b75e80b3e7ab75ad4f
image: perconalab/percona-xtradb-cluster-operator:PR-1568-f0c461f2


(nexus-repository) Removes Unnecessary Dependency

Description
Removes the dependency for TermurinJRE from the Nexus-Repository package.
Motivation and Context
Nexus, it turns out, packs a version of Java with the install. This means that the dependency is unrequired.
How Has this Been Tested?

Removed dependency from package, packed it
Installed clean on a Windows Sandbox container
Observed Nexus working nicely without any installed JRE package

Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] 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)~
~[ ] Migrated package (a package has been migrated from another repository)~

I would argue this is not a breaking change, though folk may end up with an unrequired package installed after updating their Nexus package.
Checklist:

[x] My code follows the code style of this repository.
~[ ] My change requires a change to documentation (this usually means the notes in the description of a package).~
~[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).~
~[ ] I have updated the package description and it is less than 4000 characters.~
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

Do we know if Nexus includes its own JRE? If not, we should add a comment to the description saying that a JRE (and version if necessary) is required before this package will work.

As I mentioned in the PR description, Nexus, it turns out, packs a version of Java with the install.
Assuming Nexus has installed (as default) to C:\ProgramData\nexus\, this can be found in C:\ProgramData\nexus\jre.

Apologies @JPRuskin, I never caught that!


When using cilium as Kubernetes network CNI, the coredns is running but not-ready, healthcheck failed and plugin/errors HINFO: read udp i/o timeout

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I find some error when using Cilium as Kubernetes network.

Cilium: 1.11.6
Kubernetes: 1.23.0

Describe
The step of create cluster as follow:

Use kubeadm --config kubeadm.conf to init cluster:

kind: InitConfiguration
localAPIEndpoint:
  advertiseAddress: <IP_ADDRESS>
  bindPort: 6443
nodeRegistration:
  criSocket: /var/run/dockershim.sock
  imagePullPolicy: IfNotPresent
  name: nm
  taints: null
---
apiServer:
  timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta3
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controllerManager: {}
dns: {}
etcd:
  local:
    dataDir: /var/lib/etcd
imageRepository: registry.aliyuncs.com/google_containers
kind: ClusterConfiguration
kubernetesVersion: 1.23.0
networking:
  dnsDomain: cluster.local
  serviceSubnet: <IP_ADDRESS>/12
  podSubnet: <IP_ADDRESS>/16
scheduler: {}
---
apiVersion: kubelet.config.k8s.io/v1beta1
kind: KubeletConfiguration
resolvConf: /run/systemd/resolve/resolv.conf

Runkubeadm init --config kubeadm.conf to init cluster.

Join the worker node.

master: <IP_ADDRESS>
worker1: <IP_ADDRESS>
worker2: <IP_ADDRESS>

Install Cilium
I use cilium install to install cilium. The status of coredns from Pending to Running. But it not ready!

root@nm:/work-place/kubernetes/create-cluster# kubectl get pods -A -o wide
NAMESPACE     NAME                               READY   STATUS             RESTARTS        AGE   IP               NODE   NOMINATED NODE   READINESS GATES
kube-system   cilium-99lxc                       1/1     Running            0               18m   <IP_ADDRESS>   na     <none>           <none>
kube-system   cilium-ct5s7                       1/1     Running            0               18m   <IP_ADDRESS>   nm     <none>           <none>
kube-system   cilium-drtlh                       1/1     Running            0               18m   <IP_ADDRESS>   nb     <none>           <none>
kube-system   cilium-operator-5d67fc458d-zxgdd   1/1     Running            0               18m   <IP_ADDRESS>   na     <none>           <none>
kube-system   coredns-6d8c4cb4d-jkssb            0/1     Running            8 (2m55s ago)   19m   <IP_ADDRESS>       na     <none>           <none>
kube-system   coredns-6d8c4cb4d-psxvw            0/1     CrashLoopBackOff   8 (83s ago)     19m   <IP_ADDRESS>       nb     <none>           <none>
kube-system   etcd-nm                            1/1     Running            2               25m   <IP_ADDRESS>   nm     <none>           <none>
kube-system   kube-apiserver-nm                  1/1     Running            2               25m   <IP_ADDRESS>   nm     <none>           <none>
kube-system   kube-controller-manager-nm         1/1     Running            2               25m   <IP_ADDRESS>   nm     <none>           <none>
kube-system   kube-proxy-hv5nc                   1/1     Running            0               24m   <IP_ADDRESS>   na     <none>           <none>
kube-system   kube-proxy-pbzlx                   1/1     Running            0               24m   <IP_ADDRESS>   nb     <none>           <none>
kube-system   kube-proxy-rqpxw                   1/1     Running            0               25m   <IP_ADDRESS>   nm     <none>           <none>
kube-system   kube-scheduler-nm                  1/1     Running            2               25m   <IP_ADDRESS>   nm     <none>           <none>

Here is the logs and describe of coredns.
root@nm:/work-place/kubernetes/create-cluster# kubectl describe pod  coredns-6d8c4cb4d-jkssb -n kube-system
Name:                 coredns-6d8c4cb4d-jkssb
Namespace:            kube-system
Priority:<PHONE_NUMBER>
Priority Class Name:  system-cluster-critical
Node:                 na/<IP_ADDRESS>
Start Time:           Wed, 13 Jul 2022 00:37:51 +0800
Labels:               k8s-app=kube-dns
                      pod-template-hash=6d8c4cb4d
Annotations:          <none>
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/coredns-6d8c4cb4d
Containers:
  coredns:
    Container ID:  docker://cc35b97903b120cb54765641da47c69ea8c833e6c72958407c7e605a5aa001b4
    Image:         registry.aliyuncs.com/google_containers/coredns:v1.8.6
    Image ID:      docker-pullable://registry.aliyuncs.com/google_containers/coredns@sha256:5b6ec0d6de9baaf3e92d0f66cd96a25b9edbce8716f5f15dcd1a616b3abd590e
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Wed, 13 Jul 2022 00:57:12 +0800
      Finished:     Wed, 13 Jul 2022 00:59:06 +0800
    Ready:          False
    Restart Count:  8
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:    http-get http://:8181/ready delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-v8hzn (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  kube-api-access-v8hzn:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 CriticalAddonsOnly op=Exists
                             node-role.kubernetes.io/control-plane:NoSchedule
                             node-role.kubernetes.io/master:NoSchedule
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age   From               Message
  ----     ------                  ----  ----               -------
  Normal   Scheduled               21m   default-scheduler  Successfully assigned kube-system/coredns-6d8c4cb4d-jkssb to na
  Warning  FailedCreatePodSandBox  20m   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "8ae4c118e4c3ff1c0bd2c601c808cae2c17cbc27552fb148b755b7d798f0bb71" network for pod "coredns-6d8c4cb4d-jkssb": networkPlugin cni failed to set up pod "coredns-6d8c4cb4d-jkssb_kube-system" network: unable to connect to Cilium daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get "http:///var/run/cilium/cilium.sock/v1/config": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory
Is the agent running?
  Normal   SandboxChanged  20m                   kubelet  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled          20m                   kubelet  Container image "registry.aliyuncs.com/google_containers/coredns:v1.8.6" already present on machine
  Normal   Created         20m                   kubelet  Created container coredns
  Normal   Started         20m                   kubelet  Started container coredns
  Warning  Unhealthy       20m (x2 over 20m)     kubelet  Readiness probe failed: Get "http://<IP_ADDRESS>:8181/ready": dial tcp <IP_ADDRESS>:8181: i/o timeout (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy       18m (x13 over 20m)    kubelet  Readiness probe failed: Get "http://<IP_ADDRESS>:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy       15m (x12 over 19m)    kubelet  Liveness probe failed: Get "http://<IP_ADDRESS>:8080/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Normal   Killing         14m                   kubelet  Container coredns failed liveness probe, will be restarted

We can find the healthcheck of coredns is failed.
And the logs of coredns as follow, we can find it can't access the udp <IP_ADDRESS>:53(i/o timeout).<IP_ADDRESS> is the gateway of my  network.
root@nm:/work-place/kubernetes/create-cluster# kubectl logs  coredns-6d8c4cb4d-jkssb -n kube-system
[WARNING] plugin/kubernetes: starting server with unsynced Kubernetes API
.:53
[INFO] plugin/reload: Running configuration MD5 = db32ca3650231d74073ff4cf814959a7
CoreDNS-1.8.6
linux/amd64, go1.17.1, 13a9191
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:39983-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:53240-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:49802-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:54428-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:43974-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:37821-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:36545-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:56785-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:47913-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>537686268.4300248127207674545. HINFO: read udp <IP_ADDRESS>:38162-><IP_ADDRESS>:53: i/o timeout
[INFO] SIGTERM: Shutting down servers then terminating
[INFO] plugin/health: Going into lameduck mode for 5s

And the status of cilium pod seems normally, but cilium status is not health:
root@nm:/work-place/kubernetes/create-cluster# cilium status
    /¯¯\
 /¯¯\__/¯¯\    Cilium:         3 errors
 \__/¯¯\__/    Operator:       OK
 /¯¯\__/¯¯\    Hubble:         disabled
 \__/¯¯\__/    ClusterMesh:    disabled
    \__/

DaemonSet         cilium             Desired: 3, Ready: 3/3, Available: 3/3
Deployment        cilium-operator    Desired: 1, Ready: 1/1, Available: 1/1
Containers:       cilium             Running: 3
                  cilium-operator    Running: 1
Cluster Pods:     2/2 managed by Cilium
Image versions    cilium-operator    quay.io/cilium/operator-generic:v1.11.6@sha256:9f6063c7bcaede801a39315ec7c166309f6a6783e98665f6693939cf1701bc17: 1
                  cilium             quay.io/cilium/cilium:v1.11.6@sha256:f7f93c26739b6641a3fa3d76b1e1605b15989f25d06625260099e01c8243f54c: 3
Errors:           cilium             cilium-hn9g5    controller cilium-health-ep is failing since 27s (21x): Get "http://<IP_ADDRESS>:4240/hello": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                  cilium             cilium-7l6br    controller cilium-health-ep is failing since 27s (21x): Get "http://<IP_ADDRESS>:4240/hello": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
                  cilium             cilium-rzkb6    controller cilium-health-ep is failing since 27s (21x): Get "http://<IP_ADDRESS>:4240/hello": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Try
I do this try.

Change iptables ACCEPT policy. https://github.com/kubernetes/kubernetes/issues/86762
Check files /run/systemd/resolve/resolv.conf  and /etc/resolv.conf .

Other Info

The coredns configMap:

root@nm:/work-place/kubernetes/create-cluster# kubectl describe cm coredns -n kube-system
Name:         coredns
Namespace:    kube-system
Labels:       <none>
Annotations:  <none>

Data
====
Corefile:
----
.:53 {
    errors
    health {
       lameduck 5s
    }
    ready
    kubernetes cluster.local in-addr.arpa ip6.arpa {
       pods insecure
       fallthrough in-addr.arpa ip6.arpa
       ttl 30
    }
    prometheus :9153
    forward . /etc/resolv.conf {
       max_concurrent 1000
    }
    cache 30
    loop
    reload
    loadbalance
}

BinaryData
====

Events:  <none>

kubelet.config

root@nm:/home/lzl# cat /var/lib/kubelet/config.yaml
apiVersion: kubelet.config.k8s.io/v1beta1
authentication:
  anonymous:
    enabled: false
  webhook:
    cacheTTL: 0s
    enabled: true
  x509:
    clientCAFile: /etc/kubernetes/pki/ca.crt
authorization:
  mode: Webhook
  webhook:
    cacheAuthorizedTTL: 0s
    cacheUnauthorizedTTL: 0s
cgroupDriver: systemd
clusterDNS:
- <IP_ADDRESS>
clusterDomain: cluster.local
cpuManagerReconcilePeriod: 0s
evictionPressureTransitionPeriod: 0s
fileCheckFrequency: 0s
healthzBindAddress: <IP_ADDRESS>
healthzPort: 10248
httpCheckFrequency: 0s
imageMinimumGCAge: 0s
kind: KubeletConfiguration
logging:
  flushFrequency: 0
  options:
    json:
      infoBufferSize: "0"
  verbosity: 0
memorySwap: {}
nodeStatusReportFrequency: 0s
nodeStatusUpdateFrequency: 0s
resolvConf: /run/systemd/resolve/resolv.conf
rotateCertificates: true
runtimeRequestTimeout: 0s
shutdownGracePeriod: 0s
shutdownGracePeriodCriticalPods: 0s
staticPodPath: /etc/kubernetes/manifests
streamingConnectionIdleTimeout: 0s
syncFrequency: 0s
volumeStatsAggPeriod: 0s

kubeadm flags of kubelet:

root@nm:/home/lzl# cat /var/lib/kubelet/kubeadm-flags.env
KUBELET_KUBEADM_ARGS="--network-plugin=cni --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.6"

When I using flannel as cluster network plugin, all things is OK.
What did you expect to happen?
I want the status of coredns become ready, and kubernetes network can work normally. What should I do?
How can we reproduce it (as minimally and precisely as possible)?
Like the ahead step to create cluster.
Cilium Version
Cilium version is 1.11.6.
Kernel Version
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
$ uname -a
Linux nm 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

### Kubernetes Version

```console
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:16:20Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:09:57Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"

Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@lizonglin313 can you provide sysdump?

you may also try to deploy a network trouble shooting pod like netshoot to manually query your DNS server <IP_ADDRESS>:53 to see if it works, I suspect it may not work, and then start to trouble shoot with tcpdump, or even https://github.com/cilium/pwru

you may also try to deploy a network trouble shooting pod like netshoot to manually query your DNS server <IP_ADDRESS>:53 to see if it works, I suspect it may not work, and then start to trouble shoot with tcpdump, or even https://github.com/cilium/pwru

Thanks. Let me have a try.

Hi all! This is my cilium sysdump information.
root@nm:/work-place/kubernetes/create-cluster# cilium sysdump
🔍 Collecting sysdump with cilium-cli version: v0.11.11, args: [sysdump]
🔍 Collecting Kubernetes nodes
🔍 Collect Kubernetes nodes
🔍 Collecting Kubernetes events
🔍 Collecting Kubernetes pods
🔍 Collect Kubernetes version
🔍 Collecting Kubernetes namespaces
🔍 Collecting Kubernetes services
🔍 Collecting Kubernetes pods summary
🔍 Collecting Kubernetes endpoints
🔍 Collecting Kubernetes network policies
🔍 Collecting Cilium cluster-wide network policies
🔍 Collecting Cilium network policies
🔍 Collecting Cilium local redirect policies
🔍 Collecting Cilium egress NAT policies
🔍 Collecting Cilium endpoints
🔍 Collecting Cilium identities
🔍 Collecting Cilium nodes
🔍 Collecting Ingresses
🔍 Collecting CiliumEnvoyConfigs
🔍 Collecting CiliumClusterwideEnvoyConfigs
🔍 Collecting Cilium etcd secret
🔍 Collecting the Cilium configuration
🔍 Collecting the Cilium daemonset(s)
🔍 Collecting the Hubble daemonset
🔍 Collecting the Hubble Relay deployment
🔍 Collecting the Hubble Relay configuration
🔍 Collecting the Hubble UI deployment
🔍 Collecting the Cilium operator deployment
🔍 Collecting the CNI configuration files from Cilium pods
⚠ Deployment "hubble-ui" not found in namespace "kube-system" - this is expected if Hubble UI is not enabled
🔍 Collecting the CNI configmap
🔍 Collecting the 'clustermesh-apiserver' deployment
⚠ Deployment "hubble-relay" not found in namespace "kube-system" - this is expected if Hubble is not enabled
🔍 Collecting gops stats from Cilium pods
🔍 Collecting gops stats from Hubble pods
🔍 Collecting gops stats from Hubble Relay pods
🔍 Collecting 'cilium-bugtool' output from Cilium pods
🔍 Collecting logs from Cilium pods
🔍 Collecting logs from Cilium operator pods
⚠ Deployment "clustermesh-apiserver" not found in namespace "kube-system" - this is expected if 'clustermesh-apiserver' isn't enabled
🔍 Collecting logs from 'clustermesh-apiserver' pods
🔍 Collecting logs from Hubble pods
🔍 Collecting logs from Hubble Relay pods
🔍 Collecting logs from Hubble UI pods
🔍 Collecting platform-specific data
🔍 Collecting Hubble flows from Cilium pods
⚠ The following tasks failed, the sysdump may be incomplete:
⚠ [11] Collecting Cilium egress NAT policies: failed to collect Cilium egress NAT policies: the server could not find the requested resource (get ciliumegressnatpolicies.cilium.io)
⚠ [12] Collecting Cilium local redirect policies: failed to collect Cilium local redirect policies: the server could not find the requested resource (get ciliumlocalredirectpolicies.cilium.io)
⚠ [17] Collecting CiliumClusterwideEnvoyConfigs: failed to collect CiliumClusterwideEnvoyConfigs: the server could not find the requested resource (get ciliumclusterwideenvoyconfigs.cilium.io)
⚠ [18] Collecting CiliumEnvoyConfigs: failed to collect CiliumEnvoyConfigs: the server could not find the requested resource (get ciliumenvoyconfigs.cilium.io)
⚠ [23] Collecting the Hubble Relay configuration: failed to collect the Hubble Relay configuration: configmaps "hubble-relay-config" not found
⚠ cniconflist-cilium-7l6br: error dialing backend: dial tcp <IP_ADDRESS>:10250: connect: no route to host
⚠ cniconflist-cilium-hn9g5: command terminated with exit code 1
⚠ cniconflist-cilium-rzkb6: command terminated with exit code 1
⚠ gops-cilium-7l6br-memstats: failed to list processes "cilium-7l6br" ("cilium-agent") in namespace "kube-system": error dialing backend: dial tcp <IP_ADDRESS>:10250: connect: no route to host
⚠ gops-cilium-7l6br-stack: failed to list processes "cilium-7l6br" ("cilium-agent") in namespace "kube-system": error dialing backend: dial tcp <IP_ADDRESS>:10250: connect: no route to host
⚠ gops-cilium-7l6br-stats: failed to list processes "cilium-7l6br" ("cilium-agent") in namespace "kube-system": error dialing backend: dial tcp <IP_ADDRESS>:10250: connect: no route to host
⚠ cilium-bugtool-cilium-7l6br: failed to collect 'cilium-bugtool' output for "cilium-7l6br" in namespace "kube-system": error dialing backend: dial tcp <IP_ADDRESS>:10250: connect: no route to host:
⚠ logs-cilium-7l6br-cilium-agent: failed to collect logs for "cilium-7l6br" ("cilium-agent") in namespace "kube-system": Get "https://<IP_ADDRESS>:10250/containerLogs/kube-system/cilium-7l6br/cilium-agent?limitBytes=1073741824&sinceTime=2021-07-13T08%3A20%3A54Z&timestamps=true": dial tcp <IP_ADDRESS>:10250: connect: no route to host
⚠ logs-cilium-operator-5d67fc458d-gjdc6-cilium-operator: failed to collect logs for "cilium-operator-5d67fc458d-gjdc6" ("cilium-operator") in namespace "kube-system": Get "https://<IP_ADDRESS>:10250/containerLogs/kube-system/cilium-operator-5d67fc458d-gjdc6/cilium-operator?limitBytes=1073741824&sinceTime=2021-07-13T08%3A20%3A55Z&timestamps=true": dial tcp <IP_ADDRESS>:10250: connect: no route to host
⚠ logs-cilium-7l6br-mount-cgroup: failed to collect logs for "cilium-7l6br" ("mount-cgroup") in namespace "kube-system": Get "https://<IP_ADDRESS>:10250/containerLogs/kube-system/cilium-7l6br/mount-cgroup?limitBytes=1073741824&sinceTime=2021-07-13T08%3A20%3A54Z&timestamps=true": dial tcp <IP_ADDRESS>:10250: connect: no route to host
⚠ logs-cilium-7l6br-clean-cilium-state: failed to collect logs for "cilium-7l6br" ("clean-cilium-state") in namespace "kube-system": Get "https://<IP_ADDRESS>:10250/containerLogs/kube-system/cilium-7l6br/clean-cilium-state?limitBytes=1073741824&sinceTime=2021-07-13T08%3A20%3A54Z&timestamps=true": dial tcp <IP_ADDRESS>:10250: connect: no route to host
⚠ hubble-flows-cilium-7l6br: failed to collect hubble flows for "cilium-7l6br" in namespace "kube-system": error dialing backend: dial tcp <IP_ADDRESS>:10250: connect: no route to host:
⚠ Please note that depending on your Cilium version and installation options, this may be expected
🗳 Compiling sysdump
✅ The sysdump has been saved to /work-place/kubernetes/create-cluster/cilium-sysdump-20220713-162053.zip

can you attach the incomplete sysdump?

can you attach the incomplete sysdump? and get command output from sysctl -a | grep -w rp_filter

As Follow:
root@nm:/work-place/kubernetes/create-cluster# sysctl -a | grep -w rp_filter
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.cilium_host.rp_filter = 0
net.ipv4.conf.cilium_net.rp_filter = 0
net.ipv4.conf.cilium_vxlan.rp_filter = 0
net.ipv4.conf.default.rp_filter = 2
net.ipv4.conf.docker0.rp_filter = 2
net.ipv4.conf.ens33.rp_filter = 2
net.ipv4.conf.lo.rp_filter = 2
net.ipv4.conf.lxc_health.rp_filter = 2

I use busybox, and ping upstream dns server. DNS server cannot be accessed when using Cilium.
root@nm:/work-place/kubernetes/create-cluster# kubectl run -it --rm --restart=Never busybox --image=docker.io/library/busybox sh
If you don't see a command prompt, try pressing enter.
/ # ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes

But when I change network plugin to other cni (like flannel), it work.
root@master:/home/lzl/work-place/kubernetes/deploy-k8s# kubectl run -it --rm --restart=Never busybox --image=docker.io/library/busybox sh
If you don't see a command prompt, try pressing enter.
/ # ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
^C
--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
/ # ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=127 time=0.458 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=127 time=0.405 ms
64 bytes from <IP_ADDRESS>: seq=2 ttl=127 time=1.041 ms
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.405/0.634/1.041 ms

I wonder if I have not done well in the configuration of Cilium.

try manually add file like below in /etc/sysctl.d/ and reboot the node
cat /etc/sysctl.d/99-zzz-override_cilium.conf
# Disable rp_filter on Cilium interfaces since it may cause mangled packets to be dropped
net.ipv4.conf.lxc*.rp_filter = 0
net.ipv4.conf.cilium_*.rp_filter = 0
# The kernel uses max(conf.all, conf.{dev}) as its value, so we need to set .all. to 0 as well.
# Otherwise it will overrule the device specific settings.
net.ipv4.conf.all.rp_filter = 0

My deep appreciation is beyond words for your solution. The coredns is working normally. Can you talk a little bit about your thinking and why this problem arose. I hope this question hasn't taken up too much of your time. Thank you again!

it is a known problem I happen to know. for problem trouble shooting, start with the basic and dig step by step with proper tools :)

FYI https://github.com/cilium/cilium/pull/20072 should address the issue for you

FYI #20072 should address the issue for you

Thanks! All the best.

Closing this issue since https://github.com/cilium/cilium/pull/20072 was merged and is available on all Cilium versions

I also encountered this problem, but when applying the configuration related to "/etc/sysctl. d/99-Zzzz-override_cilium. conf", an error was reported. The software and operating system versions are consistent with this topic. How should I resolve this issue?


cache Roman storm project nfts

Current dependencies on/for this PR:

main

PR #4234   👈

This stack of pull requests is managed by Graphite.


sqlite support?

On the official website, I can see that OmniDB suppose to support sqlite database. https://omnidb.org/en/
However, after installation of the latest version, 2.14.0, I cannot see any "sqlite" in the "technology" combobox in the "Connection" dialog.  There are only "postgresql", "mariadb", "mysql" and "oracle".
So... omnidb supports sqlite or not?

Apparently, there is build of mariadb for my target platform (arm). So I will just use mariadb then.


Do not segfault when peer CN is absent

In HostNameCertificateVerifier::Verify, do not use the peer_info->common_name if it is a null pointer.
Fixes tracebacks like:
Thread 1 "grpc_tls_certif" received signal SIGSEGV, Segmentation fault.
0x00007ffff75f617d in __strlen_avx2 () from /lib64/libc.so.6
#0  0x00007ffff75f617d in __strlen_avx2 () from /lib64/libc.so.6
#1  0x00007ffff7de39e2 in std::char_traits<char>::length (__s=0x0) at /usr/include/c++/12/bits/char_traits.h:395
#2  std::basic_string_view<char, std::char_traits<char> >::basic_string_view (__str=0x0, this=<optimized out>) at /usr/include/c++/12/string_view:134
#3  grpc_core::HostNameCertificateVerifier::Verify(grpc_tls_custom_verification_check_request*, std::function<void (absl::lts_20211102::Status)>, absl::lts_20211102::Status*) (this=<optimized out>, request=<optimized out>, sync_status=sync_status@entry=0x7fffffffd978) at /builddir/build/BUILD/grpc-1.45.1/src/core/lib/security/credentials/tls/grpc_tls_certificate_verifier.cc:137
#4  0x000055555556c95a in grpc_core::testing::GrpcTlsCertificateVerifierTest_HostnameVerifierIpCheckFails_Test::TestBody (this=<optimized out>) at /builddir/build/BUILD/grpc-1.45.1/test/core/security/grpc_tls_certificate_verifier_test.cc:225
#5  0x00005555555a4d4f in testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void> (location=0x5555555b887a "the test body", method=<optimized out>, object=0x555555612910) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:2654
#6  testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void> (object=object@entry=0x555555612910, method=<optimized out>, location=location@entry=0x5555555b887a "the test body") at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:2690
#7  0x0000555555591b26 in testing::Test::Run (this=0x555555612910) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:2729
#8  testing::Test::Run (this=0x555555612910) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:2719
#9  0x0000555555591d5d in testing::TestInfo::Run (this=0x5555555f0570) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:2908
#10 0x0000555555591ee2 in testing::TestSuite::Run (this=0x5555555eeb80) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:3067
#11 0x0000555555599f27 in testing::TestSuite::Run (this=<optimized out>) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:3041
#12 testing::internal::UnitTestImpl::RunAllTests (this=0x5555555ee7b0) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:5937
#13 0x00005555555a5337 in testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> (location=0x5555555ba960 "auxiliary test code (environments or event listeners)", method=<optimized out>, object=0x5555555ee7b0) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:2654
#14 testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> (object=0x5555555ee7b0, method=<optimized out>, location=location@entry=0x5555555ba960 "auxiliary test code (environments or event listeners)") at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:2690
#15 0x0000555555592143 in testing::UnitTest::Run (this=0x5555555d9500 <testing::UnitTest::GetInstance()::instance>) at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/src/gtest.cc:5506
#16 0x00005555555657f2 in RUN_ALL_TESTS () at /builddir/build/BUILD/grpc-1.45.1/third_party/googletest/googletest/include/gtest/gtest.h:2311
#17 main (argc=<optimized out>, argv=0x7fffffffddd8) at /builddir/build/BUILD/grpc-1.45.1/test/core/security/grpc_tls_certificate_verifier_test.cc:262

We’ve been seeing these segfaults in practice since 1.42.0 when running the tests for Fedora Linux’s grpc package. Of course, we unbundle dependencies, don’t use Docker, and use OpenSSL rather than BoringSSL, so the environment is a little different than Google’s CI testing. This patch fixes the problem.

@veblush

Any thoughts on this tiny PR? Thanks!

@markdroth, since you reviewed #29568, can I draw your attention to this? It’s also a tiny fix for a null-pointer dereference. Thanks!

This looks good to me, but I'd like @ZhenLian to review before merging.
Meanwhile, I've triggered the tests to run.

Thanks for catching this and providing the quick fix!

Failures are irrelevant. Merging now.


Build instructions for Arch users?

Hate to be that guy, but I'm gonna be that guy. The following error is what I get when trying to build using Manjaro, all packages are up to date.
$ mkdir build && cd build
$ cmake .. -DCMAKE_BUILD_TYPE="Release"
-- The C compiler identification is GNU 11.1.0
-- The CXX compiler identification is GNU 11.1.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found OpenGL: /usr/lib/libOpenGL.so
-- Configuring done
CMake Error at cmake/TargetNanoVG.cmake:3 (add_library):
  Cannot find source file:

    /home/prizmo/Downloads/Aether/extern/nanovg/src/nanovg.c

  Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .h
  .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc
Call Stack (most recent call first):
  CMakeLists.txt:65 (include)

CMake Error at cmake/TargetPugl.cmake:3 (add_library):
  Cannot find source file:

    /home/prizmo/Downloads/Aether/extern/pugl/src/implementation.c

  Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .h
  .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc
Call Stack (most recent call first):
  CMakeLists.txt:63 (include)

CMake Error at cmake/TargetNanoVG.cmake:3 (add_library):
  No SOURCES given to target: nanovg
Call Stack (most recent call first):
  CMakeLists.txt:65 (include)

CMake Error at cmake/TargetPugl.cmake:3 (add_library):
  No SOURCES given to target: pugl
Call Stack (most recent call first):
  CMakeLists.txt:63 (include)

No worries! The problem seems to be that some of the git submodules are missing. The solution is to clone the repository with the --recurse-submodules flag like so:
git clone --recurse-submodules https://github.com/Dougal-s/Aether.git

or to run git submodule update --init after cloning.
Unfortunately, submodules aren't included in the "Download ZIP" zip or in the "Source Code" files under releases, so using git is the only option unless you download and extract each submodule separately.

That's what happens when I just use git clone without the --recurse-submodules. Marking as closed


Add testing workflow for Github Actions

Codecov Report

Merging #17 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev    #17   +/-   ##
===================================
  Coverage   100%   100%
===================================
  Files        11     11
  Lines       413    418    +5
===================================
+ Hits        413    418    +5

Impacted Files
Coverage Δ

lib/structures/await/index.js
100% <0%> (ø)
:arrow_up:

lib/modules/command-handler/index.js
100% <0%> (ø)
:arrow_up:

lib/structures/command/index.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Combined Searches

Thanks for this great tool.
I noticed that combined searches don't seem to work.
I tried:
-Displays wheelchair accessible museums.

Display fountains near the train station.

But each time I get an error.

Hi @MyNameIsTroll, I'm currently using GPT-3, but it has some limitations when it comes to accurately answering complex osm queries. To address this issue and avoid the cost of using GPT-3, we're researching an open-source alternative model and fine-tuning it.
see the progress here #1

@rowheat02
I understand, wise decision :)
Thank you for your reply.


[Bug]: SQL missings

Describe the bug
Hello to you, I installed hackster on my VPS to make it run on my discord, I have however a problem, I lack many tables for the DB (I created the first ones for the api to launch) do you have a list of Tables or installation sheet?thank you very much
To reproduce
(Background on this error at: https://sqlalche.me/e/20/f405)
15:43:31 - asyncio ERROR: Task exception was never retrieved
future: <Task finished name='pycord: on_message' coro=<Client._run_event() done, defined at /root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/discord/client.py:370> exception=ProgrammingError('(asyncmy.errors.ProgrammingError) (1146, "Table 'bot_dev.htb_discord_link' doesn't exist")')>
Traceback (most recent call last):
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1963, in exec_single_context
self.dialect.do_execute(
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/default.py", line 920, in do_execute
cursor.execute(statement, parameters)
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/dialects/mysql/asyncmy.py", line 95, in execute
return self.await(self._execute_async(operation, parameters))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/util/_concurrency_py3k.py", line 126, in await_only
return current.driver.switch(awaitable)  # type: ignore[no-any-return]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/util/_concurrency_py3k.py", line 187, in greenlet_spawn
value = await result
^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/dialects/mysql/asyncmy.py", line 107, in _execute_async
result = await self._cursor.execute(operation, parameters)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "asyncmy/cursors.pyx", line 179, in execute
File "asyncmy/cursors.pyx", line 364, in _query
File "asyncmy/connection.pyx", line 450, in query
File "asyncmy/connection.pyx", line 638, in _read_query_result
File "asyncmy/connection.pyx", line 1025, in read
File "asyncmy/connection.pyx", line 600, in read_packet
File "asyncmy/protocol.pyx", line 190, in asyncmy.protocol.MysqlPacket.raise_for_error
File "asyncmy/protocol.pyx", line 194, in asyncmy.protocol.MysqlPacket.raise_for_error
File "asyncmy/errors.pyx", line 128, in asyncmy.errors.raise_mysql_exception
File "asyncmy/errors.pyx", line 137, in asyncmy.errors.raise_mysql_exception
asyncmy.errors.ProgrammingError: (1146, "Table 'bot_dev.htb_discord_link' doesn't exist")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/discord/client.py", line 383, in _run_event
await self.on_error(event_name, *args, **kwargs)
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/discord/client.py", line 378, in _run_event
await coro(*args, **kwargs)
File "/hackster/hackster/src/cmds/automation/auto_verify.py", line 57, in on_message
await self.process_reverification(ctx.author)
File "/hackster/hackster/src/cmds/automation/auto_verify.py", line 30, in process_reverification
result = await session.scalars(stmt)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/ext/asyncio/session.py", line 553, in scalars
result = await self.execute(
^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/ext/asyncio/session.py", line 435, in execute
result = await greenlet_spawn(
^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/util/_concurrency_py3k.py", line 192, in greenlet_spawn
result = context.throw(*sys.exc_info())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/orm/session.py", line 2232, in execute
return self._execute_internal(
^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/orm/session.py", line 2127, in _execute_internal
result: Result[Any] = compile_state_cls.orm_execute_statement(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/orm/context.py", line 292, in orm_execute_statement
result = conn.execute(
^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1413, in execute
return meth(
^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/sql/elements.py", line 483, in _execute_on_connection
return connection._execute_clauseelement(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1637, in _execute_clauseelement
ret = self._execute_context(
^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1841, in _execute_context
return self._exec_single_context(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1982, in _exec_single_context
self._handle_dbapi_exception(
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 2339, in _handle_dbapi_exception
raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1963, in exec_single_context
self.dialect.do_execute(
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/engine/default.py", line 920, in do_execute
cursor.execute(statement, parameters)
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/dialects/mysql/asyncmy.py", line 95, in execute
return self.await(self._execute_async(operation, parameters))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/util/_concurrency_py3k.py", line 126, in await_only
return current.driver.switch(awaitable)  # type: ignore[no-any-return]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/util/_concurrency_py3k.py", line 187, in greenlet_spawn
value = await result
^^^^^^^^^^^^
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/sqlalchemy/dialects/mysql/asyncmy.py", line 107, in _execute_async
result = await self._cursor.execute(operation, parameters)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "asyncmy/cursors.pyx", line 179, in execute
File "asyncmy/cursors.pyx", line 364, in _query
File "asyncmy/connection.pyx", line 450, in query
File "asyncmy/connection.pyx", line 638, in _read_query_result
File "asyncmy/connection.pyx", line 1025, in read
File "asyncmy/connection.pyx", line 600, in read_packet
File "asyncmy/protocol.pyx", line 190, in asyncmy.protocol.MysqlPacket.raise_for_error
File "asyncmy/protocol.pyx", line 194, in asyncmy.protocol.MysqlPacket.raise_for_error
File "asyncmy/errors.pyx", line 128, in asyncmy.errors.raise_mysql_exception
File "asyncmy/errors.pyx", line 137, in asyncmy.errors.raise_mysql_exception
sqlalchemy.exc.ProgrammingError: (asyncmy.errors.ProgrammingError) (1146, "Table 'bot_dev.htb_discord_link' doesn't exist")
[SQL: SELECT htb_discord_link.id, htb_discord_link.account_identifier, htb_discord_link.discord_user_id, htb_discord_link.htb_user_id
FROM htb_discord_link
WHERE htb_discord_link.discord_user_id = %s ORDER BY htb_discord_link.id
LIMIT %s]
[parameters:<PHONE_NUMBER>199704616, 1)]
(Background on this error at: https://sqlalche.me/e/20/f405)
Expected behavior
└─# poetry run task start
14:51:28 - discord.client WARNING: PyNaCl is not installed, voice will NOT be supported
14:51:28 - main INFO: Starting bot & webhook server
INFO:     Started server process [9326]
INFO:     Waiting for application startup.
14:51:28 - discord.client INFO: logging in using static token
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:1337 (Press CTRL+C to quit)
14:51:31 - src.bot INFO: Started bot as Hckster#8721 (ID:<PHONE_NUMBER>088788000)
Loading ScheduledTasks cog...
ScheduledTasks cog loaded!
14:52:37 - asyncio ERROR: Task exception was never retrieved
future: <Task finished name='pycord: on_application_command' coro=<Client._run_event() done, defined at /root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/discord/client.py:370> exception=AttributeError("'NoneType' object has no attribute 'send'")>
Relevant log output
No response
Additional context

16:51:25 - discord.client WARNING: PyNaCl is not installed, voice will NOT be supported
16:51:26 - main INFO: Starting bot & webhook server
INFO:     Started server process [14370]
INFO:     Waiting for application startup.
16:51:26 - discord.client INFO: logging in using static token
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:1337 (Press CTRL+C to quit)
16:51:28 - src.bot INFO: Started bot as Hackster#8721 (ID:<PHONE_NUMBER>088788000)
Loading ScheduledTasks cog...
ScheduledTasks cog loaded!
16:52:18 - asyncio ERROR: Task exception was never retrieved
future: <Task finished name='pycord: on_application_command' coro=<Client._run_event() done, defined at /root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/discord/client.py:370> exception=AttributeError("'NoneType' object has no attribute 'send'")>
Traceback (most recent call last):
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/discord/client.py", line 383, in _run_event
await self.on_error(event_name, *args, **kwargs)
File "/root/.cache/pypoetry/virtualenvs/hackster-jqLlKwl8-py3.11/lib/python3.11/site-packages/discord/client.py", line 378, in _run_event
await coro(*args, **kwargs)
File "/hackster/hackster/src/bot.py", line 84, in on_application_command
await ctx.guild.get_channel(settings.channels.BOT_LOGS).send(embed=embed)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'send'
16:52:19 - src.helpers.verification ERROR: Non-OK HTTP status code returned from identifier lookup: 401.

@Frozenka please excuse us for not responding earlier. You will find all the required migrations under alembic/versions folder. Also, you can find a .test.env that you can use in order to assign the correct environmental variables.


Licensing

Based on email from Helen:
Individual Resource pages - make sure resources you manage have licensing details displayed prominently, are unambiguous (eg don't refer to EBI general terms of use in one place and cc0 in another) and are up to date. https://www.ebi.ac.uk/licencing has some boilerplate text on licensing to reuse if required - by end of March

I don't think CC0 is recommended for code. The license in the OLS3 repo https://github.com/EBISPOT/OLS/blob/dev/LICENSE is Apache 2.0.

@serjoshua has a nice footer implementation in OXO2 we should add to OLS4

Merged initial changes to dev branch. I haven't deployed anything to any environments. Feel free to play around with it. I don't think I have plenty of sample pages in my local to test the footer to.

One thing about OLS is that most of the content it displays has nothing to do with EBI. We should probably make that clear in the footer?

Ooh. If we have an existing verbiage we could copy or something, that would be great. I also noticed some of the footers of our tools in production are cluttered with links and info. Maybe there is an existing behavior we could pattern as well.


Update params

Rename userIds to speakerIds
Remove less relevant params from examples

@sushant-hiray can u release version after merging this branch


Reproduce the code

After reading your readme and want to reproduce your paper, are there more detailed steps? At the same time, I also want to combine with YOLOV7? Thank you

To reproduce the reported performance, you should just download the corresponding yolox detector weights and run the inference code, whose config files are already provided.
There is an example to incorporate other detectors, you can customize it yourself (there is an example). Or you can use the oc-sort support in mmtracking.


Missing file: unstruct_terms.txt

Hi :)
would it be possible that you add the file: unstruct_terms.txt?
It is used in the README under the "Example" section  right after the imports. That would be great, because otherwise its not possible to test the examples.
Thank you,
Simon

Hi Simon,
Sorry for the delay. The newest version includes a test/unstruct_terms.txt file with extremely basic terms. The README has been updated such that you could copy and paste an example command and it will run, so long as you are using a remote or cached ontology.
Please let us know if there is anything else, but I will mark this as closed.


CouchPotato Complaining, but not sure why?

11-02 21:37:14 ERROR [              PostProcess] Failed to execute post processing on file /var/hda/files/drives/8TB/Plex/Movies/Bad Moms (2016)/Bad Moms (2016) 720p.mp4
11-02 21:37:14 ERROR [              PostProcess] Traceback (most recent call last):
File "/var/hda/web-apps/couchpotato/data/custom_plugins/PostProcess/main.py", line 40, in callscript process = subprocess.Popen([exec_me, imdbid, inputfile, original], shell=False, stdin=subprocess.PIPE, stdout=subprocess.PIPE, stderr=subprocess.PIPE, env={})
File "/usr/lib64/python2.7/subprocess.py", line 710, in init
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 20] Not a directory
Any ideas to what this referencing to? I set my permissions for it to be able to write to the folder just as I did for Sonarr...

Did you edit your main.py file to reflect the appropriate script path as directed in the readme?
Looks like that path isn't set or is set incorrectly

Yea I noticed the instructions last night said to point to where it resides. Not and actual script. Thanks again. All is good now.

On Nov 3, 2016, at 07:14, Michael Higgins<EMAIL_ADDRESS>wrote:
Did you edit your main.py file to reflect the appropriate script path as directed in the readme?
Looks like that path isn't set or is set incorrectly
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/mdhiggins/sickbeard_mp4_automator/issues/589#issuecomment-258126674, or mute the thread https://github.com/notifications/unsubscribe-auth/AWD90b44UY32rl646xx4lngvNyLYH3r7ks5q6dBDgaJpZM4Kn-1u.


add UI to split and download incident alerts

to fix #88 and #90

the changes to column-generator.jsx will conflict with #307 so i guess you will need to uh rebase or something? i am not smart enough to do that


Adding SleepSort Algorithm in JavaScript

🚀 Feature
I would like sleep sort algorithm/technique in JavaScript Sort Section
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
I would like to spread my knowledge regarding this unique sorting technique, can i work on this issue?
Pitch
SleepSort algorithm in javascript is a Unique way of sorting an array, which most of the javaScript users doesn't know.
Sleepsort is an algorithm which works on basic timeout function but can sort an array easily. I will write a clean, self-explanatory code of this algorithm.

I would like to do this in java

@gupta-piyush19 Go ahead with implementation in Javascript.
Do remember to mention constraints in your algo like negative numbers


RuntimeError:   CUDA报错

RuntimeError:
CUDA Setup failed despite GPU being available. Inspect the CUDA SETUP outputs above to fix your environment!
If you cannot find any issues and suspect a bug, please open an issue with detals about your environment:
https://github.com/TimDettmers/bitsandbytes/issues

报错显示GPU无法使用，你看下cuda安装是否正确。


chore: refuse to include source files into package

Informations

Type
Breaking change

Chore
No

Description
There's no point in including source files into npm package. It not only affects on a package size, but also can lead to re-compile .ts files in node_modules.

But if the source isn't included, the source mapping won't works correctly if any bug occurs in your code.
But you have to exclude node_modules in tsconfig to avoid recompilation :) The problem is here ;)
{
  "compilerOptions": {
    "target": "es2016",
    "lib": ["es2016"],
    "typeRoots": [
      "./node_modules/@types"
    ],
    "module": "commonjs",
    "moduleResolution": "node",
    "experimentalDecorators":true,
    "emitDecoratorMetadata": true,
    "allowSyntheticDefaultImports": true
  },
  "exclude": [
    "node_modules"  // don't forget this line
  ]
}

Hi @Romakita ,
I have some remarks)

The problem is here ;)

Just see following example: https://github.com/ArtemDerevnjuk/tsed-example. How you can see it doesn't solve that issue

you have to exclude node_modules in tsconfig to avoid recompilation

exclude has direct influence on search source files. It doesn't effect on module resolution. It means, if the compiler needs some .ts or .d.ts files to compile your sources, it will include them regardless exclude directive.
https://github.com/Microsoft/TypeScript/wiki/FAQ#why-is-a-file-in-the-exclude-list-still-picked-up-by-the-compiler
https://www.typescriptlang.org/docs/handbook/module-resolution.html#how-typescript-resolves-modules

If the source isn't included, the source mapping won't works correctly

It doesn't matter. First, tsc allows to include source code into your source maps, you just need to enable inlineSources. Second, the published packages don't have the config files and dev dependencies to make a useful debugging experience. Therforce, there is no way for users to modify and compile .ts files in node_modules.

Ok ;). I'll take a time to test your PR on my machine before to be sure all is fine. I'll check tomorrow.
See you :)

@ArtemDerevnjuk Thanks for your tips. It works like a charm ;)

:tada: This PR is included in version 5.33.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Plex Widget disappeared

Client tested: Chrome and Safari, Windows11 Laptop and MacBook
Version: 0.11.5
Environment: Docker
Issue: I added the Plex widget successfully. I was exploring the other tiles and came back to the main screen and the plex widget is gone. I scrolled to the bottom of the page and its not there, nor is it listed in the widget section to add again.
Log: This is the only error I see in the logs.
02/26/2023 5:37:00 PM
Error: 'sharp' is required to be installed in standalone mode for the image optimization to function correctly. Read more at: https://nextjs.org/docs/messages/sharp-missing-in-production

@ajnart can you look into this?
@danielmbrown603 would you be able to send us an MVP (minimal reproducible example)? This means, that you would remove all credentials, private information and apps that are not related to Plex. That way, we can reproduce your problem and maybe find what's causing this issue.
It would also be helpful if you could provide more information what you did before it disappeared.
Your widget is most likely not gone in the config.

Here are the steps that I did.

Added plex widget
Saved dashboard
Added new category tile to trial it
Moved an App into the category.
Didn't see a need for the category and deleted it.
After I deleted the category, the plex widget disappeared.

Happy to share any information, configs, screenshots, etc. Just let me know.
Thanks.

That helps a lot. I think your config had faulty position indexes (some issue where positions can decouple from their actual value).
Did you by any chance migrate from 0.10 or ran 0.11.0?

That helps a lot. I think your config had faulty position indexes (some issue where positions can decouple from their actual value). Did you by any chance migrate from 0.10 or ran 0.11.0?

Yes.

Okay, that's most likely the issue.
Can you post the contents of the following sections of your config?

The wrapper section
The category section
The media server widge

Then I can show you how to fix it :)
Make sure to remove all personal information

These the sections? I don't know what the ID is for, so I omitted that. Would it be easier for me to just start over and not come from v.10? It wouldn't take me more than 10mins.
},
"categories": [],
"widgets": [
{
"id": "calendar",
"properties": {
"useSonarrv4": false,
"sundayStart": true
},
"area": {
"type": "wrapper",
"properties": {
"id": "000000000000"
}
},
"shape": {
"lg": {
"location": {
"x": 6,
"y": 0
},
"size": {
"width": 3,
"height": 4
}
},
"md": {
"location": {
"x": 0,
"y": 2
},
"size": {
"width": 2,
"height": 2
}
},
"sm": {
"location": {
"x": 0,
"y": 5
},
"size": {
"width": 2,
"height": 2
}
}
}
},
{
"id": "media-server",
"properties": {},
"area": {
"type": "wrapper",
"properties": {
"id": "000000000"
}
},
"shape": {
"sm": {
"location": {
"x": 0,
"y": 0
},
"size": {
"width": 3,
"height": 2
}
},
"md": {
"location": {
"x": 0,
"y": 0
},
"size": {
"width": 3,
"height": 2
}
},
"lg": {
"location": {
"x": 0,
"y": 1
},
"size": {
"width": 6,
"height": 2
}
}
}
},
{
"id": "dlspeed",
"properties": {},
"area": {
"type": "wrapper",
"properties": {
"id": "0000000000"
}
},
"shape": {
"sm": {
"location": {
"x": 0,
"y": 0
},
"size": {
"width": 2,
"height": 2
}
},
"md": {
"location": {
"x": 0,
"y": 0
},
"size": {
"width": 2,
"height": 2
}
},
"lg": {
"location": {
"x": 0,
"y": 2
},
"size": {
"width": 2,
"height": 2
}
}
}
}
],

Cool! Let me know if you have any other questions or issues. Please close the issue if the issue has been resolved

fixed


Add measurement-kit to the integration tests

This change adds measurement-kit client to the integration test suite. Previously, it was the only client that reported an error from https://github.com/m-lab/ndt-server/issues/160

This change is

Pull Request Test Coverage Report for Build 899

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 74.02%

Totals

Change from base Build 897:
0.0%

Covered Lines:
1416

Relevant Lines:
1913

💛  - Coveralls

m-lab/dev-tracker#401


Fix missing include

It's not possible to compile lib without this include.
Platform: Linux, Qt-5.15

It was already fixed in develop branch. Merged to master