CI: K8sServicesTest Checks service across nodes Tests NodePort BPF Tests with direct routing Tests with secondary NodePort device

Over the past 14 days, happened once in master and at least once in PRs:
https://jenkins.cilium.io/job/cilium-ginkgo/job/cilium/job/master/5046/testReport/Suite-k8s-1/11/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_direct_routing_Tests_with_secondary_NodePort_device/
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Kernel/2145/testReport/Suite-k8s-1/17/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_direct_routing_Tests_with_secondary_NodePort_device/
Could be a duplicate of #8945?
Stacktrace
/home/jenkins/workspace/cilium-ginkgo_cilium_master/k8s-1.11-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:512
Request from k8s1 to service tftp://[::ffff:<IP_ADDRESS>]:30151/hello failed
Expected command: kubectl exec -n kube-system log-gatherer-6c79s -- /bin/sh -c 'set -e; for i in $(seq 1 10); do curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 tftp://[::ffff:<IP_ADDRESS>]:30151/hello; done'
To succeed, but it failed:
Exitcode: 28
Stdout:

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=55510
	 	real path=/hello
	 	request_scheme=tftp

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=52738
	 	real path=/hello
	 	request_scheme=tftp

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=33402
	 	real path=/hello
	 	request_scheme=tftp

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=47691
	 	real path=/hello
	 	request_scheme=tftp

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=50861
	 	real path=/hello
	 	request_scheme=tftp

Stderr:
 	 command terminated with exit code 28

/home/jenkins/workspace/cilium-ginkgo_cilium_master/k8s-1.11-gopath/src/github.com/cilium/cilium/test/k8sT/Services.go:676

Standard Output
Number of "context deadline exceeded" in logs: 0
⚠  Number of "level=error" in logs: 8
⚠  Number of "level=warning" in logs: 54
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
Top 5 errors/warnings:
Deleting no longer present service
Mutation detector is enabled, this will result in memory leakage.
Unable to enqueue endpoint policy visibility event
Hubble server will be exposing its API insecurely on this address
BPF system config check: NOT OK.
Cilium pods: [cilium-8s7pc cilium-zfp98]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod                           Ingress   Egress
prometheus-556f8994ff-vjjsm
test-k8s2-848b6f7864-wclfd
testclient-jdxfl
testclient-pvq76
testds-ffr2t
testds-hz59j
coredns-687db6485c-fvvfj
grafana-5968d99cc4-zr9qn
Cilium agent 'cilium-8s7pc': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 28 Failed 0
Cilium agent 'cilium-zfp98': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 28 Failed 0

Standard error
See standard error
21:49:30 STEP: Installing Cilium
21:49:31 STEP: Waiting for Cilium to become ready
21:49:31 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
21:49:36 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
21:49:41 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
21:49:46 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
21:49:51 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
21:49:56 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
21:50:01 STEP: Number of ready Cilium pods: 2
21:50:01 STEP: Validating if Kubernetes DNS is deployed
21:50:01 STEP: Checking if deployment is ready
21:50:01 STEP: Checking if kube-dns service is plumbed correctly
21:50:01 STEP: Checking if DNS can resolve
21:50:01 STEP: Checking if pods have identity
21:50:02 STEP: Kubernetes DNS is up and operational
21:50:02 STEP: Validating Cilium Installation
21:50:02 STEP: Performing Cilium controllers preflight check
21:50:02 STEP: Performing Cilium status preflight check
21:50:02 STEP: Performing Cilium health check
21:50:04 STEP: Performing Cilium service preflight check
21:50:04 STEP: Performing K8s service preflight check
21:50:05 STEP: Waiting for cilium-operator to be ready
21:50:05 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator")
21:50:05 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") => <nil>
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://[::ffff:<IP_ADDRESS>]:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://[::ffff:<IP_ADDRESS>]:30151/hello"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://[::ffff:<IP_ADDRESS>]:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://[::ffff:<IP_ADDRESS>]:30151/hello"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 HTTP requests from outside cluster to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 HTTP requests from outside cluster to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 HTTP requests from outside cluster to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 HTTP requests from outside cluster to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 HTTP requests from outside cluster to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 HTTP requests from outside cluster to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 HTTP requests from outside cluster to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 HTTP requests from outside cluster to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://<IP_ADDRESS>:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://<IP_ADDRESS>:10080"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://<IP_ADDRESS>:10069/hello"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://[::ffff:<IP_ADDRESS>]:31686"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://<IP_ADDRESS>:30151/hello"
21:50:06 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://[::ffff:<IP_ADDRESS>]:30151/hello"
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service tftp://<IP_ADDRESS>:10069/hello
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service http://<IP_ADDRESS>:10080
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service http://<IP_ADDRESS>:31686
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service tftp://<IP_ADDRESS>:30151/hello
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service http://[::ffff:<IP_ADDRESS>]:31686
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service tftp://[::ffff:<IP_ADDRESS>]:30151/hello
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service http://<IP_ADDRESS>:31686
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service tftp://<IP_ADDRESS>:30151/hello
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service http://[::ffff:<IP_ADDRESS>]:31686
21:50:07 STEP: Making 10 curl requests from testclient-jdxfl pod to service tftp://[::ffff:<IP_ADDRESS>]:30151/hello
21:50:09 STEP: Making 10 curl requests from testclient-pvq76 pod to service http://<IP_ADDRESS>:10080
21:50:10 STEP: Making 10 curl requests from testclient-pvq76 pod to service http://<IP_ADDRESS>:31686
21:50:10 STEP: Making 10 curl requests from testclient-pvq76 pod to service tftp://<IP_ADDRESS>:30151/hello
21:50:10 STEP: Making 10 curl requests from testclient-pvq76 pod to service tftp://<IP_ADDRESS>:10069/hello
21:50:10 STEP: Making 10 curl requests from testclient-pvq76 pod to service http://[::ffff:<IP_ADDRESS>]:31686
21:50:11 STEP: Making 10 curl requests from testclient-pvq76 pod to service tftp://[::ffff:<IP_ADDRESS>]:30151/hello
21:50:11 STEP: Making 10 curl requests from testclient-pvq76 pod to service tftp://[::ffff:<IP_ADDRESS>]:30151/hello
21:50:11 STEP: Making 10 curl requests from testclient-pvq76 pod to service http://<IP_ADDRESS>:31686
21:50:11 STEP: Making 10 curl requests from testclient-pvq76 pod to service http://[::ffff:<IP_ADDRESS>]:31686
21:50:12 STEP: Making 10 curl requests from testclient-pvq76 pod to service tftp://<IP_ADDRESS>:30151/hello
FAIL: Request from k8s1 to service tftp://[::ffff:<IP_ADDRESS>]:30151/hello failed
Expected command: kubectl exec -n kube-system log-gatherer-6c79s -- /bin/sh -c 'set -e; for i in $(seq 1 10); do curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 tftp://[::ffff:<IP_ADDRESS>]:30151/hello; done'
To succeed, but it failed:
Exitcode: 28
Stdout:

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=55510
	 	real path=/hello
	 	request_scheme=tftp

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=52738
	 	real path=/hello
	 	request_scheme=tftp

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=33402
	 	real path=/hello
	 	request_scheme=tftp

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=47691
	 	real path=/hello
	 	request_scheme=tftp

	 Hostname: testds-hz59j

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=50861
	 	real path=/hello
	 	request_scheme=tftp

Stderr:
 	 command terminated with exit code 28

=== Test Finished at 2020-06-09T21:50:32Z====
21:50:32 STEP: Running JustAfterEach block for EntireTestsuite K8sServicesTest
===================== TEST FAILED =====================
21:50:38 STEP: Running AfterFailed block for EntireTestsuite K8sServicesTest
21:50:38 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:39 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:50:39 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:40 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0
Stdout:
 	 NAMESPACE           NAME                               READY   STATUS    RESTARTS   AGE   IP              NODE   NOMINATED NODE
	 cilium-monitoring   grafana-5968d99cc4-zr9qn           1/1     Running   0          1h    <IP_ADDRESS>      k8s1   <none>
	 cilium-monitoring   prometheus-556f8994ff-vjjsm        1/1     Running   0          1h    <IP_ADDRESS>      k8s1   <none>
	 default             test-k8s2-848b6f7864-wclfd         2/2     Running   0          9m    <IP_ADDRESS>       k8s2   <none>
	 default             testclient-jdxfl                   1/1     Running   0          9m    <IP_ADDRESS>      k8s1   <none>
	 default             testclient-pvq76                   1/1     Running   0          9m    <IP_ADDRESS>      k8s2   <none>
	 default             testds-ffr2t                       2/2     Running   0          2m    <IP_ADDRESS>       k8s1   <none>
	 default             testds-hz59j                       2/2     Running   0          2m    <IP_ADDRESS>       k8s2   <none>
	 kube-system         cilium-8s7pc                       1/1     Running   0          1m    <IP_ADDRESS>   k8s2   <none>
	 kube-system         cilium-operator-5c59bd8f8c-46t6p   1/1     Running   0          1m    <IP_ADDRESS>   k8s2   <none>
	 kube-system         cilium-zfp98                       1/1     Running   0          1m    <IP_ADDRESS>   k8s1   <none>
	 kube-system         coredns-687db6485c-fvvfj           1/1     Running   0          1h    <IP_ADDRESS>      k8s2   <none>
	 kube-system         etcd-k8s1                          1/1     Running   0          1h    <IP_ADDRESS>   k8s1   <none>
	 kube-system         kube-apiserver-k8s1                1/1     Running   0          1h    <IP_ADDRESS>   k8s1   <none>
	 kube-system         kube-controller-manager-k8s1       1/1     Running   0          1h    <IP_ADDRESS>   k8s1   <none>
	 kube-system         kube-scheduler-k8s1                1/1     Running   0          1h    <IP_ADDRESS>   k8s1   <none>
	 kube-system         log-gatherer-6c79s                 1/1     Running   0          1h    <IP_ADDRESS>   k8s1   <none>
	 kube-system         log-gatherer-d28vk                 1/1     Running   0          1h    <IP_ADDRESS>   k8s2   <none>
	 kube-system         log-gatherer-qggqx                 1/1     Running   0          1h    <IP_ADDRESS>   k8s3   <none>
	 kube-system         registry-adder-4lfz9               1/1     Running   0          1h    <IP_ADDRESS>   k8s3   <none>
	 kube-system         registry-adder-dbsdh               1/1     Running   0          1h    <IP_ADDRESS>   k8s2   <none>
	 kube-system         registry-adder-lv2rf               1/1     Running   0          1h    <IP_ADDRESS>   k8s1   <none>

Stderr:

Fetching command output from pods [cilium-8s7pc cilium-zfp98]
21:50:41 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:41 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:50:41 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:41 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:50:42 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:42 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:50:43 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:43 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:50:43 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:43 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:50:44 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:44 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:50:45 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:45 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:50:45 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium")
21:50:45 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium") => <nil>
21:51:02 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs --field-selector='spec.nodeName!=k8s3'")
21:51:02 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs --field-selector='spec.nodeName!=k8s3'") => <nil>
21:51:02 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs --field-selector='spec.nodeName!=k8s3'")
21:51:02 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs --field-selector='spec.nodeName!=k8s3'") => <nil>
21:51:03 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs --field-selector='spec.nodeName!=k8s3'")
21:51:03 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs --field-selector='spec.nodeName!=k8s3'") => <nil>
cmd: kubectl exec -n kube-system cilium-8s7pc -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend               Service Type   Backend
	 1    <IP_ADDRESS>:443          ClusterIP      1 => <IP_ADDRESS>:6443
	 2    <IP_ADDRESS>:53          ClusterIP      1 => <IP_ADDRESS>:53
	 3    <IP_ADDRESS>:3000      ClusterIP      1 => <IP_ADDRESS>:3000
	 4    <IP_ADDRESS>:9090      ClusterIP      1 => <IP_ADDRESS>:9090
	 5    <IP_ADDRESS>:20080    ExternalIPs    1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 6    <IP_ADDRESS>:20069    ExternalIPs    1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 7    <IP_ADDRESS>:30909    NodePort       1 => <IP_ADDRESS>:80
	 8    <IP_ADDRESS>:30811    NodePort       1 => <IP_ADDRESS>:69
	 9    <IP_ADDRESS>:80         ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 10   <IP_ADDRESS>:69         ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 11   <IP_ADDRESS>:10080   ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 12   <IP_ADDRESS>:10069   ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 13   <IP_ADDRESS>:31686    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 15   <IP_ADDRESS>:31686          NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 16   <IP_ADDRESS>:30151          NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 17   <IP_ADDRESS>:30151    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 19   <IP_ADDRESS>:10069    ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 20   <IP_ADDRESS>:10080    ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 22   <IP_ADDRESS>:31904    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 23   <IP_ADDRESS>:31904          NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 24   <IP_ADDRESS>:30198          NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 25   <IP_ADDRESS>:30198    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 27   <IP_ADDRESS>:10080   ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 28   <IP_ADDRESS>:10069   ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 30   <IP_ADDRESS>:30909    NodePort       1 => <IP_ADDRESS>:80
	 31   <IP_ADDRESS>:30909          NodePort       1 => <IP_ADDRESS>:80
	 32   <IP_ADDRESS>:30811    NodePort       1 => <IP_ADDRESS>:69
	 34   <IP_ADDRESS>:30811          NodePort       1 => <IP_ADDRESS>:69
	 35   <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80
	 36   <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69
	 37   <IP_ADDRESS>:31463    NodePort       1 => <IP_ADDRESS>:80
	 39   <IP_ADDRESS>:31463          NodePort       1 => <IP_ADDRESS>:80
	 40   <IP_ADDRESS>:31887    NodePort       1 => <IP_ADDRESS>:69
	 42   <IP_ADDRESS>:31887          NodePort       1 => <IP_ADDRESS>:69
	 43   <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69
	 44   <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80
	 45   <IP_ADDRESS>:31349    NodePort       1 => <IP_ADDRESS>:69
	 47   <IP_ADDRESS>:31349          NodePort       1 => <IP_ADDRESS>:69
	 48   <IP_ADDRESS>:31970    NodePort       1 => <IP_ADDRESS>:80
	 50   <IP_ADDRESS>:31970          NodePort       1 => <IP_ADDRESS>:80
	 51   <IP_ADDRESS>:80      ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 53   <IP_ADDRESS>:30903          NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 54   <IP_ADDRESS>:30903    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 55   <IP_ADDRESS>:80       ClusterIP      1 => <IP_ADDRESS>:80
	 56   <IP_ADDRESS>:31843    NodePort       1 => <IP_ADDRESS>:80
	 58   <IP_ADDRESS>:31843          NodePort       1 => <IP_ADDRESS>:80
	 59   <IP_ADDRESS>:20080     ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 60   <IP_ADDRESS>:20069     ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 61   <IP_ADDRESS>:20080      ExternalIPs    1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 62   <IP_ADDRESS>:20069      ExternalIPs    1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 64   <IP_ADDRESS>:32755          NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 65   <IP_ADDRESS>:32755    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 66   <IP_ADDRESS>:31124    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 68   <IP_ADDRESS>:31124          NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 69   <IP_ADDRESS>:8080     HostPort       1 => <IP_ADDRESS>:80
	 70   <IP_ADDRESS>:6969     HostPort       1 => <IP_ADDRESS>:69
	 71   <IP_ADDRESS>:30903    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 72   <IP_ADDRESS>:30198    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 73   <IP_ADDRESS>:31904    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 74   <IP_ADDRESS>:31887    NodePort       1 => <IP_ADDRESS>:69
	 75   <IP_ADDRESS>:31463    NodePort       1 => <IP_ADDRESS>:80
	 76   <IP_ADDRESS>:31970    NodePort       1 => <IP_ADDRESS>:80
	 77   <IP_ADDRESS>:31349    NodePort       1 => <IP_ADDRESS>:69
	 78   <IP_ADDRESS>:31843    NodePort       1 => <IP_ADDRESS>:80
	 79   <IP_ADDRESS>:31686    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 80   <IP_ADDRESS>:30151    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 81   <IP_ADDRESS>:32755    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 82   <IP_ADDRESS>:31124    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69

Stderr:

cmd: kubectl exec -n kube-system cilium-8s7pc -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                       IPv6       IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 218        Disabled           Disabled          4          reserved:health                                   fd00::4b   <IP_ADDRESS>   ready
	 1232       Disabled           Disabled          16555      k8s:io.cilium.k8s.policy.cluster=default          fd00::c8   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=coredns
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=kube-dns
	 2183       Disabled           Disabled          23024      k8s:io.cilium.k8s.policy.cluster=default          fd00::86   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=test-k8s2
	 2474       Disabled           Disabled          5683       k8s:io.cilium.k8s.policy.cluster=default          fd00::cb   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDS
	 3093       Disabled           Disabled          1          reserved:host                                                             ready
	 3254       Disabled           Disabled          10761      k8s:io.cilium.k8s.policy.cluster=default          fd00::33   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDSClient

Stderr:

cmd: kubectl exec -n kube-system cilium-zfp98 -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend               Service Type   Backend
	 1    <IP_ADDRESS>:9090      ClusterIP      1 => <IP_ADDRESS>:9090
	 2    <IP_ADDRESS>:443          ClusterIP      1 => <IP_ADDRESS>:6443
	 3    <IP_ADDRESS>:53          ClusterIP      1 => <IP_ADDRESS>:53
	 4    <IP_ADDRESS>:3000      ClusterIP      1 => <IP_ADDRESS>:3000
	 5    <IP_ADDRESS>:20080    ExternalIPs    1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 6    <IP_ADDRESS>:20069    ExternalIPs    1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 7    <IP_ADDRESS>:31843    NodePort
	 8    <IP_ADDRESS>:31463    NodePort
	 9    <IP_ADDRESS>:69         ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 10   <IP_ADDRESS>:80         ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 11   <IP_ADDRESS>:10080   ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 12   <IP_ADDRESS>:10069   ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 13   <IP_ADDRESS>:31686    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 15   <IP_ADDRESS>:31686          NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 16   <IP_ADDRESS>:30151    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 18   <IP_ADDRESS>:30151          NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 19   <IP_ADDRESS>:10069    ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 20   <IP_ADDRESS>:10080    ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 21   <IP_ADDRESS>:30198          NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 22   <IP_ADDRESS>:30198    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 25   <IP_ADDRESS>:31904          NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 26   <IP_ADDRESS>:31904    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 27   <IP_ADDRESS>:10080   ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 28   <IP_ADDRESS>:10069   ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 29   <IP_ADDRESS>:30909    NodePort       1 => <IP_ADDRESS>:80
	 31   <IP_ADDRESS>:30909          NodePort       1 => <IP_ADDRESS>:80
	 32   <IP_ADDRESS>:30811    NodePort       1 => <IP_ADDRESS>:69
	 34   <IP_ADDRESS>:30811          NodePort       1 => <IP_ADDRESS>:69
	 35   <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80
	 36   <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69
	 38   <IP_ADDRESS>:31463    NodePort
	 39   <IP_ADDRESS>:31463          NodePort
	 41   <IP_ADDRESS>:31887    NodePort
	 42   <IP_ADDRESS>:31887          NodePort
	 43   <IP_ADDRESS>:10080     ClusterIP      1 => <IP_ADDRESS>:80
	 44   <IP_ADDRESS>:10069     ClusterIP      1 => <IP_ADDRESS>:69
	 45   <IP_ADDRESS>:31970    NodePort       1 => <IP_ADDRESS>:80
	 47   <IP_ADDRESS>:31970          NodePort       1 => <IP_ADDRESS>:80
	 49   <IP_ADDRESS>:31349          NodePort       1 => <IP_ADDRESS>:69
	 50   <IP_ADDRESS>:31349    NodePort       1 => <IP_ADDRESS>:69
	 51   <IP_ADDRESS>:80      ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 52   <IP_ADDRESS>:30903    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 54   <IP_ADDRESS>:30903          NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 55   <IP_ADDRESS>:80       ClusterIP      1 => <IP_ADDRESS>:80
	 56   <IP_ADDRESS>:31843    NodePort
	 58   <IP_ADDRESS>:31843          NodePort
	 59   <IP_ADDRESS>:20080     ClusterIP      1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 60   <IP_ADDRESS>:20069     ClusterIP      1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 61   <IP_ADDRESS>:20080      ExternalIPs    1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 62   <IP_ADDRESS>:20069      ExternalIPs    1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 64   <IP_ADDRESS>:32755          NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 65   <IP_ADDRESS>:32755    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 66   <IP_ADDRESS>:31124    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 68   <IP_ADDRESS>:31124          NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 69   <IP_ADDRESS>:31887    NodePort
	 70   <IP_ADDRESS>:30903    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 71   <IP_ADDRESS>:31686    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 72   <IP_ADDRESS>:30151    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 73   <IP_ADDRESS>:30909    NodePort       1 => <IP_ADDRESS>:80
	 74   <IP_ADDRESS>:30811    NodePort       1 => <IP_ADDRESS>:69
	 75   <IP_ADDRESS>:30198    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80
	 76   <IP_ADDRESS>:31904    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 77   <IP_ADDRESS>:31970    NodePort       1 => <IP_ADDRESS>:80
	 78   <IP_ADDRESS>:31349    NodePort       1 => <IP_ADDRESS>:69
	 79   <IP_ADDRESS>:31124    NodePort       1 => <IP_ADDRESS>:69
	                                            2 => <IP_ADDRESS>:69
	 80   <IP_ADDRESS>:32755    NodePort       1 => <IP_ADDRESS>:80
	                                            2 => <IP_ADDRESS>:80

Stderr:

cmd: kubectl exec -n kube-system cilium-zfp98 -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                              IPv6        IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 168        Disabled           Disabled          10761      k8s:io.cilium.k8s.policy.cluster=default                 fd00::13a   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDSClient
	 372        Disabled           Disabled          16453      k8s:app=prometheus                                       fd00::112   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=prometheus-k8s
	                                                            k8s:io.kubernetes.pod.namespace=cilium-monitoring
	 692        Disabled           Disabled          5683       k8s:io.cilium.k8s.policy.cluster=default                 fd00::17f   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDS
	 1283       Disabled           Disabled          6100       k8s:app=grafana                                          fd00::1d9   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=cilium-monitoring
	 1672       Disabled           Disabled          1          reserved:host                                                                     ready
	 2514       Disabled           Disabled          4          reserved:health                                          fd00::136   <IP_ADDRESS>   ready

Stderr:

===================== Exiting AfterFailed =====================
21:51:03 STEP: Running AfterEach for block EntireTestsuite K8sServicesTest
21:51:03 STEP: Running AfterEach for block EntireTestsuite

1dd77f1b_K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_direct_routing_Tests_with_secondary_NodePort_device.zip
96a5b6da_K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_direct_routing_Tests_with_secondary_NodePort_device.zip

Could be a duplicate of #8945?

Yep, the symptoms are the same.

Last occurrence on master: https://jenkins.cilium.io/job/cilium-ginkgo/job/cilium/job/master/5238/
1604061f_K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_direct_routing_Tests_with_secondary_NodePort_device.zip

Last occurrence on master: https://jenkins.cilium.io/job/cilium-ginkgo/job/cilium/job/master/5238/
1604061f_K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_direct_routing_Tests_with_secondary_NodePort_device.zip

@nebril This was run before the fix in #12248 was merged. To verify, I checked and found thousands of lines of this in cilium agent logs:
...
2020-06-26T20:16:58.232516281Z level=debug msg="dnsproxy: Wrote DNS response (12/12 bytes) from <IP_ADDRESS>:38341 to <IP_ADDRESS>:69" subsys=fqdn/dnsproxy
2020-06-26T20:16:58.232687923Z level=debug msg="dnsproxy: Wrote DNS response (12/12 bytes) from <IP_ADDRESS>:38341 to <IP_ADDRESS>:69" subsys=fqdn/dnsproxy
2020-06-26T20:16:58.232740204Z level=debug msg="dnsproxy: Wrote DNS response (12/12 bytes) from <IP_ADDRESS>:38341 to <IP_ADDRESS>:69" subsys=fqdn/dnsproxy
2020-06-26T20:16:58.232959706Z level=debug msg="dnsproxy: Wrote DNS response (12/12 bytes) from <IP_ADDRESS>:38341 to <IP_ADDRESS>:69" subsys=fqdn/dnsproxy
2020-06-26T20:16:58.233163419Z level=debug msg="dnsproxy: Wrote DNS response (12/12 bytes) from <IP_ADDRESS>:38341 to <IP_ADDRESS>:69" subsys=fqdn/dnsproxy
2020-06-26T20:16:58.233358984Z level=debug msg="dnsproxy: Wrote DNS response (12/12 bytes) from <IP_ADDRESS>:38341 to <IP_ADDRESS>:69" subsys=fqdn/dnsproxy
2020-06-26T20:16:58.233509821Z level=debug msg="dnsproxy: Wrote DNS response (12/12 bytes) from <IP_ADDRESS>:38341 to <IP_ADDRESS>:69" subsys=fqdn/dnsproxy
2020-06-26T20:16:58.233679704Z level=debug msg="dnsproxy: Wrote DNS response (12/12 bytes) from <IP_ADDRESS>:38341 to <IP_ADDRESS>:69" subsys=fqdn/dnsproxy
...

In the above the port 38341 is the DNS proxy listening port, and 69 is the TFTP server port.
In the testds-udp logs we find:
2020-06-26T20:16:40.279867593Z 2020/06/26 20:16:40 Read "hello" requested from <IP_ADDRESS>:38341
2020-06-26T20:16:42.485746943Z 2020/06/26 20:16:42 Read "hello" requested from <IP_ADDRESS>:38341
2020-06-26T20:16:44.489791668Z 2020/06/26 20:16:44 Read "hello" requested from <IP_ADDRESS>:38341

i.e., three attempts for "hello" from the source port 38341, replies to which were intercepted by the DNS proxy.

Fixed by #12248, closing.


Fix instance_name if statement in templates

This is the fix for PR #47

Thanks for submitting this - I've fixed the bug in a more robust way in edfac57cf19c183b922c82d1c63dc098b56e923c, version 4.1.4 has also been released to the Forge :)

Thanks. Your patch is indeed a more elegant way to fix it it 👍


bug: Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/treesitter/language.lua:107: no parser for 'fstab' language, see :help treesitter-parsers

Neovim version (nvim -v)
NVIM v0.11.0-dev-504+gaa853f362-dirty
Build type: Release
LuaJIT 2.1.1716656478

Operating system
Linux
Terminal emulator / GUI
kitty 0.35.2
Describe the bug
I have a markdown file with a code block containing # vim: ft=fstab (which is a valid file type). This triggers the following error when opening said markdown file with markdown.nvim enabled:
Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/treesitter/language.lua:107: no parser for 'fstab' language, see :help treesitter-parsers
stack traceback:
	[C]: in function 'error'
	/usr/share/nvim/runtime/lua/vim/treesitter/language.lua:107: in function 'add'
	/usr/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:111: in function 'new'
	/usr/share/nvim/runtime/lua/vim/treesitter.lua:41: in function '_create_parser'
	/usr/share/nvim/runtime/lua/vim/treesitter.lua:108: in function 'get_parser'
	...share/nvim/lazy/markdown.nvim/lua/render-markdown/ui.lua:119: in function 'parse_buffer'
	...share/nvim/lazy/markdown.nvim/lua/render-markdown/ui.lua:74: in function 'render'
	...share/nvim/lazy/markdown.nvim/lua/render-markdown/ui.lua:39: in function <...share/nvim/lazy/markdown.nvim/lua/render-markdown/ui.lua:33>

To reproduce:

Add # vim: ft=fstab (also occurs with # vim: ft=zzz for example) in a code block of a new markdown file
Open the markdown file with markdown.nvim enabled
The error is triggered

Expected behavior
No error.
Healthcheck output
==============================================================================
render-markdown: require("render-markdown.health").check()

markdown.nvim [neovim version] ~
- OK Version >= 0.10

markdown.nvim [configuration] ~
- OK valid

markdown.nvim [nvim-treesitter] ~
- OK installed
- OK markdown: parser installed
- OK markdown: highlight enabled
- OK markdown_inline: parser installed
- OK markdown_inline: highlight enabled
- WARNING latex: parser not installed
  - ADVICE:
    - Disable LaTeX support to avoid this warning by setting { latex = { enabled = false } }

markdown.nvim [executables] ~
- WARNING latex2text: not installed
  - ADVICE:
    - Disable LaTeX support to avoid this warning by setting { latex = { enabled = false } }

markdown.nvim [conflicts] ~
- OK headlines: not installed
- OK obsidian: not installed

Plugin configuration
return {
  "MeanderingProgrammer/markdown.nvim",
  ft = "markdown",
  opts = {},
}

Confirmations

[X] I have provided markdown text for any screenshots used in my description & understand that my issue will be closed if I have not

Additional information
No response

Since the filetype gets overridden to fstab and there is no parser defined by treesitter for this filetype I wouldn't expect it to work. This type of setup creates 2 FileType events, the first one for markdown causes this plugin to attempt to parse the file. However when we later attempt to get the parser, treesitter only picks up the fstab filetype and fails.
I have pushed a fix to avoid errors in these cases: https://github.com/MeanderingProgrammer/markdown.nvim/commit/ddb454792dd85c0f6039ec14006aecaee67e782d.
So at least it won't break but it also won't do any rendering, effectively becomes a no-op. If you want this plugin to render fstab as it would markdown you'll need to add the following somewhere in your config:
vim.treesitter.language.register('markdown', 'fstab')

Which tells treesitter to parse fstab files as if they were markdown. Similar for all other filetypes you want to treat as markdown.
This will change the highlighting behavior for all of these filetypes.


Switch "native" check from being x86_64 only to checking HOST

If HOST==TARGET, we know we're compiling natively. Set a new rustc cfg for this and use it where we previously checked for x86_64.
I was trying to run tests on my M1 MacBook Pro and couldn't since it isn't x86_64. Also, the currently configured nightly compiler for asm doesn't have M1 support, so I updated that. I'm fine reverting that change though, I can just do that locally, but I'm sure others will hit the same issue and it's a bit old...

🏷 @japaric since it looks like rust-highfive doesn't like this PR and you modified this area of the build script previously

Failing until #372 merges

rebased on top of the asm PR to fix CI

This is pretty straight forward and enables ARM computers to run the CI


cask/url: deprecate url do blocks.

We're removing these in https://github.com/Homebrew/homebrew-cask/pull/186501 and forbidding in https://github.com/Homebrew/brew/pull/18404 so let's deprecate them too (because having functionality like this we don't allow in official taps is recipe for accidental breakage and deprecation later).

Thanks @Rylan12!

How would you recommend using HTTP header authentication for downloads without url do?

As the linked PR says:

This PR adds a rubocop check that forbids the use of url do blocks in homebrew/cask. It still allows them to be used in non-official taps.

So nothing changes for third-party taps, really.


it sometimes crashes

Description
What steps will reproduce the problem?

What is the expected output? What do you see instead?
Please provide any additional information below
Version and main components

Spyder Version: 3.2.6
Python Version: 3.6.5
Qt Versions: 5.6.2, PyQt5 5.6 on Windows

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  0.22.0 (OK)
numpy >=1.7      :  1.14.0 (OK)
sphinx >=0.6.6   :  1.6.6 (OK)
rope >=0.9.4     :  0.10.7 (OK)
jedi >=0.9.0     :  0.11.1 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
sympy >=0.7.3    :  1.1.1 (OK)
cython >=0.21    :  0.27.3 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
IPython >=4.0    :  6.2.1 (OK)
pylint >=0.25    :  1.8.2 (OK)

Closing because there's no information here to understand what could be the cause of the error.

If you can describe in detail the circumstances in which the error occurred, and post the information listed in relevant subsection of the Spyder Troubleshooting Guide as a comment to this issue, then please re-open.


  The terminal process terminated with exit code:<PHONE_NUMBER>

Issue Type: Bug
while opeing Terminal ,getting The terminal process terminated with exit code:<PHONE_NUMBER>
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:54:45.096Z)
OS version: Windows_NT x64 10.0.10240

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz (4 x 2395)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
5.90GB (1.98GB free)

Process Argv
C:\Users\srini\Desktop\Angular_Tutorial\First-app

Screen Reader
no

VM
0%

Extensions: none

Nothing worked out

Please follow the guidance in https://github.com/microsoft/terminal/issues/1838 and see if that helps.

Yup ..its working now ..Thanks

/duplicate https://github.com/microsoft/vscode/issues/73790, you need to disable legacy console mode in cmd.exe/conhost's properties.


FuzzyEnumModule validation against enum name() instead of toString() breaks compatibility with jsonschema2pojo

Since upgrading from DW 0.6.2 to 0.7.1 I'm getting the following error deserializing enum values in POJOs generated by jsonschema2pojo:
partlyCloudy was not one of [PARTY_CLOUDY, CLEAR]

This is happening with a field in a class generated by jsonschema2pojo. When jsonschema2pojo sees a field in a JSON schema that is declared as an enum...
"weather": {
    "enum": [ "partlyCloudy", "clear"]
},

It generates a Java enum like this:
public static enum Weather {
    PARTY_CLOUDY("partlyCloudy"),
    CLEAR("clear");
    private final String value;

    private Weather(String value) {
        this.value = value;
    }

    @JsonValue
    @Override
    public String toString() {
        return this.value;
    }
}

But FuzzyEnumModule.deserialize() is calling name() instead of toString() on the enum to compare its value to the deserialized value, and the literal enum name "PARTLY_CLOUDY" doesn't match the deserialized value "partlyCloudy". Changing FuzzyEnumModule to use toString() might break existing code (although presumably that's what the old deserializer did). If that's not feasible, would it be possible to provide a configuration option to make FuzzyEnumModule be even more fuzzy and call toString()? Either that, or is there a way to specify that the standard deserializer should be used?

This should depend on com.fasterxml.jackson.databind.DeserializationFeature.READ_ENUMS_USING_TO_STRING being enabled or not in the object mapper?

The read enums using to string is a global config which isn't always true.  We have a mix-match use where sometimes we need to string and sometimes JsonCreator.  I already have a PR that fixes this with unit tests.
https://github.com/dropwizard/dropwizard/pull/1220

In Jackson 2, @JsonValue is used to mark a method to serialize to, but also (as a special case) is used to mark how enums should deserialize. From the javadoc for @JsonValue:

NOTE: when use for Java enums, one additional feature is that value returned by annotated method is also considered to be the value to deserialize from, not just JSON String to serialize as. This is possible since set of Enum values is constant and it is possible to define mapping, but can not be done in general for POJO types; as such, this is not used for POJO deserialization.

Rather than consuming toString, would it make sense to consume this annotation in FuzzyEnumModule as well to maintain compatibility with base Jackson?  Without this, enums that deserialize correctly in raw Jackson will throw JsonMappingException when FuzzyEnumModule is added.

Has this been fixed by #1340?

Closed by #1220/#1340


SITES-22111 - Extend core CIF graphQL resolver with new function/API to expose Errors

added getErrors() in AbstractRetriever
provided implementation for getErrors() in existing retrievers

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

@LSantha pls also add Adi as reviewer thanks!

@ asilaghi


docs: add a note regarding aiohttp and proxy envvars

Hello everyone,
I just spent quite some time debugging why I couldn't use gcsfs to read from a bucket, allthough gsutil worked fine. I realized that aiohttp ignores HTTP_PROXY and HTTPS_PROXY by default.
This PR adds a small note to the docs to point other users to the solution.
Cheers,
Andreas 😃

Thanks for digging.


Version 1.14.3 failing with obscure "Code is too complex to typecheck!" error

I include luau-lsp v1.14.3 in my foreman.toml and I have the following script to run it:
#!/usr/bin/env bash

curl -s -O https://raw.githubusercontent.com/JohnnyMorganz/luau-lsp/master/scripts/globalTypes.d.lua

rojo sourcemap --include-non-scripts --output sourcemap.json

luau-lsp analyze --sourcemap=sourcemap.json --defs=globalTypes.d.lua --defs=testez.d.lua --ignore=**/_Index/** src/

rm globalTypes.d.lua

However, on this version I'm getting the following errors which don't give me any helpful information on what needs to be fixed:
$ ./scripts/analyze.sh
Created sourcemap at sourcemap.json
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area
(1,1): TypeError: Internal error: Code is too complex to typecheck! Consider adding type annotations around this area

This typically means you are hitting internal type checker limits. There isn't much we can do right now, apart from bumping up those limits.
You can try playing around with the following FFlags (by using --flag:NAME=VALUE). I've also included the current defaults for reference, I would recommend increasing those defaults:

LuauTarjanChildLimit - 10000 (or set to 0 to disable)
LuauTypeInferIterationLimit - 20000 (or set to 0 to disable)

The following are extra flags which may be useful if the above don't work:

LuauCheckRecursionLimit - 300
LuauTypeInferTypePackLoopLimit - 5000
LuauTypeInferRecursionLimit - 165
LuauAutocompleteCheckTimeoutMs - (or set to 0 to disable) - only really affects the language server rather than CLI


QoS Settings & NodeOptions

Same as here: https://github.com/THI-Drone/common_package/pull/12

Unfortunately, it doesn't seem to work when used with the qr_code_scanner_node.
It complains about not finding NodeOptions in rclpy.node.

Is this a potential blocker if it stays unsolved? I would think it does not make sense to only have the QoS in the cpp nodes (in case this does not work out)

@J0las said that it seems like NodeOptions don't exist in the Python version as they do in C++.
Maybe there are other ways to set the QoS, but yes, this is a blocker.

@J0las said that it seems like NodeOptions don't exist in the Python version as they do in C++. Maybe there are other ways to set the QoS, but yes, this is a blocker.

@Finndows @maf0115 you guys should also be aware of this. Please see if you can help out on this topic.

According to @J0las and @di-math, setting the QoS in the subscriber is enough. Therefore, we can close this PR.


Address review comments on Arm(R) Ethos(TM)-U PR 3/6

This patch addresses the review comments left on https://github.com/apache/tvm/pull/8806. Small changes are made to the API of ScheduleBuilder so that it can be reused in the NPU compiler, allowing us to remove a largely duplicated piece of code.

cc @mbs-octoml @jroesch PTAL

Apologies for the delay fixing CI here, having some environment problems locally. Will hopefully be fixed by next week.


Network Instance Config Reconciler

The process of converting the declarative high-level network instance config coming from the controller into the corresponding low-level (Linux) network stack config items (routes, bridges, iptables, etc.) is scattered all across the zedrouter codebase (+ VLANs are configured in domainmgr) and it is tightly coupled to the Linux network stack. Given the considerable amount of config items that even a single network instance with only a couple of ACL rules translates into, the current implementation ended up being quite complicated to understand and debug/maintain, not to mention extend. In order to avoid adding even more complexity, it doesn't support most kinds of config changes (it is necessary to recreate network instances). Lastly, since the current code makes netlink and other syscalls directly, without hiding them behind some interface, it is not possible to "mock" the host system and write some unit tests for zedrouter.
In this commit we introduce a new component NIReconciler (NI = network instance), which, just like NIM's DPCReconciler, is based on Reconciler. NIReconciler is an interface and LinuxNIReconciler is just one (and currently the only one) implementation. By using the generic Reconciler, NIReconciler only needs to determine what the intended state of the network stack should be for the given EdgeDevConfig received from the controller wrt. app connectivity (specifically it reads the config for network instances and app interfaces). And then the problem of intended vs. current state reconciliation is taken care of by the Reconciler, making NIReconciler considerably less complex than the current zedrouter's approach, while additionally supporting any config change (that makes sense).
LinuxNIReconciler is covered by unit tests (around 86% coverage, excluding "mocked" parts).
This commit only introduces NIReconciler as another package under pillar. It is not yet integrated into zedrouter. This will be done in the next commit/PR (already prepared on my fork, including documentation). I decided to split this into two PRs to make the challenging review process somewhat easier.
The only changes outside of introducing a new package here are:

Small improvements in iptables - mainly adding support for ipsets
Split base routing table index between DPC and network instances for more clarity
Change HostSubnet() to return net.IPNet with pointer, not as a value (in net and other standard packages IPNet is always used with pointer)

Do you think such a split into pre and post parts will be hampered by applying the reconciles to the app network configuration?

That should be relative easy to do - just returning from this function with empty set of intended ACL rules if the particular VIF does not exist yet. When the VIF will appear the set of intended rules would be rebuilt and reconciliation triggered. In similar way access VLANs are done, i.e. only after VIF appears we can set access VLAN parameters (with NIReconciler, managing switch NI VLANs is going to be moved out of domainmgr).

I don't understand why yetus complains about
Check failure on line 19 in pkg/pillar/nireconciler/linux_currentstate.go
GitHub Actions/ yetus
golangcilint: "github.com/vishvananda/netlink" imported but not used (typecheck)
because such an error would also cause a build failure.

I don't understand why yetus complains about Check failure on line 19 in pkg/pillar/nireconciler/linux_currentstate.go GitHub Actions/ yetus golangcilint: "github.com/vishvananda/netlink" imported but not used (typecheck)
because such an error would also cause a build failure.

Yes, that is some strange golangcilint fail that I cannot find any way around. The imported package is used and it builds fine so I guess we will just have to ignore it.

For once eden tests failed because there was an actual problem in the PR changes. Should be fixed now.

The fail in networking_light test that we caught here is addressed by https://github.com/lf-edge/eve/pull/3208


readMe updated

Tools ein bisschen geupdated

Hello @emiliadoe,
I found 1 problem while checking your pull request.
Problems:

The title readMe updated is not the format I expected.

Rules:

There must be a title in this format: Feature|Bugfix|Hotfix|Release: Title
If applicable, add your issue ticket (e.g. A-100) with a slash in the title (Feature/A-100: Title)
Use Feature for enhancements or new functionality
Use Bugfix only if you fixed a known bug
Use Hotfix for problems introduced by previous merges
Use proper capitalization in your title
There must be a description


API does not provide MEMBER description

Related to https://github.com/opencollective/opencollective/issues/1039
Whenever you fill in a description (aka position) of a team member, the api does not return that data.

    {
        "MemberId": 15658,
        "createdAt": "2018-04-27 16:53",
        "type": "USER",
        "role": "MEMBER",
        "isActive": true,
        "totalAmountDonated": 0,
        "lastTransactionAt": "2018-05-01 07:42",
        "lastTransactionAmount": 0,
        "profile": "https://opencollective.com/bertrand",
        "name": "Bertrand Kintanar",
        "company": null,
        "description": null,
        "image": "https://opencollective-production.s3-us-west-1.amazonaws.com/50164510-472c-11e8-bf26-4f26f620586f.png",
        "email": null,
        "twitter": null,
        "github": null,
        "website": null
    }

Should mention "documentation" somewhere.

https://opencollective.com/tenancy/members/all.json it's the same with https://opencollective.com/tenancy/members/users.json btw.

Ok, would be pretty straightforward, the description field is already taken by the user.description, we would then need to find another name for it, such as roleDescription or memberDescription.

@znarf the input form for the member actually also mentions "description" if it would be renamed to "role" one could also return a different property based on that field input naming. But then again that might be too generic, as such memberDescription might be a better solution?

As we're currently in the process of rebuilding the frontend of my website, would it be possible to push in this property @znarf ?

Please don't close this.

@luceos Thank you for jumping back. We're currently experimenting with this stale bot and need to adapt our flow, I'm re-tagging the issue.

I can imagine, and I have no issue with irrelevant issues being closed because of staleness, but this is obviously a bug; hence the bump.
🤗


Add ServoGroup bulk write

Add the ability to write a single register and value to all servos in a group.

bulk_write is not available on protocol_v1. I'll implement sync_write first.


[Feature Request] Default queries

Similar to insomna-plugin-default-headers, it would be nice to be able to set default queries. Some APIs require API keys in the query rather than headers, so this would be very useful in those cases.

Hi @garyking @gschier, has this feature been on progress or completed? I would like to submit a PR for it if possible :smile:.

Sorry, I didn't notice this has been implemented here.


RFC: Provide extension mechanism for Query Builder for extra processing

Overview
Different plugins may have additional query builder features defined in the plugin. We want to add an extension mechanism for support extra processing of lambdas and UI features.
Implementation plan

discuss what part of processing lambda / building lambda we want to extend. What part of UI we want to extend

Additional context
No response

@gayathrir11 @MauricioUyaguari Please fill in more details when we have a better understanding of the specs. Thanks!

@gayathrir11 @MauricioUyaguari could we fill in the detail here now?

Grammar for testing:
###Service
Service my::service
{
  pattern: '/e70d2c08-4169-44f1-89d4-0fa9971c3995';
  documentation: '';
  autoActivateUpdates: true;
  execution: Single
  {
    query: businessDate: Date[1]|my::Person.all($businessDate);
    mapping: my::map;
    runtime:
    #{
      mappings:
      [
        my::map
      ];
    }#;
  }
  test: Single
  {
    data: '';
    asserts:
    [
    ];
  }
}

###Relational
Database my::db
(
  Table PersonTable
  (
    NAME CHAR(200),
    FIRMID INTEGER
  )
  Table FirmTable
  (
    FIRMNAME CHAR(200),
    ID INTEGER
  )

  Join Firm_Person(PersonTable.FIRMID = FirmTable.ID)
)

###Pure
Class <<temporal.businesstemporal>> my::Person
{
  name: String[1];
  firmID: Integer[1];
}

Class my::Firm
{
  legalName: String[1];
  id: Integer[1];
}

###Mapping
Mapping my::map
(
  *my::Person: Pure
  {
  }
)


Fixed cursor issue for text input

Try to fix cursor issue for text input.

@riveram If you comment these two lines, you should be able to receive the JavaScript events:
https://github.com/readium/kotlin-toolkit/blob/85238fafe2c0b9872b7025ebb971601beedad279/readium/navigator/src/main/java/org/readium/r2/navigator/R2WebView.kt#L191-L192
Could you change the pull request to be based from the v3 branch instead of develop? Thanks.

Superseded by https://github.com/readium/kotlin-toolkit/pull/351


Better ol.events.condition.platformModifierKeyOnly documentation

See https://github.com/google/closure-library/blob/master/closure/goog/events/browserevent.js#L175-L180

The windows-key has nothing to do with it

Thanks. Please merge when build is finished.


tendermint: 0.34.4 -> 0.34.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tendermint/tendermint/releases.
meta.description for tendermint is: "Byzantine-Fault Tolerant State Machines. Or Blockchain, for short"
meta.homepage for tendermint is: "https://tendermint.com/"
meta.changelog for tendermint is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/0e5a56a9c480db459dba758208dd8361

du listing: https://gist.github.com/8d0d8a29a39d9ea79d3e0f30c91d4ccc

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
tendermint

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iy1r3shkbwal6jpahxyq38crh2qgary4-tendermint-0.34.7
ls -la /nix/store/iy1r3shkbwal6jpahxyq38crh2qgary4-tendermint-0.34.7/bin

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

1 package built:

tendermint

Maintainer pings
cc @alexfmpe @kalbasit for testing.

Result of nixpkgs-review pr 113614 at 9e4364ee run on aarch64-linux 1

1 package built:

tendermint

1 suggestion:

error: no-flags-array
buildFlagsArray is only intended to be used in Bash, not as a Nix attribute.
Near pkgs/tools/networking/tendermint/default.nix:20:3:
   |
20 |   buildFlagsArray = [ "-ldflags=-s -w -X github.com/tendermint/tendermint/version.GitCommit=${src.rev}" ];
   |   ^


Error with pysmilesutils and MolRandomizer

Hi, I am trying to run the Molbart train script and I am having problems with pysmilesutils.
molbart/data/datamodules.py is using MolRandomizer, but in the pysmilesutils repo I can only see MolAugmenter. This is throwing an error that prevents from running the training.
Are you using an older version of library? If so, which one? I am trying to work around it by switching MolRandomizer to MolAugmenter, but no idea whether this will work. Any hints?
See below:
diff --git a/MolBART/molbart/data/datamodules.py b/MolBART/molbart/data/datamodules.py
index 3c2ad67..bc909f1 100644
--- a/MolBART/molbart/data/datamodules.py
+++ b/MolBART/molbart/data/datamodules.py
@@ -5,7 +5,7 @@ from rdkit import Chem
 from functools import partial
 from typing import List, Optional
 from torch.utils.data import DataLoader
-from pysmilesutils.augment import MolRandomizer
+from pysmilesutils.augment import MolAugmenter

 from molbart.tokeniser import MolEncTokeniser
 from molbart.data.util import TokenSampler
@@ -180,7 +180,7 @@ class MoleculeDataModule(_AbsDataModule):

         if augment:
             print("Using molecule data module with augmentations.")
-            self.aug = MolRandomizer()
+            self.aug = MolAugmenter()
         else:
             print("No molecular augmentation.")
             self.aug = None
@@ -328,7 +328,7 @@ class FineTuneReactionDataModule(_AbsDataModule):
             print("Training on backward prediction task.")

         self.augment = augment
-        self.aug = MolRandomizer() if augment is not None else None
+        self.aug = MolAugmenter() if augment is not None else None
         self.forward_pred = forward_pred

     def _collate(self, batch, train=True):

Hello,
Thanks for pointing this out. The molbart code indeed developed with an older version of pysmilesutils, and we neglected to update the code before it was pushed to Github.
The changes you have suggested, should work. The MolRandomizer class was renamed MolAugmenter.
If you can confirm that your script runs smoothly with the suggested changes, it would be great. Then we can prepare a patch for the code. Or if you would like to prepare a Pull request.

The model seems to stop crashing after the change. Thank you for referring me to the Chemformer repository, I will stick with that for now.
I opened an MR in case you'd like to add this to your repo: https://github.com/MolecularAI/MolBART/pull/33


-Precord param not working on api 28+

Expected behaviour
Screenshots are successfully generated for cases declared in the sample app
@Test
fun showsAnySuperHero() {
    val superHero = givenASuperHero()
    val holder = givenASuperHeroViewHolder()
    holder.render(superHero)
    compareScreenshot(holder)
}

Actual behaviour
Test completes successfully, but screenshots folder is empty and no errors are generated
Steps to reproduce
Open shot-consumer-flavors
Create new avd 28+
Run executeScreenshotTests with following params
-Pandroid.testInstrumentationRunnerArguments.class=com.karumi.ui.view.SuperHeroViewHolderTest -Precord
Check the "screenshots" folder when execution is finished
Version of the library
5.11.0 but it also doesn't work in lower versions
Tested on api 28+
Possible solution
I think this is happens because of restrictions on non-SDK interfaces (API 28+)
So, when I executed the following command, everything works fine
Android 9 (API level 28)
adb shell settings put global hidden_api_policy_pre_p_apps 1
adb shell settings put global hidden_api_policy_p_apps 1

Android 10 (API level 29) or higher
adb shell settings put global hidden_api_policy 1

@pedrovgs How about adding this info to the docs, because I spent a lot of time to launch this type of tests?

oO first time I see this. Thanks for reporting @Stronger197. Could you please send a PR with a README.md update explaining this scenario?

Yep, sure!

I have more info. If you run compareScreenshot(view : View) without -Precord param, it also not working as expected, because /build/reports/shot/verification/images is empty

Are you sure this is a library issue and not something related to your project or your config? Could you try running shot-consumer or any other consumer example app inside this repository in your testing device to ensure we have a real bug?

Pls read "Steps to reproduce". I tested this case using shot-consumer-flavors.

Hi. I reproduced this problem too on shot-consumer.

Hi all! I'm going to be out for holiday so if anybody knows how to fix this issue without dealing with the emulators, please let me know and contribute if possible. It could be great if we can find another alternative to -P param to be able to record our screenshots. This feature should work out of the box without any further configuration

Not sure whether this is related to this issue, but worth mentioning.
I have seen similar issues happening  on the KataScreenshotKotlin
It seems the problems start with Shot 5.8.0
I cloned the project locally. It has shot version 5.5.0  configured and that one works fine (Gradle 6.7.1, emulator: Marshmallow API 23)
But if we just change the shot version, we experience the following problems:
Shot 5.7.0

Shot 5.8.0

Shot 5.11.2

Moreover, I tried with the aforementioned "workaround" on a device with API 30 and Shot 5.11.2 and it fails
I've checked the Readme and saw that the following was added in Shot 5.8.0:
"Since Shot 5.8.0 we provide support for devices running API >= 29. There is no need to configure android:requestLegacyExternalStorage="true" or provide any special storage permission in your test ``AndroidManifest`."
That's my investigation so far

Not sure whether this is related to this issue, but worth mentioning.
I have seen similar issues happening on the KataScreenshotKotlin
It seems the problems start with Shot 5.8.0
I cloned the project locally. It has shot version 5.5.0 configured and that one works fine (Gradle 6.7.1, emulator: Marshmallow API 23, targetSdk 28)
But if we just change the shot version, we experience the following problems:
Shot 5.7.0 (still fine)

Shot 5.8.0

Shot 5.11.2

Moreover, I tried with the aforementioned "workaround" on a device with API 30 and Shot 5.11.2 and it fails
I've checked the Readme and saw that the following was added in Shot 5.8.0:
"Since Shot 5.8.0 we provide support for devices running API >= 29. There is no need to configure android:requestLegacyExternalStorage="true" or provide any special storage permission in your test ``AndroidManifest`."
That's my investigation so far

I found out that it was not working because that kata is using its own testRunner instead of com.karumi.shot.ShotTestRunner, so it is not relevant to this bug.
I think it would be great to update the Kata to the latest shot version. It can serve as example to other people having issues to configure Shot.
Sorry for misleading :(

@raafaelima I'm having the same issue and it's blocking us to introduce Shot in our codebase. Have you found any solution so far?


Link the version of gcov relevant to current compiler.

Signed-off-by: Henner Zeller<EMAIL_ADDRESS>

Trying to get to the bottom of why the coverage turns out to be empty.

Codecov Report

Merging #890 (d8ec21b) into master (513203e) will increase coverage by 38.24%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #890       +/-   ##
===========================================
+ Coverage        0   38.24%   +38.24%
===========================================
  Files           0      285      +285
  Lines           0    18757    +18757
===========================================
+ Hits            0     7173     +7173
- Misses          0    11584    +11584

Impacted Files
Coverage Δ

common/analysis/command_file_lexer.cc
83.33% <0.00%> (ø)

...ilog/analysis/checkers/unpacked_dimensions_rule.cc
39.39% <0.00%> (ø)

common/lexer/lexer.h
100.00% <0.00%> (ø)

verilog/analysis/verilog_linter_configuration.cc
57.14% <0.00%> (ø)

verilog/CST/declaration.cc
9.58% <0.00%> (ø)

common/analysis/lint_waiver.cc
54.16% <0.00%> (ø)

common/util/subcommand.cc
94.11% <0.00%> (ø)

verilog/CST/net.cc
0.00% <0.00%> (ø)

common/strings/random.cc
100.00% <0.00%> (ø)

verilog/CST/class.cc
0.00% <0.00%> (ø)

... and 275 more

Continue to review full report at Codecov.

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

Looks like linking the right gcov made it work.


port 8080 doesn't work

here's what I see when I haven't changed anything and just go to localhost:8080. On Arch linux. Port 3000 seems to work for everything exept the link. Started with npm run dev.

Closing this as the correct port to use is 3000.  8080 is just the backend server but won't load your webpack assets.


Resolve "Implement DateRangeParam.isDateWithinRange(Date theDate)."

Closes #1645

@jamesagnew, please review. Thanks!


patch(code.css): fix website overflow because of code

Summary
after

Ik it may broke some words but it would fix extra overflow

before  (overflown on mobile)

Related Issue
https://rspress.dev/zh/guide/basic/deploy

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

or we can https://<username>.github.io/<repository>/ -> https://<username>.github.io/<repo>/

Thank you


[VerticalLines] Fixed first line top position, if line height has been changed

The issue: http://dl2.joxi.net/drive/2016/04/10/0007/3617/495137/37/42faf332fd.png

Thank you xmityaz we'll review this pull request first thing next week.

Thank you! I have merged the fix and pushed out 0.7.4


Good sample LAS files to crossplot

In lasio examples there are some LAS files examples, however they are mostly for testing and validating use cases.
Crossplots of a good LAS file sample
Only file 6038187_v1.2.las seems like a real example, nevertheless we get the following crossplots.
DEPT
Crossplots generated comparing register DEPT vs registers:

CALI

DFAR

DNEAR

GAMN

NEUT

PR

SP

COND

TODO
After this crossplots plotted, the main point of this issue is to:

[ ] Define minimum and maximum of these registers
[ ] Find more LAS files alike
[ ] Start clustering

@MontuJav I need to merge this, but this does not mean the issue is closed, we still need to handle tasks created within this issue


Updated SharePoint remove site designs Script to add PnP PS

Needed to clear some Site Designs from my tenant so updated the CLI/SPO Example to reflect PnP PowerShell so I could run it using PnP PowerShell.
Hope this is ok
Leon

Nice addition, thank you @LeonArmston! 😊😃


[v2] loadbalancer sg is not added to inbound rule in worker sg

I was running a sample of https://github.com/kubernetes-sigs/aws-alb-ingress-controller/tree/master/docs/examples/2048
with 2.0.0-rc2 and it wasn't working, so I found that the loadbalancer sg was not being added to the worker's sg and the health check was not passing.
Is this a specification..?
apiVersion: v1
kind: Service
metadata:
  name: "service-2048"
  namespace: "test"
spec:
  ports:
    - port: 80
      targetPort: 80
      protocol: TCP
  type: ClusterIP
  selector:
    app: "2048"
---
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: "2048-ingress"
  namespace: "test"
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/group.name: test
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/security-groups: sg-XXX
    alb.ingress.kubernetes.io/healthcheck-interval-seconds: '10'
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 8080}]'
    alb.ingress.kubernetes.io/healthcheck-port: '80'
    alb.ingress.kubernetes.io/healthy-threshold-count: '3'
    alb.ingress.kubernetes.io/subnets: subnet-XXX,subnet-XXX,subnet-XXX
    alb.ingress.kubernetes.io/target-type: ip
  labels:
    app: 2048-ingress
spec:
  rules:
    - http:
        paths:
          - path: /*
            backend:
              serviceName: "service-2048"
              servicePort: 80
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: "2048-deployment"
  namespace: "test"
spec:
  selector:
    matchLabels:
      app: "2048"
  replicas: 2
  template:
    metadata:
      labels:
        app: "2048"
    spec:
      containers:
      - image: alexwhen/docker-2048
        imagePullPolicy: Always
        name: "2048"
        ports:
        - containerPort: 80

I tried with alb.ingress.kubernetes.io/target-type: instance and NodePort but it didn't work.

@cw-sakamoto
If you specified alb.ingress.kubernetes.io/security-groups: sg-XXX, the sg-XXX you specified won't be added to worker node SGs, you need to manually add it by yourself.
If you don't specify alb.ingress.kubernetes.io/security-groups, the controller should create a SG-LB and attach to LoadBalancer, and also modify worker node SG to allow traffic from SG-LB.
It's the same behavior of old versions.

@M00nF1sh Sorry, I misunderstood, I confirmed the same behavior in v1.


OpenNebula: Group of resources

Author Name: kvaps kvaps (kvaps kvaps)
Original Redmine Issue: 5401, https://dev.opennebula.org/issues/5401
Original Date: 2017-09-25

There is need possibility to group resources for set quotas
Example:
Datastores

I want to group 5 datastores with images type into one datastore.
I want to set quotas to only this datastore, and allow users place images on it.
If free space on this group comes to an end, I will add another one datastore to this group, this action will be transparent for user.

Connected with #5127
Virtual Networks

I want to group 10 virtual networks into one.
I want to set quotas to only this virtual network, and set this virtual network for use on my templates.
If free leases on this group comes to an end, I will just add another one virtual network to this group, there is no necessity to update my templates for use new network.

Proposed solution:
I think it may be realized using dummy drivers that used now for network reservations: https://docs.opennebula.org/5.4/operation/network_management/manage_vnets.html#virtual-network-self-provisioning-reservations
When creating group of resurce, the new dummy resource will be created, that linked to several another resources.
Workaround for networks:
For now I use several virtual networks each with separated subnet and separated VLAN_ID. I found that there is possibility to override network parameters if assign variables like VLAN_ID to address range.
This is working fine, I would like something like this for datastores.

For now we believe that cluster and VDC provide all the needed grouping capabilities. We'll revisit it if needed

@juanmont, hi
This is not exactly the case, for example: how can we allocate a quota for use 100GB on ANY of three images datastore using VDCs?
Or, how do you want to set in VM tempalate "take unsused IP-adress from one of theese five networks"

Hi kvaps,
Yes, you are right that you cannot impose quotas on a aggregated set of resources. This issue can be reformulated to describe this issue. is that what you need?
As for the networks, not sure what is your use-case, but a network with 3 ARs implements exactly that feature.

Yes, you are right that you cannot impose quotas on a aggregated set of resources.
Yes, this is what exactly I mean

Network with 3 ARs implements exactly that feature
Yes, I already wrote that is is a solution for me.
Enchanced qutas can solve this issue more flexible.

This issue has been reopen to implement aggregated quotas.

@rsmontero what about making this configurable on VDC level as VDC quotas?


Merge sync 07502e9

Summary
Sync to latest upstream #07502e9

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 8 committers have signed the CLA.:white_check_mark: dkstyle:x: chenxsan:x: vankop:x: snitin315:x: DavidTanner:x: f3ndot:x: eviltester:x: xp44mmYou have signed the CLA already but the status is still pending? Let us recheck it.


GKE Ingress Health Check middleware

The ingress requires the root path of the target to return a 200 (OK) to
indicate the service's good health. The middleware handles the specific
health check call.
Description
This change adds the middle ware required to handle that specific call.
Motivation and Context
This is required to run the proxy smoothly on GKE
How Has This Been Tested?
The code has been tested and it has been tested on our clusters.
Checklist:

[x] My change requires a change to the documentation or CHANGELOG.
[ ] I have updated the documentation/CHANGELOG accordingly.
[x] I have created a feature (non-master) branch for my PR.

Hey @benfdking, thanks for submitting this. I'm reasonably happy with the implementation from my initial scan but I would like to request that we put this behind a feature flag.
At present this would add the wrapper to all requests for all users of the project which, while minimal, will increase the processing due to the additional handler. I think it would be better to have the middleware enabled only for those who actually need it, WDYT?

Hey, I somehow missed this PR.  I wrote something similar for GCP App Engine here:  https://github.com/pusher/oauth2_proxy/pull/110
Do you think it would be a good idea to combine these, or at least do them in the same way?

Personally I prefer the approach in #110 as it keeps the logic in-line with the rest of the endpoints, is there any way we can fix this GKE issue in a similar way?

Sorry I have been AWOL. Work... I think you can replicate what #110 has done and merge them together. All we need to do is merge the two into a GCP wrapper. In line 29 of http.go just add a check that matches that uses this essentially:

const userAgentHeader = "User-Agent"
const googleHealthCheckUserAgent = "GoogleHC/1.0"
const rootPath = "/"

// IngressHealthCheck is a middleware that is designed to be used with the Ingress in GKE. The ingress requires the root
// path of the target to return a 200 (OK) to indicate the service's good health. This can be quite a challenging demand
// depending on the application's path structure. This middleware filters out the requests from the health check by
//
// 1. checking that the request path is indeed the root path
// 2. ensuring that the User-Agent is "GoogleHC/1.0", the health checker
// 3. ensuring the request method is "GET"
//
// The ping can be used to indicate the health of the service. Like the sql package implementation, if it returns an
// error, the middleware will return a unhealthy response by returning a 500 (Internal). Otherwise if healthy, it
// returns a 200 (OK).
//
// An error that causes an "unhealthy" is not returned to the health check for security purposes.
func IngressHealthCheck(next http.Handler, ping func() error) http.Handler {
	return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		if r.URL.Path == rootPath &&
			r.Header.Get(userAgentHeader) == googleHealthCheckUserAgent &&
			r.Method == http.MethodGet {
			if err := ping(); err != nil {
				w.WriteHeader(http.StatusInternalServerError)
				return
			}
			w.WriteHeader(http.StatusOK)
			return
		}
		next.ServeHTTP(w, r)
	})
}

I incorporated your suggestion in https://github.com/pusher/oauth2_proxy/pull/110.  Let me know if that works properly for you!

@benfdking Happy to close this now the changes are incorporated in #110?

Definitely go for it!


Unresolved External Symbol

When trying to compile my project using cereal::JSONInputArchive I get:
error LNK2019: unresolved external symbol "public: void __cdecl walletCommunication::serialize<class cereal::JSONInputArchive>(class cereal::JSONInputArchive &)" (??$serialize@VJSONInputArchive@cereal@@@walletCommunication@@QEAAXAEAVJSONInputArchive@cereal@@@Z) referenced in function main
I can't find any mention of this elsewhere and thought I wouldn't encounter this due to cereal being header only I've made a mock up of the situation separate to my project and works just fine. I get no other errors when building. I wonder if it could be a header include issue? Does anyone have any ideas?

No idea what I did but it started working! 🤷♂  Never going to look at it again 😃


Add new package: Mosh to spec-extended

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[ ] The toolchain has been rebuilt successfully (or no changes were made to it)
[ ] The toolchain/worker package manifests are up-to-date
[ ] Any updated packages successfully build (or no packages were changed)
[ ] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[ ] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[ ] All package sources are available
[X] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[ ] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[ ] All source files have up-to-date hashes in the *.signatures.json files
[ ] sudo make go-tidy-all and sudo make go-test-coverage pass
[ ] Documentation has been updated to match any changes to the build system
[ ] If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
[ ] Ready to merge

Summary
Getting more than than a few requests for mariner to have the package mosh added, adding it to specs-extended
Change Log

New Package addition

Does this affect the toolchain?

NO
Associated issues

#xxxx

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

I was not able to build it locally, was hopping to use a buddy build

Unblocked the PR checks and started a new buddy build https://dev.azure.com/mariner-org/mariner/_build/results?buildId=566882&view=results

https://dev.azure.com/mariner-org/mariner/_build/results?buildId=618714&view=results

https://dev.azure.com/mariner-org/mariner/_build/results?buildId=619765&view=results


Flutter Desktop on Windows CMake Error: Could not create named generator Visual Studio 16 2019

 flutter doctor
[✓] Flutter (Channel dev, 2.6.0-11.0.pre, on Microsoft Windows [Version 10.0.19042.630], locale zh-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Chrome - develop for the web
[✓] Visual Studio - develop for Windows (Visual Studio Professional 2019 16.0.22)
[✓] Android Studio (version 4.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2019.3)
[✓] Connected device (4 available)

• No issues found!

flutter run -d windows
Launching lib\main.dart on Windows in debug mode...
CMake Error: Could not create named generator Visual Studio 16 2019

Generators
  Visual Studio 15 2017 [arch] = Generates Visual Studio 2017 project files.
                                 Optional [arch] can be "Win64" or "ARM".
  Visual Studio 14 2015 [arch] = Generates Visual Studio 2015 project files.
                                 Optional [arch] can be "Win64" or "ARM".
  Visual Studio 12 2013 [arch] = Generates Visual Studio 2013 project files.
                                 Optional [arch] can be "Win64" or "ARM".
  Visual Studio 11 2012 [arch] = Generates Visual Studio 2012 project files.
                                 Optional [arch] can be "Win64" or "ARM".
  Visual Studio 10 2010 [arch] = Generates Visual Studio 2010 project files.
                                 Optional [arch] can be "Win64" or "IA64".
  Visual Studio 9 2008 [arch]  = Generates Visual Studio 2008 project files.
                                 Optional [arch] can be "Win64" or "IA64".
  Borland Makefiles            = Generates Borland makefiles.
  NMake Makefiles              = Generates NMake makefiles.
  NMake Makefiles JOM          = Generates JOM makefiles.
  Green Hills MULTI            = Generates Green Hills MULTI files
                                 (experimental, work-in-progress).
  MSYS Makefiles               = Generates MSYS makefiles.
  MinGW Makefiles              = Generates a make file for use with
                                 mingw32-make.
  Unix Makefiles               = Generates standard UNIX makefiles.
  Ninja                        = Generates build.ninja files.
  Watcom WMake                 = Generates Watcom WMake makefiles.
  CodeBlocks - MinGW Makefiles = Generates CodeBlocks project files.
  CodeBlocks - NMake Makefiles JOM
                               = Generates CodeBlocks project files.
  CodeBlocks - Ninja           = Generates CodeBlocks project files.
  CodeBlocks - Unix Makefiles  = Generates CodeBlocks project files.
  CodeLite - MinGW Makefiles   = Generates CodeLite project files.
  CodeLite - NMake Makefiles   = Generates CodeLite project files.
  CodeLite - Ninja             = Generates CodeLite project files.
  CodeLite - Unix Makefiles    = Generates CodeLite project files.
  Sublime Text 2 - MinGW Makefiles
                               = Generates Sublime Text 2 project files.
  Sublime Text 2 - NMake Makefiles
                               = Generates Sublime Text 2 project files.
  Sublime Text 2 - Ninja       = Generates Sublime Text 2 project files.
  Sublime Text 2 - Unix Makefiles
                               = Generates Sublime Text 2 project files.
  Kate - MinGW Makefiles       = Generates Kate project files.
  Kate - NMake Makefiles       = Generates Kate project files.
  Kate - Ninja                 = Generates Kate project files.
  Kate - Unix Makefiles        = Generates Kate project files.
  Eclipse CDT4 - NMake Makefiles
                               = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - MinGW Makefiles
                               = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - Ninja         = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - Unix Makefiles= Generates Eclipse CDT 4.0 project files.

Building Windows application...
Exception: Unable to generate build files

I have installed the component "Desktop development with C++" ships with Visual Studio 2019.
I have installed cmake  version 3.14.0-rc1.

Hi @txl19881019,

I have installed the component "Desktop development with C++" ships with Visual Studio 2019.
I have installed cmake version 3.14.0-rc1.

when you open a flutter project (windows Desktop enabled) does your IDE (Android Studio or vscode) detect windows device? Also, did you try restarting the system post Visual studio install?
Thanks

Hi @txl19881019,

I have installed the component "Desktop development with C++" ships with Visual Studio 2019.
I have installed cmake version 3.14.0-rc1.

when you open a flutter project (windows Desktop enabled) does your IDE (Android Studio or vscode) detect windows device? Also, did you try restarting the system post Visual studio install?
Thanks

Yes ,I have restarted my computer,Windows Desktop has enabled.I use AS run the project ,console print
Exception: No Windows desktop project configured. See https://flutter.dev/desktop#add-desktop-support-to-an-existing-flutter-app to learn about adding Windows support to a project.

I don't know what's wrong with it.

Also make sure you have enabled desktop support by running
flutter config --enable-windows-desktop

if that still does not work then probably you should try reinstalling Visual studio with the required tools

Visual Studio 2019 (not to be confused with Visual Studio Code). For Win32 you need the “Desktop development with C++” workload installed, including all of its default components. For UWP you need the “Universal Windows Platform development” workload installed, with the optional UWP C++ tools.

@txl19881019  was this resolved?


[#79] Time sheets "week of" should show monday's date

Fixed the entry.start_time to use the existing week_start template tag

Update README with note of fix then merge into master.