The two nodes cannot ping each other

Expected Behavior
I hope that my k8s cluster can communicate with each other

Current Behavior
My previous k8s cluster was running normally. For some reason, I wanted to re-divide the network segment, so I reset my previous cluster and re-init, but I encountered a problem. Calico seemed to be normal, but it could not communicate with each other.
Use kubectl describe pod -n calico-system calico-node-7cwl2. There will be warnings, but they will disappear after a while and return to normal
warning:
Warning  Unhealthy  29m  kubelet  Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused

normal:
  kube-api-access-wdsf5:
    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:                 :NoSchedule op=Exists
                             :NoExecute op=Exists
                             CriticalAddonsOnly op=Exists
                             node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:                      <none>

The following is part of calico-node log:

2024-08-15 07:08:17.264 [INFO][85] felix/hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"calie3ba9b96e53", Addrs:set.Typed[string]{"fe80::ecee:eeff:feee:eeee":set.v{}}}
2024-08-15 07:08:31.401 [INFO][85] felix/summary.go 100: Summarising 29 dataplane reconciliation loops over 1m1.8s: avg=6ms longest=17ms (resync-filter-v4,resync-mangle-v4,update-filter-v4)
bird: KIF: Received address message for unknown interface 128090
2024-08-15 07:08:58.378 [INFO][85] felix/int_dataplane.go 1289: Linux interface state changed. ifIndex=128090 ifaceName="calie3ba9b96e53" state="down"
2024-08-15 07:08:58.378 [INFO][85] felix/int_dataplane.go 1893: Received interface update msg=&intdataplane.ifaceStateUpdate{Name:"calie3ba9b96e53", State:"down", Index:128090}
2024-08-15 07:08:58.378 [INFO][85] felix/int_dataplane.go 1325: Linux interface addrs changed. addrs=set.Set{} ifaceName="calie3ba9b96e53"
2024-08-15 07:08:58.379 [INFO][85] felix/int_dataplane.go 1913: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"calie3ba9b96e53", Addrs:set.Typed[string]{}}
2024-08-15 07:08:58.379 [INFO][85] felix/iface_monitor.go 238: Netlink address update for known interface.  addr="fe80::ecee:eeff:feee:eeee" exists=false ifIndex=128090
2024-08-15 07:08:58.379 [INFO][85] felix/hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"calie3ba9b96e53", Addrs:set.Typed[string]{}}
2024-08-15 07:08:58.379 [INFO][85] felix/endpoint_mgr.go 431: Workload interface state changed; marking for status update. ifaceName="calie3ba9b96e53"
2024-08-15 07:08:58.379 [INFO][85] felix/endpoint_mgr.go 490: Re-evaluated workload endpoint status adminUp=true failed=false known=true operUp=false status="down" workloadEndpointID=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:08:58.379 [INFO][85] felix/status_combiner.go 58: Storing endpoint status update ipVersion=0x4 status="down" workload=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:08:58.379 [INFO][85] felix/status_combiner.go 78: Endpoint down for at least one IP version id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"} ipVersion=0x4 status="down"
2024-08-15 07:08:58.379 [INFO][85] felix/status_combiner.go 98: Reporting combined status. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"} status="down"
2024-08-15 07:08:58.381 [INFO][85] felix/int_dataplane.go 1289: Linux interface state changed. ifIndex=128090 ifaceName="calie3ba9b96e53" state=""
2024-08-15 07:08:58.381 [INFO][85] felix/int_dataplane.go 1325: Linux interface addrs changed. addrs=<nil> ifaceName="calie3ba9b96e53"
2024-08-15 07:08:58.381 [INFO][85] felix/int_dataplane.go 1893: Received interface update msg=&intdataplane.ifaceStateUpdate{Name:"calie3ba9b96e53", State:"", Index:128090}
2024-08-15 07:08:58.381 [INFO][85] felix/int_dataplane.go 1913: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"calie3ba9b96e53", Addrs:set.Set[string](nil)}
2024-08-15 07:08:58.381 [INFO][85] felix/hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"calie3ba9b96e53", Addrs:set.Set[string](nil)}
2024-08-15 07:08:58.381 [INFO][85] felix/endpoint_mgr.go 431: Workload interface state changed; marking for status update. ifaceName="calie3ba9b96e53"
2024-08-15 07:08:58.381 [INFO][85] felix/endpoint_mgr.go 490: Re-evaluated workload endpoint status adminUp=true failed=false known=true operUp=false status="down" workloadEndpointID=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:08:58.381 [INFO][85] felix/status_combiner.go 58: Storing endpoint status update ipVersion=0x4 status="down" workload=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:08:58.381 [INFO][85] felix/status_combiner.go 78: Endpoint down for at least one IP version id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"} ipVersion=0x4 status="down"
2024-08-15 07:08:58.381 [INFO][85] felix/status_combiner.go 98: Reporting combined status. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"} status="down"
2024-08-15 07:08:58.489 [INFO][85] felix/calc_graph.go 465: Local endpoint deleted id=WorkloadEndpoint(node=izuf640eb7mh8kgvyg4b4jz, orchestrator=k8s, workload=default/debug, name=eth0)
2024-08-15 07:08:58.489 [INFO][85] felix/int_dataplane.go 1836: Received *proto.WorkloadEndpointRemove update from calculation graph msg=id:<orchestrator_id:"k8s" workload_id:"default/debug" endpoint_id:"eth0" >
2024-08-15 07:08:58.489 [INFO][85] felix/int_dataplane.go 1836: Received *proto.ActiveProfileRemove update from calculation graph msg=id:<name:"kns.default" >
2024-08-15 07:08:58.489 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-pri-kns.default" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.489 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-pro-kns.default" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.489 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-pro-kns.default" ipVersion=0x4 table="mangle"
2024-08-15 07:08:58.489 [INFO][85] felix/int_dataplane.go 1836: Received *proto.ActiveProfileRemove update from calculation graph msg=id:<name:"ksa.default.default" >
2024-08-15 07:08:58.489 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-pri-ksa.default.default" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.490 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-pro-ksa.default.default" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.490 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-pro-ksa.default.default" ipVersion=0x4 table="mangle"
2024-08-15 07:08:58.490 [INFO][85] felix/int_dataplane.go 1836: Received *proto.RouteRemove update from calculation graph msg=dst:"<IP_ADDRESS>/32"
2024-08-15 07:08:58.490 [INFO][85] felix/endpoint_mgr.go 703: Workload removed, deleting its chains. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:08:58.490 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-tw-calie3ba9b96e53" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.490 [INFO][85] felix/table.go 593: Chain no longer referenced, marking it for removal chainName="cali-pri-kns.default"
2024-08-15 07:08:58.490 [INFO][85] felix/table.go 593: Chain no longer referenced, marking it for removal chainName="cali-pri-ksa.default.default"
2024-08-15 07:08:58.490 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-fw-calie3ba9b96e53" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.490 [INFO][85] felix/table.go 593: Chain no longer referenced, marking it for removal chainName="cali-pro-kns.default"
2024-08-15 07:08:58.490 [INFO][85] felix/table.go 593: Chain no longer referenced, marking it for removal chainName="cali-pro-ksa.default.default"
2024-08-15 07:08:58.490 [INFO][85] felix/endpoint_mgr.go 558: Workload removed, deleting old state. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:08:58.491 [INFO][85] felix/table.go 508: Queueing update of chain. chainName="cali-from-wl-dispatch" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.491 [INFO][85] felix/table.go 593: Chain no longer referenced, marking it for removal chainName="cali-from-wl-dispatch-e"
2024-08-15 07:08:58.491 [INFO][85] felix/table.go 508: Queueing update of chain. chainName="cali-to-wl-dispatch" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.491 [INFO][85] felix/table.go 593: Chain no longer referenced, marking it for removal chainName="cali-to-wl-dispatch-e"
2024-08-15 07:08:58.491 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-from-wl-dispatch-e" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.491 [INFO][85] felix/table.go 593: Chain no longer referenced, marking it for removal chainName="cali-fw-calie3ba9b96e53"
2024-08-15 07:08:58.491 [INFO][85] felix/table.go 539: Queuing deletion of chain. chainName="cali-to-wl-dispatch-e" ipVersion=0x4 table="filter"
2024-08-15 07:08:58.491 [INFO][85] felix/table.go 593: Chain no longer referenced, marking it for removal chainName="cali-tw-calie3ba9b96e53"
2024-08-15 07:08:58.491 [INFO][85] felix/endpoint_mgr.go 490: Re-evaluated workload endpoint status adminUp=false failed=false known=false operUp=false status="" workloadEndpointID=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:08:58.491 [INFO][85] felix/status_combiner.go 58: Storing endpoint status update ipVersion=0x4 status="" workload=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:08:58.491 [INFO][85] felix/route_table.go 1185: Failed to access interface because it doesn't exist. error=Link not found ifaceName="calie3ba9b96e53" ifaceRegex="^cali.*" ipVersion=0x4 tableIndex=254
2024-08-15 07:08:58.491 [INFO][85] felix/route_table.go 1253: Failed to get interface; it's down/gone. error=Link not found ifaceName="calie3ba9b96e53" ifaceRegex="^cali.*" ipVersion=0x4 tableIndex=254
2024-08-15 07:08:58.492 [INFO][85] felix/route_table.go 589: Interface missing, will retry if it appears. ifaceName="calie3ba9b96e53" ifaceRegex="^cali.*" ipVersion=0x4 tableIndex=254
2024-08-15 07:08:58.492 [INFO][85] felix/conntrack.go 90: Removing conntrack flows ip=<IP_ADDRESS>
2024-08-15 07:08:58.507 [INFO][85] felix/status_combiner.go 86: Reporting endpoint removed. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug", EndpointId:"eth0"}
2024-08-15 07:09:34.028 [INFO][85] felix/summary.go 100: Summarising 19 dataplane reconciliation loops over 1m2.6s: avg=6ms longest=25ms ()
2024-08-15 07:10:37.652 [INFO][85] felix/summary.go 100: Summarising 12 dataplane reconciliation loops over 1m3.6s: avg=5ms longest=25ms ()
2024-08-15 07:11:40.381 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m2.7s: avg=4ms longest=7ms (resync-filter-v4)
2024-08-15 07:12:42.652 [INFO][85] felix/summary.go 100: Summarising 11 dataplane reconciliation loops over 1m2.3s: avg=5ms longest=23ms ()
2024-08-15 07:13:46.856 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m4.2s: avg=5ms longest=23ms ()
2024-08-15 07:14:49.555 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m2.7s: avg=3ms longest=7ms (resync-mangle-v4,resync-nat-v4)
2024-08-15 07:15:53.574 [INFO][85] felix/summary.go 100: Summarising 10 dataplane reconciliation loops over 1m4s: avg=5ms longest=24ms ()
2024-08-15 07:16:55.997 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m2.4s: avg=5ms longest=23ms ()
2024-08-15 07:18:00.032 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m4s: avg=3ms longest=9ms (resync-mangle-v4,resync-nat-v4)
2024-08-15 07:19:00.518 [INFO][85] felix/summary.go 100: Summarising 10 dataplane reconciliation loops over 1m0.5s: avg=6ms longest=25ms ()
2024-08-15 07:20:05.005 [INFO][85] felix/summary.go 100: Summarising 11 dataplane reconciliation loops over 1m4.5s: avg=5ms longest=26ms ()
2024-08-15 07:21:06.364 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m1.4s: avg=7ms longest=24ms ()
2024-08-15 07:22:11.083 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m4.7s: avg=3ms longest=7ms (resync-filter-v4)
2024-08-15 07:23:15.050 [INFO][85] felix/summary.go 100: Summarising 10 dataplane reconciliation loops over 1m4s: avg=5ms longest=24ms ()
2024-08-15 07:24:18.783 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m3.7s: avg=4ms longest=10ms (resync-mangle-v4,resync-nat-v4)
2024-08-15 07:25:20.846 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m2.1s: avg=5ms longest=23ms ()
2024-08-15 07:26:24.458 [INFO][85] felix/summary.go 100: Summarising 11 dataplane reconciliation loops over 1m3.6s: avg=5ms longest=23ms ()
2024-08-15 07:27:27.327 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m2.9s: avg=5ms longest=24ms ()
2024-08-15 07:28:28.004 [INFO][85] felix/summary.go 100: Summarising 8 dataplane reconciliation loops over 1m0.7s: avg=3ms longest=8ms (resync-filter-v4)
2024-08-15 07:29:33.163 [INFO][85] felix/summary.go 100: Summarising 11 dataplane reconciliation loops over 1m5.2s: avg=5ms longest=24ms ()
2024-08-15 07:30:36.941 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m3.8s: avg=6ms longest=23ms ()
2024-08-15 07:31:41.070 [INFO][85] felix/summary.go 100: Summarising 10 dataplane reconciliation loops over 1m4.1s: avg=3ms longest=8ms (resync-mangle-v4,resync-nat-v4)
2024-08-15 07:32:44.669 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m3.6s: avg=5ms longest=24ms ()
2024-08-15 07:33:46.507 [INFO][85] felix/summary.go 100: Summarising 10 dataplane reconciliation loops over 1m1.8s: avg=6ms longest=26ms ()
2024-08-15 07:34:49.507 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m3s: avg=3ms longest=8ms (resync-mangle-v4,resync-nat-v4)
2024-08-15 07:35:51.803 [INFO][85] felix/summary.go 100: Summarising 9 dataplane reconciliation loops over 1m2.3s: avg=5ms longest=23ms ()
2024-08-15 07:36:54.878 [INFO][85] felix/summary.go 100: Summarising 12 dataplane reconciliation loops over 1m3.1s: avg=6ms longest=24ms ()
2024-08-15 07:37:58.721 [INFO][85] felix/summary.go 100: Summarising 7 dataplane reconciliation loops over 1m3.8s: avg=2ms longest=3ms (resync-routes-v4,resync-routes-v4,resync-routes-v4,resync-routes-v4,resync-routes-v4,resync-rules-v4,resync-wg)
2024-08-15 07:39:02.954 [INFO][85] felix/summary.go 100: Summarising 11 dataplane reconciliation loops over 1m4.2s: avg=5ms longest=23ms ()
2024-08-15 07:40:06.437 [INFO][85] felix/summary.go 100: Summarising 10 dataplane reconciliation loops over 1m3.5s: avg=5ms longest=23ms ()

Below is the log of calico-apiserver:
I0815 09:05:32.239608 1 resource.go:207] Watch called with key: projectcalico.org/bgppeers on resource BGPPeer
time="2024-08-15T09:05:32Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:05:56Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:05:56Z" level=info msg="Terminating main client watcher loop"
I0815 09:05:56.436277 1 resource.go:207] Watch called with key: projectcalico.org/profiles on resource Profile
time="2024-08-15T09:05:56Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:06:36Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:06:36Z" level=info msg="Terminating main client watcher loop"
I0815 09:06:36.235471 1 resource.go:207] Watch called with key: projectcalico.org/kubecontrollersconfigurations on resource KubeControllersConfiguration
time="2024-08-15T09:06:36Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:07:00Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:07:00Z" level=info msg="Terminating main client watcher loop"
I0815 09:07:00.400414 1 resource.go:207] Watch called with key: projectcalico.org/ipamconfigurations on resource IPAMConfiguration
time="2024-08-15T09:07:00Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:07:06Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:07:06Z" level=info msg="Terminating main client watcher loop"
I0815 09:07:06.186406 1 resource.go:207] Watch called with key: projectcalico.org/caliconodestatuses on resource CalicoNodeStatus
time="2024-08-15T09:07:06Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:07:29Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:07:29Z" level=info msg="Terminating main client watcher loop"
I0815 09:07:29.437958 1 resource.go:207] Watch called with key: projectcalico.org/felixconfigurations on resource FelixConfiguration
time="2024-08-15T09:07:29Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:07:30Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:07:30Z" level=info msg="Terminating main client watcher loop"
I0815 09:07:30.213593 1 resource.go:207] Watch called with key: projectcalico.org/globalnetworksets on resource GlobalNetworkSet
time="2024-08-15T09:07:30Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:07:49Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:07:49Z" level=info msg="Terminating main client watcher loop"
I0815 09:07:49.407763 1 resource.go:207] Watch called with key: projectcalico.org/bgpconfigurations on resource BGPConfiguration
time="2024-08-15T09:07:49Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:09:17Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:09:17Z" level=info msg="Terminating main client watcher loop"
I0815 09:09:17.413098 1 resource.go:207] Watch called with key: projectcalico.org/clusterinformations on resource ClusterInformation
time="2024-08-15T09:09:17Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:09:38Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:09:38Z" level=info msg="Terminating main client watcher loop"
I0815 09:09:38.764253 1 resource.go:207] Watch called with key: projectcalico.org/bgpfilters on resource BGPFilter
time="2024-08-15T09:09:38Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:10:45Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:10:45Z" level=info msg="Terminating main client watcher loop"
I0815 09:10:45.535100 1 resource.go:207] Watch called with key: projectcalico.org/ipreservations on resource IPReservation
time="2024-08-15T09:10:45Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:11:02Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:11:02Z" level=info msg="Terminating main client watcher loop"
I0815 09:11:02.244076 1 resource.go:207] Watch called with key: projectcalico.org/bgppeers on resource BGPPeer
time="2024-08-15T09:11:02Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:11:41Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:11:41Z" level=info msg="Terminating main client watcher loop"
I0815 09:11:41.788187 1 resource.go:207] Watch called with key: projectcalico.org/ippools on resource IPPool
time="2024-08-15T09:11:41Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:11:42Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:11:42Z" level=info msg="Terminating main client watcher loop"
I0815 09:11:42.768146 1 resource.go:207] Watch called with key: projectcalico.org/blockaffinities on resource BlockAffinity
time="2024-08-15T09:11:42Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:11:58Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:11:58Z" level=info msg="Terminating main client watcher loop"
I0815 09:11:58.859334 1 resource.go:207] Watch called with key: projectcalico.org/hostendpoints on resource HostEndpoint
time="2024-08-15T09:11:58Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:12:25Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:12:25Z" level=info msg="Terminating main client watcher loop"
I0815 09:12:25.408250 1 resource.go:207] Watch called with key: projectcalico.org/globalnetworkpolicies on resource GlobalNetworkPolicy
time="2024-08-15T09:12:25Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:12:41Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:12:41Z" level=info msg="Terminating main client watcher loop"
I0815 09:12:41.442755 1 resource.go:207] Watch called with key: projectcalico.org/felixconfigurations on resource FelixConfiguration
time="2024-08-15T09:12:41Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:13:01Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:13:01Z" level=info msg="Terminating main client watcher loop"
I0815 09:13:01.412968 1 resource.go:207] Watch called with key: projectcalico.org/bgpconfigurations on resource BGPConfiguration
time="2024-08-15T09:13:01Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:13:04Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:13:04Z" level=info msg="Terminating main client watcher loop"
I0815 09:13:04.441301 1 resource.go:207] Watch called with key: projectcalico.org/profiles on resource Profile
time="2024-08-15T09:13:04Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:13:10Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:13:10Z" level=info msg="Terminating main client watcher loop"
I0815 09:13:10.240013 1 resource.go:207] Watch called with key: projectcalico.org/kubecontrollersconfigurations on resource KubeControllersConfiguration
time="2024-08-15T09:13:10Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:13:16Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:13:16Z" level=info msg="Terminating main client watcher loop"
I0815 09:13:16.654980 1 resource.go:207] Watch called with key: projectcalico.org/networkpolicies on resource NetworkPolicy
time="2024-08-15T09:13:16Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:14:56Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:14:56Z" level=info msg="Terminating main client watcher loop"
I0815 09:14:56.191850 1 resource.go:207] Watch called with key: projectcalico.org/caliconodestatuses on resource CalicoNodeStatus
time="2024-08-15T09:14:56Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:14:56Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:14:56Z" level=info msg="Terminating main client watcher loop"
I0815 09:14:56.768722 1 resource.go:207] Watch called with key: projectcalico.org/bgpfilters on resource BGPFilter
time="2024-08-15T09:14:56Z" level=info msg="Main client watcher loop"
time="2024-08-15T09:15:02Z" level=info msg="Process backend watcher done event in main client"
time="2024-08-15T09:15:02Z" level=info msg="Terminating main client watcher loop"
I0815 09:15:02.217377 1 resource.go:207] Watch called with key: projectcalico.org/globalnetworksets on resource GlobalNetworkSet
time="2024-08-15T09:15:02Z" level=info msg="Main client watcher loop"

use calicoctl node  status on master:
Calico process is running.

IPv4 BGP status
+---------------+-------------------+-------+----------+-------------+
| PEER ADDRESS  |     PEER TYPE     | STATE |  SINCE   |    INFO     |
+---------------+-------------------+-------+----------+-------------+
| <IP_ADDRESS> | node-to-node mesh | up    | 08:53:11 | Established |
+---------------+-------------------+-------+----------+-------------+

IPv6 BGP status
No IPv6 peers found.

use calicoctl node status on worker:
Calico process is running.

IPv4 BGP status
+---------------+-------------------+-------+----------+-------------+
| PEER ADDRESS  |     PEER TYPE     | STATE |  SINCE   |    INFO     |
+---------------+-------------------+-------+----------+-------------+
| <IP_ADDRESS> | node-to-node mesh | up    | 08:53:11 | Established |
+---------------+-------------------+-------+----------+-------------+

IPv6 BGP status
No IPv6 peers found.

Possible Solution
I have no idea

Steps to Reproduce (for bugs)
Just a normal deployment cluster

Both servers use the cri-dockerd container runtime
Initialize the cluster using kubeadm init --config=my-config.yaml
Use kubectl create -f tigera-operator.yaml
Use kubectl create -f custom-resources.yaml
Watch the pod status until they are all started
Use kubectl describe pod -n calico-system calico-node-7cwl2
Use kubectl run -i --tty --rm debug --image=busybox --restart=Never -- ping [calico-apiserver-ip], You can see

If you don't see a command prompt, try pressing enter.
^C
--- <IP_ADDRESS> ping statistics ---
72 packets transmitted, 0 packets received, 100% packet loss
pod "debug" deleted
pod default/debug terminated (Error)

Your Environment

Calico version: v3.26.4
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.30.1
Operating System and version: Ubuntu 20.04.6 LTS

@ja-mitiankai nothing is standing out to me as especially wrong here - logs look normal. What is the main symptom that you're trying to diagnose?

Warning  Unhealthy  29m  kubelet  Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused

This looks like it happened 29m ago but hasn't happened since, and is a potentially normal transient event as part of bootstrapping, so long as it doesn't persist. Considering your BGP statis is "Established", it looks like everything is working correctly.

72 packets transmitted, 0 packets received, 100% packet loss

I would expect a pod to be able to ping this IP, so that's potentially suspicious. Are other pods having trouble communicating?

@caseydavenport I can't communicate across nodes now. He looks fine, but he's not actually working properly. I want to try to use tcpdump to capture packets. I'm sorry, I don't know much about tcpdump.
node1 ip: <IP_ADDRESS> (master)
node2 ip: <IP_ADDRESS> (worker)
The pod I tested the ping command with is running on node1. name: debug, ip: <IP_ADDRESS>. command like this: kubectl run -i --tty --rm debug --image=busybox --restart=Never -- ping <IP_ADDRESS>
ip: <IP_ADDRESS> is csi-node-driver-9zbv7, and it is running on node2
route at node1:
<IP_ADDRESS> <IP_ADDRESS>         <IP_ADDRESS> U     0      0        0 *
<IP_ADDRESS> <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 cali5331bf8f64b
<IP_ADDRESS> <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 cali2f01c522b60
<IP_ADDRESS> <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 calie5460d1dd77
<IP_ADDRESS> <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 cali726ebf83671
<IP_ADDRESS> <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 calie3ba9b96e53
<IP_ADDRESS>  <IP_ADDRESS>   <IP_ADDRESS> UG    0      0        0 eth0

ip route at node1:
blackhole <IP_ADDRESS>/26 proto 80
<IP_ADDRESS> dev cali5331bf8f64b scope link
<IP_ADDRESS> dev cali2f01c522b60 scope link
<IP_ADDRESS> dev calie5460d1dd77 scope link
<IP_ADDRESS> dev cali726ebf83671 scope link
<IP_ADDRESS> dev calie3ba9b96e53 scope link
<IP_ADDRESS>/26 via <IP_ADDRESS> dev eth0 proto 80 onlink

route at node2:
<IP_ADDRESS> <IP_ADDRESS>   <IP_ADDRESS> UG    0      0        0 eth0
<IP_ADDRESS>  <IP_ADDRESS>         <IP_ADDRESS> U     0      0        0 *
<IP_ADDRESS>  <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 califdd333fac30
<IP_ADDRESS>  <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 calie923cf83e08
<IP_ADDRESS>  <IP_ADDRESS>         <IP_ADDRESS> UH    0      0        0 cali73b51134a71

ip route at node2:
<IP_ADDRESS>/26 via <IP_ADDRESS> dev eth0 proto 80 onlink
blackhole <IP_ADDRESS>/26 proto 80
<IP_ADDRESS> dev califdd333fac30 scope link
<IP_ADDRESS> dev calie923cf83e08 scope link
<IP_ADDRESS> dev cali73b51134a71 scope link

I use tcpdump -i calie3ba9b96e53 -nn. (calie3ba9b96e53: <IP_ADDRESS>)
tcpdump -i calie3ba9b96e53 -nn
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on calie3ba9b96e53, link-type EN10MB (Ethernet), capture size 262144 bytes
12:19:12.173454 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4462, length 64
12:19:13.173573 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4463, length 64
12:19:14.173701 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4464, length 64
12:19:15.173793 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4465, length 64
12:19:16.173884 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4466, length 64
12:19:17.173975 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4467, length 64
12:19:18.174075 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4468, length 64
12:19:19.174168 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4469, length 64
12:19:20.174274 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4470, length 64
12:19:21.174391 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4471, length 64
12:19:22.174484 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4472, length 64
12:19:22.420710 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
12:19:22.420740 ARP, Reply <IP_ADDRESS> is-at ee:ee:ee:ee:ee:ee, length 28
12:19:23.174589 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4473, length 64
12:19:24.174711 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4474, length 64

I use tcpdump -i eth0 icmp -nn | grep <IP_ADDRESS>. ( eth0:
<IP_ADDRESS>     <IP_ADDRESS>      <IP_ADDRESS>    UG       0         0           0    eth0)
tcpdump -i eth0 icmp -nn | grep <IP_ADDRESS>
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
12:19:57.178169 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4507, length 64
12:19:58.178264 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4508, length 64
12:19:59.178383 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4509, length 64
12:20:00.178462 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4510, length 64
12:20:01.178553 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4511, length 64
12:20:02.178654 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4512, length 64
12:20:03.178772 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4513, length 64
12:20:04.178855 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4514, length 64
12:20:05.178947 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4515, length 64
12:20:06.179033 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 1, seq 4516, length 64

I don't know where to go next using tcpdump.

Yep, sounds like the traffic is leaving the source node properly and then being dropped by your network fabric somewhere in the middle before reaching node2.
Where is this environment running?
Also just to confirm, it looks like you don't have any encapsulation enabled on your Calico IP pools - is that right?

I changed the encapsulation in the custom-resources.yaml file from VXLANCrossSubnet to VXLAN and my problem was solved. Thank you very much for your help. @caseydavenport

Cool, glad that helped. For some additional information:
That likely means your nodes were in the same subnet, but that something was dropping the traffic (e.g., reverse path filtering or AWS src/dst checks) because the node was sending traffic with the source / destination of pod IPs.
If you're on Amazon, that would be something like this: https://docs.tigera.io/calico/latest/reference/public-cloud/aws#routing-traffic-within-a-single-vpc-subnet

OK, thanks for your addition.


Mention a dedicated client for Node projects

This is good for now until we do #323.
Thanks! :cake:

:sunflower:


Improve README of examples

I had a look at the examples, but I still have no idea how to interpret them. I reckon that expanding the READMEs to describe what the example process does will be helpful in understanding how one's project pieces fit in the Surround framework.
I suppose that a couple of data analysis examples would also be very helpful, at least for me. I am thinking about "label cats vs dogs using a simple model", which teaches users where the processing code goes, how the config file is used in the context etc.
Another example could be a more complex routine, for example the bibs project, where several parts are at work, e.g. locating the bib, reading the numbers within etc.

I think this issue is addressed now that we have a lot of examples. Moreover, PR #63 also added description.


Add number of people watching to Discovery

This adds the current number of people watching to the live stream discovery cards for streams that are currently live.
We expect an optional integer value to be returned from the api for the key number_people_watching.
cc @Jwomers

Just added a signal to hide the number of people watching if the value is not available, that way we can merge this and when it's returned from the api it'll 'just work' 😄


Fix some spelling/grammar issues and some incongruent formatting

This pull request fixes some minor typos and grammatical issues, along with some incongruent formatting in lists/tables.

Thanks for fixing this, @dchristle! Merged.


[Intention] Remove image rendering from indices and concatenate indices analysis

Although we build and maintain a monolith, our AnalysisPrograms.exe application has the concept of actions. Each action acts like its own program and allows us to do a broad range of analysis for different types of studies. Packaging our application as a monolith is useful for maintenance and we won't be changing that.
Expected behaviour
Each action of our program should more or less do one thing. For example, we can generate indices, render a visualization, or run an event recognizer. This follows the Unix philosophy of creating programs (in our case, sub-programs/actions) that do one thing which allows users to compose the results as they like.
Actual behaviour
Two of our actions (indices generation and indices concatenation) are very complicated because they render a visualization. Generally, the default visualizations they render are only appropriate for some of the analysis input/configuration options that are available. The results are

visualization code that sometimes works or sometimes doesn't, depending on the analysis that was run
multiple code paths create a heavy maintenance burden.
complex command line and configuration switches that are unrelated to the main analysis, and are duplicate functionality of existing visualization actions
in the case of concatenate indices multiple (redundant) executions of index concatenation have to be done to render different visualizations (See recently introduced features from #138 )

Any other details
This change is a low priority enhancement that may not be implemented for a while. We encourage any interested stakeholders to comment on the issue.

Okay, We've since reversed our stance on this. The indices produced by the current concat command are unreliable.
We'd prefer people did quantitative analysis on raw indices from each source audio files, and used concat to produce images. This will reflect the defaults going forward.

Sorry to reopen this but I want to understand your logic.
The idea of "one command does one and only one function" makes things clean but it means every function must produce an output. In particular it means that concat would have to produce concatenated csv files. But you say these are unreliable. Why are they unreliable - is it because of timing issues i.e. recordings do not start on a minute?
One command - one function would work but then need to offer powershell scripts to tie workflows together.

In particular it means that concat would have to produce concatenated csv files.

Concatenate's primary utility thus far has been rendering images. I'm suggesting it should only do that.

Why are they unreliable - is it because of timing issues i.e. recordings do not start on a minute?

Yes, that's exactly why. With our current code, we produce images and indices that are not aligned to minutes of a day and can pad on every join. We can produce in some scenarios 1460 minutes per day! And that's an average case scenario, not worse case.

One command - one function would work but then need to offer PowerShell scripts to tie workflows together.

Absolutely not.


netcore build: fix runtime patch selection issues

Issue:
When switching between command line and IDE builds, the build will often fail
with an error similar to:
NETSDK1061: The project was restored using Microsoft.NETCore.App version
2.1.9, but with current settings, version 2.1.0 would be used instead. To
resolve this issue, make sure the same settings are used for restore and for
subsequent operations such as build or publish. Typically this issue can occur
if the RuntimeIdentifier property is set during build or publish but not during
restore. For more information, see
https://aka.ms/dotnet-runtime-patch-selection.
My understanding is that this can happen when the runtime used by the restore
operation does not match the runtime expected by the publish operation. As the
publish operation might not call restore itself, it will generate this error
when the runtime does not match the expected version.
To fix this, the BuildGVFSForMac.sh script will not include the runtime
identifier when calling restore. The projects that generate self-contained
applications will also set the TargetLatestRuntimePatch property to target
the latest runtime.

@jamill I had this same problem on my home machine after playing with Stryker.  I'll give this topic a try later to see if it fixes the issue.


why with all this drama, vs code shouldn't have no problem accepting such situation -should be a more simple button to download something

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Proposal to update ToPublicName to be go-idiomatic

Proposed change to generated Struct/Field names.
The names become CamelCase and abbreviations are fully capitalized.
Examples

full_name-> FullName
person_id -> PersonID
url -> URL

The dependency on snaker can be removed, if desired, as the code can be copied over and is fairly short.

Thanks, this is definitely a better way to generate idiomatic variable names :)
Since this is backwards-incompatible, I'm going to cut a v3 branch for gopkg.in at this point. The old-style names will still be available on the v2 branch.


Grid lines, horizontal and vertical

I tried to decorate every cell with a shape drawable having border lines to create grid lines over the view. But the borders meet creating a thick line and inconsistency with other cell, especially from the cells at the end and middle.

Maybe try using a twice smaller drawable instead


Replace kaniko with buildah in the build pipeline

Currently we are using kaniko to build & push the image.  Try to see if we can replace that with buildah bud & buildah push.

We updated kanino executor image with buildah in the build task of the pieplines, and tested successfully in our environment with below pipelines till now.

Nodejs-express
Nodejs
Spring-boot
Java-Microprofile

Remaining to be tested with the update
5. Nodejs-loopback
We have created a pull request for this in collections repo:
https://github.com/kabanero-io/collections/pull/80
Once we test with remaining pipeline, we will merge above pull request and mark this issue as done.


Make getJoinableTeams return a sorted array of teams

Summary
Make getJoinableTeams returns a sorted array of teams
This is as per comment on webapp - https://github.com/mattermost/mattermost-webapp/pull/1073#discussion_r184318356
Ticket Link
none
Checklist

[x] Added or updated unit tests (required for all new features)
[x] All new/modified APIs include changes to the drivers

Test Information
This PR was tested on: [mobile app on iOS 11.2/iPhone 8 simulator, Chrome/FF on MacOS]

@jwilander I updated this PR as I'm getting circular dependency error on webapp client when getCurrentUser is imported at team selectors. Please take a look again. Thanks!


Display clan information in clan tooltip

(Requires API support)

[x] Decide which information to show about clans
[x] Implement the tooltip

How about we style the dropdown so that it doesn't look like a dropdown until the user hovers over it?
Otherwise it will look very ugly I assume :)

Yeah i already thought about that... Not sure how to do that yet but ill find out ;)

I managed to do so


Highlights on search matches practically invisible

I've fixed it for myself by including following CSS items (you might consider adding them to the theme):
/* Search-related styles */
--jp-search-toggle-off-opacity: 0.6;
--jp-search-toggle-hover-opacity: 0.8;
--jp-search-toggle-on-opacity: 1;
--jp-search-selected-match-background-color: rgb(255, 225, 0);
--jp-search-selected-match-color: black;
--jp-search-unselected-match-background-color: rgb(255, 123, 0);
--jp-search-unselected-match-color: var(--jp-ui-inverse-font-color0);

Thanks for the contribution, just published an update with these changes to pypi.


[bug]: No tailwind css configuration found

Describe the bug
I have created a new Vite project and made all the changes as described on shadcn docs but after using npx shadcn@latest init the command, I am getting an error. That's why I am not able to use shadcn components.
Following error will be displayed:

Affected component/components
All
How to reproduce

Create a Vite project
Make changes as described on Vite installation docs
Use command npx shadcn@latest init

Codesandbox/StackBlitz link
No response
Logs
No response
System Info
Windows 11
Node v22.9.0

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Install tailwind first then use the shadcn command
https://tailwindcss.com/docs/guides/vite

I have the same problem.
Tailwind already is installed for me.

Had the same issue but managed to make it work by adding the tailwind directives to index.css. Looks to me like the shadcn docs are missing a step.
@tailwind base;
@tailwind components;
@tailwind utilities;

Had the same issue but managed to make it work by adding the tailwind directives to index.css. Looks to me like the shadcn docs are missing a step.
@tailwind base;
@tailwind components;
@tailwind utilities;

thank you

AFAICT nextjs/postcss/tailwind can presently work without any css files at all, whereas shadcn explicitly checks for a css file importing tailwind base (https://github.com/shadcn-ui/ui/blob/main/packages/cli/src/utils/get-project-info.ts#L149). Maybe just a simple bug where that check can get removed, or do a more complicated check for the right setup/versioning, especially if itxtoledo's WA worked.

The following code in index.css would cause the error
@import "tailwindcss/base";
@import "tailwindcss/components";
@import "tailwindcss/utilities";

But the following code in index.css works for me
@tailwind base;
@tailwind components;
@tailwind utilities;

shadcn/ui should be one step less, after installing tailwindcss, it needs to be configured so that shadcn/ui can correctly check tailwindcss.
@tailwind base;
@tailwind components;
@tailwind utilities;

Not sure if anybody else has this issue, but I'm installing shadcn in an Nx monorepo where I have multiple tailwind.config.js. Just tried to update shadcn/ui, but it's saying that there's no tailwind.config.js in the root directory. How can I work around this?
Happy to open up a new issue if need be, but figured this was something minor.

I don't think this works with monorepos. I have a monorepo too with turborepo and it couldn't recognize a valid tailwind config.

Fixed.


Clickable website link

Please add a clickable link to the website in the header of the repository.

Done.


Fix panic in apkdb parsing on empty "provides" values

A bug was introduced in https://github.com/anchore/syft/pull/1063 where Syft would panic if a package listed in the installed DB doesn't "provide" anything.
This PR reworks the logic so that Syft allows for empty "provides" values. It also adjusts the stripVersionSpecifier helper function to remove the possibility of panicking (index out of range).

Having trouble making sense of the failure logs: https://github.com/anchore/syft/actions/runs/3963383936/jobs/6791170964#step:6:159
Help appreciated 😃

@luhring we've updated this in main now where this CLI test is fixed - if you're able to merge from upstream you should no longer see this failure

I basically submitted the same fix for #1484, just in a different way.
Don't mind in which way this is fixed, though this also applies to "dependencies", not just "provides" from what I remember correctly.

@Nirusu Ah! I hadn't seen your PR, sorry — I'm glad you caught this. I actually like your solution better! I say we merge it, and I can close mine. My PR was just trying to stop the bleeding.
Yours might need a rebase, and I like the idea of incorporating the changes to stripVersionSpecifier to prevent panics in the future — but to me the first priority is preventing panics, which your PR does elegantly. 👏

@luhring  I'm going to merge the PR that @Nirusu  provided for this, however I do think keeping the stripVersionSpecifier fix also make sense -- if you'd like you could rescope this PR to just that enhancement or open another PR.

@luhring I'm going to merge the PR that @Nirusu provided for this, however I do think keeping the stripVersionSpecifier fix also make sense -- if you'd like you could rescope this PR to just that enhancement or open another PR.

Sounds good, thanks @wagoodman!

note: the force push was to rebase on the latest in main (fixes the failing CLI test)
changes made:

added some explicit tests for stripVersionSpecifier
removed the empty value check before calling stripVersionSpecifier


add pluto image (by Fairwinds)

New Image Pull Request Template
Image Size

[ ] The Image is smaller in size than its common public counterpart.
[ ] The Image is larger in size than its common public counterpart (please explain in the notes).
[X] There is no public image

Notes:
Image Vulnerabilities

[ ] The Grype vulnerability scan returned 0 CVE(s).
[ ] The Grype vulnerability scan returned > 0 CVE(s) (please explain in the notes).

Notes:
Image Tagging

[ ] The image is not tagged with version tags.
[ ] The image is tagged with :latest
[ ] The image is not tagged with :latest (please explain in the notes).

Notes:
Basic Testing - K8s cluster

[ ] The container image was successfully loaded into a kind cluster.
[ ] The container image could not be loaded into a kind cluster (please explain in the notes).

Notes:
Basic Testing - Package/Application

[ ] The application is accessible to the user/cluster/etc. after start-up.
[ ] The application is not accessible to the user/cluster/etc. after start-up. (please explain in the notes).

Notes:
Helm

[ ] A Helm chart has been provided and the container image can be used with the chart.  If needed, please add a -compat package to close any gaps with the public helm chart.
[ ] A Helm chart has been provided and the container image is not working with the chart (please explain in the notes).
[ ] A Helm chart was not provided.

Notes:
Processor Architectures

[ ] The image was built and tested for x86_64.
[ ] The image could not be built for x86_64 (please explain in the notes).
[ ] The image was built and tested for aarch64.
[ ] The image could not be built for aarch64. (please explain in the notes).

Notes:
Functional Testing + Documentation

[ ] Functional tests have been included and the tests are passing.  All tests have been documnted in the notes section.

Notes:
Environment Testing + Documentation

[ ] There has not been a request and/or there is no indication that this image needs tested on a public cloud provider.
[ ] The container image has been tested successfully on a public cloud provider (AWS, GCP, Azure).
[ ] The container image has not been tested successfully on a public cloud provider (AWS, GCP, Azure) (please explain in the notes).

Notes:
Version

[ ] The package version is the latest version of the package.  The latest tag points to this version.
[ ] The package version is the not the latest version of the package (please explain in the notes).

Notes:
Dev Tag Availability

[ ] There is a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base')
[ ] There is not a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base') (please explain in the notes).

Notes:
Access Control + Authentication

[ ] The image runs as nonroot and GID/UID are set to 65532 or upstream default
[ ] Alternatively the username and GID/UID may be a commonly used one from the ecosystem e.g: postgres
[ ] The image requires a non-standard username or non-standard GID/UID (please explain in the notes).

ENTRYPOINT

[ ] applications/servers/utilities set to call main program with no arguments e.g. [redis-server]
[ ] applications/servers/utilities not set to call main program with no arguments e.g. [redis-server] (please explain in the notes)
[ ] base images leave empty.
[ ] base image and not empty (please explain in the notes).
[ ] dev variants is set to entrypoint script that falls back to system.
[ ] dev variants is not set to entrypoint script that falls back to system (please explain in the notes).

CMD

[ ] For server applications give arguments to start in daemon mode (may be empty)
[ ] For utilities/tooling bring up help e.g. –help
[ ] For base images with a shell, call it e.g. [/bin/sh]

Environment Variables

[ ] Environment variables added.
[ ] Environment variables not added and not required.

SIGTERM

[ ] The image responds to SIGTERM (e.g., docker kill $(docker run -d --rm cgr.dev/chainguard/nginx))

Logs

[ ] Error logs write to stderr and normal logs to stdout. Logs DO NOT write to file.

Documentation - README

[ ] A README file has been provided and it follows the README template.

Dear chainguard maintainers, I saw that some nice person submitted pluto yesterday, so I thought I would try to prepare the pluto image.
I based this on the helm image, which also only contains the helm golang binary and thus should be similar.
There might be things that I messed up or overlooked, so please check thoroughly and point out what I can improve.
Thanks in advance,
Johannes
(off reading the docs again)

As part of a Chainguard effort to reduce code duplication and provide higher quality images, we have stopped accepting pull requests for changes to images in this repository. Due to this, we are closing all pull requests today in order to start fresh.
If you think this pull request was closed in error, please feel free to re-open this pull request or open an issue and we will try to help you out. Thank you!

Actually I still think this would be useful. I have not yet gotten around to fully understand if there is something missing in this PR, so I am not sure if it makes sense to reopen it.


Black area on desktop after electron close

After the electron window has been attached to the desktop, the area where the electron app is displayed will be left black after the app quits. The only way to prevent it is to refresh() the window before the app quits (on BrowserWindow's close event). Detaching the window without refresh() afterwards also cause the black area problem. Manually refeshing the desktop after the app quits doesn't restore the area. I have to actually change the desktop wallpaper to restore that black area.

Can you please tell me what windows version u using? ( 10 or 11 ).
And the code where refresh function is used.

Windows 10 Home 22H2
The code is something like this
mainWindow.on("close", function () {
  refresh();
});

And whenever detach is used.
detach();
refresh();

If refresh is missing, the desktop area behind the electron window will become black.

if u closed the window before detaching you will face the black screen 100%.
so if u call
detach();
refresh();

and it still result a black screen?

As long as the refresh() is there the desktop won't go black. Maybe you should update the readme and inform the users that they need to do so.

I did mention it in the Readme but it wasn't clear why you should call refresh if u closed the window before detaching, I'll include it next commit.
Because no issue is here I'll close it, thanks.


add example

this is a an example on how to listen to tx pool inspect

ty
but there's something wrong with the deps that needs fixing

my pleasure, no problem
i think it's because the cargo.toml because the code work fine in my pc

how can i fix those error?


vfs_mount not working, but regular SD communication is.

I was using the library with no problems when suddenly, I got an error saying unable to open database file. I thought I was doing something wrong with the code or the wiring, but when I tried to use the SD with SD.h, it did open, so it is the function.
I found out that it returns NULL in case of an error, and indeed it does, but I haven't changed the code or the wiring, so I don't know what the error is.
This is my code:
void setup(void) {
  Serial.begin(115200);
  Wire.begin();
  RTC.begin();
  SPI.begin();
  nfc.begin();

  if (vfs_mount("/SD0", D8) == NULL)
    Serial.println("Unable to set vfs");

  if (RTC.lostPower())
    RTC.adjust(DateTime(F(__DATE__), F(__TIME__)));

  sqlite3_initialize();

  Serial.println("System initialized");
}

And on behalf of the SD, I am wiring:

D5 → SCK
D6 → MISO
D7 → MOSI
D8 → CS

I hope I am doing something wrong to fix it quickly.
Thanks for any help.

Hi, sounds like there could be some noise in the connections.
Try lowering the SPI speed (optional parameter to begin()).
Please also use shorter wires for the above connections.
If possible use a PCB with ground planes covering these lines.

Hi! Thanks for the reply.
I am using the shortest jumper wires available, I even changed them.
How do I lower the speed? It says that SPI.begin() takes no parameters, so it is not from there. If you need any more of my code, I will provide it.

Hi, please see this for changing clock speed:
https://github.com/siara-cc/esp_arduino_sqlite3_lib/issues/21#issuecomment-1140217727
I have not tried it, but I know that higher speeds often cause issues.  You may have to wade through docs to find out how to set it, if that is causing your issue.  I am not sure what else could be the problem.
Another potential issue is number of files open which also I remember can be set when initialising SPIFFS/LITTLEFFS.

Nope, it is still not working. I reestarted the project, but it is still not working.

Maybe I can go buy an esp32 and try with that, or change the esp8266. What do you think is the best option? Cause if it suddenly stopped working, it must be something with the hardware, and I can't determine what it is.

I found another way to lower the speed and indeed it worked. I had to go to .SdFat\src\SdCard\SdInfo.h, to check the speed definitions. FULL and DIV3 speeds don't work, I had to copy SPI_HALF_SPEED. Then paste it SdFat\src\SdFat.h in the functions begin and cardBegin, replacing the SPI_FULL_SPEED in the parameters of the functions (you can find these by CTRL + Click in begin in if (!sdFat->begin(num)) inside Sqlite3 for ESP8266\src\sdfat_fns.cpp).
Thank you for your time.

Great!  I have faced this issue before quite some time ago and thats why I could related to your issue.
Wires or even PCB lines pick up noises from nearby lines or static unless shielded with Ground.  So with faster speeds the detection of 0 or 1 for digital communication is more erratic because of the noises.  Electromagnetic noises cause less interference at lower speeds as the MCU has more time to detect 0 or 1.  The second problem is that jumper wires are highly prone to loose contact.
So it is always better to make a PCB instead of using wires for connection and there are rules to how much gap should be present between lines and where possible make sure the lines are surrounded by Ground planes with vias to other side.


CheckBox issue

OpenUI5 version: 1.48.5 (issues also exist for older versions like 1.46)
Browser/version (+device/version): Chrome 59.0.3071.115, MacBookAir macOS: 10.12.4 (16E195)
The issue seems to be an internal sap.m.Label problem inside CheckBox control. It appears sometimes. In general the view works fine but when navigating in app and coming back to this view the following error can appear (but not always, sometimes):
control definition in xml:
<m:CheckBox id="idcb1" class="sapUiSmallMarginBeginEnd" text="{i18n>field1}" selected="{selection>/field2}" select="xxx"/>
`
Error message in console log:

Uncaught (in promise) Error: "Element sap.m.Label#__xmlview5--idcb1-label" is not valid for aggregation "_label" of Element sap.m.CheckBox#__xmlview5--idcb1
at f.j.validateAggregation (ManagedObject-dbg.js:1614)
at f.j.setAggregation (ManagedObject-dbg.js:1663)
at f.a._getLabel (CheckBox-dbg.js:311)
at f.a.setText (CheckBox-dbg.js:167)
at f.j.updateProperty (ManagedObject-dbg.js:3079)
at constructor.w (ManagedObject-dbg.js:2928)
at constructor.a.fireEvent (EventProvider-dbg.js:229)
at constructor.B._fireChange (Binding-dbg.js:247)
at constructor.R.checkUpdate (ResourcePropertyBinding-dbg.js:49)
at constructor.B.initialize (Binding-dbg.js:373)

Hi @jobberwalker
can you please provide some snipped that reproduces the issue or can you tell me is it reproducible here: https://sapui5.hana.ondemand.com/explored.html#/sample/sap.m.sample.CheckBox/preview ?
Thanks & Kind Regards,
Gery

Hello,
in the example you provided the text property of checkbox is not binded to model. I will try to prepare test app to reproduce this issue and come back to you.
JB

Hello,
I was not able to reproduce this issue into repeatable procedure. It was happening randomly. I have found an workaround which is working now. I have removed text property from checkbox controls and added an extra label control with the same text. Please note this text property from checkbox was binded to i18n model only. For now everything works fine.
JB

@jobberwalker if you have time, we will appreciate it to send us an example that reproduces the problem.  Also check what is included in the i18n resources and how it affects the reproduction of the problem.

I am closing this one as there is no activity in the thread. Feel free to open a new thread linking this issue, if you want to continue the discussion


fix: fix license classifier

Hey 👋🏻,
I am currently looking into licensing at Home Assistant, and I found that we could not detect the license of this library properly. According to pyproject.toml documentation about the license field:

If you are using a standard, well-known license, it is not necessary to use this field. Instead, you should use one of the classifiers starting with License ::. (As a general rule, it is a good idea to use a standard, well-known license, both to avoid confusion and because some organizations avoid software whose license is unapproved.)

If you could do a release after this PR, and maybe bump in Home Assistant, that would be awesome :)

This isn't necessary anymore. Hatchling will use license = MIT to populate the new License-Expression field.
https://hatch.pypa.io/1.11/config/metadata/#spdx-expression


HA App crashes with long name templates because history-explorer-cards

The Home Assistant app was crashing right after opening on some devices. I found that the problem went away if I deleted the history-explorer-cards, so I've been testing until I found the problem. I couldn't see logs because I don't understand, so it was a trial and error search.
The problem is caused by templates with long names. In my case I had one with 65 characters. The funny thing is that it worked perfectly on the PC, as well as on some mobiles, but it blocked the application on others. Reducing the number of characters in the name solved the problem.
Name of the template that was causing me problems: "sensor.thermo_lavadora_congelador_frigochico_frigo_cocina_vitro_pc".
Mobile where it crashed: Doogee N10, Redmi Note 9S with MIUI 13.0.2, Poco X5 5G with MIUI 14.0.6
Mobile where it worked fine: Redmi Note 8 Pro MIUI 12.5.7
Latest stable versions of Home Assistant (Docker) and history-explorer-card (HACS) existing at the time of writing this issue.

Sadly the history explorer card has been declared end of life and won't be developed anymore. So I will have to close this issue / FR without resolution. This repository will be archived and set to read-only shortly.
See this post on the HA forum for more information:
https://community.home-assistant.io/t/new-interactive-history-explorer-custom-card/369450/978


remove map_merge from lunar

I have decided to do binary release only for upcoming melodic via #17882. This removes the doc job from lunar to avoid confusion on the wiki.

In general we recommend having the doc and source entries there in case users want to use packages from source even if you're not going to release binaries. We work to differentiate the availability of binary packages from just having documentation.

Sounds reasonable.
The trouble is that while this package works with ROS lunar, it also needs PCL>=1.8. So basically it works only with Debian Stretch ROS Lunar combination. This causes confusion to users (https://github.com/hrnr/map-merge/issues/1). I think it is more clear to only have this available in melodic, which have PCL>=1.8 available on every supported distro.
I'm sorry for introducing this package to lunar at the first place, but was working on Debian and I only realised the PCL problem later.

Ok, that makes sense.


regress-sv_function11_iv

Surelog issue: https://github.com/chipsalliance/Surelog/issues/2328

Issue fixed.


docs: update readme 2

update readme 2

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy


fix #140, add matrix.map

#140 wasn't broken, per se, but an in-place operation is deceiving. as mentioned in that issue, it would be nice to have a separate function for an in-place operation, in case it's needed. perhaps a suffix of IP would be suitable.
matrix.applyFunction takes a matrix (or vector) and applies a function to every element to a copy of the matrix (not in-place!). the purpose behind this function is to imitate how some of Numpy's functions operate element-by-element on Numpy arrays. so instead of writing matrix.sin, matrix.cos... etc. the user can just pass this function.
the catch: the function passed can only take one parameter, so it would be nice (and pretty simple, methinks) to create something that would behave like so:
f = function(x, a, b) {
  return a*x + b;
}
var m = [[1,2,3],[4,5,6]];

var m2 = matrix.applyFunctionNEW(m, f, a, b);

so that any additional parameters passed to matrix.applyFunctionNEW (name is a work in progress) are passed to f too.

Shouldn't this be called a "map" function?

Yes you're correct. I was struggling to come up with a name. Will fix in a
bit
On Jun 6, 2015 5:51 PM, "Philip I. Thomas"<EMAIL_ADDRESS>wrote:

Shouldn't this be called a "map" function?
—
Reply to this email directly or view it on GitHub
https://github.com/numbers/numbers.js/pull/147#issuecomment-109653311.

@KartikTalwar mind reviewing this? should only take a minute :hamburger:

Mostly lgtm :hamburger:

looking at some benchmarks, doing a direct call is faster. I think doing this for a single argument is okay, but if we want to generalize it we can use apply.

Cool, feel free to merge
On Sunday, June 7, 2015, Dakota St. Laurent<EMAIL_ADDRESS>wrote:

looking at some benchmarks
https://jsperf.com/function-calls-direct-vs-apply-vs-call-vs-bind/6,
doing a direct call is faster. I think doing this for a single argument is
okay, but if we want to generalize it we can use apply.
—
Reply to this email directly or view it on GitHub
https://github.com/numbers/numbers.js/pull/147#issuecomment-109809159.

anyone have a suggestion for the name of the second version of matrix.map?


[Suggestion] Lily Pad renewability

The new Lily Pad items currently have no way to renewably collect them! I have some suggestions here.
Minecraft Lily Pads can be obtained through fishing, as well as the Wandering Trader. This should be turned into a tag instead, which includes the vanilla and all three modded items.
The Giant Lily Pad, when flowering, should drop a Giant Lily Pad seed. It could also be implemented that using Bonemeal on a flowering Giant Lily Pad will drop a seed item, whatever fits the mod better.
Small Lily Pads I have an additional suggestion for, it would be nice to mimic the way Pink Petals were implemented. Be able to place 1-4 and rotate them as the player desires. This could work by placing the Small Lily Pad item up to four times, as well as using Bonemeal to increase the count by one. Once the block hits 4, any additional Bonemeal just drops a Small Lily Pad item into the world. This would then also function for making them renewable!

Added all of the above, except I did not add a tag, I hardcoded them in.


GSSOC'24 Want to LLM Related projects

Is your feature request related to a problem? Please describe.
Yes, with the rapid advancement of language models (LLMs), there's a growing demand for opportunities to explore, contribute to, and learn from projects related to this field.
What if we make new folder for only project realted to generative AI or LLM based project
Describe the solution you'd like.
By using API like Gemini and chatgpt we can make many generative AI and LLM realted project and also using framework like langchain
Describe alternatives you've considered.
we can also make project on RAG based techniques
Add any other context or screenshots about the feature request here.
No response
@Kushal997-das

Hey @Kushal997-das can you add label gssoc and level1, level2, or level3
and also I am gonna add GenAI related projects and I will do it from strach so make it level 3.

Hey @Kushal997-das can you add label gssoc and level1, level2, or level3 and also I am gonna add GenAI related projects and I will do it from strach so make it level 3.

Sure , but level I'm suppose to add .

@Kushal997-das can you change level 1 to level 2 or 3 ? Because I am gonna add GenAI project from scratch


Issue 437  Ignore order of points for bounding box caching

Should close #437, thank you @TNT0305 for bringing this up and proposing a solution.

Pull Request Test Coverage Report for Build 1226

0 of 8 (0.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 43.447%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/tegola/cmd/cache.go
0
8
0.0%

Files with Coverage Reduction
New Missed Lines
%

provider/gpkg/binary_header.go
2
100.0%

Totals

Change from base Build 1224:
-0.008%

Covered Lines:
4916

Relevant Lines:
11315

💛  - Coveralls

yw...stupid fingers!  :p
On Thu, Jun 28, 2018 at 8:00 PM Julio<EMAIL_ADDRESS>wrote:

@ear7h commented on this pull request.
In cmd/tegola/cmd/cache.go
https://github.com/go-spatial/tegola/pull/444#discussion_r199029164:

_, xi, yi := upperLeft.ZXY()

_, xf, yf := bottomRight.ZXY()

_, xi, yi := corner.ZXY()

_, xf, yf := diagCorder.ZXY()

// ensure the initials are smaller than finals

if xi > xf {xi, xf = xf, xi}

if yi > yi {yi, yf = yf, yi}

oops, thank you for catching that
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/go-spatial/tegola/pull/444#discussion_r199029164, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFTXI5aCzTSepMV9JLATiDbgXtZPAwmHks5uBXwwgaJpZM4U8OQW
.

@ear7h should this PR be closed and not merged pending the work happening on cache-seed branch?


Develop

Pull Request Test Coverage Report for Build 10

5 of 5 (100.0%) changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 8:
0.0%

Covered Lines:
16

Relevant Lines:
16

💛  - Coveralls


cuDNN v8.3.2

Close #34. Close #35. Close #36. Close #37.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

TODO after merge: remove the ppc64le branch.

My hypothesis is we should copy zlib.dll from libzlib, rename it to zlibwapi.dll, and distribute it with cuDNN. But I don't have a way to verify if this would work (nor do I have bandwidth for this extra surprise).

Alternatively, we can redistribute zlibwapi.dll provided by NVIDIA (just like we redistribute cuDNN).

Alternatively, we can redistribute zlibwapi.dll provided by NVIDIA, pretending it's part of cuDNN (just like we redistribute cuDNN).

This is done in b35e330. Let me know if it's acceptable, if not I'll revert.

@jaimergp do you have thoughts on Windows here?

@leofang anything holding this (and cudnn84xx) from being released here?

Or, sorry, @IvanYashchuk...

oh what a minefield lol, I am also going to say bye! (but it would be great to get this going again, thanks friends!)

(realistically can we drop windows and move on? maybe not... but asking as someone who hasn't used windows since the early 2000s...)

Now that you mentioned, it's probably worth considering. I didn't consider it because it'd be a bit annoying to add Windows when it's ready while other versions already move away.

We can merge this PR once https://github.com/conda-forge/zlib-feedstock/pull/54 is merged. I'm sorry that PR was blocked on me, I just resolved the conflict and addressed review feedback there, so I hope it can be merged soon.

No worries Ivan, thanks for taking over 🙂

Thanks @IvanYashchuk, we are all here to help --- it is a community effort :)
Do you know what the procedure is like to get cudnn 84xx up here too? It seems everything is manual... but I am happy to help initiate it

My plan was to get this done first and then update to v8.4.x, which would be easier.
In the long run, we want the conda-forge bot to automatically pick up version updates for NVIDIA packages, and https://github.com/regro/cf-scripts/pull/1530 is the first step. But we are still working with the cuDNN team to make sure this is applicable to cuDNN (which it isn't at the moment).

Friends, let's skip windows...........

Actually you know better, I will stay out of this 😅

This is my thinking. If we shrink the build matrix now, and keep releasing new versions for non-Windows platforms, we're essentially leaving Windows users behind, but we originally "promised" to support (not in the literal sense, ofc). Another consideration is on the completeness: This would result in some versions of cuDNN missing on anaconda.org, but only for Windows. It'd be confusing for users to find
conda install -c conda-forge cudnn=8.3.2

works on Linux but not on Windows. Let's wait for @IvanYashchuk to make the final call.

This is my thinking. If we shrink the build matrix now, and keep releasing new versions for non-Windows platforms, we're essentially leaving Windows users behind, but we originally "promised" to support (not in the literal sense, ofc). Another consideration is on the completeness: This would result in some versions of cuDNN missing on anaconda.org, but only for Windows. It'd be confusing for users to find
conda install -c conda-forge cudnn=8.3.2

works on Linux but not on Windows. Let's wait for @IvanYashchuk to make the final call.

Is it me or are the nvidia people not actually interested in actually getting the nvidia packages across the line here? 😆

This is my thinking. If we shrink the build matrix now, and keep releasing new versions for non-Windows platforms, we're essentially leaving Windows users behind, but we originally "promised" to support (not in the literal sense, ofc). Another consideration is on the completeness: This would result in some versions of cuDNN missing on anaconda.org, but only for Windows. It'd be confusing for users to find
conda install -c conda-forge cudnn=8.3.2

works on Linux but not on Windows. Let's wait for @IvanYashchuk to make the final call.

Is it me or are the nvidia people not actually interested in actually getting the nvidia packages across the line here? 😆

To be fair I joined Nvidia 3 weeks ago and all of this as for many others is all volunteering effort.

To be fair I joined Nvidia 3 weeks ago and all of this as for many others is all volunteering effort.

Same here. I wasn't hired for doing conda-forge at all. It's all volunteering effort, and Ivan and I do not represent NVIDIA. Some are paid to do it, but not us.

If there is any concern, I am happy to communicate offline via email or other means, but I don't think continuing this discussion in this PR or any public space is appropriate, especially if it's just a tease.

@conda-forge-admin please rerender

@conda-forge-admin please rerender

Looks like the CDN has not been synced yet...
$ conda search --platform win-64 libzlib-wapi
Loading channels: done
No match found for: libzlib-wapi. Search: *libzlib-wapi*

PackagesNotFoundError: The following packages are not available from current channels:

  - libzlib-wapi

@conda-forge-admin, please restart ci

I think there're some issues with CDN starting yesterday/today. I've seen other packages (ex: libarchive) whose recent builds are not visible to the conda/mamba solver either.

Thanks, John! Looks like the CDN just restored. Let's give it a shot.
@conda-forge-admin restart ci

@conda-forge-admin rerender

Thanks @leofang, this is great 🥳

Thanks, @IvanYashchuk and all!


Unable to create charts using REST api

Hello
I am using apache superset in my platform that I am building at the moment. One of the features of this platform is to create basic visualizations on a given dataset. To do this I am working with the REST api of superset (as documented here: https://superset.apache.org/docs/rest-api). Currently I am trying to create charts using this api but I have stumbled upon a problem.
The problem is that upon calling the api, a response is send back with status code 500 and the message "fatal error"

I have provided a code snippet that makes the POST request to create a chart. At first the access token is retrieved (which seems to work). This token gets added to the headers of the actually request. The payload is hardcoded for now just to see if the chart is actually created. I should note that it is possible to manually login in superset and using swagger/v1, to create a chart using the payload used in the given code snippet.
code snippet:
...
@router.post("/chart/")
async def create_chart(datasource_id: int, viz_type: str, client: AsyncClient = Depends(superset_connection.get_superset_client)):
dataset = await get_dataset(datasource_id, client)
login = {
    "password": "admin",
    "provider": "db",
    "refresh": True,
    "username": "admin"
}

headers = {
    'Content-Type': 'application/json'
}
response = await client.post(url='/security/login', headers = headers, json = login)

token = response.json()['access_token']

headers = {
    'accept': 'application/json',
    'Authorization': 'Bearer ' + token,
    'Content-Type': 'application/json'
}

# payload for POST request
payload = {
    "cache_timeout": 0,
    "dashboards": [],
    "datasource_id": 9,
    "datasource_name": "ob201",
    "datasource_type": "table",
    "description": "lorem ipsum",
    "owners": [],
    "params": "",
    "slice_name": "test_slice",
    "viz_type": "table"
}

response = await client.post(url="/chart", json = payload, headers = headers)

# verify if request has succeeded
if(response.status_code != 200):
    raise HTTPException(status_code=response.status_code, detail=response.json())

return response

...
Stack trace:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/flask_appbuilder/api/init.py", line 84, in wraps
return f(self, *args, **kwargs)
File "/app/superset/views/base_api.py", line 80, in wraps
duration, response = time_function(f, self, *args, **kwargs)
File "/app/superset/utils/core.py", line 1400, in time_function
response = func(*args, **kwargs)
File "/app/superset/utils/log.py", line 217, in wrapper
value = f(*args, **kwargs)
File "/app/superset/charts/api.py", line 274, in post
new_model = CreateChartCommand(g.user, item).run()
File "/app/superset/charts/commands/create.py", line 46, in run
chart = ChartDAO.create(self._properties)
File "/app/superset/dao/base.py", line 104, in create
db.session.add(model)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/scoping.py", line 163, in do
return getattr(self.registry(), name)(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 2019, in add
self._save_or_update_state(state)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 2036, in _save_or_update_state
"save-update", state, halt_on=self.contains_state
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/mapper.py", line 3104, in cascade_iterator
halt_on,
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/relationships.py", line 1937, in cascade_iterator
tuples = state.manager[self.key].impl.get_all_pending(state, dict)
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/attributes.py", line 1148, in get_all_pending
for c in current
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/orm/attributes.py", line 1148, in
for c in current
File "/usr/local/lib/python3.7/site-packages/werkzeug/local.py", line 347, in getattr
return getattr(self._get_current_object(), name)
AttributeError: 'AnonymousUserMixin' object has no attribute '_sa_instance_state'
<IP_ADDRESS> - - [22/Mar/2021:19:45:49 +0000] "POST /api/v1/chart/ HTTP/1.1" 500 26 "-" "python-httpx/0.17.1"
I tried to search to related problems but I can't seem to find something similar. What are the possible causes of this? I was thinking that I did something wrong in configuring superset but I can't seem to put my finger on it.

@dpgaspar does the auth token correctly set the current user?

+1
I'm also encountering this problem.
@junlincc Not sure this is a question: @nytai Is this "Fatal error" due to a configuration error or should this issue be labeled as "bug"?

@timwil
The auth token should correctly set the user, using the default configuration to invoke the API programatically you have to send the CSRF token also. AnonymousUserMixin error, seems that chart POST is allowed by an anonymous user, do you have PUBLIC_ROLE_LIKE set?

@dpgaspar
Getting same error. AttributeError: 'AnonymousUserMixin' object has no attribute '_sa_instance_state'
I am passing a JWT Auth token of user which also has Admin as well as Gamma role.
AUTH_ROLE_PUBLIC = 'Gamma'
PUBLIC_ROLE_LIKE = 'Gamma'
and in the Gamma role, i have can read on & can write on permission of ReportSchedule.

The CSRF token header is X-CSRFToken. Not sure why you're getting that error as as you're logging in as a user. Which role does the user have you're logging into /api/v1/security/login? I would remove the AUTH_ROLE_PUBLIC = 'Gamma' and
PUBLIC_ROLE_LIKE = 'Gamma' and try again.

Not sure why you're getting AnonymousUserMixin as the user should not be anonymous

@nytai I m getting token for Admin role. I tried removing AUTH_ROLE_PUBLIC = 'Gamma' and PUBLIC_ROLE_LIKE = 'Gamma' and tried. Getting 401 unauthorised error. Even I am passing JWT bearer token.
Did superset init and then tried, no luck.
I am making a API call from the node server, so I do not have any cookies. Do we need session cookies or anything else along with JWT token.

@anilvpatel21 I am facing this same issue while creating dashboard. Tried the fixes above to test it but unfortunately didn't work. Could you paste your superset_config.py over here? If you can include the complete sample code that will be also great!
Superset version: 1.3

For now, did a workaround mentioned in https://github.com/apache/superset/issues/16398 to login into the website and obtain the auth cookie & proceeding to create the dashboard afterwards.


[Feature] WAcentric Homepage

Does not have vanity URL; current url will be /wa-landingpage
Possible to change it to something nicer? (and consistent)
Add permalink: /wa-nice-landing/ under home: true in the YAML frontmatter

Please see


Move docker

Move the docker files and such into src. Delete duplicates of various folders (src, utils) that we've accumulated

All unit tests passed, I think integration tests passed


Update engine list

I didnt seen engines with custom languages support and I think people should see this uniq system.

i will say nice add! but also are you able to make things maybe juuust a bit less verbose? then I'll merge it in all nice!


Example not working

Hi
Describe the bug
I'm running the example from the 'colab tutorial' and this is the result I get.
from mmdet.apis import inference_detector, init_detector, show_result_pyplot

# Specify the path to model config and checkpoint file
config_file = r'/home/mb2/Dan/mmdetection/configs/mask_rcnn/mask_rcnn_r50_fpn_mstrain-poly_3x_coco.py'
checkpoint_file = r'/home/mb2/Dan/mmdetection/checkpoints/mask_rcnn_r50_caffe_fpn_mstrain-poly_3x_coco_bbox_mAP-0.408__segm_mAP-0.37_20200504_163245-42aa3d00.pth'

# build the model from a config file and a checkpoint file
model = init_detector(config_file, checkpoint_file, device='cuda:0')

img = r'/home/mb2/Dan/mmdetection/demo/demo.jpg'
result = inference_detector(model, img)
show_result_pyplot(model, img, result, score_thr=0.3)

No bounding box's

Does this script have any log printed out?

That's the only thing in printed:
load checkpoint from local path: /home/mb2/Dan/mmdetection_old/checkpoints/mask_rcnn_r50_caffe_fpn_mstrain-poly_3x_coco_bbox_mAP-0.408__segm_mAP-0.37_20200504_163245-42aa3d00.pth
/home/mb2/Dan/mmdetection_old/mmdet/datasets/utils.py:69: UserWarning: "ImageToTensor" pipeline is replaced by "DefaultFormatBundle" for batch inference. It is recommended to manually replace it in the test data pipeline in your config file.
  'data pipeline in your config file.', UserWarning)

I have the same problem ,but in windows sys
When I run this: result = inference_detector(model,img)
then,get errors:
C:\Anaconda\envs\mmdet\lib\site-packages\mmdet\datasets\utils.py:69: UserWarning: "ImageToTensor" pipeline is replaced by "DefaultFormatBundle" for batch inference. It is recommended to manually replace it in the test data pipeline in your config file.
'data pipeline in your config file.', UserWarning)
C:\Anaconda\envs\mmdet\lib\site-packages\torch\nn\functional.py:718: UserWarning: Named tensors and all their associated APIs are an experimental feature and subject to change. Please do not use them for anything important until they are released as stable. (Triggered internally at  ..\c10/core/TensorImpl.h:1156.)
return torch.max_pool2d(input, kernel_size, stride, padding, dilation, ceil_mode)


feat: Add warning for Snap installations

Needs testing
closes #398

Rebasing to resolve conflicts and clean up the history.
No review existed and the prior state was broken so I force pushed.
Future changes will be additional commits.

As for testing, I guess we'll just do it in production ¯\_(ツ)_/¯

I've tested it by manually injecting values on an Ubuntu LTS Desktop install.
steamlocate-rs does not currently support snap, https://github.com/WilliamVenner/steamlocate-rs/pull/30

Welp, guess we just future proofed then a bit, haha


fix: replace cfg = "host" with cfg = "exec"

This is a no-op cleanup, 'host' is being renamed to 'exec', see: https://github.com/bazelbuild/bazel/issues/17032
Fixes #2514 ☕

/gcbrun


If I switch between two vim windows, audo save does not work.

Hi @Shandun, the autosave functionality is only intended to work when navigating from Vim to tmux, but does not fire when navigating between two vim windows.
If you'd like to have autosave when navigating between vim windows you could implement that entirely outside this plugging by adding something like the following to your vimrc:
autocmd BufLeave * update

Hope that helps!

Hi @christoomey , your solution works perfectly! That's what I really want for weeks. Thanks very much!


conditionals

if ... else statements
eq op
neq op
function lang tests

Conditionals
Conditional statements allow a block of code to be executed if a condition is true or if specified, execution of an alternative block.
if...else statements
if (true) {
  /* code to run if condition is true */
} else {
  /* run some other code instead */
}

else block is optional, one can use if statements without it.
Example:
if (true) {
  /* code to run if condition is true */
}

New Operators
| ==   | Equal | 1 == 2|
| !=   | Not Equal | 2 != 1|
| ||   | Or | true \|\| false|
| &&   | And | true && false|

Mostly LGTM. Just a handful of comments.

squashed :point_right:  e9b7ca2c988616968ff250e0c359a5e6487a7775

bors try

we can do an r+.
bors try-

bors r+


Add documentation

As this project is listed on the GitHub developers page, and being the only Android SDK / API for GitHub, could you provide documentation to show how this can be used.
Ideally something similar to the example on this project's README, but showcasing all of the features and how they can be used in Android.

I have to add a Wiki pages for it, i will do at holidays, thanks

Thank you

This is really necessary. The current "INIT" section of the README is not really obvious at all :/. Also, all the old 1.x authentication classes are gone, with no migration strategy.

I added a wiki section, check it out

Thanks.
It's a great improvement, however I was wondering whether there could be documentation on getting a list of repositories, or using other features of the SDK.
Thanks again.

It's in the roadmap


Need to optimize performance

CPU Time per execution is >10ms for 99th percentile, which is over the limit of Cloudflare Workers free plan.

As of #8, performance issue is partly resolved.


verticle-deploy with options

more like a feature request: command 'verticle-deploy' doesn't come with the possibility to add deployment options. If a second argument (json-string?) is given, a verticle with deployment options could be deployed from the shell (which would be nice, since verticles without any config/options are pretty rare)

+1

@vietj kindly see #29

@EmadAlblueshi thanks for the contribution!


change port for arminc/clair-db as a docker postgresql container is running on the same port

Hi, could you please let me know while running the command
docker run -p 5432:5432 -d --name db arminc/clair-db:2017-09-18 , i already have a postgres container for my project running on that 5432 port, if i simple change
docker run -p 5432:5432 -d --name db arminc/clair-db:2017-09-18 this port number to
docker run -p XXXX:XXXX -d --name db arminc/clair-db:2017-09-18 would the scanner work fine or does it gives any error?

You can't change the port that easily because it is configured in clair here https://github.com/arminc/clair-local-scan/blob/master/clair/config.yaml. You can do two things:

Create your own Docker container with Clair - here is the one I provide -> https://github.com/arminc/clair-local-scan/tree/master/clair and change the port there
Instead of exposing the DB port link the DB container with the Clair container trough Docker

Thanks , i will check it and let you know :)

Hi, can you just throw some light on how to build the container after
modifiying the DB port in config.yaml in
https://github.com/arminc/clair-local-scan/tree/master/clair
On Tue, Jul 31, 2018 at 12:02 PM Armin Coralic<EMAIL_ADDRESS>wrote:

You can't change the port that easily because it is configured in clair
here
https://github.com/arminc/clair-local-scan/blob/master/clair/config.yaml.
You can do two things:

Create your own Docker container with Clair - here is the one I
provide -> https://github.com/arminc/clair-local-scan/tree/master/clair
and change the port there
Instead of exposing the DB port link the DB container with the
Clair container trough Docker

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/arminc/clair-scanner/issues/51#issuecomment-409110493,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL2vFh8d9pnHu2Ewzkll8g5z9Ksw2fu4ks5uL_nngaJpZM4Vnjh9
.

i have created a container using docker build, then when i try to run modified build it says dial tcp error <IP_ADDRESS>:XXXX  XXXX(is the modified port). can you just say me where was i going wrong

This is not an issue for me but posting because I'm curious what's going on.
I'm running your image by following GitLab's docs https://docs.gitlab.com/ce/ci/examples/container_scanning.html
If I use arminc/clair-db:latest the container starts up:
2019-02-22 16:31:33.014 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2019-02-22 16:31:33.015 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2019-02-22 16:31:33.021 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-02-22 16:31:33.070 UTC [18] LOG:  database system was shut down at 2019-02-21 01:43:33 UTC
2019-02-22 16:31:33.080 UTC [1] LOG:  database system is ready to accept connections

But if I clone https://github.com/arminc/clair-local-scan, docker build --tag clair-test ., and docker run clair-test I get the issue described above:
{"Event":"pgsql: could not open database: dial tcp: lookup postgres on <IP_ADDRESS>:53: no such host","Level":"fatal","Location":"main.go:96","Time":"2019-02-22 16:30:54.080244"}

There seems to be a difference between how arminc/clair-db:latest was built and the images built using this Dockerfile https://github.com/arminc/clair-local-scan/blob/master/clair/Dockerfile.

Just in case if someone is facing the same issue with podman in 2023. Here are the steps that i followed to resolve "no such host error"..
Links feature of Docker is now deprecated and is no longer supported. Placing containers in a pod and networking them is an alternative to links functionality.
arminc/clair-db:latest  image built using the Dockerfile https://github.com/arminc/clair-local-scan/blob/master/clair/Dockerfile requires postgres db to be exposed on host postgres with 5432 listener port.
Clair Config.yaml uses the following connection string to interact with postgres db

source: host=postgres port=5432 user=postgres password=password sslmode=disable statement_timeout=60000

Link parameter was previously used to set network aliases for a running container. Here clair-db can be accessed via alias name postgres

docker run -p 6060:6060 --link clair-db:postgres -d --name clair arminc/clair-local-scan:v2.0.8_fe9b059d930314b54c78f75afe265955faf4fdc1

This functionality is no longer supported ; hence created a pod with name "postgres" and expose port 5432/6060 and associate the clair-db & clair containers.

podman pod create -n postgres -p 6060:6060 -p 5432:5432
podman run  -d --pod postgres --name db arminc/clair-db:latest
podman run  -d --pod postgres --name clair arminc/clair-local-scan:latest

Now, Clair API Server can successfully connect to Clair postgres DB and the following logs are recorded during start-up.
Ramasubramanians-MacBook-Pro:Downloads ramkasivisvanathan$ podman logs db

PostgreSQL Database directory appears to contain a database; Skipping initialization

2023-04-06 08:32:31.018 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-04-06 08:32:31.021 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-04-06 08:32:31.028 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-04-06 08:32:31.105 UTC [16] LOG:  database system was shut down at 2023-04-11 01:08:34 UTC
2023-04-06 08:32:31.158 UTC [1] LOG:  database system is ready to accept connections

Ramasubramanians-MacBook-Pro:Downloads ramkasivisvanathan$ podman logs clair
{"Event":"running database migrations","Level":"info","Location":"pgsql.go:216","Time":"2023-04-06 08:32:59.116644"}
{"Event":"database migration ran successfully","Level":"info","Location":"pgsql.go:223","Time":"2023-04-06 08:32:59.324439"}
{"Event":"notifier service is disabled","Level":"info","Location":"notifier.go:77","Time":"2023-04-06 08:32:59.334704"}
{"Event":"starting main API","Level":"info","Location":"api.go:52","Time":"2023-04-06 08:32:59.338241","port":6060}
{"Event":"starting health API","Level":"info","Location":"api.go:85","Time":"2023-04-06 08:32:59.348191","port":6061}
{"Event":"updater service started","Level":"info","Location":"updater.go:83","Time":"2023-04-06 08:32:59.352866","lock identifier":"9d63d055-f18c-4605-95a3-10e4f8e9aa91"}


ListTileTheme.merge(): add missing mouseCursor & visualDensity

This PR adds missing mouseCursor and visualDensity arguments to ListTileTheme.merge, makes it query the respective values from the parent theme, and passes them to the newly created ListTileThemeData. This ensures that ListTileThemeData.mouseCursor and ListTileThemeData.visualDensity are not lost when using ListTileTheme.merge.
Fixes: #121974
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

Thanks for the PR! @jpnurmi
This looks good, however, we're just testing explicit values in the ListTileTheme.merge.
When trying something like this, parent values are null in your test.
        print('mouseCursor: $mouseCursor, parent.mouseCursor: ${parent.mouseCursor}');
        print('mouseCursor: $visualDensity: parent.visualDensity: ${parent.visualDensity}');

It would be great if the test checks that all properties actually getting merged with parent ListTileTheme, this will ensure all properties are supported as you're testing them here.
Looks like we're also missing titleTextStyle, subtitleTextStyle, and leadingAndTrailingTextStyle. I added these properties and somehow missed the ListTileTheme.merge.


Resp EVAL/EVAL_RO/EVALSHA/EVALSHA_RO/SCRIPT LOAD|EXISTS|FLUSH

Depends on #13190
I will also add a section on scripting to the resp docs once #13198 is merged
Closes #13192

I need to exclude the lua stuff from the native server

Does this add support for these resp commands?
I am looking at the feasibility of using infinispan as a drop in replacement for the Redis, unfortunately it will not work with the .NET client for redis (StackExchange.Redis) as Infinispan does not support the eval command, I am not sure which other commands may be required,
It does not look like the HotRod client for .NET has been updated in some time,
Really what I am looking to do is use the Infinispan as a distributed cache in .NET (IDistributedCache) but I cannot find any recent / supported libraries to do this,

Yes, this adds those commands. I will use that client as additional validation that it  works and I'll update you.