CNI plugin: error getting ClusterInformation: connection is unauthorized: Unauthorized

K8S & Calico information
HostOS: RHEL 8.2
K8S:  on-premise cluster; version is v1.21.1;  "IPVS" mode;  IP4/IP6 dual stack; installed using kubespray
Calico: version is v3.18.4; non-BGP mode;  enabled "IP6" DNAT.
Our docker image is built on top of "RHEL ubi:8"
We do not setup external ETCD cluster.
"kubectl describe" output
[support@node-cont-1-qa conf]$ kubectl describe pod export-job-job-dp8hb
Name:           export-job-job-dp8hb
Namespace:      pio
Priority:       0
Node:           node-df1-1/<IP_ADDRESS>
Start Time:     Wed, 23 Feb 2022 05:57:18 -0800
Labels:         app.kubernetes.io/instance=export-job-job
                controller-uid=5d9f3e4b-e74c-4280-a3be-e31d37e92b84
                job-name=export-job-job
Annotations:    cni.projectcalico.org/podIP:
                cni.projectcalico.org/podIPs:
Status:         Pending
IP:
IPs:            <none>
Controlled By:  Job/export-job-job
Containers:
  export-job-job:
    Container ID:
    Image:         <IP_ADDRESS>:5000/img-admf:<IP_ADDRESS>B038
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      csh
    Args:
      -c
      source /TT9/configXcp.sh; lis_conf; python2 /etc/pio/APPL/XcdbBackup.py --exportdb --dir /var/tmp; sleep 300
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     500m
      memory:  512Mi
    Requests:
      cpu:        200m
      memory:     256Mi
    Environment:  <none>
    Mounts:
      /TT9/PIO/9.0.0/RUN/config/APPL/DBConMgr.cnfg from db-conf (rw,path="DBConMgr.cnfg")
      /TT9/PIO/9.0.0/RUN/config/feature_conf.json from feature-conf (rw,path="feature_conf.json")
      /TT9/PIO/9.0.0/RUN/license/license.json from license-conf (rw,path="license.json")
      /etc/pio/APPL/XcdbBackup.py from job-script (rw,path="XcdbBackup.py")
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-jh7lg (ro)
      /var/tmp from external-pv (rw)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  job-script:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      export-job-script
    Optional:  false
  db-conf:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  db-secret
    Optional:    false
  feature-conf:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      feature
    Optional:  false
  license-conf:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      license
    Optional:  false
  external-pv:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  backup-pvc
    ReadOnly:   false
  kube-api-access-jh7lg:
    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:              <none>
Tolerations:                 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               52m                 default-scheduler  Successfully assigned pio/export-job-job-dp8hb to node-df1-1
  Warning  FailedCreatePodSandBox  52m                 kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "e46d8d9df11ef97e7e1d8b38ced7efef32e1cb4bfb0aa85809cb3198464b6167" network for pod "export-job-job-dp8hb": networkPlugin cni failed to set up pod "export-job-job-dp8hb_pio" network: connection is unauthorized: Unauthorized, failed to clean up sandbox container "e46d8d9df11ef97e7e1d8b38ced7efef32e1cb4bfb0aa85809cb3198464b6167" network for pod "export-job-job-dp8hb": networkPlugin cni failed to teardown pod "export-job-job-dp8hb_pio" network: error getting ClusterInformation: connection is unauthorized: Unauthorized]
  Normal   SandboxChanged          50m (x10 over 52m)  kubelet            Pod sandbox changed, it will be killed and re-created.

Expected Behavior
Should start POD successfully
Steps to Reproduce
Sorry, the issue happened two times on different K8S cluster in our lab. And I did not keep any logs....
Myself want to know to reproduce too.
My initial thought(maybe wrong)
Since "kubectl describe" has "connection is unauthorized", I searched source code of K8S v1.21.1. K8S code does NOT has it. Then search it in Calico v3.22 (I am using V3.18.4, but there is not be big difference), find that "connection is unauthorized" exist in "libcalico-go/lib/erros/errors.go" . So, looks like the issue is caused by Calico.   Then, use "error getting ClusterInformation" as keyword to search in K8S code but cannot find. And search in Calico code, can find it. So, I have confidence to say the issue is 100% related with Calico.
Because "connection is unauthorized" error prompt is related with "type ErrorConnectionUnauthorized struct", and "ErrorConnectionUnauthorized " is related with cooperation with ETCD, looks like that the issue is communication issue between Calico and ETCD.
By the way, /var/log/calico/cni/ does NOT has anything related with "etcd" during POD start/destroy while I did normal operation.
What I expect:
If possible, can you please tell me
1). Which webpage describes control/data flow between Calico and ETCD
2). log files and location that whole Calico uses
3). Did I miss any debug information
Thanks

This looks similar to: https://github.com/projectcalico/calico/issues/4857

In that linked issue, one of the user's reported that they did not see the issue with k8s 1.20 - that might be worth trying.

Thanks for your all for the information.
Cannot replace K8S v1.21 to v1.20.
Will continue to debug and share process with you guys.
Thanks

k8s 1.21 added token cycling and pro-active token withdrawal when pods are deleted.  As far as we can tell, there's something weird about how this interacts with Calico on some systems.
I'm attempting to reproduce, but no luck so far.  Do you have any clues about how to trigger this behaviour?

Not sure how useful my comment would be, but I encountered this error when i accidentally rebooted one of the nodes in the cluster.
The full error is as follows:
error killing pod: failed to "KillPodSandbox" for "%some-guid%" with KillPodSandboxError: "rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \"%some-pod-id%\" network: error getting ClusterInformation: connection is unauthorized: Unauthorized"
The killing was triggered due to disk pressure event being triggered on the node, reasons of which I'm no entirely sure. Lowered imageGC thresholds a bit before, but from my understanding they shouldn't trigger disk pressure. Maybe I'm wrong.
ps: I also recall a similar situation with an api that constnatly got evicted every couple of days (disk pressure) and it's evicted pods were never cleaned up. Didn't really look up into why the pods remained, but maybe they also were supposed to be cleaned up, but never did.

@earthlovepython: this may sound silly, but could you try to restart kubelet.
Had a little bit of fun today with it.. Spend hours of upgrading from different k8s and Calico versions, in order to reproduce the issue on a second cluster, led my nowhere. I then tried to activate debug logging and restarted kubelet and suddenly all pods (in my case calico-kube-controller and coredns) just became ready...
Luckily I had a snapshot of all VMs of the "broken" cluster, so I could verify that, and I can confirm it works like a charm.
I guess networkPlugin cni failed to teardown pod combined with the kubelet log message like "Error deleting pod from network" means, that some kind of cleanup/garbage collection needs to run.
Restarting kubelet seems to trigger this.

Found a way to reproduce this issue, at least on a "Calico the hard way" setup (haven't tested it with regular deployments):
kill all calico (kube-controller, typha, node) and coredns pods.
After this the cni logs also print these messages:
2022-05-16 13:05:37.905 [DEBUG][104919] client.go 30: Using datastore type 'kubernetes'
2022-05-16 13:05:37.906 [DEBUG][104919] k8s.go 210: Calico is configured to use calico-ipam
2022-05-16 13:05:37.906 [DEBUG][104919] k8s.go 628: Performing 'Get' for ClusterInformation(default)
2022-05-16 13:05:37.906 [DEBUG][104919] customresource.go 205: Get custom Kubernetes resource Key=ClusterInformation(default) Resource="ClusterInformations" Revision=""
2022-05-16 13:05:37.906 [DEBUG][104919] customresource.go 216: Get custom Kubernetes resource by name Key=ClusterInformation(default) Name="default" Namespace="" Resource="ClusterInformations" Revision=""
2022-05-16 13:05:37.912 [DEBUG][104919] customresource.go 224: Error getting resource Key=ClusterInformation(default) Name="default" Namespace="" Resource="ClusterInformations" Revision="" error=Unauthorized
2022-05-16 13:05:37.912 [ERROR][104919] plugin.go 518: Final result of CNI DEL was an error. error=error getting ClusterInformation: connection is unauthorized: Unauthorized

Restarting kubelet afterwards again, solves the issue again.
Running: k8s 1.21.15 / 1.22.9 and calico 3.21.5

When do you plan on releasing 3.23.2 ?
We have this error that's preventing from performing a rolling update to the cluster

Encountering the same issue, how to solve it?

I installed the latest version of Calico, and kubernetes is 1.24.2

@winkee01 I'd recommend opening a new issue and filing it out with the exact version of Calico as well as other platform and environment information as requested by the issue template.

hit the same issue, and lbogdan's workaround fixed it for me.

in our case, it was the cert expired.
we did cluster cert renewal by kubeadm and then restarted all the calico nodes, problem solved.

Same issue in 1.22 with Calico
Events:
Type     Reason                  Age                  From               Message

Normal   Scheduled               3m47s                default-scheduler  Successfully assigned default/pod-with-cm to worker-node01
Warning  FailedCreatePodSandBox  3m46s                kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "3dcfdb21462e255a8f4059ca8540c8df05863bd6444cb22290133f894840845e" network for pod "pod-with-cm": networkPlugin cni failed to set up pod "pod-with-cm_default" network: error getting ClusterInformation: connection is unauthorized: Unauthorized, failed to clean up sandbox container "3dcfdb21462e255a8f4059ca8540c8df05863bd6444cb22290133f894840845e" network for pod "pod-with-cm": networkPlugin cni failed to teardown pod "pod-with-cm_default" network: error getting ClusterInformation: connection is unauthorized: Unauthorized]

v3.23.2
root@bpf1:~/wspace/wcni/calico/2-calico-vxlan# kk describe pods calico-kube-controllers-c55c48989-z4kbt
Name:                      calico-kube-controllers-c55c48989-z4kbt
Namespace:                 kube-system
Priority:<PHONE_NUMBER>
Priority Class Name:       system-cluster-critical
Node:                      bpf1/<IP_ADDRESS>
Start Time:                Sun, 13 Nov 2022 13:14:26 +0800
Labels:                    k8s-app=calico-kube-controllers
                           pod-template-hash=c55c48989
Annotations:               cni.projectcalico.org/containerID: 0020fe737e31e0082d371b9707d9831cbe9ad72f00c0d9b33fb0e745a8d5b439
                           cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                           cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
Status:                    Terminating (lasts 3m51s)
Termination Grace Period:  30s
IP:                        <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/calico-kube-controllers-c55c48989
Containers:
  calico-kube-controllers:
    Container ID:   docker://e9770e244d60bbc2301e2dc5da478c85b80273f6cbe100b5ee4522b8b738ac48
    Image:          <IP_ADDRESS>:5000/calico/kube-controllers:v3.23.2
    Image ID:       docker-pullable://<IP_ADDRESS>:5000/calico/kube-controllers@sha256:57c40fdfb86dce269a8f93b4f5545b23b7ee9ba36d62e67e7ce367df8d753887
    Port:           <none>
    Host Port:      <none>
    State:          Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Sun, 13 Nov 2022 13:14:31 +0800
      Finished:     Sun, 13 Nov 2022 14:53:05 +0800
    Ready:          False
    Restart Count:  0
    Liveness:       exec [/usr/bin/check-status -l] delay=10s timeout=10s period=10s #success=1 #failure=6
    Readiness:      exec [/usr/bin/check-status -r] delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      ENABLED_CONTROLLERS:  node
      DATASTORE_TYPE:       kubernetes
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-dsmrc (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kube-api-access-dsmrc:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
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   Killing        4m21s                kubelet  Stopping container calico-kube-controllers
  Warning  FailedKillPod  4s (x24 over 4m20s)  kubelet  error killing pod: failed to "KillPodSandbox" for "02a4f270-45e4-4bd7-805d-dfe99763ea66" with KillPodSandboxError: "rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \"calico-kube-controllers-c55c48989-z4kbt_kube-system\" network: error getting ClusterInformation: connection is unauthorized: Unauthorized"
root@bpf1:~/wspace/wcni/calico/2-calico-vxlan#

Same issue in 1.22 with Calico
Events: Type Reason Age From Message
Normal Scheduled 3m47s default-scheduler Successfully assigned default/pod-with-cm to worker-node01 Warning FailedCreatePodSandBox 3m46s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "3dcfdb21462e255a8f4059ca8540c8df05863bd6444cb22290133f894840845e" network for pod "pod-with-cm": networkPlugin cni failed to set up pod "pod-with-cm_default" network: error getting ClusterInformation: connection is unauthorized: Unauthorized, failed to clean up sandbox container "3dcfdb21462e255a8f4059ca8540c8df05863bd6444cb22290133f894840845e" network for pod "pod-with-cm": networkPlugin cni failed to teardown pod "pod-with-cm_default" network: error getting ClusterInformation: connection is unauthorized: Unauthorized]

did you fix this

This just happened to me in an older v1.22.3 cluster, and I've noticed that the calico-node pods had an age of 365d. The problem self-resolved after I deleted all calico-node pods and they were recreated. Is there a certificate / token that has a TTL of 1 year and doesn't get automatically renewed?

I had slightly different issue, but restarting calico pod and then my failed pod helped. MicroK8s v1.26.0 revision 4390, Calico v3.23.5

Hi,
Restarting the calico pods are not working for me. I am on v1.24.6 kubespray

networkPlugin cni failed to teardown po

I did restart, NetworkManager, Containerd & Kubelet. Still the problem remains.

hi @vyom-soft, Is the configuration of autodetect interface in your calico correct? if calico was not able to identify the Ethernet card property, for example, it was configured to detect the eth but on machine it was configured as ens so placing the regex helps it to identify the ethernet card and associated ip properly.
https://www.unixcloudfusion.in/2022/02/solved-caliconode-is-not-ready-bird-is.html

I just had to kubectl delete pod calico-node-xxxx on the node where the issue was happening. A new Pod was created and the problem is solved.

kubectl delete pods --all --all-namespaces fixed my issue
I had a similar issue today and all the pods on my cluster were stuck in Unknown or Terminating status, including the calico-node-xxxx.
I ran kubectl delete pod calico-node-xxxx which fixed the calico-node pod, but the other pods were still not ok, so I ran kubectl delete pods --all --all-namespaces to delete ALL the pods and a couple of minutes after the command everything was back up and running well!

@davidassigbi 's solution worked for me.  Was using Microk8s, guess something weird with calico-node-xxxx haven't noticed the issue return.

Sorry, I'm still a learner. But kubectl delete -f calico.yaml  seems better.
I learned it from StackOverFlow.

NO! Do not do this unless you want to completely remove Calico and trash your cluster; it will delete Calico's IP address database.

Sorry, I'm still a learner. But kubectl delete -f calico.yaml  seems better.
I learned it from StackOverFlow.

我修改了master 和node的时间，然后出现了相同的报错Jan 25 11:34:46 test-node01 kubelet: E0125 11:34:46.938130   56745 remote_runtime.go:269] "StopPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to destroy network for sandbox "969d9ca8a8fef61b41ed6810db45e3d5765e85a62f080ae9135a1d61cf508417": plugin type="calico" failed (delete): error getting ClusterInformation: connection is unauthorized: Unauthorized" podSandboxID="969d9ca8a8fef61b41ed6810db45e3d5765e85a62f080ae9135a1d61cf508417"
我删除了calico后重新安装calico  一切恢复了正常

我修改了master 和node的时间，然后出现了相同的报错Jan 25 11:34:46 test-node01 kubelet: E0125 11:34:46.938130 56745 remote_runtime.go:269] "StopPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to destroy network for sandbox "969d9ca8a8fef61b41ed6810db45e3d5765e85a62f080ae9135a1d61cf508417": plugin type="calico" failed (delete): error getting ClusterInformation: connection is unauthorized: Unauthorized" podSandboxID="969d9ca8a8fef61b41ed6810db45e3d5765e85a62f080ae9135a1d61cf508417" 我删除了calico后重新安装calico 一切恢复了正常

I have the same problem on windows node.

This just happened to me in an older v1.22.3 cluster, and I've noticed that the calico-node pods had an age of 365d. The problem self-resolved after I deleted all calico-node pods and they were recreated. Is there a certificate / token that has a TTL of 1 year and doesn't get automatically renewed?

It Works!

clusterVersion: v1.23
Not sure how useful my comment would be, but I encountered this error when i accidentally rebooted one of the nodes in the cluster. The full error is as follows: error killing pod: failed to "KillPodSandbox" for "%some-guid%" with KillPodSandboxError: "rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod \"%some-pod-id%\" network: error getting ClusterInformation: connection is unauthorized: Unauthorized"
The killing was triggered due to disk pressure event being triggered on the node, reasons of which I'm no entirely sure. Lowered imageGC thresholds a bit before, but from my understanding they shouldn't trigger disk pressure. Maybe I'm wrong.
ps: I also recall a similar situation with an api that constnatly got evicted every couple of days (disk pressure) and it's evicted pods were never cleaned up. Didn't really look up into why the pods remained, but maybe they also were supposed to be cleaned up, but never did because of this error.

it's useful for me!!! I got the same mistake, and I reboot the machine, than it's recovered.

I met issue again. It was first seen earlier this month. Resolved by rebooting the nodes because they are just my test env on VMware.  I paused VMs during nights.
Unfortunately, issue occurred again today when I add a volume mounts. It stuck at terminating state. I dumped some logs if anyone were interested in it.
  Warning  FailedKillPod  2m16s (x25 over 7m10s)  kubelet  error killing pod: failed to "KillPodSandbox" for "a431db4f-976a-468c-9b30-083cae3f4a1a" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to destroy network for sandbox \"aad27fa53c53747a4565e60dab22133157199656d297699d297c86dc50f85560\": plugin type=\"calico\" failed (delete): error getting ClusterInformation: connection is unauthorized: Unauthorized"

[root@master1 prom]$ k get pods | grep prom
prometheus-adapter-6c4cc5465b-q6mnd    1/1     Running       0          32h
prometheus-adapter-6c4cc5465b-z76x4    1/1     Running       0          32h
prometheus-k8s-0                       2/2     Running       0          31h
prometheus-k8s-1                       0/2     Terminating   0          31h
prometheus-operator-57cf88fbcb-wt8x9   2/2     Running       0          32h

k describe pod prometheus-k8s-1
[root@master1 prom]$ k describe pod prometheus-k8s-1
Name:                      prometheus-k8s-1
Namespace:                 monitoring
Priority:                  0
Service Account:           prometheus-k8s
Node:                      node1/<IP_ADDRESS>
Start Time:                Mon, 23 Sep 2024 15:44:09 +0800
Labels:                    app.kubernetes.io/component=prometheus
                           app.kubernetes.io/instance=k8s
                           app.kubernetes.io/managed-by=prometheus-operator
                           app.kubernetes.io/name=prometheus
                           app.kubernetes.io/part-of=kube-prometheus
                           app.kubernetes.io/version=2.46.0
                           controller-revision-hash=prometheus-k8s-7c7bdb6c6d
                           operator.prometheus.io/name=k8s
                           operator.prometheus.io/shard=0
                           prometheus=k8s
                           statefulset.kubernetes.io/pod-name=prometheus-k8s-1
Annotations:               cni.projectcalico.org/containerID: aad27fa53c53747a4565e60dab22133157199656d297699d297c86dc50f85560
                           cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                           cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
                           kubectl.kubernetes.io/default-container: prometheus
Status:                    Terminating (lasts 42m)
Termination Grace Period:  600s
IP:                        <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  StatefulSet/prometheus-k8s
Init Containers:
  init-config-reloader:
    Container ID:  containerd://270f4290bb379004cf2760024c939d29884265a8fcf1a0de9e5d6dab5aaa2553
    Image:         quay.io/prometheus-operator/prometheus-config-reloader:v0.67.1
    Image ID:      quay.io/prometheus-operator/prometheus-config-reloader@sha256:0fe3cf36985e0e524801a0393f88fa4b5dd5ffdf0f091ff78ee02f2d281631b5
    Port:          8080/TCP
    Host Port:     0/TCP
    Command:
      /bin/prometheus-config-reloader
    Args:
      --watch-interval=0
      --listen-address=:8080
      --config-file=/etc/prometheus/config/prometheus.yaml.gz
      --config-envsubst-file=/etc/prometheus/config_out/prometheus.env.yaml
      --watched-dir=/etc/prometheus/rules/prometheus-k8s-rulefiles-0
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Mon, 23 Sep 2024 15:44:14 +0800
      Finished:     Mon, 23 Sep 2024 15:44:39 +0800
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     10m
      memory:  50Mi
    Requests:
      cpu:     10m
      memory:  50Mi
    Environment:
      POD_NAME:  prometheus-k8s-1 (v1:metadata.name)
      SHARD:     0
    Mounts:
      /etc/prometheus/config from config (rw)
      /etc/prometheus/config_out from config-out (rw)
      /etc/prometheus/rules/prometheus-k8s-rulefiles-0 from prometheus-k8s-rulefiles-0 (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5fpsk (ro)
Containers:
  prometheus:
    Container ID:  containerd://c7c473c643ba6694af8f025e916893ba6be98c90bb5177e3d0a87f454bdf8eff
    Image:         quay.io/prometheus/prometheus:v2.46.0
    Image ID:      quay.io/prometheus/prometheus@sha256:d6ead9daf2355b9923479e24d7e93f246253ee6a5eb18a61b0f607219f341a80
    Port:          9090/TCP
    Host Port:     0/TCP
    Args:
      --web.console.templates=/etc/prometheus/consoles
      --web.console.libraries=/etc/prometheus/console_libraries
      --config.file=/etc/prometheus/config_out/prometheus.env.yaml
      --web.enable-lifecycle
      --web.route-prefix=/
      --storage.tsdb.retention.time=24h
      --storage.tsdb.path=/prometheus
      --web.config.file=/etc/prometheus/web_config/web-config.yaml
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Mon, 23 Sep 2024 15:44:41 +0800
      Finished:     Tue, 24 Sep 2024 21:55:16 +0800
    Ready:          False
    Restart Count:  0
    Requests:
      memory:     400Mi
    Liveness:     http-get http://:web/-/healthy delay=0s timeout=3s period=5s #success=1 #failure=6
    Readiness:    http-get http://:web/-/ready delay=0s timeout=3s period=5s #success=1 #failure=3
    Startup:      http-get http://:web/-/ready delay=0s timeout=3s period=15s #success=1 #failure=60
    Environment:  <none>
    Mounts:
      /etc/prometheus/certs from tls-assets (ro)
      /etc/prometheus/config_out from config-out (ro)
      /etc/prometheus/rules/prometheus-k8s-rulefiles-0 from prometheus-k8s-rulefiles-0 (rw)
      /etc/prometheus/secrets/etcd-healthcheck-certs from etcd-healthcheck-certs (rw)
      /etc/prometheus/web_config/web-config.yaml from web-config (ro,path="web-config.yaml")
      /prometheus from prometheus-k8s-db (rw,path="prometheus-db")
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5fpsk (ro)
  config-reloader:
    Container ID:  containerd://12228eb60a98c74333db746c34649cbc6e48de7a8555284305cc83ad5ab150e2
    Image:         quay.io/prometheus-operator/prometheus-config-reloader:v0.67.1
    Image ID:      quay.io/prometheus-operator/prometheus-config-reloader@sha256:0fe3cf36985e0e524801a0393f88fa4b5dd5ffdf0f091ff78ee02f2d281631b5
    Port:          8080/TCP
    Host Port:     0/TCP
    Command:
      /bin/prometheus-config-reloader
    Args:
      --listen-address=:8080
      --reload-url=http://localhost:9090/-/reload
      --config-file=/etc/prometheus/config/prometheus.yaml.gz
      --config-envsubst-file=/etc/prometheus/config_out/prometheus.env.yaml
      --watched-dir=/etc/prometheus/rules/prometheus-k8s-rulefiles-0
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Mon, 23 Sep 2024 15:44:43 +0800
      Finished:     Tue, 24 Sep 2024 21:55:20 +0800
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     10m
      memory:  50Mi
    Requests:
      cpu:     10m
      memory:  50Mi
    Environment:
      POD_NAME:  prometheus-k8s-1 (v1:metadata.name)
      SHARD:     0
    Mounts:
      /etc/prometheus/config from config (rw)
      /etc/prometheus/config_out from config-out (rw)
      /etc/prometheus/rules/prometheus-k8s-rulefiles-0 from prometheus-k8s-rulefiles-0 (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-5fpsk (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  prometheus-k8s-db:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  prometheus-k8s-db-prometheus-k8s-1
    ReadOnly:   false
  config:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  prometheus-k8s
    Optional:    false
  tls-assets:
    Type:                Projected (a volume that contains injected data from multiple sources)
    SecretName:          prometheus-k8s-tls-assets-0
    SecretOptionalName:  <nil>
  config-out:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     Memory
    SizeLimit:  <unset>
  prometheus-k8s-rulefiles-0:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      prometheus-k8s-rulefiles-0
    Optional:  false
  web-config:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  prometheus-k8s-web-config
    Optional:    false
  etcd-healthcheck-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  etcd-healthcheck-certs
    Optional:    false
  kube-api-access-5fpsk:
    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:                 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   Killing        52m                   kubelet  Stopping container prometheus
  Normal   Killing        52m                   kubelet  Stopping container config-reloader
  Warning  Unhealthy      51m (x2 over 52m)     kubelet  Readiness probe failed: Get "http://<IP_ADDRESS>:9090/-/ready": dial tcp <IP_ADDRESS>:9090: connect: connection refused
  Warning  FailedKillPod  115s (x231 over 51m)  kubelet  error killing pod: failed to "KillPodSandbox" for "a431db4f-976a-468c-9b30-083cae3f4a1a" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to destroy network for sandbox \"aad27fa53c53747a4565e60dab22133157199656d297699d297c86dc50f85560\": plugin type=\"calico\" failed (delete): error getting ClusterInformation: connection is unauthorized: Unauthorized"

Your Environment
Calico version: 3.28.0
Orchestrator version: kubernetes v1.26.15
Operating System and version: Rockey 9.4
[root@master3 ~]$ k get pods -n kube-system -owide | grep calico
calico-kube-controllers-599ff45f46-htxqq           1/1     Running   12 (2d4h ago)    61d    <IP_ADDRESS>    master3   <none>           <none>
calico-node-4694r                                  1/1     Running   11 (2d5h ago)    61d    <IP_ADDRESS>   master3   <none>           <none>
calico-node-58wxz                                  1/1     Running   17 (2d5h ago)    61d    <IP_ADDRESS>   node1     <none>           <none>
calico-node-k7vh6                                  1/1     Running   35 (2d5h ago)    61d    <IP_ADDRESS>   node2     <none>           <none>
calico-node-nfzc9                                  1/1     Running   11 (2d5h ago)    61d    <IP_ADDRESS>   master1   <none>           <none>
calico-node-rtj6c                                  1/1     Running   14 (2d3h ago)    61d    <IP_ADDRESS>   master2   <none>           <none>

calico node yaml:
[root@master2 ~]$ k -n kube-system get pods calico-node-58wxz  -oyaml
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: "2024-07-25T11:09:44Z"
  generateName: calico-node-
  labels:
    controller-revision-hash: dd6b874b5
    k8s-app: calico-node
    pod-template-generation: "1"
  name: calico-node-58wxz
  namespace: kube-system
  ownerReferences:
  - apiVersion: apps/v1
    blockOwnerDeletion: true
    controller: true
    kind: DaemonSet
    name: calico-node
    uid: 7071a2a6-f396-4b8f-ac47-44d94c8887ad
  resourceVersion: "3471983"
  uid: 6c9030e0-2700-4ee4-8653-abff4bd180b6
spec:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchFields:
          - key: metadata.name
            operator: In
            values:
            - node1
  containers:
  - env:
    - name: DATASTORE_TYPE
      value: kubernetes
    - name: WAIT_FOR_DATASTORE
      value: "true"
    - name: NODENAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: spec.nodeName
    - name: CALICO_NETWORKING_BACKEND
      valueFrom:
        configMapKeyRef:
          key: calico_backend
          name: calico-config
    - name: CLUSTER_TYPE
      value: k8s,bgp
    - name: IP
      value: autodetect
    - name: CALICO_IPV4POOL_IPIP
      value: Always
    - name: CALICO_IPV4POOL_VXLAN
      value: Never
    - name: CALICO_IPV6POOL_VXLAN
      value: Never
    - name: FELIX_IPINIPMTU
      valueFrom:
        configMapKeyRef:
          key: veth_mtu
          name: calico-config
    - name: FELIX_VXLANMTU
      valueFrom:
        configMapKeyRef:
          key: veth_mtu
          name: calico-config
    - name: FELIX_WIREGUARDMTU
      valueFrom:
        configMapKeyRef:
          key: veth_mtu
          name: calico-config
    - name: CALICO_IPV4POOL_CIDR
      value: <IP_ADDRESS>/16
    - name: CALICO_DISABLE_FILE_LOGGING
      value: "true"
    - name: FELIX_DEFAULTENDPOINTTOHOSTACTION
      value: ACCEPT
    - name: FELIX_IPV6SUPPORT
      value: "false"
    - name: FELIX_HEALTHENABLED
      value: "true"
    envFrom:
    - configMapRef:
        name: kubernetes-services-endpoint
        optional: true
    image: docker.io/calico/node:v3.28.0
    imagePullPolicy: IfNotPresent
    lifecycle:
      preStop:
        exec:
          command:
          - /bin/calico-node
          - -shutdown
    livenessProbe:
      exec:
        command:
        - /bin/calico-node
        - -felix-live
        - -bird-live
      failureThreshold: 6
      initialDelaySeconds: 10
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 10
    name: calico-node
    readinessProbe:
      exec:
        command:
        - /bin/calico-node
        - -felix-ready
        - -bird-ready
      failureThreshold: 3
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 10
    resources:
      requests:
        cpu: 250m
    securityContext:
      privileged: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /host/etc/cni/net.d
      name: cni-net-dir
    - mountPath: /lib/modules
      name: lib-modules
      readOnly: true
    - mountPath: /run/xtables.lock
      name: xtables-lock
    - mountPath: /var/run/calico
      name: var-run-calico
    - mountPath: /var/lib/calico
      name: var-lib-calico
    - mountPath: /var/run/nodeagent
      name: policysync
    - mountPath: /sys/fs/bpf
      name: bpffs
    - mountPath: /var/log/calico/cni
      name: cni-log-dir
      readOnly: true
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-w28qx
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  hostNetwork: true
  initContainers:
  - command:
    - /opt/cni/bin/calico-ipam
    - -upgrade
    env:
    - name: KUBERNETES_NODE_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: spec.nodeName
    - name: CALICO_NETWORKING_BACKEND
      valueFrom:
        configMapKeyRef:
          key: calico_backend
          name: calico-config
    envFrom:
    - configMapRef:
        name: kubernetes-services-endpoint
        optional: true
    image: docker.io/calico/cni:v3.28.0
    imagePullPolicy: IfNotPresent
    name: upgrade-ipam
    resources: {}
    securityContext:
      privileged: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/lib/cni/networks
      name: host-local-net-dir
    - mountPath: /host/opt/cni/bin
      name: cni-bin-dir
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-w28qx
      readOnly: true
  - command:
    - /opt/cni/bin/install
    env:
    - name: CNI_CONF_NAME
      value: 10-calico.conflist
    - name: CNI_NETWORK_CONFIG
      valueFrom:
        configMapKeyRef:
          key: cni_network_config
          name: calico-config
    - name: KUBERNETES_NODE_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: spec.nodeName
    - name: CNI_MTU
      valueFrom:
        configMapKeyRef:
          key: veth_mtu
          name: calico-config
    - name: SLEEP
      value: "false"
    envFrom:
    - configMapRef:
        name: kubernetes-services-endpoint
        optional: true
    image: docker.io/calico/cni:v3.28.0
    imagePullPolicy: IfNotPresent
    name: install-cni
    resources: {}
    securityContext:
      privileged: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /host/opt/cni/bin
      name: cni-bin-dir
    - mountPath: /host/etc/cni/net.d
      name: cni-net-dir
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-w28qx
      readOnly: true
  - command:
    - calico-node
    - -init
    - -best-effort
    image: docker.io/calico/node:v3.28.0
    imagePullPolicy: IfNotPresent
    name: mount-bpffs
    resources: {}
    securityContext:
      privileged: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /sys/fs
      mountPropagation: Bidirectional
      name: sys-fs
    - mountPath: /var/run/calico
      mountPropagation: Bidirectional
      name: var-run-calico
    - mountPath: /nodeproc
      name: nodeproc
      readOnly: true
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-w28qx
      readOnly: true
  nodeName: node1
  nodeSelector:
    kubernetes.io/os: linux
  preemptionPolicy: PreemptLowerPriority
  priority:<PHONE_NUMBER>
  priorityClassName: system-node-critical
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: calico-node
  serviceAccountName: calico-node
  terminationGracePeriodSeconds: 0
  tolerations:
  - effect: NoSchedule
    operator: Exists
  - key: CriticalAddonsOnly
    operator: Exists
  - effect: NoExecute
    operator: Exists
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/disk-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/memory-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/pid-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/unschedulable
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/network-unavailable
    operator: Exists
  volumes:
  - hostPath:
      path: /lib/modules
      type: ""
    name: lib-modules
  - hostPath:
      path: /var/run/calico
      type: ""
    name: var-run-calico
  - hostPath:
      path: /var/lib/calico
      type: ""
    name: var-lib-calico
  - hostPath:
      path: /run/xtables.lock
      type: FileOrCreate
    name: xtables-lock
  - hostPath:
      path: /sys/fs/
      type: DirectoryOrCreate
    name: sys-fs
  - hostPath:
      path: /sys/fs/bpf
      type: Directory
    name: bpffs
  - hostPath:
      path: /proc
      type: ""
    name: nodeproc
  - hostPath:
      path: /opt/cni/bin
      type: ""
    name: cni-bin-dir
  - hostPath:
      path: /etc/cni/net.d
      type: ""
    name: cni-net-dir
  - hostPath:
      path: /var/log/calico/cni
      type: ""
    name: cni-log-dir
  - hostPath:
      path: /var/lib/cni/networks
      type: ""
    name: host-local-net-dir
  - hostPath:
      path: /var/run/nodeagent
      type: DirectoryOrCreate
    name: policysync
  - name: kube-api-access-w28qx
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          items:
          - key: ca.crt
            path: ca.crt
          name: kube-root-ca.crt
      - downwardAPI:
          items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
            path: namespace
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2024-09-22T09:21:10Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2024-09-22T09:23:01Z"
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2024-09-22T09:23:01Z"
    status: "True"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2024-07-25T11:09:44Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: containerd://e1fe61157237d46f9004e57ae53a97b2801ce1d421121fa15d67e1b2e1a94f93
    image: docker.io/calico/node:v3.28.0
    imageID: docker.io/calico/node@sha256:385bf6391fea031649b8575799248762a2caece86e6e3f33ffee19c0c096e6a8
    lastState:
      terminated:
        containerID: containerd://b3519095fa4d62c6c29b3309228a9b23e051a6357151815e72c5744600de0450
        exitCode: 0
        finishedAt: "2024-09-22T09:22:19Z"
        reason: Completed
        startedAt: "2024-09-22T09:21:12Z"
    name: calico-node
    ready: true
    restartCount: 17
    started: true
    state:
      running:
        startedAt: "2024-09-22T09:22:21Z"
  hostIP: <IP_ADDRESS>
  initContainerStatuses:
  - containerID: containerd://be9ffd822b13ae25f060c7364d2f6694aaee1e517801573692a655e377fa3bc6
    image: docker.io/calico/cni:v3.28.0
    imageID: docker.io/calico/cni@sha256:cef0c907b8f4cadc63701d371e6f24d325795bcf0be84d6a517e33000ff35f70
    lastState: {}
    name: upgrade-ipam
    ready: true
    restartCount: 2
    state:
      terminated:
        containerID: containerd://be9ffd822b13ae25f060c7364d2f6694aaee1e517801573692a655e377fa3bc6
        exitCode: 0
        finishedAt: "2024-09-22T09:20:36Z"
        reason: Completed
        startedAt: "2024-09-22T09:20:33Z"
  - containerID: containerd://142f1a60440b3e9d1ef85ac2d6645b8386c04039323197ca17885edf77323989
    image: docker.io/calico/cni:v3.28.0
    imageID: docker.io/calico/cni@sha256:cef0c907b8f4cadc63701d371e6f24d325795bcf0be84d6a517e33000ff35f70
    lastState: {}
    name: install-cni
    ready: true
    restartCount: 0
    state:
      terminated:
        containerID: containerd://142f1a60440b3e9d1ef85ac2d6645b8386c04039323197ca17885edf77323989
        exitCode: 0
        finishedAt: "2024-09-22T09:20:53Z"
        reason: Completed
        startedAt: "2024-09-22T09:20:39Z"
  - containerID: containerd://39f0adc5c3f9c99866311258226905cffc9c6e8990ab21cfbe4c9cb7e74bcc72
    image: docker.io/calico/node:v3.28.0
    imageID: docker.io/calico/node@sha256:385bf6391fea031649b8575799248762a2caece86e6e3f33ffee19c0c096e6a8
    lastState: {}
    name: mount-bpffs
    ready: true
    restartCount: 0
    state:
      terminated:
        containerID: containerd://39f0adc5c3f9c99866311258226905cffc9c6e8990ab21cfbe4c9cb7e74bcc72
        exitCode: 0
        finishedAt: "2024-09-22T09:21:05Z"
        reason: Completed
        startedAt: "2024-09-22T09:20:59Z"
  phase: Running
  podIP: <IP_ADDRESS>
  podIPs:
  - ip: <IP_ADDRESS>
  qosClass: Burstable
  startTime: "2024-07-25T11:09:45Z"

journalctl --unit containerd --no-pager >containerd-unauthorized.log
containerd-unauthorized.log
k -n kube-system  logs calico-node-58wxz > calico-node-node1-logs.log
calico-node-node1-logs.log

rebooting solved my issue (my nodes are for testing and control plan was shut down for some days around holidays).


Cant flash Tuya TC-US

Hello I'm flashing Tuya TC-US 2 gang and it stopped here
here is my logs
smarthack-mqtt

1560774309: mosquitto version 1.4.10 (build date Wed, 13 Feb 2019 00:45:38 +0000) starting
1560774309: Using default config.
1560774309: Opening ipv4 listen socket on port 1883.
1560774309: Opening ipv6 listen socket on port 1883.
^C1560775106: mosquitto version 1.4.10 terminating
1560775116: mosquitto version 1.4.10 (build date Wed, 13 Feb 2019 00:45:38 +0000) starting
1560775116: Using default config.
1560775116: Opening ipv4 listen socket on port 1883.
1560775116: Opening ipv6 listen socket on port 1883.
^C1560775316: mosquitto version 1.4.10 terminating
1560775321: mosquitto version 1.4.10 (build date Wed, 13 Feb 2019 00:45:38 +0000) starting
1560775321: Using default config.
1560775321: Opening ipv4 listen socket on port 1883.
1560775321: Opening ipv6 listen socket on port 1883.
^C1560776097: mosquitto version 1.4.10 terminating
1560776102: mosquitto version 1.4.10 (build date Wed, 13 Feb 2019 00:45:38 +0000) starting
1560776102: Using default config.
1560776102: Opening ipv4 listen socket on port 1883.
1560776102: Opening ipv6 listen socket on port 1883.
^C1560776607: mosquitto version 1.4.10 terminating
1560776611: mosquitto version 1.4.10 (build date Wed, 13 Feb 2019 00:45:38 +0000) starting
1560776611: Using default config.
1560776611: Opening ipv4 listen socket on port 1883.
1560776611: Opening ipv6 listen socket on port 1883.

smarthack-smartconfig

Put` Device in Learn Mode! Sending SmartConfig Packets now
Sending SSID                  vtrust-flash
Sending wifiPassword          flashmeifyoucan
SmartConfig in progress
..........
SmartConfig complete.
Put Device in Learn Mode! Sending SmartConfig Packets now
Sending SSID                  vtrust-flash
Sending wifiPassword          flashmeifyoucan
SmartConfig in progress
..........
SmartConfig complete.
Put Device in Learn Mode! Sending SmartConfig Packets now
Sending SSID                  vtrust-flash
Sending wifiPassword          flashmeifyoucan
SmartConfig in progress
..........
SmartConfig complete.
Put Device in Learn Mode! Sending SmartConfig Packets now
Sending SSID                  vtrust-flash
Sending wifiPassword          flashmeifyoucan
SmartConfig in progress
..........
SmartConfig complete.
Put Device in Learn Mode! Sending SmartConfig Packets now
Sending SSID                  vtrust-flash
Sending wifiPassword          flashmeifyoucan
SmartConfig in progress
..........
SmartConfig complete.

smarthack-web

Traceback` (most recent call last):
File "./fake-registration-server.py", line 9, in
import tornado.web
ImportError: No module named 'tornado'
Traceback (most recent call last):
File "./fake-registration-server.py", line 9, in
import tornado.web
ImportError: No module named 'tornado'
Traceback (most recent call last):
File "./fake-registration-server.py", line 9, in
import tornado.web
ImportError: No module named 'tornado'
Traceback (most recent call last):
File "./fake-registration-server.py", line 9, in
import tornado.web
ImportError: No module named 'tornado'
Traceback (most recent call last):
File "./fake-registration-server.py", line 9, in
import tornado.web
ImportError: No module named 'tornado'

smarthack-wifi

Backing up NetworkManager.cfg...
Restarting NetworkManager...
Backing up /etc/dnsmasq.conf...
Writing dnsmasq config file...
Creating new /etc/dnsmasq.conf...
Writing hostapd config file...
Configuring AP interface...
Applying iptables rules...
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Starting DNSMASQ server...
Starting AP on wlan0 in screen terminal...
Configuration file: /etc/hostapd/hostapd.conf
Failed to create interface mon.wlan0: -95 (Operation not supported)
wlan0: Could not connect to kernel driver
Using interface wlan0 with hwaddr b8:27:eb:da:ef:de and ssid "vtrust-flash"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 40:9c:28:a9:8f:92
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 40:9c:28:a9:8f:92
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 40:9c:28:a9:8f:92
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 RADIUS: starting accounting session 7F3045D3FE0F6A98
wlan0: STA 40:9c:28:a9:8f:92 WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: associated
wlan0: AP-STA-CONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d RADIUS: starting accounting session 8D6AD5D75645954A
wlan0: STA bc:dd:c2:28:ea:6d WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d WPA: group key handshake completed (RSN)
wlan0: STA 40:9c:28:a9:8f:92 WPA: group key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
^Cwlan0: interface state ENABLED->DISABLED
wlan0: AP-STA-DISCONNECTED 40:9c:28:a9:8f:92
wlan0: AP-DISABLED
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Backing up NetworkManager.cfg...
Restarting NetworkManager...
Backing up /etc/dnsmasq.conf...
Writing dnsmasq config file...
Creating new /etc/dnsmasq.conf...
Writing hostapd config file...
Configuring AP interface...
Applying iptables rules...
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Starting DNSMASQ server...
RTNETLINK answers: File exists
Starting AP on wlan0 in screen terminal...
Configuration file: /etc/hostapd/hostapd.conf
Failed to create interface mon.wlan0: -95 (Operation not supported)
wlan0: Could not connect to kernel driver
Using interface wlan0 with hwaddr b8:27:eb:da:ef:de and ssid "vtrust-flash"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 RADIUS: starting accounting session 7C66215AFD4A65DF
wlan0: STA 40:9c:28:a9:8f:92 WPA: pairwise key handshake completed (RSN)
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 RADIUS: starting accounting session A0E21539A5DD3C57
wlan0: STA 40:9c:28:a9:8f:92 WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: associated
wlan0: AP-STA-CONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d RADIUS: starting accounting session 5A68F75F2A5BBD9B
wlan0: STA bc:dd:c2:28:ea:6d WPA: pairwise key handshake completed (RSN)
^Cwlan0: interface state ENABLED->DISABLED
wlan0: AP-STA-DISCONNECTED bc:dd:c2:28:ea:6d
wlan0: AP-STA-DISCONNECTED 40:9c:28:a9:8f:92
wlan0: AP-DISABLED
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Backing up NetworkManager.cfg...
Restarting NetworkManager...
Backing up /etc/dnsmasq.conf...
Writing dnsmasq config file...
Creating new /etc/dnsmasq.conf...
Writing hostapd config file...
Configuring AP interface...
Applying iptables rules...
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Starting DNSMASQ server...
RTNETLINK answers: File exists
Starting AP on wlan0 in screen terminal...
Configuration file: /etc/hostapd/hostapd.conf
Failed to create interface mon.wlan0: -95 (Operation not supported)
wlan0: Could not connect to kernel driver
Using interface wlan0 with hwaddr b8:27:eb:da:ef:de and ssid "vtrust-flash"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 RADIUS: starting accounting session 0D6835E054E744CF
wlan0: STA 40:9c:28:a9:8f:92 WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: associated
wlan0: AP-STA-CONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d RADIUS: starting accounting session 698622E00E654D44
wlan0: STA bc:dd:c2:28:ea:6d WPA: pairwise key handshake completed (RSN)
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 RADIUS: starting accounting session 20684D2C31F1C2F8
wlan0: STA 40:9c:28:a9:8f:92 WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: associated
wlan0: AP-STA-CONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d RADIUS: starting accounting session CF7E2774E50D6398
wlan0: STA bc:dd:c2:28:ea:6d WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 WPA: group key handshake completed (RSN)
^Cwlan0: interface state ENABLED->DISABLED
wlan0: AP-STA-DISCONNECTED 40:9c:28:a9:8f:92
wlan0: AP-DISABLED
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Backing up NetworkManager.cfg...
Restarting NetworkManager...
Backing up /etc/dnsmasq.conf...
Writing dnsmasq config file...
Creating new /etc/dnsmasq.conf...
Writing hostapd config file...
Configuring AP interface...
Applying iptables rules...
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Starting DNSMASQ server...
RTNETLINK answers: File exists
Starting AP on wlan0 in screen terminal...
Configuration file: /etc/hostapd/hostapd.conf
Failed to create interface mon.wlan0: -95 (Operation not supported)
wlan0: Could not connect to kernel driver
Using interface wlan0 with hwaddr b8:27:eb:da:ef:de and ssid "vtrust-flash"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 RADIUS: starting accounting session B5EB64E76637D483
wlan0: STA 40:9c:28:a9:8f:92 WPA: pairwise key handshake completed (RSN)
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 RADIUS: starting accounting session<PHONE_NUMBER>7645E1
wlan0: STA 40:9c:28:a9:8f:92 WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: associated
wlan0: AP-STA-CONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d RADIUS: starting accounting session F39A12B7854DCE22
wlan0: STA bc:dd:c2:28:ea:6d WPA: pairwise key handshake completed (RSN)
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED 40:9c:28:a9:8f:92
wlan0: STA 3c:dc:bc:f1:bc:03 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 3c:dc:bc:f1:bc:03
wlan0: STA 3c:dc:bc:f1:bc:03 RADIUS: starting accounting session BABFB03C73BAA0E8
wlan0: STA 3c:dc:bc:f1:bc:03 WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
^Cwlan0: interface state ENABLED->DISABLED
wlan0: AP-STA-DISCONNECTED 3c:dc:bc:f1:bc:03
wlan0: AP-DISABLED
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Backing up NetworkManager.cfg...
Restarting NetworkManager...
Backing up /etc/dnsmasq.conf...
Writing dnsmasq config file...
Creating new /etc/dnsmasq.conf...
Writing hostapd config file...
Configuring AP interface...
Applying iptables rules...
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. iptables v1.6.0: can't initialize iptables table filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Starting DNSMASQ server...
RTNETLINK answers: File exists
Starting AP on wlan0 in screen terminal...
Configuration file: /etc/hostapd/hostapd.conf
Failed to create interface mon.wlan0: -95 (Operation not supported)
wlan0: Could not connect to kernel driver
Using interface wlan0 with hwaddr b8:27:eb:da:ef:de and ssid "vtrust-flash"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: STA 3c:dc:bc:f1:bc:03 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 3c:dc:bc:f1:bc:03
wlan0: STA 3c:dc:bc:f1:bc:03 RADIUS: starting accounting session 9574DF1991C2B2DA
wlan0: STA 3c:dc:bc:f1:bc:03 WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: associated
wlan0: AP-STA-CONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d RADIUS: starting accounting session C52960B39CED9027
wlan0: STA bc:dd:c2:28:ea:6d WPA: pairwise key handshake completed (RSN)
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 40:9c:28:a9:8f:92
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 40:9c:28:a9:8f:92
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 40:9c:28:a9:8f:92
wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: disassociated
wlan0: STA 40:9c:28:a9:8f:92 IEEE 802.11: associated
wlan0: AP-STA-CONNECTED 40:9c:28:a9:8f:92
wlan0: STA 40:9c:28:a9:8f:92 RADIUS: starting accounting session F4F0CB59B19601AD
wlan0: STA 40:9c:28:a9:8f:92 WPA: pairwise key handshake completed (RSN)
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: AP-STA-DISCONNECTED bc:dd:c2:28:ea:6d
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated
wlan0: STA bc:dd:c2:28:ea:6d IEEE 802.11: disassociated

Make sure your system is up to date and you've installed all the prerequisites. Skimming through the logs I see you don't have tornado installed and you need to update iptables.

Closing due to inactivity. If you're still having issues, try the latest tuya-convert and open a new issue.


Allow zero ohm resistor

There are 0 ohm resistors, however this script currently assumes all resistor values are >=1. If you attempt to generate a 0 ohm resistor it will be skipped.
    resistor_values = [
        [0,         1,          10],
        [100,       1000,       10000],
        [0.1,       0.01,       0.001],
        [200000,    3000000,    40000000],
    ]

Before

After

~Note:  Technically 0 ohm resistors have only 1 band instead of 3. However refactoring this script to allow only single band images may be a much larger refactor, which may or may not be worth the effort for this single obscure resistor value.~

Update:
Now shows single band.

Good catch! This change will definitely be merged.
https://www.reichelt.de/widerstand-metallschicht-0-0-ohm-0207-0-6-w-1--metall-0-00-p184962.html
Seems like they exist both with the single stripe as also with the full 5 stripes. It's there an official norm?

It seems that the most common marking on SMD is "0" or "000", indicating precision. From my first search I very rarely found "R0", this one seems more dominant in schematics, but not in the resistor itself.

Seems like they exist both with the single stripe as also with the full 5 stripes. Is there an official norm?

The through hole ones I own are a single stripe.

It seems that the most common marking on SMD is "0" or "000", indicating precision. From my first search I very rarely found "R0", this one seems more dominant in schematics, but not on the resistor itself.

I can change R0 to 0

I can change R0 to 0 or 000. Do you have a preference?

The ones I have seen the most often when browsing through the web were 0 and 000, so those two are the ones I would display.
I'll do some minor changes and push to your branch, if that's fine.

I'll do some minor changes and push to your branch, if that's fine.

Please do. I'm sure there are many ways to optimize this code.

After thinking about it some more, I think you were right with the 000 and 0000, for consistency; it's always 3-digit and 4-digit.
I updated the Example.pdf as well to include a 0 Ohm value.
Give me your thumbs up if you agree with my changes in your code and the current state, then I'll merge.

Much cleaner, thank you 👍

Thanks for your contribution :)


Install Error on MacBook (IDFGH-14087)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.4-dev-4291-g7a305c0284
Operating System used.
macOS
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
None
What is the expected behavior?
I am new to ESP and trying to install the IDF to start working on it.
I cloned git clone --recursive https://github.com/espressif/esp-idf.git
and then ./install.sh esp32 but get the below error.
Error --> ERROR: Failed to download, and retry count has expired

What is the actual behavior?
To be able to use IDF
Steps to reproduce.
I cloned git clone --recursive https://github.com/espressif/esp-idf.git
and then ./install.sh esp32 but get the below error.
Error --> ERROR: Failed to download, and retry count has expired
Build or installation Logs.
latheefth@Abduls-MBP esp-idf % ./install.sh esp32
Detecting the Python interpreter
Checking "python3" ...
Python 3.13.0
"python3" has been detected
Checking Python compatibility
Installing ESP-IDF tools
Selected targets are: esp32c2, esp32s3, esp32c6, esp32p4, esp32c3, esp32, esp32s2, esp32c5, esp32h2, esp32c61
Current system platform: macos
Installing tools: xtensa-esp-elf-gdb, riscv32-esp-elf-gdb, xtensa-esp-elf, riscv32-esp-elf, esp32ulp-elf, openocd-esp32, esp-rom-elfs
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Installing<EMAIL_ADDRESS>Using GitHub assets mirror for URL: https://github.com/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz => https://dl.espressif.com/github_assets/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz
Downloading https://dl.espressif.com/github_assets/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz
Destination: /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp
98%WARNING: file size mismatch for /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp, expected 182793460, got 180173727
WARNING: Download failure: <urlopen error retrieval incomplete: got only 180173727 out of 182793460 bytes>
WARNING: Failed to download https://dl.espressif.com/github_assets/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz to /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp
Downloading https://dl.espressif.com/github_assets/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz
Destination: /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp
98%WARNING: file size mismatch for /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp, expected 182793460, got 180224867
WARNING: Download failure: <urlopen error retrieval incomplete: got only 180224867 out of 182793460 bytes>
WARNING: Failed to download https://dl.espressif.com/github_assets/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz to /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp
Downloading https://dl.espressif.com/github_assets/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz
Destination: /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp
97%WARNING: file size mismatch for /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp, expected 182793460, got 178382928
WARNING: Download failure: <urlopen error retrieval incomplete: got only 178382928 out of 182793460 bytes>
WARNING: Failed to download https://dl.espressif.com/github_assets/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz to /Users/latheefth/.espressif/dist/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz.tmp
ERROR: Failed to download, and retry count has expired
Please make sure you have a working Internet connection.

More Information.
No response

I have Sonoma os installed on Mac pro15 using open core patcher.

Hi @latheefth, can you please try to verify that if you download the file directly it will download the whole tar as expected? You can use wget with the following command:
wget https://dl.espressif.com/github_assets/espressif/crosstool-NG/releases/download/esp-14.2.0_20240906/xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz

and check the file size with e.g. ls -l xtensa-esp-elf-14.2.0_20240906-x86_64-apple-darwin.tar.xz
I also recommend checking whether you have enough space left on the disk for this file.
I am also on Mac OS (but 15.1; arm), and I was able to download this file (and also the arm version) without any issues. The expected size matches the one that was downloaded.

Please find the log as below, I don't find any issue with the wget

Can you please verify that you can still see the issue if you run the install script? Maybe it was some issue with the server which has been resolved already. If that does not help, please try not using the dl espressif mirror but using the GitHub assets directly. (unset IDF_GITHUB_ASSETS env var)

@latheefth We are sorry for the inconvenience. The only workaround I can offer now is to download the missing files with wget and put them into the ~/.espressif/dist directory. After that install.sh will be able to install them.

OK..but I am not able to find list directory below. Shall I  create dist directory and then do wget for each missing files? Please confirm.

@latheefth dist directory is not part of the ESP-IDF source git directory but is located with other installed tools in your home directory in ~/.espressif/dist as mentioned by Roland.


fix: NullPointException in the case of task queuing #2174

Please see #2174 for details.

Codecov Report

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

@@          Coverage Diff           @@
##             dev    #2175   +/-   ##
======================================
  Coverage       ?   29.84%
  Complexity     ?     1631
======================================
  Files          ?      336
  Lines          ?    17821
  Branches       ?     2246
======================================
  Hits           ?     5318
  Misses         ?    11939
  Partials       ?      564

Impacted Files
Coverage Δ
Complexity Δ

...heduler/server/master/runner/MasterExecThread.java
0% <0%> (ø)
0 <0> (?)

Continue to review full report at Codecov.

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


Bug on "enc" wiki page

As I didn't get a reply when I reported this to wiki-support[at]openssl.org and marquess[at]opensslfoundation.com about a month ago, I decided to open an issue on Github.
There's a bug on the "Enc" wiki page: https://wiki.openssl.org/index.php/Enc
-pass arg
This specifies the password source. Possible values for arg are
pass:password or pass:filename, where password is your password and
filename file containing the password.

It's file:filename not pass:filename
This is quite bad. If e.g. pass:/path/to/file is used as explained
in the wiki article, the password used to encrypt / decrypt is
literally /path/to/file, it is not read from file /path/to/file
It should say and filename is the file (missing is the)

(It's not just the man pages, there's whole sections of the wiki that are several years out of date and have incorrect or outdated information).   When using search engines for things (i.e. "openssl list digests"), the man pages rank highly, so we could replace each page with just a link to https://www.openssl.org/docs/manpages.html

list of pages to delete (i'll just do this via the api tomorrow or Mon):
media.txt

In theory we regularly upload fresh versions of the man pages to the wiki. But I suspect that broke a long time ago and no one noticed. Better to ditch them anyway.

Agreed. Done. There might be a little cleanup of links needed over time (but so many wiki links are broken anyway).  I'll also go through and make sure we didn't get any edits from anyone to them we lost.
In case we ever want to restore them we can just modify this quick script I used
delpages.py.txt


Backend skeleton

Added Skeleton code for Backend,
Includes Makefile, handlers and Backend folder structuring.

put all the go backend code inside folder named backend like below:
.
├── LICENSE.md
├── REAMDE.md (main)
├── backend/
└── ui/
I'll take care of the ui folder


chore(dependencies): 🤖 thorvg v0.13.6, emsdk v3.1.61, uniffi-rs v0.27.3

build artifacts for wasm/ios/android passes
https://github.com/LottieFiles/dotlottie-rs/actions/runs/9412757895


feat: prisma go client added

Closes issue #344
📑 Description

I've added the support for prisma go client to the artisan commands and the list of artisan commands are now updated with prisma commands as I added each command to the database directory service provider and tested each command, so no error happens. This prisma client is not supposed to change the way Goravel handles the DB right now. It's simply a database tool to handle migrations and database schema easier and it's fully compatible with the current built-in ORM tool. I haven't changed the facades.Orm() functionalities, and simply all I did is, added commands for prisma schema. Hope everyone has a better time developing great apps

[x] Added prisma commands besides current artisan console commands
[ ] Prisma Studio command (according to this issue it's in development process)

✅ Checks

[x] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required (It doesn't require any changes to the docs, as it has all documentation included here)
[x] All the tests have passed

ℹ Additional Information

Dependencies added:

prisma-client-go

Comparisons between new and old behavior:

more artisan commands available, prisma included

Thanks for your PR. Great work, but based on the https://github.com/goravel/goravel/issues/344, I just think you want to use Prisma instead of Gorm in the Orm module and create a new development package for it.
We need to have a deep discussion if you want to add a new feature(like the commands in this PR) first, so unfortunately, this PR may not be merged into master at this time.

Thanks for your PR. Great work, but based on the goravel/goravel#344, I just think you want to use Prisma instead of Gorm in the Orm module and create a new development package for it.
We need to have a deep discussion if you want to add a new feature(like the commands in this PR) first, so unfortunately, this PR may not be merged into master at this time.

Actually there is no replacement for the Gorm in the Orm module because it may change a lot of settings and a lot of files, which is not convenient. My goal was to make database operations easier, as if you check my added codes, you'll see that i'm not replacing Gorm with Prisma, but leveraging Prisma migration tools and commands to automate the migration creation, and make database module a lot more abstract than what it already is. All app models and Gorm functionalities may work just like before and also, current database artisan commands may work perfectly, and there's no change in the flow of Goravel app, and all Prisma will do is ease the way developers interact with database and also supports Mongodb as NoSQL and many relational databases which are yet to be added to Goravel, as their drivers don't exist(yet). Prisma is way more mature than Gorm by the way, but I actually haven't implemented the replacement for Gorm because i didn't want to change many codes and chose to get on with the Goravel flow and code principle. I made my intentions clear, so that my offered features may not sound too complicated or out of context

Yes, I understand, the PR is great, but we are not ready to integrate Prisma into the framework yet, this involves many aspects, so I suggest you can add these commands to an independent development package first. For detail: https://www.goravel.dev/digging-deeper/package-development.html

Yes, I understand, the PR is great, but we are not ready to integrate Prisma into the framework yet, this involves many aspects, so I suggest you can add these commands to an independent development package first. For detail: https://www.goravel.dev/digging-deeper/package-development.html

Very well, I'll put them in a separate package as a library, and i'll open another PR. Thanks

Hello again, I just finished developing the Go Prisma Client by following Goravel Extend package workflow.
You can find it here: Goravel Prisma
If you want to transfer ownership of the package, or use it by only referring to Goravel name on it, feel free to fork the mentioned repository, to create a new repository for Goravel.
Best Regards.

Thanks @hosseinmirzapur That's great!


Clinton/integration tests

Reworked DropoutNetwork architecture to inherit from tf.keras.Model which required changes to models wrapper to call self() instead of self.model(). Also temporarily added a self.num_passes in model wrapper so that I could use for integration tests. Feel free to change, but if you change the way it is set please check in builders, test_builders, integration/models/keras/test_predictions.py to make sure it doesn't break anything.
Otherwise a bunch of formatting changes and changes related to PR with Hrvoje. Take a look, double check and approve and merge it if there is nothing of note.

Oh, and added some default parameters that seemed to work well with branin(1000) dataset. This is reflected throughout in models, architectures, layers, etc.


always failing for years

always fails on ubuntu but then works
it's annoying
please fix it
always displays "error, send stuff"
no
I had this on lots of different ubuntu versions
the client looks abandoned
what happened to keybase????

it is impossible to help you without actual error messages.   what problem are you seeing?


fix(registry/github-cli): set exe=gh for aquq backend entry

Fixes error when trying to install/upgrade gh/github-cli, for example:
$ mise upgrade gh
mise ERROR failed to install<EMAIL_ADDRESS>mise ERROR Failed to install with ubi<EMAIL_ADDRESS>could not find any files named cli in the downloaded zip file
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

exe= is a setting for ubi, not aqua

Interesting, because my local build of mise with the change in this PR did successfully upgrade gh to 2.63.0, while the latest release (2024.11.32) cannot upgrade it, complaining it couldn't find a file named cli in the zip file.

it looks like what's happening here is an issue with the state, it's a bigger problem. I think the ~/.local/share/mise/installs/gh/.mise.backend file is reporting ubi but we changed this to aqua. What mise should do is continue to use ubi (because you may have other versions installed and the versions installed with one backend may not be compatible with another so we keep you on whatever backend you used for the first install).
If you delete ~/.local/share/mise/installs/gh it should fix this though, but let me know what is in that file to verify my suspicion first.

Ah, yeah that makes more sense. My ~/.local/share/mise/installs/gh/.mise.backend file contains:
gh
ubi:cli/cli

And I can confirm that fully removing gh and re-isntalling 2.62.0 and upgrading to 2.63.0 works fine via aqua, and the state file is updated to contain details for aqua instead.
So I guess the issue might be that with the state set to ubi, but registry pointing to aqua (without the exe) option, it ends up running ubi without the exe option? Since me adding the exe option to aqua in registry, made the upgrade via ubi work again.


Added requirments into requirments.txt

Added the new requirements,  needed.

Try again after installing the modules.


Y24-183 - Move Sequencescape API v1 calls over to API v2

User story
Sequencescape API v1 will be shut down in the near future and has been deprecated for the past 5 years.  We should switch usage of the API over to v2, using the already installed json_api_client gem.
Who are the primary contacts for this story
Stuart McHattie
Who is the nominated tester for UAT
PSD
Acceptance criteria
To be considered successful the solution must allow:

[ ] No more API v1 calls are made to Sequencescape
[ ] All traces of sequencescape-client-api and its config have been removed.

Dependencies
Any new endpoints required in Sequencescape will have to be created as they are discovered to be missing.  A new story should be created under that repository if there are indeed endpoints to create.
Additional context
The calls made during the last two week period are as below, with counts for each endpoint:

GET    - /api/1/: 17

GET    - /api/1/plate_purposes: 32

GET    - /api/1/plate_purposes/2: 16

GET    - /api/1/plate_purposes/3: 16

GET    - /api/1/plate_purposes/4: 16

GET    - /api/1/{uuid}: 17

GET    - /api/1/{uuid}/wells: 17

POST   - /api/1/{uuid}/extraction_attributes: 17

POST   - /api/1/{uuid}/plates: 16

Briefly reviewing the code and the list of calls being made to v1, I think we need to start using the PlatePurpose JSON API endpoint that was only created recently.  This endpoint might need to be updated to support creating plates and extraction attributes as these are currently not obviously available in SequenceScape.  I don't think there are any actual new endpoints to create.


lama-refine

Thank you for your work, can you please provide the pre-trained model weights for the lama-refine

Hi @mldemox, the repository for lama-with-refiner is this one: https://github.com/geomagical/lama-with-refiner
The refiner works by inference on pre-trained models, we haven't trained any new model. You can just directly use the Big-Lama weights, and pass --refine=True, as mentioned here: https://github.com/geomagical/lama-with-refiner#inference-
python3 bin/predict.py refine=True model.path=$(pwd)/big-lama indir=$(pwd)/LaMa_test_images outdir=$(pwd)/output

It should also be noted that the geomagical/lama-with-refiner repository has been merged into the official advimman/lama repo. Please take any further discussion into that repository.


Can't activate an account when activation link is lost

What I'm trying to achieve
Activate an account when the activation link is lost, I've tried to restore the password, I get the expired link error message
What I expected to happen
Resend a new account activation link email

Sounds like a bug. I would expect the password reset link to allow to bypass the activation as a feature.

No, when you get the password link and you try to restore it, you get token expired error

Yes, most likely because the user is flagged as inactive. It could be a feature to allow inactive users to reset their password in order to activate their account.


Allow to hook the initial build from outside

Add a new attribute to trigger_build to do not execute the task but just return the immutable signature of it, so it can be chained into a bigger task from outside when it's needed to do something else before/after it's execution.
Needed by https://github.com/readthedocs/readthedocs-corporate/issues/99
Also Closes #3888

This is pretty close to what we want: all the initial project import is handled with chained async calls.
The only problem/issue that I'm experimenting now is that as has_valid_webhook is default to False, after importing the project I'm immediately seeing a message like:

This repository doesn't have a valid webhook set up, commits won't trigger new builds for this project.

from https://github.com/rtfd/readthedocs.org/blob/3a78b848c205399e16bb270d331be4a85c9f3843/readthedocs/templates/core/project_bar_base.html#L29-L42
This message dissapears once the Celery task completes and I refresh the page.

There is a linting error because it seems that we are requiring django-dynamic-fixture for some strange reason and it's not in the requirements.

There is a linting error because it seems that we are requiring django-dynamic-fixture for some strange reason and it's not in the requirements.

I think this is because you updated the common submodule, you only need to rebase (the requirements were moved in other PR a long time ago).

After the talk from today:

I created a new message storage NonPersistentStorage based on PersistentStorage from messages_extends to save one-time messages in the database for a new group of message levels. This backend mark them all as read when they are retrieved the first time.
I created a new class SiteNotification (the name could be improved) as a helper for simple on site notifications. To use it, just inherit and define the success and failure messages

These things needs some decisions:
As I mentioned in https://github.com/rtfd/readthedocs.org/pull/4033#issuecomment-394738262, now immediately after importing the project we will see a message saying that our repo doesn't have a valid webhook setup that is created inside the template (checking Project.has_valid_webhook).
Anthony said that we should remove this from the template but I'm not sure how to imitate the same behaviour if we remove it: show this message every time the user opens the project's page. We could add a PERSISTENT message with an actionable link (that will mark the message as read) from the Celery task after knowing that the webhook has failed. At that point, the user will fix (or not) the issue and the message won't appear anymore. The edge case here is that if the user doesn't fix the problem, the message will disappear and we won't be communicating this to the user anymore.

I'm not sure how to imitate the same behaviour if we remove it: show this message every time the user opens the project's page

We could add a persistent message every time that the project dashboard's page is viewed if has_valid_webhook is still False.

@agjohnson I worked on your feedback:

refactor the SiteNotification code and make it more flexible
SiteNotification can be extended via get_context_data and extra_context
the string is rendered as a django Template
worked on copy
remove unnecessary error message and log an error instead
added test cases

The only design decision missing from my point of view is https://github.com/rtfd/readthedocs.org/pull/4033#issuecomment-394738262 . I'd like to know your thoughts there.

The only design decision missing from my point of view is #4033 (comment) . I'd like to know your thoughts there.

I thought I reviewed this or talked about it maybe. I think we can remove this small piece from the UI. The user will be warned about the webhook not working, i don't think we need this on all the project pages. There is a better UI somewhere, but i don't think we have it yet.
Alternatively, we could make the failure case messages on this notification to be persistent, so we know the user will see them. Eventually, i think there might be a warning indicator we want to add as well, but for now, a persistent message is at least a common pattern.

We can address the issue with the pseudo-notification later in https://github.com/rtfd/readthedocs.org/issues/4235

I updated the copy you mentioned and change the You by The. The work around the notification will be addressed by #4235

But with this change now, won't there be 3 notifications? 1 telling the user to connect their account, 1 telling them their webhook isn't set up (from Notification), and 1 other notification telling them their webhook isn't set up (hardcoded in template)?
If so, we should remove the hardcoded template notification that we're duplicating.

That's fine, I'd expect a 404 as a user.


@notweuz is this 1.6.0 update canon?1!1?1!1!1

What is your question?
@notweuz is this canon is this canon is this canon is this canon is this canon is this canon is this canon is this canon is this canon is this canon is this canon is this canon is this canon

h


onprem sharepoint server to sharepoint online

we are migrating onprem sharepoint server to share point online using sharepoint tools so when we try to migrate it. it will provide error.
ERROR-The host name of side you provided cannot be resolved. please cheack URL

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

ID: 0dccdf92-2869-83ce-1565-d50b4b84729f
Version Independent ID: ea4ef549-4335-b6c3-d902-996847ca663b
Content: Introduction to SharePoint Online - SharePoint Online
Content Source: SharePoint/SharePointOnline/introduction.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

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

@scanum Thank you for update.


Updating OTA

What's the best way to take OTA updates?
Do we have to go back to the pre-patch EFI and then patch, then switch back each time?
Or is there a way to patch it before restarting?

I have tried updating with OTA, without uninstalling the legacy patches, and I ended up in a boot loop. I do not recommend updating. Do it on your OWN risk if you want to.
I am doing a clean install now.


feat: add chroma component

Because

We want to integrate VDP with chroma self hosted vector db
We want more vector db component choice

This commit

Add chroma component along with the basic tasks (query, upsert, ..)
Use api key auth that user determine themselves

Note:
This PR will be drafted while waiting for the chroma logo

@chuang8511 Please check the changes i've made, thank you

@zidanehakim   cc @kuroxx
Thanks for your contribution!
Could you provide your recipe when you test this component?
So, Anni or I can use it as a reference to verify it and use it as the marketing content!

@chuang8511
Sure, I did test it using the earlier version of instill-core rather than using the latest no-code pipeline, so it might be a little bit different. The way I tested it is by testing the output for different tasks one by one
NOTE: the url is my self host aws ec2 chroma url which now has been terminated
{
  "version": "v1beta",
  "component": {
    "chroma-0": {
      "task": "TASK_QUERY",
      "type": "chroma",
      "input": {
        "collection-name": "testqueryembedding2",
        "n-results": 100,
        "vector": "${[0.1,0.2]}"
      },
      "setup": {
        "api-key": "${secret.chromaapikey}",
        "url": "http://<IP_ADDRESS>:8000"
      }
    }
  },
  "variable": {
    "a": {
      "instillFormat": "semi-structured/json",
      "title": "a"
    }
  },
  "output": {
    "b": {
      "title": "b",
      "value": "${chroma-0.output}"
    }
  }
}


Add all RCT1LL coaster trains

Adds all RCT1LL coaster trains as compat objects. Also adjusts the buildMenuPriority of the RCT1 2-across invert trains and the RCT2 4-across invert trains to fix some oddities with which icon is displayed when grouping by ride types. Now the values are as follows:
RCT2 Vekoma Giant Boomerang Trains: 1
RCT1/2 Vekoma Face-off Trains: 2
RCT2 Vekoma SLC Trains/RCT1 Giovanola Invert Trains: 3
RCT1/2 B&M 4-Across Trains: 4

Could you explain why it is necessary to also modify the RCT2 trains?

It's mainly due to how the 2-across trains are available for both the compact + b&m inverted coasters, as the 2-across trains use the same buildMenuPriority for both ride types.
With the old 2-across value of just 1, they would get overwritten by the face-off trains on the compact invert, and by increasing their value to 3 that would make them overwrite the 4-across trains on the b&m invert. So as such the RCT1LL & RCT2 4-across trains have had their priority set to 4 so that way they will always overwrite the 2-across trains while still ensuring that the 2-across trains will always overwrite the face-off cars (and giant boomerang trains if you enable them with cheats or in custom scenarios.)
The only RCT2 train modified by this is the 4-across trains, i just posted the others to give more context as to what the buildmenu priorities for all of them would be in relation to one another.


adjust .vscode/settings.json

This sets the default language for the popular 'Code Spell Checker' extension to en-GB (overriding my user-level setting of en-US), and also enables adding trailing newlines to files on save.
Before submitting the PR, please make sure you do the following

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts

🇬🇧


Update define-your-kubernetes-target-infrastructure.md

Typo:
Instead of RFC-1035, it is called DNS-1035.
RFC-1035 is about Domain name implementation and specification.
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b78b7b51be0c252bcbbd4b--harness-developer.netlify.app


Detect Ambulance Siren

About
The way we detect an ambulance right now is using a simple switch at the intersection. This obviously was a workaround and is not ideal.  We just want you to build a small component of it. Make a python file, or any other language of your choice to take in a sound file (.mp3, .wav) etc and tell if the sound contains an ambulance siren in the background. The ambulance has a continuously oscillating fixed frequency. Use this to our advantage to detect an ambulance
Bounty 150

Hi, I would like to contribute to this issue.
Can you assign this task to me?

hey, really sorry, but this issue is to be solved for an internal hacktoberfest event

hey i would like to work on this

@harveen-10 , you can start working on this !

can i get assigned?

please assign me

@Acc0LadE, @RishavSinha sorry it has been assigned already

@Acc0LadE, @RishavSinha20 sorry it has been assigned already

please assign it to me

please assign it to me

@Acc0LadE you can start working on this!, please open a draft pr in 30 mins to lmk your progress

@Acc0LadE please open a draft pr, its almost 30 mins since you have been assigned

@RishavSinha20 you have been assigned, you can start working on this!

can u assign pls?

@sumukhacharya03  You can start working on this! Please open a PR in 30 mins to show your progress on the issue

i want to solve this issue can you assign me ??

@sumukhacharya03 , please open a pr to show progress!

can i get assigned if this is still open?

Can i be assigned this issue?

@bwaklog you can work on this issue, make sure to open a draft PR in 30 mins to show your progress!

i'm working on the issue

@bwaklog heyy, could you open a draft pr? I'd like to see your progress on this issue

can i try

can i be assigned the issue?

hey can i be assigned this?

hi
can i be assigned this
i think i got it