CI: K8sDatapathServicesTest Checks N/S loadbalancing Tests with XDP, direct routing, DSR with Geneve and Maglev

Test Name
K8sDatapathServicesTest Checks N/S loadbalancing Tests with XDP, direct routing, DSR with Geneve and Maglev

Failure Output
FAIL: Can not connect to service "tftp://[fd04::11]:30424/hello" from outside cluster (1/10)

Stack Trace
/home/jenkins/workspace/Cilium-PR-K8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:515
Can not connect to service "tftp://[fd04::11]:30424/hello" from outside cluster (1/10)
Expected command: kubectl exec -n kube-system log-gatherer-9wnxw -- curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 tftp://[fd04::11]:30424/hello -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'" | grep client_address=
To succeed, but it failed:
Exitcode: 1
Err: exit status 1
Stdout:

Stderr:
 	 command terminated with exit code 71

/home/jenkins/workspace/Cilium-PR-K8s-1.26-kernel-net-next/src/github.com/cilium/cilium/test/k8s/service_helpers.go:255

Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 2
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
Top 1 errors/warnings:
UpdateIdentities: Skipping Delete of a non-existing identity
Cilium pods: [cilium-rwq6q cilium-wzqx6]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod                         Ingress   Egress
app1-586cfd8997-4qc6t       false     false
app3-5db68b966f-wkd4p       false     false
coredns-6d97d5ddb-kqtks     false     false
testclient-5w6f8            false     false
testclient-bmmq7            false     false
testds-d8zjt                false     false
app1-586cfd8997-f97vb       false     false
app2-775964bd4-qqs64        false     false
echo-85bb976686-mn7ks       false     false
echo-85bb976686-zb8fx       false     false
test-k8s2-f5fdd6457-v5kks   false     false
testds-tdhkh                false     false
Cilium agent 'cilium-rwq6q': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 46 Failed 0
Cilium agent 'cilium-wzqx6': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 56 Failed 0

Standard Error
02:27:36 STEP: Installing Cilium
02:27:38 STEP: Waiting for Cilium to become ready
02:28:00 STEP: Validating if Kubernetes DNS is deployed
02:28:00 STEP: Checking if deployment is ready
02:28:00 STEP: Checking if kube-dns service is plumbed correctly
02:28:00 STEP: Checking if pods have identity
02:28:00 STEP: Checking if DNS can resolve
02:28:04 STEP: Kubernetes DNS is up and operational
02:28:04 STEP: Validating Cilium Installation
02:28:04 STEP: Performing Cilium controllers preflight check
02:28:04 STEP: Performing Cilium health check
02:28:04 STEP: Performing Cilium status preflight check
02:28:04 STEP: Checking whether host EP regenerated
02:28:12 STEP: Performing Cilium service preflight check
02:28:12 STEP: Performing K8s service preflight check
02:28:12 STEP: Cilium is not ready yet: connectivity health is failing: Cluster connectivity is unhealthy on 'cilium-rwq6q': Exitcode: 1
Err: exit status 1
Stdout:

Stderr:
 	 Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), install-cni-binaries (init)
	 Error: Cannot get status/probe: Put "http://%2Fvar%2Frun%2Fcilium%2Fhealth.sock/v1beta/status/probe": dial unix /var/run/cilium/health.sock: connect: no such file or directory

	 command terminated with exit code 1

02:28:12 STEP: Performing Cilium controllers preflight check
02:28:12 STEP: Performing Cilium health check
02:28:12 STEP: Checking whether host EP regenerated
02:28:12 STEP: Performing Cilium status preflight check
02:28:20 STEP: Performing Cilium service preflight check
02:28:20 STEP: Performing K8s service preflight check
02:28:25 STEP: Cilium is not ready yet: host EP is not ready: cilium-agent "cilium-rwq6q" host EP is not in ready state: "regenerating"
02:28:25 STEP: Performing Cilium controllers preflight check
02:28:25 STEP: Performing Cilium health check
02:28:25 STEP: Performing Cilium status preflight check
02:28:25 STEP: Checking whether host EP regenerated
02:28:33 STEP: Performing Cilium service preflight check
02:28:33 STEP: Performing K8s service preflight check
02:28:39 STEP: Waiting for cilium-operator to be ready
02:28:39 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator")
02:28:39 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") => <nil>
02:28:39 STEP: Making 10 HTTP requests from outside cluster (using port 0) to "http://<IP_ADDRESS>:32315"
02:28:41 STEP: Making 10 HTTP requests from outside cluster (using port 0) to "tftp://<IP_ADDRESS>:30251/hello"
02:28:46 STEP: Making 10 HTTP requests from outside cluster (using port 0) to "http://[fd04::11]:30445"
02:28:47 STEP: Making 10 HTTP requests from outside cluster (using port 0) to "tftp://[fd04::11]:30424/hello"
FAIL: Can not connect to service "tftp://[fd04::11]:30424/hello" from outside cluster (1/10)
Expected command: kubectl exec -n kube-system log-gatherer-9wnxw -- curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 tftp://[fd04::11]:30424/hello -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'" | grep client_address=
To succeed, but it failed:
Exitcode: 1
Err: exit status 1
Stdout:

Stderr:
 	 command terminated with exit code 71

=== Test Finished at 2023-06-11T02:28:57Z====
02:28:57 STEP: Running JustAfterEach block for EntireTestsuite K8sDatapathServicesTest
===================== TEST FAILED =====================
02:28:58 STEP: Running AfterFailed block for EntireTestsuite K8sDatapathServicesTest
cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0
Stdout:
 	 NAMESPACE           NAME                               READY   STATUS    RESTARTS   AGE   IP              NODE   NOMINATED NODE   READINESS GATES
	 cilium-monitoring   grafana-67ff49cd99-t8qs9           0/1     Running   0          77m   <IP_ADDRESS>      k8s1   <none>           <none>
	 cilium-monitoring   prometheus-8c7df94b4-xkrns         1/1     Running   0          77m   <IP_ADDRESS>      k8s1   <none>           <none>
	 default             app1-586cfd8997-4qc6t              2/2     Running   0          16m   <IP_ADDRESS>      k8s1   <none>           <none>
	 default             app1-586cfd8997-f97vb              2/2     Running   0          16m   <IP_ADDRESS>      k8s1   <none>           <none>
	 default             app2-775964bd4-qqs64               1/1     Running   0          16m   <IP_ADDRESS>      k8s1   <none>           <none>
	 default             app3-5db68b966f-wkd4p              1/1     Running   0          16m   <IP_ADDRESS>      k8s1   <none>           <none>
	 default             echo-85bb976686-mn7ks              2/2     Running   0          16m   <IP_ADDRESS>       k8s2   <none>           <none>
	 default             echo-85bb976686-zb8fx              2/2     Running   0          16m   <IP_ADDRESS>      k8s1   <none>           <none>
	 default             test-k8s2-f5fdd6457-v5kks          2/2     Running   0          16m   <IP_ADDRESS>      k8s2   <none>           <none>
	 default             testclient-5w6f8                   1/1     Running   0          16m   <IP_ADDRESS>       k8s2   <none>           <none>
	 default             testclient-bmmq7                   1/1     Running   0          16m   <IP_ADDRESS>       k8s1   <none>           <none>
	 default             testds-d8zjt                       2/2     Running   0          16m   <IP_ADDRESS>      k8s2   <none>           <none>
	 default             testds-tdhkh                       2/2     Running   0          16m   <IP_ADDRESS>       k8s1   <none>           <none>
	 kube-system         cilium-operator-5866d666ff-9td98   1/1     Running   0          84s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         cilium-operator-5866d666ff-cglpm   1/1     Running   0          85s   <IP_ADDRESS>   k8s3   <none>           <none>
	 kube-system         cilium-rwq6q                       1/1     Running   0          85s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         cilium-wzqx6                       1/1     Running   0          85s   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         coredns-6d97d5ddb-kqtks            1/1     Running   0          18m   <IP_ADDRESS>       k8s2   <none>           <none>
	 kube-system         etcd-k8s1                          1/1     Running   0          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-apiserver-k8s1                1/1     Running   0          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-controller-manager-k8s1       1/1     Running   0          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-scheduler-k8s1                1/1     Running   0          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         log-gatherer-9wnxw                 1/1     Running   0          77m   <IP_ADDRESS>   k8s3   <none>           <none>
	 kube-system         log-gatherer-s78k9                 1/1     Running   0          77m   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         log-gatherer-swmwf                 1/1     Running   0          77m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         registry-adder-bs9ct               1/1     Running   0          78m   <IP_ADDRESS>   k8s3   <none>           <none>
	 kube-system         registry-adder-cxc8m               1/1     Running   0          78m   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         registry-adder-grh5s               1/1     Running   0          78m   <IP_ADDRESS>   k8s1   <none>           <none>

Stderr:

Fetching command output from pods [cilium-rwq6q cilium-wzqx6]
cmd: kubectl exec -n kube-system cilium-rwq6q -c cilium-agent -- cilium service list
Exitcode: 0
Stdout:
 	 ID    Frontend                Service Type   Backend
	 1     <IP_ADDRESS>:443           ClusterIP      1 => <IP_ADDRESS>:6443 (active)
	 2     <IP_ADDRESS>:53           ClusterIP      1 => <IP_ADDRESS>:53 (active)
	 3     <IP_ADDRESS>:9153         ClusterIP      1 => <IP_ADDRESS>:9153 (active)
	 4     <IP_ADDRESS>:3000       ClusterIP
	 5     <IP_ADDRESS>:9090     ClusterIP      1 => <IP_ADDRESS>:9090 (active)
	 7     <IP_ADDRESS>:69        ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 8     <IP_ADDRESS>:80        ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 9     <IP_ADDRESS>:69          ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 10    <IP_ADDRESS>:80          ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 11    <IP_ADDRESS>:10069       ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 12    <IP_ADDRESS>:10080       ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 13    <IP_ADDRESS>:32315     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 14    <IP_ADDRESS>:32315           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 19    <IP_ADDRESS>:30251           NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 20    <IP_ADDRESS>:30251     NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 21    <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 22    <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 25    <IP_ADDRESS>:32309     NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 26    <IP_ADDRESS>:32309           NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 29    <IP_ADDRESS>:31290     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 30    <IP_ADDRESS>:31290           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 31    <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 32    <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 37    <IP_ADDRESS>:30439     NodePort       1 => <IP_ADDRESS>:69 (active)
	 38    <IP_ADDRESS>:30439/i   NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 39    <IP_ADDRESS>:30439           NodePort       1 => <IP_ADDRESS>:69 (active)
	 40    <IP_ADDRESS>:30439/i         NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 45    <IP_ADDRESS>:30043     NodePort       1 => <IP_ADDRESS>:80 (active)
	 46    <IP_ADDRESS>:30043/i   NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 47    <IP_ADDRESS>:30043           NodePort       1 => <IP_ADDRESS>:80 (active)
	 48    <IP_ADDRESS>:30043/i         NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 49    <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	 50    <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	 55    <IP_ADDRESS>:32231     NodePort       1 => <IP_ADDRESS>:69 (active)
	 56    <IP_ADDRESS>:32231/i   NodePort       1 => <IP_ADDRESS>:69 (active)
	 57    <IP_ADDRESS>:32231           NodePort       1 => <IP_ADDRESS>:69 (active)
	 58    <IP_ADDRESS>:32231/i         NodePort       1 => <IP_ADDRESS>:69 (active)
	 63    <IP_ADDRESS>:31630     NodePort       1 => <IP_ADDRESS>:80 (active)
	 64    <IP_ADDRESS>:31630/i   NodePort       1 => <IP_ADDRESS>:80 (active)
	 65    <IP_ADDRESS>:31630           NodePort       1 => <IP_ADDRESS>:80 (active)
	 66    <IP_ADDRESS>:31630/i         NodePort       1 => <IP_ADDRESS>:80 (active)
	 67    <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	 68    <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	 69    <IP_ADDRESS>:30046           NodePort       1 => <IP_ADDRESS>:80 (active)
	 72    <IP_ADDRESS>:30046     NodePort       1 => <IP_ADDRESS>:80 (active)
	 75    <IP_ADDRESS>:30917     NodePort       1 => <IP_ADDRESS>:69 (active)
	 76    <IP_ADDRESS>:30917           NodePort       1 => <IP_ADDRESS>:69 (active)
	 77    <IP_ADDRESS>:80         ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 79    <IP_ADDRESS>:31343     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 81    <IP_ADDRESS>:31343           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 82    <IP_ADDRESS>:80       ClusterIP      1 => <IP_ADDRESS>:80 (active)
	 87    <IP_ADDRESS>:31517     NodePort       1 => <IP_ADDRESS>:80 (active)
	 88    <IP_ADDRESS>:31517/i   NodePort       1 => <IP_ADDRESS>:80 (active)
	 89    <IP_ADDRESS>:31517           NodePort       1 => <IP_ADDRESS>:80 (active)
	 90    <IP_ADDRESS>:31517/i         NodePort       1 => <IP_ADDRESS>:80 (active)
	 91    <IP_ADDRESS>:20080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 92    <IP_ADDRESS>:20069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 93    <IP_ADDRESS>:20080       ExternalIPs    1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 94    <IP_ADDRESS>:20069       ExternalIPs    1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 97    <IP_ADDRESS>:30052     NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 98    <IP_ADDRESS>:30052           NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 101   <IP_ADDRESS>:32464     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 102   <IP_ADDRESS>:32464           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 103   <IP_ADDRESS>:80        ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 104   <IP_ADDRESS>:69        ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 107   <IP_ADDRESS>:31500     NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 108   <IP_ADDRESS>:31500           NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 109   <IP_ADDRESS>:30872           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 112   <IP_ADDRESS>:30872     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 113   [fd03::19f9]:80         ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 114   [fd03::19f9]:69         ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 115   [fd03::35ef]:10080      ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 116   [fd03::35ef]:10069      ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 117   [fd04::12]:30445        NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 118   [::]:30445              NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 120   [::]:30424              NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 122   [fd04::12]:30424        NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 123   [fd03::5d08]:10080      ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 124   [fd03::5d08]:10069      ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 125   [fd04::12]:30963        NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 127   [::]:30963              NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 128   [::]:31147              NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 130   [fd04::12]:31147        NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 131   [fd03::2fbb]:10069      ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 132   [fd03::2fbb]:10080      ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 135   [fd04::12]:31501        NodePort       1 => [fd02::18b]:80 (active)
	 136   [fd04::12]:31501/i      NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 137   [::]:31501              NodePort       1 => [fd02::18b]:80 (active)
	 138   [::]:31501/i            NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 139   [fd04::12]:30589        NodePort       1 => [fd02::18b]:69 (active)
	 140   [fd04::12]:30589/i      NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 143   [::]:30589              NodePort       1 => [fd02::18b]:69 (active)
	 144   [::]:30589/i            NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 145   [fd03::dcc5]:10080      ClusterIP      1 => [fd02::1da]:80 (active)
	 146   [fd03::dcc5]:10069      ClusterIP      1 => [fd02::1da]:69 (active)
	 149   [fd04::12]:32628        NodePort       1 => [fd02::1da]:80 (active)
	 150   [fd04::12]:32628/i      NodePort       1 => [fd02::1da]:80 (active)
	 151   [::]:32628              NodePort       1 => [fd02::1da]:80 (active)
	 152   [::]:32628/i            NodePort       1 => [fd02::1da]:80 (active)
	 155   [fd04::12]:32450        NodePort       1 => [fd02::1da]:69 (active)
	 156   [fd04::12]:32450/i      NodePort       1 => [fd02::1da]:69 (active)
	 157   [::]:32450              NodePort       1 => [fd02::1da]:69 (active)
	 158   [::]:32450/i            NodePort       1 => [fd02::1da]:69 (active)
	 159   [fd03::eaef]:10080      ClusterIP      1 => [fd02::1da]:80 (active)
	 160   [fd03::eaef]:10069      ClusterIP      1 => [fd02::1da]:69 (active)
	 162   [fd04::12]:31862        NodePort       1 => [fd02::1da]:80 (active)
	 163   [::]:31862              NodePort       1 => [fd02::1da]:80 (active)
	 164   [fd04::12]:31027        NodePort       1 => [fd02::1da]:69 (active)
	 165   [::]:31027              NodePort       1 => [fd02::1da]:69 (active)
	 167   [fd03::d293]:20080      ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 168   [fd03::d293]:20069      ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 169   [fd03::999]:20080       ExternalIPs    1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 170   [fd03::999]:20069       ExternalIPs    1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 171   [fd04::12]:30826        NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 173   [::]:30826              NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 175   [fd04::12]:32158        NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 176   [::]:32158              NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 179   <IP_ADDRESS>:8080      HostPort       1 => <IP_ADDRESS>:80 (active)
	 180   <IP_ADDRESS>:8080            HostPort       1 => <IP_ADDRESS>:80 (active)
	 181   [fd04::12]:8080         HostPort       1 => [fd02::1da]:80 (active)
	 183   [::]:8080               HostPort       1 => [fd02::1da]:80 (active)
	 186   <IP_ADDRESS>:6969      HostPort       1 => <IP_ADDRESS>:69 (active)
	 187   <IP_ADDRESS>:6969            HostPort       1 => <IP_ADDRESS>:69 (active)
	 189   [fd04::12]:6969         HostPort       1 => [fd02::1da]:69 (active)
	 190   [::]:6969               HostPort       1 => [fd02::1da]:69 (active)
	 191   [fd04::11]:20080        ExternalIPs    1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 192   [fd04::11]:20069        ExternalIPs    1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 193   <IP_ADDRESS>:20080     ExternalIPs    1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 194   <IP_ADDRESS>:20069     ExternalIPs    1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 195   <IP_ADDRESS>:443      ClusterIP      1 => <IP_ADDRESS>:4244 (active)

Stderr:

cmd: kubectl exec -n kube-system cilium-rwq6q -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                                  IPv6        IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 68         Disabled           Disabled          8708       k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system   fd02::112   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=coredns
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=kube-dns
	 686        Disabled           Disabled          7573       k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default       fd02::18b   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDS
	 1356       Disabled           Disabled          4          reserved:health                                                              fd02::10a   <IP_ADDRESS>    ready
	 1453       Disabled           Disabled          7102       k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default       fd02::1da   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=test-k8s2
	 1479       Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s2                                                                            ready
	                                                            reserved:host
	 1859       Disabled           Disabled          12488      k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default       fd02::173   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:name=echo
	 3916       Disabled           Disabled          29629      k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default       fd02::17d   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDSClient

Stderr:

cmd: kubectl exec -n kube-system cilium-wzqx6 -c cilium-agent -- cilium service list
Exitcode: 0
Stdout:
 	 ID    Frontend                Service Type   Backend
	 2     <IP_ADDRESS>:53           ClusterIP      1 => <IP_ADDRESS>:53 (active)
	 3     <IP_ADDRESS>:9153         ClusterIP      1 => <IP_ADDRESS>:9153 (active)
	 4     <IP_ADDRESS>:3000       ClusterIP
	 5     <IP_ADDRESS>:9090     ClusterIP      1 => <IP_ADDRESS>:9090 (active)
	 6     <IP_ADDRESS>:443           ClusterIP      1 => <IP_ADDRESS>:6443 (active)
	 8     <IP_ADDRESS>:69        ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 9     <IP_ADDRESS>:80        ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 10    <IP_ADDRESS>:69          ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 11    <IP_ADDRESS>:80          ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 12    <IP_ADDRESS>:10080       ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 13    <IP_ADDRESS>:10069       ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 14    <IP_ADDRESS>:30251     NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 15    <IP_ADDRESS>:30251           NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 19    <IP_ADDRESS>:32315     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 21    <IP_ADDRESS>:32315           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 22    <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 23    <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 26    <IP_ADDRESS>:31290     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 27    <IP_ADDRESS>:31290           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 28    <IP_ADDRESS>:32309     NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 30    <IP_ADDRESS>:32309           NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 32    <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 33    <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 34    <IP_ADDRESS>:30043     NodePort       1 => <IP_ADDRESS>:80 (active)
	 35    <IP_ADDRESS>:30043/i   NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 40    <IP_ADDRESS>:30043           NodePort       1 => <IP_ADDRESS>:80 (active)
	 41    <IP_ADDRESS>:30043/i         NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 42    <IP_ADDRESS>:30439           NodePort       1 => <IP_ADDRESS>:69 (active)
	 43    <IP_ADDRESS>:30439/i         NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 44    <IP_ADDRESS>:30439     NodePort       1 => <IP_ADDRESS>:69 (active)
	 45    <IP_ADDRESS>:30439/i   NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 50    <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	 51    <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	 54    <IP_ADDRESS>:31630           NodePort
	 55    <IP_ADDRESS>:31630/i         NodePort       1 => <IP_ADDRESS>:80 (active)
	 56    <IP_ADDRESS>:31630     NodePort
	 57    <IP_ADDRESS>:31630/i   NodePort       1 => <IP_ADDRESS>:80 (active)
	 60    <IP_ADDRESS>:32231           NodePort
	 61    <IP_ADDRESS>:32231/i         NodePort       1 => <IP_ADDRESS>:69 (active)
	 66    <IP_ADDRESS>:32231     NodePort
	 67    <IP_ADDRESS>:32231/i   NodePort       1 => <IP_ADDRESS>:69 (active)
	 68    <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	 69    <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	 70    <IP_ADDRESS>:30917     NodePort       1 => <IP_ADDRESS>:69 (active)
	 73    <IP_ADDRESS>:30917           NodePort       1 => <IP_ADDRESS>:69 (active)
	 74    <IP_ADDRESS>:30046     NodePort       1 => <IP_ADDRESS>:80 (active)
	 75    <IP_ADDRESS>:30046           NodePort       1 => <IP_ADDRESS>:80 (active)
	 78    <IP_ADDRESS>:80         ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 79    <IP_ADDRESS>:31343           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 80    <IP_ADDRESS>:31343     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 83    <IP_ADDRESS>:80       ClusterIP      1 => <IP_ADDRESS>:80 (active)
	 88    <IP_ADDRESS>:31517     NodePort
	 89    <IP_ADDRESS>:31517/i   NodePort       1 => <IP_ADDRESS>:80 (active)
	 90    <IP_ADDRESS>:31517           NodePort
	 91    <IP_ADDRESS>:31517/i         NodePort       1 => <IP_ADDRESS>:80 (active)
	 92    <IP_ADDRESS>:20080     ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 93    <IP_ADDRESS>:20069     ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 94    <IP_ADDRESS>:20080       ExternalIPs    1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 95    <IP_ADDRESS>:20069       ExternalIPs    1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 98    <IP_ADDRESS>:32464     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 99    <IP_ADDRESS>:32464           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 100   <IP_ADDRESS>:30052     NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 101   <IP_ADDRESS>:30052           NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 104   <IP_ADDRESS>:80        ClusterIP      1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 105   <IP_ADDRESS>:69        ClusterIP      1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 107   <IP_ADDRESS>:30872     NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 109   <IP_ADDRESS>:30872           NodePort       1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 110   <IP_ADDRESS>:31500     NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 112   <IP_ADDRESS>:31500           NodePort       1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 114   [fd03::19f9]:80         ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 115   [fd03::19f9]:69         ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 116   [fd03::35ef]:10069      ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 117   [fd03::35ef]:10080      ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 119   [fd04::11]:30424        NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 120   [::]:30424              NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 121   [::]:30445              NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 123   [fd04::11]:30445        NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 124   [fd03::5d08]:10080      ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 125   [fd03::5d08]:10069      ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 127   [fd04::11]:30963        NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 128   [::]:30963              NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 130   [fd04::11]:31147        NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 131   [::]:31147              NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 132   [fd03::2fbb]:10080      ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 133   [fd03::2fbb]:10069      ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 134   [::]:30589              NodePort       1 => [fd02::66]:69 (active)
	 135   [::]:30589/i            NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 136   [fd04::11]:30589        NodePort       1 => [fd02::66]:69 (active)
	 137   [fd04::11]:30589/i      NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 140   [fd04::11]:31501        NodePort       1 => [fd02::66]:80 (active)
	 141   [fd04::11]:31501/i      NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 142   [::]:31501              NodePort       1 => [fd02::66]:80 (active)
	 143   [::]:31501/i            NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 146   [fd03::dcc5]:10069      ClusterIP      1 => [fd02::1da]:69 (active)
	 147   [fd03::dcc5]:10080      ClusterIP      1 => [fd02::1da]:80 (active)
	 150   [fd04::11]:32628        NodePort
	 151   [fd04::11]:32628/i      NodePort       1 => [fd02::1da]:80 (active)
	 152   [::]:32628              NodePort
	 153   [::]:32628/i            NodePort       1 => [fd02::1da]:80 (active)
	 156   [fd04::11]:32450        NodePort
	 157   [fd04::11]:32450/i      NodePort       1 => [fd02::1da]:69 (active)
	 158   [::]:32450              NodePort
	 159   [::]:32450/i            NodePort       1 => [fd02::1da]:69 (active)
	 160   [fd03::eaef]:10080      ClusterIP      1 => [fd02::1da]:80 (active)
	 161   [fd03::eaef]:10069      ClusterIP      1 => [fd02::1da]:69 (active)
	 163   [fd04::11]:31862        NodePort       1 => [fd02::1da]:80 (active)
	 164   [::]:31862              NodePort       1 => [fd02::1da]:80 (active)
	 165   [fd04::11]:31027        NodePort       1 => [fd02::1da]:69 (active)
	 167   [::]:31027              NodePort       1 => [fd02::1da]:69 (active)
	 168   [fd03::d293]:20080      ClusterIP      1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 169   [fd03::d293]:20069      ClusterIP      1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 170   [fd03::999]:20080       ExternalIPs    1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 171   [fd03::999]:20069       ExternalIPs    1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 173   [fd04::11]:30826        NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 174   [::]:30826              NodePort       1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 175   [fd04::11]:32158        NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 176   [::]:32158              NodePort       1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 178   [fd04::11]:20069        ExternalIPs    1 => [fd02::66]:69 (active)
	                                              2 => [fd02::18b]:69 (active)
	 179   [fd04::11]:20080        ExternalIPs    1 => [fd02::66]:80 (active)
	                                              2 => [fd02::18b]:80 (active)
	 180   <IP_ADDRESS>:20080     ExternalIPs    1 => <IP_ADDRESS>:80 (active)
	                                              2 => <IP_ADDRESS>:80 (active)
	 181   <IP_ADDRESS>:20069     ExternalIPs    1 => <IP_ADDRESS>:69 (active)
	                                              2 => <IP_ADDRESS>:69 (active)
	 182   <IP_ADDRESS>:443      ClusterIP      1 => <IP_ADDRESS>:4244 (active)

Stderr:

cmd: kubectl exec -n kube-system cilium-wzqx6 -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                              IPv6       IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 7          Disabled           Disabled          59456      k8s:id=app3                                                              fd02::9b   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testapp
	 266        Disabled           Disabled          35101      k8s:id=app1                                                              fd02::b9   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=app1-account
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testapp
	 321        Disabled           Disabled          12488      k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default   fd02::ed   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:name=echo
	 355        Disabled           Disabled          35101      k8s:id=app1                                                              fd02::3    <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=app1-account
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testapp
	 719        Disabled           Disabled          7573       k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default   fd02::66   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDS
	 1447       Disabled           Disabled          1719       k8s:appSecond=true                                                       fd02::5a   <IP_ADDRESS>   ready
	                                                            k8s:id=app2
	                                                            k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=app2-account
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testapp
	 3216       Disabled           Disabled          29629      k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default   fd02::ad   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDSClient
	 3687       Disabled           Disabled          4          reserved:health                                                          fd02::17   <IP_ADDRESS>   ready
	 3883       Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s1                                                                       ready
	                                                            k8s:node-role.kubernetes.io/control-plane
	                                                            k8s:node.kubernetes.io/exclude-from-external-load-balancers
	                                                            reserved:host

Stderr:

===================== Exiting AfterFailed =====================
02:29:35 STEP: Running AfterEach for block EntireTestsuite

Resources

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/681/
ZIP file(s):

7422ed94_K8sDatapathServicesTest_Checks_N-S_loadbalancing_Tests_with_XDP,_direct_routing,_DSR_with_Geneve_and_Maglev.zip
Anything else?
No response

cilium-sysdump.zip

Similar flake
https://github.com/cilium/cilium/issues/23309
command terminated with exit code 71

The nodeport request fd04::13:36556  -> fd04::11:30424  hits fd02::66:69 on k8s1 and its reply packet is reverse SNATetd via index 119. It seems that the Nodeport implementation is working as expected. But, as for the tFTP flow, there was something unusual going on. The exit code 71 means Illegal TFTP operation.
cilium-sysdump/cilium-bugtool-cilium-wzqx6-20230611-022858/cmd/cilium-bpf-ct-list-global.md
UDP OUT fd04::11:30424 -> fd04::13:36556 service expires=16782137 RxPackets=0 RxBytes=25 RxFlagsSeen=0x00 LastRxReport=0 TxPackets=0 TxBytes=0 TxFlagsSeen=0x00 LastTxReport=16782075 Flags=0x0000 [ ] RevNAT=119 SourceSecurityID=0 IfIndex=0
UDP OUT fd04::13:36556 -> fd02::66:69 expires=16782137 RxPackets=4 RxBytes=361 RxFlagsSeen=0x00 LastRxReport=16782079 TxPackets=4 TxBytes=304 TxFlagsSeen=0x00 LastTxReport=16782075 Flags=0x0020 [ NodePort ] RevNAT=119 SourceSecurityID=2 IfIndex=3
UDP IN fd04::13:36556 -> fd02::66:69 expires=16782137 RxPackets=4 RxBytes=304 RxFlagsSeen=0x00 LastRxReport=16782075 TxPackets=4 TxBytes=361 TxFlagsSeen=0x00 LastTxReport=16782079 Flags=0x0020 [ NodePort ] RevNAT=0 SourceSecurityID=2 IfIndex=0

cilium-sysdump/cilium-bugtool-cilium-wzqx6-20230611-022858/cmd/cilium-bpf-lb-list---revnat.md
119   [fd04::11]:30424

test_results/126-/K8sDatapathServicesTest_Checks_N-S_loadbalancing_Tests_with_XDP,_direct_routing,_DSR_with_Geneve_and_Maglev/pod-default-testds-tdhkh-udp.log
2023-06-11T02:28:47.600245296Z 2023/06/11 02:28:47 Read "hello" requested from [fd04::13]:36556

Hitting something similar for https://github.com/cilium/cilium/pull/27832 (1.12 backport), but for K8sServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Checks in-cluster KPR Tests NodePort with externalTrafficPolicy=Local
3480ddc4_K8sServicesTest_Checks_E-W_loadbalancing_(ClusterIP,_NodePort_from_inside_cluster,_etc)_Checks_in-cluster_KPR_Tests_NodePort_with_externalTrafficPolicy=Local.zip.zip (in fact a 7z archive)

Hit this again in E2E Test (1.30, f13-datapath-service-ns-xdp-1)


Makefile: Use "pkg-config" instead of hardcoded paths

E.g. on fedora some header files weren't found (E.g. glibconfig.h)
This fixes this issue in a future-proof way

Thanks for your contribution. Please note that I'm currently working on the gtk4 branch. I plan to merge gtk4 into main soon and then discontinue with gtk3.


when i run the file lcss_neignbors.py，there are no result in my context

the file is 0kB ,but the DTW method is right.

In order to properly run lcss_neighbors.py, you need to produce the pickle file named final_cleaned.df.
Execution of datacleaning.py outputs this file.


As a user, I can navigate through the application flawlessly due to full coverage and effective application testing

-Includes Postman API testing, Mocha JS Unit Testing, Pythong unittest unit testing, GUI acceptance tests using Selenium
-Story points estimation: 13 (~3 per testing suite)

Relates to #81, #82, #83, #84

The application should be good to test now!
@dylanlramage  should be on Selenium
@benrandall  Should be on unit

My unittests for python + postman tests took about 5 hours in total - we ended up with 94% coverage on main.py


@context and type check before issuing W3C cred

Signed-off-by: Shaanjot Gill<EMAIL_ADDRESS>
resolve #1568

Hi @TimoGlastra, an issue was reported related to w3c credential issuance, where in a credential with invalid $.type will get issued without any error [more details with examples can be found in the issue]. Even though the document_loader is working correctly and loads the correct context, the credential when expanded [jsonld.expand(cred_dict)] includes invalid expanded_type. In this PR, I have implemented a check to stop issuance in such scenarios. I will appreciate your feedback.

I think this approach won't work for all cases.
Although common, not all expanded types will contain an # appended to the url to indicate a specific type.
E.g. look at the expanded type in https://json-ld.org/playground/#startTab=tab-expanded&json-ld={"%40context"%3A"https%3A%2F%2Fschema.org"%2C"%40type"%3A"Person"}
The following JSON
{
  "@context": "https://schema.org",
  "@type": "Person"
}

expands to
[
  {
    "@type": [
      "http://schema.org/Person"
    ]
  }
]

@shaangill025 see my issue in #1568, this is an issue with Pyld and I think the fix you applied here works only for a very specific use case. If someone uses other type url formats it won't work.
I'm not sure why it caches the result as a type and uses that we another document is missing a certain type, but I think we should try to fix this on a lower level

@shaangill025 see my issue in #1568, this is an issue with Pyld and I think the fix you applied here works only for a very specific use case. If someone uses other type url formats it won't work.
I'm not sure why it caches the result as a type and uses that we another document is missing a certain type, but I think we should try to fix this on a lower level

Thanks for taking a look into this.


Airflow Tutorial page inconsistencies

I noticed some inconsistencies in your Tutorial page where you walk us through the DAG. For instance, in the code block, you have:
default_args = {
    'owner': 'airflow',
    'depends_on_past': False,
    'start_date': datetime(2015, 6, 1),
    'email'<EMAIL_ADDRESS>    'email_on_failure': False,
    'email_on_retry': False,
    'retries': 1,
    'retry_interval': timedelta(minutes=5),
    # 'queue': 'bash_queue',
    # 'pool': 'backfill',
    # 'priority_weight': 10,
    # 'schedule_interval': timedelta(1),
    # 'end_date': datetime(2016, 1, 1),
}

But when you break it down, it becomes:
args = {
    'owner': 'airflow',
    'depends_on_past': False,
    'start_date': datetime(2015, 1, 1),
    'email': ['airflow@airflow.com',],
    'email_on_failure': True,
    'email_on_retry': True,
}

And again,
t1 = BashOperator(
    task_id='print_date',
    bash_command='date',
    dag=dag)

t2 = BashOperator(
    task_id='sleep',
    bash_command='sleep 5',
    dag=dag)

which becomes:
t1 = BashOperator(
    task_id='print_date',
    bash_command='date',
    dag=dag)

t2 = BashOperator(
    task_id='sleep',
    email_on_failure=False,
    bash_command='sleep 5',
    dag=dag)

I am less concerned with the fact that you changed the code to illustrate the arguments and parameters and more concerned that you say: "Here is an example of a basic pipeline definition. Do not worry if this looks complicated, a line by line explanation follows below." leading us to believe that it will be a true reproduction, which it is not. Please fix the code in the tutorial so that it is clearer. Thanks!

I have made some changes to the tutorial so that it follows the code presented at the top.
I hope it clears some things up.
https://github.com/airbnb/airflow/pull/89


2.1-rc3: $depth = count(Edge)+count(Vertex)  ????

on OpenBeer dataset:
query 0: select count(*) as total from (traverse * from #14:22 while $depth <=2)
total=16
query 1: select * from (traverse * from #14:22 while $depth <=2) where $depth=0
----+------+-------+----+----+-----
#   |@RID  |@CLASS |id  |code|state
----+------+-------+----+----+-----
0   |#14:22|Brewery|23  |4103|Maine
----+------+-------+----+----+-----
query 2: select * from (traverse * from #14:22 while $depth <=2) where $depth=1
----+---------+----------+--------+------
#   |@RID     |@CLASS    |out     |in
----+---------+----------+--------+------
0   |#17:888  |HasBrewery|#15:1437|#14:22
1   |#17:2552 |HasBrewery|#15:1437|#14:22
2   |#17:4216 |HasBrewery|#15:1437|#14:22
3   |#17:5880 |HasBrewery|#15:1437|#14:22
4   |#17:7544 |HasBrewery|#15:1437|#14:22
5   |#17:9208 |HasBrewery|#15:1437|#14:22
6   |#17:10872|HasBrewery|#15:1437|#14:22
7   |#17:12912|HasBrewery|#15:4269|#14:22
8   |#17:14276|HasBrewery|#15:5765|#14:22
9   |#17:15204|HasBrewery|#15:1437|#14:22
10  |#17:17244|HasBrewery|#15:4269|#14:22
11  |#17:18608|HasBrewery|#15:5765|#14:22
----+---------+----------+--------+------
query 3: select * from (traverse * from #14:22 while $depth <=2) where $depth=2
----+--------+------+----+----+
#   |@RID    |@CLASS|id  |abv |
----+--------+------+----+----+
0   |#15:1437|Beer  |1438|0   |
1   |#15:4269|Beer  |4282|5   |
2   |#15:5765|Beer  |5840|8.3 |
----+--------+------+----+----+
from the query, seems the $depth are defined by count(E)+count(V). It does not fit with my personal common sense. Could you please clarify this?

Hi,
traverse * means traversing all the fields (document model), if you use
regular edges (that is the default) traversing from a vertex to another
means traversing two fields ("out_Class" on the vertex and "in" on the
edge).
To do a correct traversal on Graph API you have to use both() instead of *:
select * from (traverse both() from #14:22 while $depth <=2) where $depth=1
2015-06-12 14:16 GMT+02:00 Luca Garulli<EMAIL_ADDRESS>
Assigned #4308 https://github.com/orientechnologies/orientdb/issues/4308
to @luigidellaquila https://github.com/luigidellaquila.
—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/4308#event-329497630
.


Remove deprecated flag from Windows worker

I'm not entirely sure I remember why we included this flag in the default Windows opsfile, privileged containers aren't possible on Windows anyway. Either way it is deprecated and is being removed from k8s in v1.15.0-beta.1

@pgoodwin is the Tracker bot not enabled on this repo?

There is a webhook on this repo that's registered to Tracker. What behavior
did you expect and not see?
On Fri, May 31, 2019 at 8:16 AM Ben Moss<EMAIL_ADDRESS>wrote:

@pgoodwin https://github.com/pgoodwin is the Tracker bot not enabled on
this repo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry-incubator/kubo-deployment/pull/402?email_source=notifications&email_token=AAAZKJYXX6EOZYPRZJRSXNTPYE6MLA5CNFSM4HR3TUG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWVQG3A#issuecomment-497746796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAZKJ4QKW5JZMP2BG2FZPLPYE6MLANCNFSM4HR3TUGQ
.


Zuul server occasionally becomes unresponsive because of lots of tpc connections in close_wait state

We are using Zuul as the api gateway, and we found that the server will occasionally be unresponsive because hundreds of tcp connections are in close_wait state(which are not correctly cleaned by the server). We are using spring-cloud-starter-zuul 1.2.7-release, and zuul-core 1.3.0. We suspect it's a bug in zuul, can you help to debug the problem, thanks!

Might be related to #1970.  What version of Spring Cloud are you using?

The spring clound version is Camden SR7
Our request flow is:
load balancer -> zuul -> service

the close_wait connections is between load balancer -> zuul, so I think it is different from the problem in #1970.

If that's the case, why do you think there is a problem with zuul?

With netstat I see a lots of tcp sockets in CLOSE_WAIT status, the local address is the zuul server and the foreign address is load balancer. So I assume this means the client (load balancer) has just terminated the connection and the zuul server has not properly closed the connection at its end.

Could also be related to #1785 but that should be in Camden.SR7.  Could you update to Dalston.SR1 and see if you see the same thing?

@ltebean I think this could be related to #1970 since we are not closing the connections.  Do you have Spring Retry on the classpath?  Are you retrying specific response codes?

I was curious about the fix for #1785  after reading the documentation for http keepAlive. As Dave Bender has noted in issue 1997, there are a few issues and fixes, however we are still running into the problem, perhaps due to slightly different environment/configuration (we use jetty, etc), we have been unable to resolve the issue, though it seems very similar to the issues described here (1979) and the others.
Specifically, in the finally block of the writeResponse  method of SendResponseFilter, there is a try-catch. If I/O exception, there is only a line to log the message.
	catch (IOException ex) {
			log.warn("Error while sending response to client: " + ex.getMessage());
	}

How does this handle 404s, where an error stream is opened? For example, shouldn't the code be something similar to the keepAlive documentation, and attempt to close the errorStream?
Here's what the Oracle doc says:
What can you do to help with Keep-Alive?

Do not abandon a connection by ignoring the response body. Doing so may results in idle TCP connections. That needs to be garbage collected when they are no longer referenced.
If getInputStream() successfully returns, read the entire response body.
When calling getInputStream() from HttpURLConnection, if an IOException occurs, catch the exception and call getErrorStream() to get the response body (if there is any).

Of course, in writing this out here, it occurs to me,  that we should be able test this out as we are currently restarting our Zuul instances every few hours.

@kupci potentially.  Are you just pointing out one spot where we could not be closing the connection successfully or is this specifically where you think you are running into an issue?

This is one of the possibilities, we haven't proven anything yet. Dave Bender is setting up a test environment, plain vanilla Zuul, so we can try out some ideas without impacting users.

OK I am going to close this issue for now.  Once you have more information please reopen this issue or create another one so we can address this.  We appreciate your analysis!


OCW-128 #comment Removed gutter margins and applied max-width and mar…

…gin at the streamfield block level
OCW-112 #comment Don't apply margin max width to this streamfield to create an outdent

Created an updated pull request and merged.


OpenAIFile: status_details is a string

Hi there
According to the API documentation the status_details of a file must be an object or null. But I never receive an object there but we ran into the issue that it returns a string.
This happens if we upload a (very long) jsonl file with a syntax error in it and then hit the FineTunes Create endpoint.
Here is the response I got:
{
  "object": "fine-tune",
  "id": "ft-kSsak20Ml0faDIpmvbTvmKEP",
  "hyperparams": {
    "n_epochs": 4,
    "batch_size": null,
    "prompt_loss_weight": 0.01,
    "learning_rate_multiplier": null
  },
  "organization_id": "org-****",
  "model": "curie",
  "training_files": [
    {
      "object": "file",
      "id": "file-OGHjVIyNB7svNc6vaUXNgR87",
      "purpose": "fine-tune",
      "filename": "MyFile_corrupt.jsonl",
      "bytes": 181023,
      "created_at":<PHONE_NUMBER>,
      "status": "error",
      "status_details": "Invalid file format. Example 1273 cannot be parsed. Error: line contains invalid json: Expecting ',' delimiter: line 1 column 79 (char 78) (line 1273)"
    }
  ],
  "validation_files": [],
  "result_files": [],
  "created_at":<PHONE_NUMBER>,
  "updated_at":<PHONE_NUMBER>,
  "status": "pending",
  "fine_tuned_model": null,
  "events": [
    {
      "object": "fine-tune-event",
      "level": "info",
      "message": "Created fine-tune: ft-kSsak20Ml0faDIpmvbTvmKEP",
      "created_at":<PHONE_NUMBER>
    }
  ]
}

Can you help us to understand what return types we can expect there?
Thank you in advance!
Sandro

This is fixed now!


DOC: clarify scale parameter of scipy.stats.invgauss

Issue with current documentation:
The doc on scipy.stats.invgauss doesn’t mention how to “back out” the common two-parameter form (mu, lambda) from the one-parameter form. It would be helpful to mention it for the casual user (like me) to be able to use it right away.
Idea or request for content:
Insert the following paragraph into the documentation:
A common two-parameter form of the inverse Gaussian distribution with parameters (mu, lambda) is equivalent to invgamma(mu/lambda, scale=lambda).
Additional context (e.g. screenshots, GIFs)
A related page in SciPy Tutorial provides some hint on the transform needed, but the writing style of that page is more of a “note” for someone who already knows the stuff than a “tutorial” for someone who doesn’t know the stuff.

We have notes like this in scipy.stats.norminvgauss, scipy.stats.gamma, and others. In those cases, the PDF of the alternative parameterization is also given, so I'd suggest doing that here.
This looks simple enough, so I'd be willing to review a PR after gh-19932 if you're interested in submitting it. (One at a time, please.)

for the casual user (like me)

After opening 5 issues and a PR in a week, you have graduated from casual user : )

Cool, let me make a PR after the other one.
I’ll also like to take a look at the tutorial page and see how it fits with the other distribution docs. I tend to write too much in tutorials; I’ll try not to for this one!


Set X-Forwarded-Host headers

This ensures that Fastly sets the X-Forwarded-Host headers to a single value that is the same original request host. This helps mitigates against clients for spoofing the X-Forwarded-Host header and prevents cache poisoning.
This assumes that backend requests are only for client requests that have valid and non-spoofed hosts, which is fine as Fastly will only be dealing with request that have to correct Host header for the service.
e.g. curl -H 'Host: phishing.com' https://assets.publishing.service.gov.uk/ won't be handled by our Fastly service, as Fastly will look for the "phishing.com" service, not the "assets.publishing.service.gov.uk" service.
⚠ The changes need to be deployed manually to all relevant environments. Follow the guidance on how to deploy Fastly.

Closed in favour of https://github.com/alphagov/govuk-cdn-config/pull/414. Moved the request headers to the vcl_recv subroutine instead of vcl_miss and vcl_pass.


[50$ bounty] need help to update the UI during the incoming stream

I'm having major trouble updating a text field with each incoming token of the stream. I have tried multiple approaches none of which work. Note I'm developing a keyboard so I cannot call runOnUiThread (there is no base activity).
A)
service.streamChatCompletion(chatCompletionRequest).blockingIterable()
This seems to return the iterable only when it has received the full stream, so I cannot update on each token.
B)
service.streamChatCompletion(chatCompletionRequest).elementAt()
The idea is to call one by one and update the UI in between, However, the second time I get IllegalStateException: Already executed..
C)
service.streamChatCompletion(chatCompletionRequest).subscribe(new Consumer<ChatCompletionChunk>() { @Override public void accept(ChatCompletionChunk chatCompletionChunk) throws Exception {update view}})
This calls the view updates upon each incoming token but it does not draw the updated view until the stream is finished. This happens also with blockingForEach and forEach.
The person that helps me solve this issue I will send 50$ via PayPal.

Try set callbackExecutor(RxSchedulerToExecutor(Schedulers.io())) on Retrofit

Thanks drakeet, to make this change do I need to fork the project and then import module in Android Studio? Do I need to build service, api and client in any particular order? I get Plugin with id 'com.vanniktech.maven.publish' not found. when building api.

Try set callbackExecutor(RxSchedulerToExecutor(Schedulers.io())) on Retrofit
// The Chinese comment is saying: Otherwise it will block the main thread.

Thanks @drakeet , to make this change do I have to rebuild OpenAiService or is there an easier way?

You can make a quick try: copy the source code of OpenAiService.java, then modify it and use it.

I got it to work, thanks a lot! I ended up using .callBackExecutor(scheduler) which I defined on the main thread. Want to claim the bounty? Let me know your paypal mail.


Read an account from the service

As a customer or API consumer
I need the ability to retrieve account information by providing a unique account identifier
So that I can access and display account details when needed.
Details and Assumptions

The service includes a database with account data.
The API endpoint /api/accounts/{account_id} is designed for this purpose.

Acceptance Criteria
Given a valid account ID
When I make a GET request to the endpoint `/api/accounts/{account_id}`
Then I should receive a JSON response with the account details.


LinkMap Key misbehaving when contains "]"

Hello Orient Team,
We are using OrientDB V 2.1.7
We have a structure similar to the one described in Time Series.
We recently have had problems with the key of one of our linkmaps. it seems like the character "]" is not supported inside map's key.
We have a very "bad" key like [123_abc_#1239#1___'0571234'512354128|||] .
We have no problem in adding it to the map, but we do have problems while retrieving its value.
A Simple
SELECT code["[123_abc_#1239#1___'0571234'512354128|||]"] from TransitsCode

Returns nothing:

And also the count is wrong
Actually, the returning count is as I would have run
SELECT from TransitsCode

If I try to insert in the map a key like [123_abc_#1239#1___'0571234'512354128||| (without the ending closed square bracket ) then the query works properly.
Any ideas?
It seems like the closed square bracket breaks the SQL Parser.
Our workaround is to convert our map key to HEX to avoid this issue, but this increases dramatically the difficulty of writing queries by hand (in the studio, for instance).
Regards

Hi @guglielmomoretti
This issue was fixed in v 2.2.1
Closing
Thanks
Luigi


ReferenceError: Headers is not defined

Hey! Thanks for your work on this project. It's so exciting 🤩
I'm using this lib inside https://github.com/sullivan-sean/chat-langchainjs and got the following error when importing docs:
ReferenceError: Headers is not defined
    at null.createRequest (./chat-langchainjs/node_modules/langchain/src/util/axios-fetch-adapter.js:96:19)
    at null.fetchAdapter (./chat-langchainjs/node_modules/langchain/src/util/axios-fetch-adapter.js:20:19)
    at null.dispatchRequest (./chat-langchainjs/node_modules/axios/lib/core/dispatchRequest.js:58:10)
    at Axios.request (./chat-langchainjs/node_modules/axios/lib/core/Axios.js:108:15)
    at Function.wrap (./chat-langchainjs/node_modules/axios/lib/helpers/bind.js:9:15)
    at null.<anonymous> (./chat-langchainjs/node_modules/openai/dist/common.js:147:22)
    at null.<anonymous> (./chat-langchainjs/node_modules/openai/dist/api.js:1539:123)

Where is the Headers definition supposed to come from?
https://github.com/hwchase17/langchainjs/blob/main/langchain/src/util/axios-fetch-adapter.js#L102
From here?
https://github.com/hwchase17/langchainjs/blob/main/langchain/src/agents/tools/requests.ts#L3

Pinging @nfcampos since you recently worked on https://github.com/hwchase17/langchainjs/pull/118 🙏

Hi @conroywhitney
Headers is meant to be in global scope with fetch. Can you confirm the version of Node you're running this on? See these new instructions here for running it in Node 16 https://hwchase17.github.io/langchainjs/docs/getting-started#installation
Does that fix it?

Thanks -- you're totally right. I was on Node 16, so this fixed it:
NODE_OPTIONS='--experimental-fetch' yarn ingest


ENH: concat and append now can handle unordered categories

this must be after #13763

[x] closes #13524
[x] tests added / passed
[x] passes git diff upstream/master | flake8 --diff
[x] whatsnew entry

on current master:
# different categoricals
pd.concat([pd.Series([1, 2], dtype='category'),
           pd.Series([3, 4], dtype='category')])
# ValueError: incompatible categories in categorical concat

# categorical + normal (values are contained in categories) -> object dtype
pd.concat([pd.Series([1, 2], dtype='category'),
           pd.Series([1, 2])])
# 0    1
# 1    2
# 0    1
# 1    2
# dtype: object

# categorical + normal (values are not contained in categories) -> object dtype
pd.concat([pd.Series([1, 2], dtype='category'),
           pd.Series([3, 4])])
# 0    1
# 1    2
# 0    3
# 1    4
# dtype: object

this PR:
# different categoricals
pd.concat([pd.Series([1, 2], dtype='category'),
           pd.Series([3, 4], dtype='category')])
# 0    1
# 1    2
# 0    3
# 1    4
# dtype: category
# Categories (4, int64): [1, 2, 3, 4]

# categorical + normal (values are contained in categories) -> category dtype
pd.concat([pd.Series([1, 2], dtype='category'),
           pd.Series([1, 2])])
# 0    1
# 1    2
# 0    1
# 1    2
# dtype: category
# Categories (2, int64): [1, 2]

# categorical + normal (values are not contained in categories) -> int dtype (keep original dtype)
pd.concat([pd.Series([1, 2], dtype='category'),
           pd.Series([3, 4])])
# 0    1
# 1    2
# 0    3
# 1    4
# dtype: int64

CC: @janschulz, @chris-b1

[Current coverage][cc-pull] is 84.57% (diff: 100%)

No coverage report found for master at b60e42b.

Powered by Codecov. Last update [b60e42b...e687e9d][cc-compare]
[cc-base-branch]: https://codecov.io/gh/pydata/pandas/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/pydata/pandas/compare/b60e42b02040624f319cadd60a99fe50eb62d62e...e687e9db54165c86c23b66257f921ba34c71560c?src=pr
[cc-pull]: https://codecov.io/gh/pydata/pandas/pull/13767?src=pr

What is the actual "problem" or use case here?
I'm opposed to this PR: IMO concat() should not change the categories. In my thinking (pd.Series([1, 2], dtype='category'), pd.Series([3, 4], dtype='category') is as (un)similar as ([1,2], ["A", "B"]). The latter might cast to a type which can take both (object) but not to a new int_or_string type...
So, I find the master variant more in line with that thinking. What I'm not sure is whether it should raise or (as it does now) convert to object. Other cat handling of two different cats (apart form the special union_categoricals) raises but pandas in general casts to object.
I can see a logic for "categorical + iterable of the same values as in the categories = new categorical with the same categories as the first one" as that can be thought similar as cat[x] = value.

@janschulz thx for sharing your opinion. Can you illustrate your intention covering possible patterns? (I copied mine from #13524).

concat 2 categories -> use the rule of union_categorical
concat category and other dtype (which values are all in the category, including empty) -> category

this rule is applied regardless of order (if there is at least one category in concatenating values)
the property like ordered should be preserved.

concat category and other dtype (which values are not in the category) -> not category (dtype is infered)

I come from using catagoricals as things like lickert scales: "Fully agree ... full disagree" and such things. From that standpoint, I usually read data in, convert to cat and replace the categories with the full set.  In that case the categories have a specific meaning (e.g the lickert scale or in other cases the 50 US states or such things which are fixed).
Form that comes the rule that you shouldn't be able to set a value in the cat column to something not in categories. And from that the "error if combining two different categories" rule. So I'm fully happy that there isn't any "default" (i.e. anything in the cat accessor) way to combine two different categories and trying to do it would error.
I see union_categorical as a way to use a categorical as a memory saving string type and as in the other issues where such additions/changes were proposed, I would love to see such a type instead of changing categorical to fit that needs.
The second usecase is  as an internal helper for someone using it with reading in csv files before letting the user do some "meaningful" replacements.

Thanks for sharing the usecase. Based on this, what the "rules" on your mind are? can u list up possible rules like: category + category (same category) = category covering possible patterns to discuss the expected behavior.

IMO therse are the rules:

category + setting with values in the categories = fine
category + setting with values not in the categories = error (not converting to object/common "normal" type)
category + same category configuration ("order" +  categories OR "unordered" + same categories (the unordered case could actually be less strict and only test if the set of categories is the same)) = fine
category + different category = error

I agree with @janschulz rules, except where error -> just coerce to the base type (of the categorical) if there is one, if multiple categoricals and different base types then must upcast (potentially to object).
The idea is that concat/append would always work, whether you add new categoricals or not, but the dtype will be preserved in a strict way.
I suppose that we could further add an argument to concat itself that just calls union_categoricals, IOW allows a non-strict interpretation. maybe union_categoricals=False as the default

@jreback

category + setting with values not in the categories = error (not converting to object/common "normal" type)

except where error -> just coerce to the base type (of the categorical) if there is one, if multiple categoricals and different base types then must upcast (potentially to object).

If you also want to change setting as well, then this is a whole different thing... IMO the above rules are what currently applies.
I'm still not convinced:  So what happens if I have a Categorical which is encoded as complete agree ... completly disagree (5 step lickert scale) and now I concat a column which is encoded as a categorical which encode the 50 US States. It will now work (both are string dtypes), but the meaning is completely screwed. Or imaging things like two categoricals which have one category in common (50 US states + 50 states capitals -> washington is in both...): will that mean that the final categorical have x+y-1 categories? In my opinion the a categorical configuration is it's own dtype (is_dtype_equal in Categorical actually tests just that: https://github.com/pydata/pandas/blob/master/pandas/core/categorical.py#L1791-L1809).
What is the actual usecase here: internal csv parsing of different files to a single dataframe? If so, then in my eyes this looks (again :-)) like the "pd-String" usecase: you encode it directly to save memory and then you are have the problem to concat two dfs because you don't know the strings (=you have no beforehand knowledge about the expected categories).
If so, then there are multiple different ways to solve this:

add a pd.String dtype :-)
add a convenience method like pd.append_nonstrict() which would basically do a union_categorical on the category columns.
add a nonstrict_category_checks=False to concat/append which would basically switch to pd.append_nonstrict() behaviour above.

I agree that concat shouldn't fail, as users understand what they're doing. Considering all dtypes (not only category), coercing to the object dtype should be a basic rule (such as DatetimeTZ with differen tz).
Based on this, I've organized the rules as below table.

left
right
result

category
category (identical categories and ordered)
category

category
category (different categories or ordered)
object (dtype is inferred)

category
not category
object (dtype is inferred)

Also, adding following options to concat should cover all cases:

union_categorical (default False): work as @jreback suggested. Apply union_categorical rule to concat Categorical.
strict (default False): raise when different dtype / different categories are being concatenated.

once updated based on the discussion. Note that following fixed are not included:

union_categoricals with Index.append (being included in #13660)
strict option (should be after #13660)

cc @janschulz
cc @chris-b1
can you have a look.
@wesm ?

This pair of results was unexpected - it seems like either both should be Categorical, or both the category's dtype?  Although I'm not sure which.
In [6]: pd.__version__
Out[6]: '0.18.1+314.gc82629c'

In [4]: pd.concat([pd.Series([1,2], dtype='category'),
   ...:            pd.Series([2,1])], union_categoricals=True)
Out[4]:
0    1
1    2
0    2
1    1
dtype: category
Categories (2, int64): [1, 2]

In [5]: pd.concat([pd.Series([1,2], dtype='category'),
   ...:            pd.Series([2,1, 3])], union_categoricals=True)
Out[5]:
0    1
1    2
0    2
1    1
2    3
dtype: int64

@chris-b1 Agreed the above is confusing. The first example keeps category dtype as 2nd values are all in 1st categories.
Maybe the following rule is simpler? (category + non-category always results in non-category, regardless of union_categoricals)

left
right
result
union_categoricals=True

category
category (identical categories)
category
category

category
category (different categories, both not ordered)
object (dtype is inferred)
category

category
category (different categories, either one is ordered)
object (dtype is inferred)
object (dtype is inferred)

category
not category
object (dtype is inferred)
object (dtype is inferred)

@sinhrks I like that table better.

Yeah, that makes sense to me.

Thanks for the feedback. Updated the impl based on the above table.

cc @mrocklin
In [7]: s1 = Series(pd.Categorical(list('baca'),categories=list('abc')))

In [8]: s2 = Series(pd.Categorical(list('baca'),categories=list('bac')))

In [9]: s1
Out[9]:
0    b
1    a
2    c
3    a
dtype: category
Categories (3, object): [a, b, c]

In [10]: s2
Out[10]:
0    b
1    a
2    c
3    a
dtype: category
Categories (3, object): [b, a, c]

In [11]: s1.cat.codes
Out[11]:
0    1
1    0
2    2
3    0
dtype: int8

In [12]: s2.cat.codes
Out[12]:
0    0
1    1
2    2
3    1
dtype: int8

In [13]: pd.concat([s1,s2],union_categoricals=True)
Out[13]:
0    b
1    a
2    c
3    a
0    b
1    a
2    c
3    a
dtype: category
Categories (3, object): [a, b, c]

In [14]: pd.concat([s1,s2],union_categoricals=True).cat.codes
Out[14]:
0    1
1    0
2    2
3    0
0    1
1    0
2    2
3    0
dtype: int8

Cool.  I'm very glad to see this.  Dask.dataframe can definitely make use
of this feature.
On Sat, Aug 6, 2016 at 12:01 PM, Jeff Reback<EMAIL_ADDRESS>wrote:

cc @mrocklin https://github.com/mrocklin
In [7]: s1 = Series(pd.Categorical(list('baca'),categories=list('abc')))
In [8]: s2 = Series(pd.Categorical(list('baca'),categories=list('bac')))
In [9]: s1
Out[9]:
0    b
1    a
2    c
3    a
dtype: category
Categories (3, object): [a, b, c]
In [10]: s2
Out[10]:
0    b
1    a
2    c
3    a
dtype: category
Categories (3, object): [b, a, c]
In [11]: s1.cat.codes
Out[11]:
0    1
1    0
2    2
3    0
dtype: int8
In [12]: s2.cat.codes
Out[12]:
0    0
1    1
2    2
3    1
dtype: int8
In [13]: pd.concat([s1,s2],union_categoricals=True)
Out[13]:
0    b
1    a
2    c
3    a
0    b
1    a
2    c
3    a
dtype: category
Categories (3, object): [a, b, c]
In [14]: pd.concat([s1,s2],union_categoricals=True).cat.codes
Out[14]:
0    1
1    0
2    2
3    0
0    1
1    0
2    2
3    0
dtype: int8
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pydata/pandas/pull/13767#issuecomment-238030521, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszIoHtnmUQ3HtH5vpWATcLOeo52HKks5qdK_xgaJpZM4JTey6
.

lgtm. @jorisvandenbossche @TomAugspurger @shoyer comments?

👍 to the last table.

anyone want to summarize where we are on this PR and what if any issues remain for discussion?

Remaining discussion is only one (pls allow me if i missed something)

What the concat keyword name should be (union_categoricals, or descriptive name like less_strict_categorical_checks)

Now I feel less_strict... may not be enough clear for users, as it doesn't say what the result be (less strictly keep category or coerces to object). But leave decision as I'm not a native:)

This seems okay to me. As an aside, having a type-specific argument in pd.concat isn't ideal, but I'm not sure what's better. You could be more explicit / general with something like
options = {
    'types': {
        'category': {
            'union': True
        }
    }
}
pd.concat(chunks, options=options)

Ok with the option specification as proposed by @wesm . We should create an issue to make this a bit more general, maybe using: attrdict.
But can change to using this for now (as in reality its used only internally ATM).

or remove union_categoricals arg ATM. It gets less important because we've decided concatenating different categories coerces to object (yser can re-categorize the object if they want).

you need for read_csv

ah, i meant union categoricals option in concat. the function itself is useful.

OK, we have to take a decision here if we want to include this one for 0.19. I tried to summarise below, but it has gotten a bit long :-)
But maybe the conclusion is just that this can be merged as is? (or at least part 1)

1. dtype of return value of concat (in the default case, without specifying kwargs)
I think most people agreed with the table above: https://github.com/pydata/pandas/pull/13767#issuecomment-237806603?
This comes down to returning object dtype where you now got "ValueError: incompatible categories in categorical concat"
Additionally:

concatting a categorical Series with a plain Series that only has values included in the categories no longer returns a Categorical Series. Eg with current PR:

In [20]: s1 = pd.Series(['a', 'b'], dtype='category')
In [21]: pd.concat([s1, s1]).dtype
Out[21]: category
In [22]: pd.concat([s1, s1.astype(object)]).dtype
Out[22]: dtype('O')
On current master this gives two times `'category'`.
@sinhrks If we keep this, this should actually be mentioned in the whatsnew docs I think.

- you do not get the clear error any more when concatting categoricals with different categories, but a silent downcast to object dtype (or the dtype of the categories). This can possibly give surprises further down the road when users wonder why they have no longer a category dtype.

As @sinhrks said, we can also already include this part, and leave part 2 (below) for a later PR

### **2. addition of new keyword to `concat` to union categoricals with different categories**

Current PR proposes to add a `union_categoricals` keyword to `concat`, which lets you concatenate categoricals with different categories (like the `union_categoricals` function does). Default would be False.

There was some discussion about the name to use. @wesm suggested to use a dict to pass type specific options. But that is maybe something we should first explore further to see if there are other use cases for such a construct?

As I understand, this part of the PR is less pressing, as users can also use the `union_categoricals` function directly (although IMO it would be nice to not have to expose this function, but let people use `concat`)

+1
I think we do need to do something, but ok to wait and add this later.

Right now union_categoricals is a good soln, it is a semi-private API, but likely to be exposed to a developer API at some point. Since we are adding API, can just push this back a bit.

ok, let's take out union_categoricals arg to concat for now and put it in a separate PR, @sinhrks ?

@jreback that sounds good to me. Easier to add it later, and having the extra function is a stopgap for users who need it

@sinhrks can you update

@sinhrks can you update?

@sinhrks I think the decision was to take out the kwarg for now? (see https://github.com/pydata/pandas/pull/13767#issuecomment-244550869 above).
(but maybe that is quite some work ..)

@jorisvandenbossche You're right. Updated to remove union_categoricals kw.

@sinhrks @jreback I am going to merge this, the final comments can be addressed in a follow-up PR (but they are not critical for the rc I think).


Radio Buttons - different behaviour from example

I'm trying to figure out a strange behaviour in the development of a set radio buttons elements.
First of all, I'm using a MAC and the issue is replicable both in Chrome and both in Firefox.
I created the control-group following the code snippet reported here: http://www.jque.re/plugins/version3/bootstrap.switch under the item Radio javascript.
The behaviour of the example is correct:

only one radio button is active
the draggable label trigger the event only if the radio button is OFF
the click event is triggered only if the radio button is OFF
all the other radio buttons change the state accordingly

If I cut and paste this code and including the necessary libraries, the radio buttons appear as normal radio button without the "switch" layout.
If I initialize them like this: $('.radio1').bootstrapSwitch(); they area displayed correctly but I lose the possibility to change the state in anyway (click and drag).
Is it an old distribution version? Is it a bug or I lost something somewhere? I looked, also, into the official documentation and I tried to use the "radioAllOff" options but nothing change...

Yes this is a very old version.
go to http://www.bootstrap-switch.org/

Thank you for your reply.
I used this code snippet, because it solved a problem that I have with the official version:
In the examples section on http://www.bootstrap-switch.org/, there are two radio buttons to explain the use of the option "radioAllOff".
I would like to use this feature in order to have, at least, one button on (radioAllOff = Disabled), but if I drag the active button switch I can turn off all buttons and this is not what I look for...
Any suggestion?

Sorry not realy, i don't have a working Dev Plattform at this time. So i can't check the code.

No hurry, when you have a free moment trying to look at it and let me know if the problem is only mine


Fix DEFAULT keyword in generated protobuf class

Add a test that instantiates all of the generated protobuf classes in src/generated
Rename instance of invalid DEFAULT keyword

PHP, you are weird.
This looks reasonable to me, but since I don't have much familiarity with the things you are calling, let someone else look too.

Codecov Report

Merging #94 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #94   +/-   ##
=======================================
  Coverage   90.52%   90.52%
=======================================
  Files          33       33
  Lines        2249     2249
=======================================
  Hits         2036     2036
  Misses        213      213

Continue to review full report at Codecov.

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

@shinfan @neozwu Can either of you take a look? If possible I would like to merge this today. Thanks!


Link VIB version to the build version.

The vib version was not being set for each build or release.
As per documentation an additional release version is added.
Versioning VIBs

Because VIBs are intended to allow the ESXi installer to handle updates as well as initial installs, it is
important to use the versioning variables in the VIB correctly.

The package version can have a length of up to 35 characters. It includes the version number, immediately
followed by a hyphen (‐) followed by the release version, as in the following example:

5.0.0-1.0vmw

Both the version number and the release version number consist of one or more characters in the set
[a‐a‐Z0‐9], with periods separating two or more groups.

Testing:
Make vib and install.
Run command esxcli software profile get
Output:
(Original Vendor):VMware, Inc.
      2016-07-06T10:45:12.595760+00:00: The following VIBs are
      installed:
        esx-vmdkops-service   0.7.14b2727-0.0.1

What's the output of /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py status ?

[root@localhost:~]  /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py status
Version: 0.7.14b2727-0.0.1
Status: Running
Pid: 697796
Port: 1019
LogConfigFile: /etc/vmware/vmdkops/log_config.json
LogFile: /var/log/vmware/vmdk_ops.log
LogLevel: INFO

LGTM


channledb: expose codec

Simple change to expose the channeldb codec methods:

readElement -> ReadElement
readElements -> ReadElements
writeElement -> WriteElement
writeElements -> WriteElements

This will allow other subsystems to reuse the bulk of the db encoding. Currently, we often manually write serialization logic in subsystems such as the utxn, brar, and (soon) watchtowers. This change will allow us to reuse any previously specified types, extend the codec with new, package-specific types, and moreover create simpler persistent objects.

I've also added a concrete error type to the codec, which will make it possible for any extensions to reliably determine if a type is unsupported by the base codec

Superseded by #1458.


kconfig: Make 'source' non-globbing and use 'gsource'

Until now, Zephyr has used a patched Kconfiglib that turns 'source' into
a globbing source (by replacing 'source' with 'gsource' at the token
level). There's two problems with this:

The patch needs to be maintained separately

Misspelled filenames are silently ignored, as they look like glob
patterns that don't match anything

Fix it as follows:

Replace all 'source' statements that use wildcards with 'gsource'

Remove the custom Kconfiglib patch so that 'source' no longer globs

The sed pattern /source.*[*?]/s/source/gsource/ was run over all
Kconfig* files to do the replacement.
source's that use environment variables that might contain glob patterns
were manually changed to gsource.
Building the docs in doc/ is a good test, as doc/Makefile deliberately
sets the environment variables to glob up as many Kconfig files as
possible.
Signed-off-by: Ulf Magnusson<EMAIL_ADDRESS>

Codecov Report

Merging #7402 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7402   +/-   ##
=======================================
  Coverage   55.26%   55.26%
=======================================
  Files         467      467
  Lines       51641    51641
  Branches     9886     9886
=======================================
  Hits        28541    28541
  Misses      19190    19190
  Partials     3910     3910

Continue to review full report at Codecov.

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


[bug] Trying to buy tokens from an incorrect pool results in chain halting

Description
When buying incorrect tokens from a pool the chain halts
Error

0atom is smaller than 996atom: insufficient funds

How to reproduce
Compiling

make install

Initializing chain

liquidityd init testing --chain-id testing

liquidityd keys add validator --keyring-backend test

liquidityd add-genesis-account $(liquidityd keys show validator --keyring-backend test -a)<PHONE_NUMBER>stake,1000000000token

liquidityd add-genesis-account $(liquidityd keys show user1 --keyring-backend test -a)<PHONE_NUMBER>stake,1000000000atom

liquidityd gentx validator --chain-id testing --keyring-backend test

liquidityd collect-gentxs

liquidityd start > liquidityd.log 2>&1 &

sleep 10

Creating pool

liquidityd tx liquidity create-pool 1 100000000stake,100000000token --from validator --keyring-backend test --chain-id testing -y

Creating pool 2

liquidityd tx liquidity create-pool 1 100000000stake,100000000atom --from user1 --keyring-backend test --chain-id testing -y

Swap command that fails

liquidityd tx liquidity swap 1 1 1 1000stake atom 1.15 --from validator --chain-id testing --keyring-backend test -y

Log
:arrow_down:  this contains the log after running the commands :arrow_down:
failBuyingWith0Balance.log
cat failBuyingWith0Balance.log | grep CONSENSUS to see the error without noise :+1:

I fixed it in this PR, thank you for writing a detailed issue! It's been a great help :)

Ace, great job fixing this issue so quickly :smile:


Added option to change the default action on link clicked

Awesome! Thank you very much for accepting the pull request. If I can help with any other thing let me know ;)


Add customizable arguments to the functions

Signed-off-by: Farhaan Bukhsh<EMAIL_ADDRESS>

Codecov Report

Merging #59 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #59   +/-   ##
=======================================
  Coverage   42.46%   42.46%
=======================================
  Files           5        5
  Lines         146      146
=======================================
  Hits           62       62
  Misses         83       83
  Partials        1        1

Continue to review full report at Codecov.

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