text:
v2.6.0-rc2: Policy controller panic during long running test

I was running a long running pod and policy churn test and had the included panic.
Expected Behavior
No panics
Current Behavior
A panic
Possible Solution
Fix it
Steps to Reproduce (for bugs)
Not sure of specific cause

Have pod and policy churn test running
Check for policy-controller restarts

Your Environment

Kubernetes version (kubectl version): v1.7.6
Manifest file used to deploy k8s policy:
Operating System and version: Ubuntu 16.04.3

thread dump
2017-09-26 00:35:56.091 [INFO][1] policy_controller.go 251: Add/Update Policy knp.default.cali-ns-1.cross-client1-cali-ns-0-server1-cali-ns-7771 in Calico datastore
2017-09-26 00:35:56.093 [INFO][1] policy_controller.go 251: Add/Update Policy knp.default.cali-ns-0.same-client3-cali-ns-0-server0-cali-ns-7770 in Calico datastore
2017-09-26 00:35:56.205 [INFO][1] policy_controller.go 251: Add/Update Policy knp.default.cali-ns-0.same-client0-cali-ns-0-server0-cali-ns-7770 in Calico datastore
2017-09-26 00:35:56.405 [INFO][1] policy_controller.go 251: Add/Update Policy knp.default.cali-ns-2.cross-client2-cali-ns-0-server2-cali-ns-7772 in Calico datastore
2017-09-26 00:35:56.609 [INFO][1] policy_controller.go 251: Add/Update Policy knp.default.cali-ns-1.cross-client4-cali-ns-0-server1-cali-ns-7771 in Calico datastore
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.server0-cali-ns-0-3779729070-8d6hm" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client1-cali-ns-0-3174722842-7425g" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client3-cali-ns-0-570746494-r0sgf" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] pod_controller.go 248: No corresponding WorkloadEndpoint in cache, re-loading cache from datastore wep="cali-ns-0.server0-cali-ns-0-3779729070-8d6hm"
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client1-cali-ns-0-3174722842-1kmfp" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client4-cali-ns-0-3349495990-knq81" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-2.client5-cali-ns-2-998486221-86zpd" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client4-cali-ns-0-3349495990-rp5dk" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client2-cali-ns-0-242985648-2rqjj" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client3-cali-ns-0-570746494-gvgdz" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="default.test-operator-1128193883-07qhg" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.server0-cali-ns-0-3779729070-hc8cm" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.210 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="kube-system.grafana-import-smj9t" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.211 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-2.client5-cali-ns-2-998486221-tjr78" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.211 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-1.server1-cali-ns-1-3692877936-nw52n" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.211 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client3-cali-ns-0-570746494-mxd9m" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.211 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="kube-system.grafana-3199060373-1b1rd" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.211 [WARNING][1] cache.go 246: Value for key is missing in datastore, queueing update to reprogram key="cali-ns-0.client1-cali-ns-0-3174722842-lh23w" type=converter.WorkloadEndpointData
2017-09-26 00:35:57.250 [INFO][1] pod_controller.go 263: Pod hasn't been created by the CNI plugin yet. wep="cali-ns-0.server0-cali-ns-0-3779729070-8d6hm"
2017-09-26 00:35:57.250 [WARNING][1] pod_controller.go 248: No corresponding WorkloadEndpoint in cache, re-loading cache from datastore wep="cali-ns-0.client1-cali-ns-0-3174722842-7425g"
2017-09-26 00:35:57.272 [INFO][1] pod_controller.go 263: Pod hasn't been created by the CNI plugin yet. wep="cali-ns-0.client1-cali-ns-0-3174722842-7425g"
2017-09-26 00:35:57.272 [WARNING][1] pod_controller.go 248: No corresponding WorkloadEndpoint in cache, re-loading cache from datastore wep="cali-ns-0.client3-cali-ns-0-570746494-r0sgf"
2017-09-26 00:35:57.287 [INFO][1] pod_controller.go 263: Pod hasn't been created by the CNI plugin yet. wep="cali-ns-0.client3-cali-ns-0-570746494-r0sgf"
2017-09-26 00:35:57.287 [WARNING][1] pod_controller.go 248: No corresponding WorkloadEndpoint in cache, re-loading cache from datastore wep="cali-ns-0.client1-cali-ns-0-3174722842-1kmfp"
2017-09-26 00:35:57.306 [INFO][1] pod_controller.go 263: Pod hasn't been created by the CNI plugin yet. wep="cali-ns-0.client1-cali-ns-0-3174722842-1kmfp"
2017-09-26 00:35:57.306 [WARNING][1] pod_controller.go 248: No corresponding WorkloadEndpoint in cache, re-loading cache from datastore wep="cali-ns-0.client4-cali-ns-0-3349495990-knq81"
2017-09-26 00:35:57.329 [INFO][1] pod_controller.go 263: Pod hasn't been created by the CNI plugin yet. wep="cali-ns-0.client4-cali-ns-0-3349495990-knq81"
2017-09-26 00:35:57.329 [WARNING][1] pod_controller.go 248: No corresponding WorkloadEndpoint in cache, re-loading cache from datastore wep="cali-ns-2.client5-cali-ns-2-998486221-86zpd"
2017-09-26 00:35:57.341 [INFO][1] policy_controller.go 241: Deleting Policy knp.default.cali-ns-0.random-server0-cali-ns-0-client0-cali-ns-0-2630 from Calico datastore
fatal error: concurrent map writes

goroutine 46 [running]:
runtime.throw(0x15faa76, 0x15)
        /usr/local/go/src/runtime/panic.go:596 +0x95 fp=0xc420dd1748 sp=0xc420dd1728
runtime.mapassign(0x143e1c0, 0xc42028ab70, 0xc420dd18e8, 0xc420986000)
        /usr/local/go/src/runtime/hashmap.go:499 +0x667 fp=0xc420dd17e8 sp=0xc420dd1748
github.com/projectcalico/k8s-policy/pkg/controllers/pod.(*PodController).populateEndpointCache(0xc420065860, 0x1633a12, 0x4b)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/pod/pod_controller.go:322 +0x210 fp=0xc420dd1ba0 sp=0xc420dd17e8
github.com/projectcalico/k8s-policy/pkg/controllers/pod.(*PodController).syncToCalico(0xc420065860, 0xc420ac60f0, 0x2b, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/pod/pod_controller.go:249 +0xd57 fp=0xc420dd1f60 sp=0xc420dd1ba0
github.com/projectcalico/k8s-policy/pkg/controllers/pod.(*PodController).processNextItem(0xc420065860, 0x1)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/pod/pod_controller.go:228 +0xa6 fp=0xc420dd1fb8 sp=0xc420dd1f60
github.com/projectcalico/k8s-policy/pkg/controllers/pod.(*PodController).runWorker(0xc420065860)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/pod/pod_controller.go:215 +0x2b fp=0xc420dd1fd8 sp=0xc420dd1fb8
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420dd1fe0 sp=0xc420dd1fd8
created by github.com/projectcalico/k8s-policy/pkg/controllers/pod.(*PodController).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/pod/pod_controller.go:206 +0x44c

goroutine 1 [select (no cases), 245 minutes]:
main.main()
        /go/src/github.com/projectcalico/k8s-policy/main.go:100 +0x4e3

goroutine 5 [chan receive]:
github.com/projectcalico/k8s-policy/vendor/github.com/golang/glog.(*loggingT).flushDaemon(0x1f5cc20)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/golang/glog/glog.go:879 +0x7a
created by github.com/projectcalico/k8s-policy/vendor/github.com/golang/glog.init.1
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/golang/glog/glog.go:410 +0x21d

goroutine 13 [select]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.(*delayingType).waitingLoop(0xc4202f16c0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue/delaying_queue.go:161 +0x84d
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.newDelayingQueue
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue/delaying_queue.go:55 +0x22a

goroutine 14 [chan receive, 245 minutes]:
github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy.(*PolicyController).Run(0xc420273f80, 0x1, 0x135f20e, 0x2, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy/policy_controller.go:207 +0x42d
created by main.main
        /go/src/github.com/projectcalico/k8s-policy/main.go:93 +0x6d3

goroutine 15 [select]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.(*delayingType).waitingLoop(0xc4202f1730)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue/delaying_queue.go:161 +0x84d
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.newDelayingQueue
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue/delaying_queue.go:55 +0x22a

goroutine 16 [chan receive, 245 minutes]:
github.com/projectcalico/k8s-policy/pkg/controllers/namespace.(*NamespaceController).Run(0xc42018a300, 0x1, 0x135f20e, 0x2, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/namespace/namespace_controller.go:165 +0x3d0
created by main.main
        /go/src/github.com/projectcalico/k8s-policy/main.go:90 +0x660

goroutine 33 [select]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.(*delayingType).waitingLoop(0xc4202f17a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue/delaying_queue.go:161 +0x84d
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.newDelayingQueue
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue/delaying_queue.go:55 +0x22a

goroutine 49 [semacquire]:
sync.runtime_notifyListWait(0xc42009f168, 0xb415)
        /usr/local/go/src/runtime/sema.go:298 +0x10b
sync.(*Cond).Wait(0xc42009f158)
        /usr/local/go/src/sync/cond.go:57 +0x89
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*DeltaFIFO).Pop(0xc42009f140, 0xc42028a150, 0x0, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/delta_fifo.go:438 +0xe1
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).processLoop(0xc4203aa300)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:147 +0x40
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).(github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.processLoop)-fm()
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:121 +0x2a
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc4205e0fb0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:97 +0x5e
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc4205cbfb0, 0x3b9aca00, 0x0, 0x13b7901, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:98 +0xbd
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc4205e0fb0, 0x3b9aca00, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:52 +0x4d
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run(0xc4203aa300, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:121 +0x237
created by github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy.(*PolicyController).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy/policy_controller.go:192 +0x178

goroutine 34 [chan receive, 245 minutes]:
github.com/projectcalico/k8s-policy/pkg/controllers/pod.(*PodController).Run(0xc420065860, 0x1, 0x135f20e, 0x2, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/pod/pod_controller.go:210 +0x507
created by main.main
        /go/src/github.com/projectcalico/k8s-policy/main.go:87 +0x5a0

goroutine 24 [semacquire]:
sync.runtime_notifyListWait(0xc42009f2e8, 0x10e56)
        /usr/local/go/src/runtime/sema.go:298 +0x10b
sync.(*Cond).Wait(0xc42009f2d8)
        /usr/local/go/src/sync/cond.go:57 +0x89
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*DeltaFIFO).Pop(0xc42009f2c0, 0xc42028b2f0, 0x0, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/delta_fifo.go:438 +0xe1
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).processLoop(0xc4203aa500)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:147 +0x40
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).(github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.processLoop)-fm()
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:121 +0x2a
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc4205e1fb0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:97 +0x5e
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc420d73fb0, 0x3b9aca00, 0x0, 0x13b7901, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:98 +0xbd
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc4205e1fb0, 0x3b9aca00, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:52 +0x4d
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run(0xc4203aa500, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:121 +0x237
created by github.com/projectcalico/k8s-policy/pkg/controllers/pod.(*PodController).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/pod/pod_controller.go:195 +0x2a0

goroutine 67 [chan receive, 245 minutes]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run.func1(0xc4200654a0, 0xc4203aa480)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:103 +0x40
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:105 +0x9c

goroutine 93203 [select, 6 minutes]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch.func1(0xc420b280f8, 0xc4200654a0, 0xc420fcc180, 0xc4202fa000, 0xc420fcc120, 0xc420b28100)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:268 +0x30c
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:285 +0x864

goroutine 38 [semacquire, 208 minutes]:
sync.runtime_notifyListWait(0xc42009f228, 0xd)
        /usr/local/go/src/runtime/sema.go:298 +0x10b
sync.(*Cond).Wait(0xc42009f218)
        /usr/local/go/src/sync/cond.go:57 +0x89
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*DeltaFIFO).Pop(0xc42009f200, 0xc42028a930, 0x0, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/delta_fifo.go:438 +0xe1
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).processLoop(0xc4203aa480)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:147 +0x40
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).(github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.processLoop)-fm()
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:121 +0x2a
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc420038fb0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:97 +0x5e
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc4205ddfb0, 0x3b9aca00, 0x0, 0x13b7901, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:98 +0xbd
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc420038fb0, 0x3b9aca00, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:52 +0x4d
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run(0xc4203aa480, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:121 +0x237
created by github.com/projectcalico/k8s-policy/pkg/controllers/namespace.(*NamespaceController).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/namespace/namespace_controller.go:151 +0x205

goroutine 68 [select, 4 minutes]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).watchHandler(0xc42016c2d0, 0x1eec800, 0xc420b420f0, 0xc4205cfc78, 0xc4202fc600, 0xc4200654a0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:350 +0x10db
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch(0xc42016c2d0, 0xc4200654a0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:321 +0xe1d
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).RunUntil.func1()
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:200 +0x33
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc4202de0e0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:97 +0x5e
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc4202de0e0, 0x3b9aca00, 0x0, 0xc420386701, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:98 +0xbd
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc4202de0e0, 0x3b9aca00, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:52 +0x4d
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).RunUntil
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:203 +0x19d

goroutine 18 [chan receive, 245 minutes]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run.func1(0xc4200654a0, 0xc4203aa300)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:103 +0x40
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:105 +0x9c

goroutine 19 [select]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).watchHandler(0xc4202fa000, 0x1eec800, 0xc420f71380, 0xc4209b1c78, 0xc420fcc120, 0xc4200654a0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:350 +0x10db
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch(0xc4202fa000, 0xc4200654a0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:321 +0xe1d
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).RunUntil.func1()
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:200 +0x33
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc4203c0000)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:97 +0x5e
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc4203c0000, 0x3b9aca00, 0x0, 0xc420320401, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:98 +0xbd
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc4203c0000, 0x3b9aca00, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:52 +0x4d
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).RunUntil
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:203 +0x19d

goroutine 81 [select]:
github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client.(*simpleHTTPClient).Do(0xc4201a0c80, 0x7f06c4775ed0, 0xc4208199e0, 0x1ee2500, 0xc420a14d40, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client/client.go:531 +0x95d
github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client.(*redirectFollowingHTTPClient).Do(0xc4208a3600, 0x7f06c4775ed0, 0xc4208199e0, 0x1ee2500, 0xc420a14d40, 0xc420014016, 0x12, 0x0, 0x0, 0x0, ...)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client/client.go:603 +0xa0
github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client.(*httpClusterClient).Do(0xc420064420, 0x7f06c4775ed0, 0xc4208199e0, 0x1ee2500, 0xc420a14d40, 0x1f59a80, 0x7f06c4775ed0, 0xc4208199e0, 0x1484f80, 0x14a6f00, ...)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client/client.go:360 +0x371
github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client.(*httpKeysAPI).Delete(0xc4200fa600, 0x7f06c476d000, 0xc42000e660, 0xc4207b81c0, 0x6b, 0xc4208a35c0, 0x0, 0x0, 0xc420feba98)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client/keys.go:402 +0x148
github.com/projectcalico/k8s-policy/vendor/github.com/projectcalico/libcalico-go/lib/backend/etcd.(*EtcdClient).Delete(0xc4200fa620, 0xc420a14d00, 0x45, 0xc420febb60)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/projectcalico/libcalico-go/lib/backend/etcd/etcd.go:184 +0x1ef
github.com/projectcalico/k8s-policy/vendor/github.com/projectcalico/libcalico-go/lib/backend/compat.(*ModelAdaptor).Delete(0xc42038e540, 0xc420a14d00, 0x0, 0x1efa800)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/projectcalico/libcalico-go/lib/backend/compat/compat.go:215 +0x1ff
github.com/projectcalico/k8s-policy/vendor/github.com/projectcalico/libcalico-go/lib/client.(*Client).delete(0xc42038e4b0, 0x1ee9400, 0xc4208199b0, 0x1ef8200, 0xc420b29578, 0xc420febc48, 0x5c245f)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/projectcalico/libcalico-go/lib/client/client.go:302 +0x185
github.com/projectcalico/k8s-policy/vendor/github.com/projectcalico/libcalico-go/lib/client.(*policies).Delete(0xc420b29578, 0x0, 0x0, 0xc42097e960, 0x45, 0x0, 0xc420421460, 0x3)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/projectcalico/libcalico-go/lib/client/policy.go:62 +0xad
github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy.(*PolicyController).syncToCalico(0xc420273f80, 0xc42097e960, 0x45, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy/policy_controller.go:242 +0x435
github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy.(*PolicyController).processNextItem(0xc420273f80, 0x85c201)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy/policy_controller.go:225 +0xa6
github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy.(*PolicyController).runWorker(0xc420273f80)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy/policy_controller.go:212 +0x2b
github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy.(*PolicyController).(github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy.runWorker)-fm()
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy/policy_controller.go:203 +0x2a
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc420126e60)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:97 +0x5e
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc420126e60, 0x3b9aca00, 0x0, 0x1, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:98 +0xbd
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc420126e60, 0x3b9aca00, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:52 +0x4d
created by github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy.(*PolicyController).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/networkpolicy/policy_controller.go:203 +0x374

goroutine 72 [chan receive, 245 minutes]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run.func1(0xc4200654a0, 0xc4203aa500)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:103 +0x40
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*controller).Run
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/controller.go:105 +0x9c

goroutine 73 [select]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).watchHandler(0xc42016c3f0, 0x1eec800, 0xc420958120, 0xc4209adc78, 0xc4205181e0, 0xc4200654a0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:350 +0x10db
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch(0xc42016c3f0, 0xc4200654a0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:321 +0xe1d
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).RunUntil.func1()
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:200 +0x33
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc42025e140)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:97 +0x5e
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc42025e140, 0x3b9aca00, 0x0, 0xc42023cc01, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:98 +0xbd
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc42025e140, 0x3b9aca00, 0xc4200654a0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:52 +0x4d
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).RunUntil
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:203 +0x19d

goroutine 32 [sleep, 5 minutes]:
time.Sleep(0x45d964b800)
        /usr/local/go/src/runtime/time.go:59 +0xf9
github.com/projectcalico/k8s-policy/pkg/cache.(*calicoCache).reconcile(0xc420101c20, 0x135f20e, 0x2)
        /go/src/github.com/projectcalico/k8s-policy/pkg/cache/cache.go:209 +0x227
created by github.com/projectcalico/k8s-policy/pkg/cache.(*calicoCache).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/cache/cache.go:168 +0x53

goroutine 30 [select, 245 minutes]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch.func1(0xc4200fe078, 0xc4200654a0, 0xc420518240, 0xc42016c3f0, 0xc4205181e0, 0xc4200fe080)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:268 +0x30c
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:285 +0x864

goroutine 77 [IO wait]:
net.runtime_pollWait(0x7f06c47c10a0, 0x72, 0x8)
        /usr/local/go/src/runtime/netpoll.go:164 +0x59
net.(*pollDesc).wait(0xc420046378, 0x72, 0x1eeaac0, 0x1ee03f8)
        /usr/local/go/src/net/fd_poll_runtime.go:75 +0x38
net.(*pollDesc).waitRead(0xc420046378, 0xc4208c6000, 0x8000)
        /usr/local/go/src/net/fd_poll_runtime.go:80 +0x34
net.(*netFD).Read(0xc420046310, 0xc4208c6000, 0x8000, 0x8000, 0x0, 0x1eeaac0, 0x1ee03f8)
        /usr/local/go/src/net/fd_unix.go:250 +0x1b7
net.(*conn).Read(0xc42000c050, 0xc4208c6000, 0x8000, 0x8000, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/net.go:181 +0x70
crypto/tls.(*block).readFromUntil(0xc42024cab0, 0x7f06c476d638, 0xc42000c050, 0x5, 0xc42000c050, 0x0)
        /usr/local/go/src/crypto/tls/conn.go:488 +0x98
crypto/tls.(*Conn).readRecord(0xc420274000, 0x1661217, 0xc420274120, 0x0)
        /usr/local/go/src/crypto/tls/conn.go:590 +0xc4
crypto/tls.(*Conn).Read(0xc420274000, 0xc420261000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
        /usr/local/go/src/crypto/tls/conn.go:1134 +0x11d
bufio.(*Reader).Read(0xc420519200, 0xc4203be0f8, 0x9, 0x9, 0x428716, 0x0, 0x0)
        /usr/local/go/src/bufio/bufio.go:213 +0x312
io.ReadAtLeast(0x1ee1c80, 0xc420519200, 0xc4203be0f8, 0x9, 0x9, 0x9, 0xc42080a820, 0x4, 0x0)
        /usr/local/go/src/io/io.go:307 +0xa9
io.ReadFull(0x1ee1c80, 0xc420519200, 0xc4203be0f8, 0x9, 0x9, 0x1661270, 0xc420547dc8, 0x0)
        /usr/local/go/src/io/io.go:325 +0x58
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.readFrameHeader(0xc4203be0f8, 0x9, 0x9, 0x1ee1c80, 0xc420519200, 0x0, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/frame.go:237 +0x7b
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.(*Framer).ReadFrame(0xc4203be0c0, 0xc420e16750, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/frame.go:464 +0xa4
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.(*clientConnReadLoop).run(0xc420547fb0, 0x165cff0, 0xc4201befb0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/transport.go:1233 +0x7c
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.(*ClientConn).readLoop(0xc42019e480)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/transport.go:1170 +0xa6
created by github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.(*Transport).NewClientConn
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/transport.go:492 +0x8ae

goroutine 50 [select, 245 minutes]:
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch.func1(0xc4200fe038, 0xc4200654a0, 0xc4202fc660, 0xc42016c2d0, 0xc4202fc600, 0xc4200fe040)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:268 +0x30c
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache.(*Reflector).ListAndWatch
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/tools/cache/reflector.go:285 +0x864

goroutine 45 [sleep]:
time.Sleep(0x45d964b800)
        /usr/local/go/src/runtime/time.go:59 +0xf9
github.com/projectcalico/k8s-policy/pkg/cache.(*calicoCache).reconcile(0xc4203602d0, 0x135f20e, 0x2)
        /go/src/github.com/projectcalico/k8s-policy/pkg/cache/cache.go:209 +0x227
created by github.com/projectcalico/k8s-policy/pkg/cache.(*calicoCache).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/cache/cache.go:168 +0x53

goroutine 56 [IO wait]:
net.runtime_pollWait(0x7f06c47c0fe0, 0x72, 0x7)
        /usr/local/go/src/runtime/netpoll.go:164 +0x59
net.(*pollDesc).wait(0xc420238a78, 0x72, 0x1eeaac0, 0x1ee03f8)
        /usr/local/go/src/net/fd_poll_runtime.go:75 +0x38
net.(*pollDesc).waitRead(0xc420238a78, 0xc420ac0000, 0x1000)
        /usr/local/go/src/net/fd_poll_runtime.go:80 +0x34
net.(*netFD).Read(0xc420238a10, 0xc420ac0000, 0x1000, 0x1000, 0x0, 0x1eeaac0, 0x1ee03f8)
        /usr/local/go/src/net/fd_unix.go:250 +0x1b7
net.(*conn).Read(0xc4204402a0, 0xc420ac0000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/net.go:181 +0x70
net/http.(*persistConn).Read(0xc4208f2a20, 0xc420ac0000, 0x1000, 0x1000, 0x4, 0x450130, 0xc420519680)
        /usr/local/go/src/net/http/transport.go:1316 +0x14b
bufio.(*Reader).fill(0xc420519500)
        /usr/local/go/src/bufio/bufio.go:97 +0x117
bufio.(*Reader).Peek(0xc420519500, 0x1, 0xc4205dcbe5, 0x1, 0x0, 0xc420c5b680, 0x0)
        /usr/local/go/src/bufio/bufio.go:129 +0x67
net/http.(*persistConn).readLoop(0xc4208f2a20)
        /usr/local/go/src/net/http/transport.go:1474 +0x196
created by net/http.(*Transport).dialConn
        /usr/local/go/src/net/http/transport.go:1117 +0xa35

goroutine 51 [sleep]:
time.Sleep(0x45d964b800)
        /usr/local/go/src/runtime/time.go:59 +0xf9
github.com/projectcalico/k8s-policy/pkg/cache.(*calicoCache).reconcile(0xc420101e00, 0x135f20e, 0x2)
        /go/src/github.com/projectcalico/k8s-policy/pkg/cache/cache.go:209 +0x227
created by github.com/projectcalico/k8s-policy/pkg/cache.(*calicoCache).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/cache/cache.go:168 +0x53

goroutine 52 [semacquire, 208 minutes]:
sync.runtime_notifyListWait(0xc42018a0d0, 0xc400000006)
        /usr/local/go/src/runtime/sema.go:298 +0x10b
sync.(*Cond).Wait(0xc42018a0c0)
        /usr/local/go/src/sync/cond.go:57 +0x89
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.(*Type).Get(0xc420101cc0, 0x0, 0x0, 0x13b7900)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue/queue.go:124 +0xba
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.(*delayingType).Get(0xc4202f1730, 0xc4202f1730, 0x13b7940, 0xc420127260)
        <autogenerated>:44 +0x49
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/util/workqueue.(*rateLimitingType).Get(0xc4201932e0, 0x1efdd20, 0xc4201932e0, 0x0)
        <autogenerated>:73 +0x49
github.com/projectcalico/k8s-policy/pkg/controllers/namespace.(*NamespaceController).processNextItem(0xc42018a300, 0xc4202fc601)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/namespace/namespace_controller.go:177 +0x56
github.com/projectcalico/k8s-policy/pkg/controllers/namespace.(*NamespaceController).runWorker(0xc42018a300)
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/namespace/namespace_controller.go:170 +0x2b
created by github.com/projectcalico/k8s-policy/pkg/controllers/namespace.(*NamespaceController).Run
        /go/src/github.com/projectcalico/k8s-policy/pkg/controllers/namespace/namespace_controller.go:161 +0x31b

goroutine 57 [select]:
net/http.(*persistConn).writeLoop(0xc4208f2a20)
        /usr/local/go/src/net/http/transport.go:1704 +0x43a
created by net/http.(*Transport).dialConn
        /usr/local/go/src/net/http/transport.go:1118 +0xa5a

goroutine 93205 [semacquire]:
sync.runtime_notifyListWait(0xc420b34180, 0xc40000052c)
        /usr/local/go/src/runtime/sema.go:298 +0x10b
sync.(*Cond).Wait(0xc420b34170)
        /usr/local/go/src/sync/cond.go:57 +0x89
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.(*pipe).Read(0xc420b34168, 0xc420daf001, 0xdff, 0xdff, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/pipe.go:60 +0xdb
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.transportResponseBody.Read(0xc420b34140, 0xc420daf001, 0xdff, 0xdff, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/transport.go:1465 +0xae
encoding/json.(*Decoder).refill(0xc420e1a000, 0xa, 0x9)
        /usr/local/go/src/encoding/json/stream.go:152 +0x109
encoding/json.(*Decoder).readValue(0xc420e1a000, 0x0, 0x0, 0x40f3d8)
        /usr/local/go/src/encoding/json/stream.go:128 +0x1ca
encoding/json.(*Decoder).Decode(0xc420e1a000, 0x1450c60, 0xc4208a3020, 0xc4208197d0, 0x0)
        /usr/local/go/src/encoding/json/stream.go:57 +0x85
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/framer.(*jsonFrameReader).Read(0xc420f71350, 0xc420db0000, 0x800, 0xa80, 0x40, 0x38, 0x149c2c0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/framer/framer.go:150 +0x2d1
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/runtime/serializer/streaming.(*decoder).Decode(0xc42036c140, 0x0, 0x1ee3bc0, 0xc420a14a80, 0x450130, 0xc420fcc420, 0xc4209b5500, 0x0, 0xc420d75f20)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/runtime/serializer/streaming/streaming.go:77 +0x8b
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/rest/watch.(*Decoder).Decode(0xc4206754a0, 0xc420fcc420, 0xc420d75fa8, 0x1ee3000, 0xc4209b5500, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/rest/watch/decoder.go:49 +0x7c
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch.(*StreamWatcher).receive(0xc420f71380)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch/streamwatcher.go:93 +0xe2
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch.NewStreamWatcher
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch/streamwatcher.go:60 +0xd9

goroutine 94124 [semacquire, 4 minutes]:
sync.runtime_notifyListWait(0xc42021d800, 0xc400000000)
        /usr/local/go/src/runtime/sema.go:298 +0x10b
sync.(*Cond).Wait(0xc42021d7f0)
        /usr/local/go/src/sync/cond.go:57 +0x89
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.(*pipe).Read(0xc42021d7e8, 0xc4208e8400, 0x200, 0x200, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/pipe.go:60 +0xdb
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.transportResponseBody.Read(0xc42021d7c0, 0xc4208e8400, 0x200, 0x200, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/transport.go:1465 +0xae
encoding/json.(*Decoder).refill(0xc420d54000, 0x20, 0x18)
        /usr/local/go/src/encoding/json/stream.go:152 +0x109
encoding/json.(*Decoder).readValue(0xc420d54000, 0x0, 0x0, 0x40f3d8)
        /usr/local/go/src/encoding/json/stream.go:128 +0x1ca
encoding/json.(*Decoder).Decode(0xc420d54000, 0x1450c60, 0xc4208abf20, 0x428716, 0x1661270)
        /usr/local/go/src/encoding/json/stream.go:57 +0x85
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/framer.(*jsonFrameReader).Read(0xc420b420c0, 0xc420d26000, 0x400, 0x400, 0x40, 0x38, 0x149c2c0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/framer/framer.go:150 +0x2d1
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/runtime/serializer/streaming.(*decoder).Decode(0xc42094e500, 0x0, 0x1ee3bc0, 0xc420ea4ac0, 0x0, 0x0, 0x0, 0xc420e1cf20, 0x42804e)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/runtime/serializer/streaming/streaming.go:77 +0x8b
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/rest/watch.(*Decoder).Decode(0xc4208abf00, 0x165d718, 0x0, 0x0, 0x0, 0xc420e1cfb0, 0x1238b5b)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/rest/watch/decoder.go:49 +0x7c
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch.(*StreamWatcher).receive(0xc420b420f0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch/streamwatcher.go:93 +0xe2
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch.NewStreamWatcher
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch/streamwatcher.go:60 +0xd9

goroutine 96161 [semacquire]:
sync.runtime_notifyListWait(0xc4200ea540, 0xc400000049)
        /usr/local/go/src/runtime/sema.go:298 +0x10b
sync.(*Cond).Wait(0xc4200ea530)
        /usr/local/go/src/sync/cond.go:57 +0x89
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.(*pipe).Read(0xc4200ea528, 0xc420bba001, 0x1dff, 0x1dff, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/pipe.go:60 +0xdb
github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2.transportResponseBody.Read(0xc4200ea500, 0xc420bba001, 0x1dff, 0x1dff, 0x0, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/golang.org/x/net/http2/transport.go:1465 +0xae
encoding/json.(*Decoder).refill(0xc420ca6700, 0xa, 0x9)
        /usr/local/go/src/encoding/json/stream.go:152 +0x109
encoding/json.(*Decoder).readValue(0xc420ca6700, 0x0, 0x0, 0x40f3d8)
        /usr/local/go/src/encoding/json/stream.go:128 +0x1ca
encoding/json.(*Decoder).Decode(0xc420ca6700, 0x1450c60, 0xc4201bcee0, 0xc420e167e0, 0x0)
        /usr/local/go/src/encoding/json/stream.go:57 +0x85
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/framer.(*jsonFrameReader).Read(0xc4209580f0, 0xc42001cc00, 0x1000, 0x1300, 0x40, 0x38, 0x149c2c0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/util/framer/framer.go:150 +0x2d1
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/runtime/serializer/streaming.(*decoder).Decode(0xc420422b40, 0x0, 0x1ee3bc0, 0xc420b384c0, 0x450130, 0xc42074e4e0, 0xc420fc6f00, 0x0, 0xc420d79f20)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/runtime/serializer/streaming/streaming.go:77 +0x8b
github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/rest/watch.(*Decoder).Decode(0xc420b3a580, 0xc42074e4e0, 0xc420d79fa8, 0x1ee52c0, 0xc420fc6f00, 0x0, 0x0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/client-go/rest/watch/decoder.go:49 +0x7c
github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch.(*StreamWatcher).receive(0xc420958120)
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch/streamwatcher.go:93 +0xe2
created by github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch.NewStreamWatcher
        /go/src/github.com/projectcalico/k8s-policy/vendor/k8s.io/apimachinery/pkg/watch/streamwatcher.go:60 +0xd9

goroutine 96270 [select]:
net/http.(*persistConn).roundTrip(0xc4208f2a20, 0xc4208a3660, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/http/transport.go:1898 +0x974
net/http.(*Transport).RoundTrip(0xc42024a000, 0xc420981b00, 0x600, 0x0, 0x0)
        /usr/local/go/src/net/http/transport.go:391 +0x74c
github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client.(*simpleHTTPClient).Do.func1(0xc4201a0c80, 0xc420981b00, 0xc420fefda0)
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client/client.go:523 +0x41
created by github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client.(*simpleHTTPClient).Do
        /go/src/github.com/projectcalico/k8s-policy/vendor/github.com/coreos/etcd/client/client.go:526 +0x200

</details

I thought this was fixed with #147 which addressed #145, so I double checked the version I was running and it is quay.io/calico/kube-policy-controller:v1.0.0-rc2.

This is by #155

authors: caseydavenport tmjd


text:
Upgrade to curation_concerns 0.3.0 (#29)

Please do not merge this request - this is for the purposes of comparison, review, and discussion.

:+1: Looks good to me. I'd say merge it and build out the specs as a next step. @yulgit1 Any thoughts?

Yeah, if the upload works and the tests pass.

From: Eliot Jordan [notifications@github.com]
Sent: Tuesday, November 10, 2015 12:17 PM
To: projecthydra-labs/geo_concerns
Cc: James, Eric
Subject: Re: [geo_concerns] Upgrade to curation_concerns 0.3.0 (#29) (#44)
[:+1:] Looks good to me. I'd say merge it and build out the specs as a next step. @yulgit1https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_yulgit1&d=AwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=3IJUJjo7agEq3E2n9IHyDxi3hKFK6Mp6IJH-DqbUGG4&m=t8O5SV2eZicX5q1wc3qDJL8MCWTYRnjn-g6S3hC13y0&s=5qd2FbHcfqkP66OolNwudBN_iUkqMGhKJQIN89CtG-Q&e= Any thoughts?
—
Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_projecthydra-2Dlabs_geo-5Fconcerns_pull_44-23issuecomment-2D155493832&d=AwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=3IJUJjo7agEq3E2n9IHyDxi3hKFK6Mp6IJH-DqbUGG4&m=t8O5SV2eZicX5q1wc3qDJL8MCWTYRnjn-g6S3hC13y0&s=eiu5EhAYZKGtE88UoQdVqHJza7keixLkPGLpHjFKZ50&e=.

source: gharchive/pull-request

authors: eliotjordan jrgriffiniii yulgit1

license_type: permissive

license_source: bigquery


text:
Update layout of Workflow Roles page

Fixes #721
Improves the layout of the Workflow Roles page:

Adds standard page header
Moves assign role form to top of page, so it'll be easier to get to when the number of assigned roles becomes long
Better separates the Assign Role and Current Roles elements
Improves presentation of the roles currently assigned to a user

I think we can further improve the Assign Role section (e.g., I don't think the required labels are really necessary here and it would be nice for the select menus to display "Select user..." and "Select workflow role..." instead of being blank) but this is probably fine for the time being.
Before

After

Seems like just one conflict/rebase question in a scss file.

@jcoyne @mjgiarlo @atz Can one of you double-check this conflict? I get no conflict when I rebase locally. Is it just an extra blank line it is saying is a conflict? I'm not sure how to interpret this one.

@ggeisler I can check it.

@ggeisler rebased.

authors: atz ggeisler jcoyne

repo: projecthydra-labs/hyrax

license_source: github-api


text:
Multi-Select with Shift+Click

If there's a bunch of files in a folder and you don't want to upload the entire folder.

That would be default browser functionality if the elements were actually options in a HTML <select multiple>, but we have them as table-rows.  We should try to use actual select/options.
Ideally, we should get away from the back-end delivering HTML partials altogether and start responding in JSON, leaving rendering to the AJAX layer.  We might also employ some jquery filepicker/tree-traverser that has all the bells and whistles we want.

source: gharchive/issue

authors: atz tpendragon

repo: projecthydra/browse-everything

license: mit


text:
Microsoft.Data.Tools.Schema.SqlTasks.targets was not found (GitHub deployment)

Hi,
I customized the deployment scripts to build and deploy an SSDT project with msbuild.exe. I added this statement:

call :ExecuteCmd "%MSBUILD_PATH%" "%DEPLOYMENT_SOURCE%\Database.sqlproj" /t:Build /t:Publish /p:SqlPublishProfilePath=Database.Production.publish.xml /p:TargetConnectionString="%DEFAULT_CONNECTION%"

And I get this error:

error MSB4019: The imported project "D:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.

I tried setting /property:VisualStudioVersion to 12.0 and 14.0 with no success. I also tried to delete "SET USE_MSBUILD=TRUE" from the deployment script but that statement doesn't exist in the default deployment scripts. That fix was suggested here.
My question is - is this possible at all? Are the other alternatives to deploy an SSDT project?
Thank you!

I'll add the missing target files.

This should be there now. @brunoligutti can you give it a try now?

authors: ahmelsayed brunoligutti

repo: projectkudu/kudu


text:
updated is_top_level calculation

Pull requests into cqm-converter require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass
[ ] If applicable, the library version number in cqm-converter.gemspec has been updated
[ ] Update cqm-execution test fixtures using update_cqm_execution_fixtures.sh script from server-scripts repo

Bonnie Reviewer:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Cypress Reviewer:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

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

@@           Coverage Diff           @@
##           master      #38   +/-   ##
=======================================
  Coverage   57.34%   57.34%
=======================================
  Files           7        7
  Lines         483      483
=======================================
  Hits          277      277
  Misses        206      206

Impacted Files
Coverage Δ

lib/cqm/converter/bonnie_measure.rb
96.8% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io zlister

repo: projecttacoma/cqm-converter


text:
Add any cast for Date/Time strings

Add support for casting Any to Date or Time
Pull requests into cqm-models require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: https://jira.mitre.org/browse/BONNIE-2076
[x] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass
[x] If applicable, the library version number in package.json and cqm-models.gemspec has been updated
[x] Cqm-execution fixtures have been updated with the update_cqm_execution_fixtures.sh script inside server-scripts using this branch in the cqm-converter

Bonnie Reviewer:
Name: @hackrm

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code

Bonnie Reviewer:
Name: @zlister

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

It looks good to me, I will approve it once Travis passes.

authors: hackrm losborne

repo: projecttacoma/cqm-models


text:
Results object

This Pull Request adds an IndividualResult object to Javascript and Ruby, which allows for the storage of results about a particular patient-measure combination. Also includes several changes to the Measure model to accommodate the relations to IndividualResult.
Pull requests into cqm-models require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: https://jira.mitre.org/browse/TACO-48
[x] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[x] Tests are included and test edge cases N/A
[x] Tests have been run locally and pass N/A
[ ] If there were any JavaScript changes, this PR has updated the dist directory using npm run dist
[ ] If applicable, the library version number in package.json and cqm-models.gemspec has been updated

Reviewer 0:
Name: @holmesie

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name: @ljades

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code

templates/index_template.js.erb  and app/assets/javascripts/index.js will also need to be updated to reference Individual Result
module.exports.IndividualResult = require('./IndividualResult').IndividualResult;
module.exports.IndividualResultSchema = require('./IndividualResult').IndividualResultSchema;

authors: dczulada okeefm


text:
update nokogiri

Pull requests into cqm-parsers require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

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

@@           Coverage Diff           @@
##           master      #45   +/-   ##
=======================================
  Coverage   88.55%   88.55%
=======================================
  Files          67       67
  Lines        1686     1686
=======================================
  Hits         1493     1493
  Misses        193      193

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 580d2c3...b61a7cd. Read the comment docs.

authors: codecov-io dczulada

repo: projecttacoma/cqm-reports


text:
Role argument validation fails when play skipped, due to a dependency on facts not gathered due to it being skipped

I am using the node_exporter role, which includes role argument validation.
Using tags to skip the inclusion of a particular play doesn't appear to stop the argument validation from taking place, which results in a failure as the role has a default var requiring gather_facts having run.  Using a tag to only run that particular playbook, or no tags at all, results in successful execution.
e.g.
# site.yml
---
- name: Deploy common exporters
  hosts: monitored,monitoring-server
  vars_files:
    - ../vars/prometheus.yml
  roles:
    - prometheus.prometheus.node_exporter
  tags:
    - exporters

- name: Setup core monitoring software
  hosts: monitoring-server
  vars_files:
    - ../vars/prometheus.yml
  roles:
    - prometheus.prometheus.prometheus
    - prometheus.prometheus.alertmanager
    - prometheus.prometheus.snmp_exporter
  tags:
    - prometheus

If I run the following commands, it works:
$ ansible-playbook -i inventory.yml site.yml --tags exporters
$
$ ansible-playbook -i inventory.yml site.yml

If I run the following, it fails:
$ ansible-playbook -i inventory.yml site.yml --tags prometheus
# output removed for brevity #
PLAY [Deploy common exporters] *************************************************************************************************************************************

TASK [prometheus.prometheus.node_exporter : Validating arguments against arg spec 'main' - Prometheus Node Exporter] ***********************************************
fatal: [srv1]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined"}
fatal: [srv2]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined"}
fatal: [monitoring-server]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined. {{ go_arch_map[ansible_architecture] | default(ansible_architecture) }}: 'ansible_architecture' is undefined. 'ansible_architecture' is undefined"}

This seems to be because the default vars for this role include a dependency on gather_facts having run on all the target hosts, as otherwise the variable ansible_architecture isn't created & set.
If I manually add the following to my own vars file, then it works as expected.
#../vars/prometheus.yml
ansible_architecture: x86_64

I don't know whether there is a way to disable the role argument validation in the case that a role is not called due to tags use, or whether this is a more fundamental bug (or feature) in Ansible.

Interesting, it looks like it's ignoring the tag completely and running the exporters play regardless, it even prints the name of the play Deploy common exporters.
After you define the ansible_architecture variable does it continue with other tasks from that play or just jump over to the Setup core monitoring software play?
The task Validating arguments against arg spec is not something that's defined in the role and is something that ansible adds to every play where roles include argument specs: https://github.com/ansible/ansible/blob/a23ea2aef25a1256bc9850d42180351d5cd54619/lib/ansible/playbook/role/init.py#L61 and I don't see any options for disabling it.
I'm a bit surprised that this issue has not been raised before as I would have thought that this issue would affect many, the only discussion on the subject that I could find is this one: https://groups.google.com/g/ansible-project/c/h3StjZ75_MI
With that being said, it's strange that it doesn't recognize ansible_architecture as you don't seem to be disabling facts gathering in the playbook.
The ansible_architecture variable is used in the other roles as well so I would have thought that they would also fail the argument spec validation.
Have you tried using --skip-tags: "exporters" to see if that makes you truly skip the exporters play?
Also curious if you would run into the same issue by including the role at a task level instead of a play level with ansible.builtin.include_role since it doesn't include the role unless needed.

Yes it looks like using roles: in the play is essentially the same as using ansible.builtin.import_role as it is being evaluated even though it is skipped because of the --tags
In addition it seems that the arg spec validation task that's injected before is not getting tagged as it should so that it runs that task no matter what.
IMHO this is a bug and can't be by design, I mean the facts gathering seems to be tagged correctly so that it doesn't run so why shouldn't the argument spec validation task be tagged as well.
At least this should be mentioned somewhere in the ansible docs.

Yes, agreed. I'll raise an issue in the ansible project.  Thanks for your help.

Raised an issue here: https://github.com/ansible/ansible/issues/82670

Closing this since it's a feature/bug of ansible and out of scope for the collection.

authors: gardar tomkivlin

repo: prometheus-community/ansible


text:
Monitor user unit services

In some cases I want to monitor systemd services setup as a user unit
sudo su -l user1

systemctl status --user app1

checking the systemd status from outside won't work

I have the same issue and I struggle to get it working :( i am running systemd exporter as root and expect it to get all metric for root and all users.

I end up making systemd-exporter run in the same user as the service being monitored
and adding
--systemd.collector.user

authors: Lusitaniae newskooler


text:
how to modify the kube prometheus prometheus.yaml.gz as follows:

I want to modify the prometheus.yaml.gz as follows:
`global:
evaluation_interval: 15s
scrape_interval: 15s
external_labels:
prometheus: monitoring/k8s
prometheus_replica: $(POD_NAME)
rule_files:

/etc/prometheus/rules/prometheus-k8s-rulefiles-0/*.yaml
scrape_configs:
job_name: serviceMonitor/monitoring/alertmanager-main/0
honor_labels: false
kubernetes_sd_configs:
..................................
alerting:
alert_relabel_configs:

action: labeldrop
regex: prometheus_replica
alertmanagers:
path_prefix: /ff-alerts
scheme: http
kubernetes_sd_configs:

role: endpoints
namespaces:
names:

monitoring
api_version: v2
relabel_configs:

action: keep
source_labels:

__meta_kubernetes_service_name
regex: alertmanager-main

action: keep
source_labels:

__meta_kubernetes_endpoint_port_name
regex: web
`

Because I need to use the second-level domain name /ff-alerts and /ff-prometheus 。
so prometheus will getting error as follows：

also need help with that issue

This issue has been automatically marked as stale because it has not had any activity in the last 60 days. Thank you for your contributions.

you need to revise prometheus-serviceMonitor.yaml file and add`
spec:
endpoints:

interval: 30s
port: web
path: /ff-prometheus/metrics
interval: 30s
port: reloader-web`

authors: TszChingLeung yahavvidaa

repo: prometheus-operator/kube-prometheus


text:
Only serve alerts page from /alerts or /.

This fixes https://github.com/prometheus/prometheus/issues/607

@beorn7

:+1:

repo: prometheus/alertmanager


text:
Silence State from API and UI

Return Silence state on /silences
silenceState = "expired" | "active" | "pending""status": {
  "state": "expired"
}

Restyle SilenceList view

Group by Silence state
Adjust styling to AlertList view

Adjust Silence view

Fixes issue #745
This does not introduce the quick filter via three check-boxes. I would suggest that we don't really need those anymore? What do you think?

As this is the last issue in the milestone 4, we could merge the new UI into master once this is merged.
=> No more syncing between master and ui-rewrite

@stuartnelson3 @w0rm I have addressed all of your comments, thanks for the review! Any other wanted changes?
@fabxc Do you agree with the changes on the golang side?

Yea, we can roll with this for now. At some point we might want to at least add a toggle/hide button to each group.

@stuartnelson3 Triggered Circle CI
@all Thanks for the review.

authors: fabxc mxinden


text:
add linkerd to directly-instrumented list

linker exports Prometheus metrics directly, currently on :9990/admin/metrics/prometheus. (See e.g. https://github.com/BuoyantIO/linkerd/blob/master/admin/src/main/scala/io/buoyant/admin/PrometheusStatsHandler.scala and https://github.com/BuoyantIO/linkerd/issues/396 for making this configurable.)

Great to hear. I could imagine @brian-brazil feels tempted now to give you some advice about the integration, but it's certainly fine to list it here.

This isn't directly instrumented, it looks to be an internal exporter that's working off one of the two twitter metrics systems. I don't think we've got a place for those yet on this page.

@brian-brazil What's the distinction?

You're not using the Prometheus java client to instrument your code, you're using a different instrumentation system.

Well that's true, but the heading for this section doesn't mention the official Prometheus Java client. It says "Some third-party software already exposes Prometheus metrics natively, so no separate exporters are needed:". I believe linkerd satisfies that description.

I agree that native instrumentation does not imply usage of an official client library.
The question is if the metrics you expose here are metrics about linkerd or if those metrics are about other systems that linkerd interacts with.

Ok, you two are saying different things.
@beorn7: to answer your question, linkerd exposes both metrics about its internal state and metrics about the systems it interacts with.
I've changed the capitalization. Happy to put it in another section or another page if you prefer.

Ok, you two are saying different things.

That happens now and then. ;)
But in fact, while @brian-brazil takes a more formal approach by requiring usage of the client library, we both agree on the results: The exposed metrics should have proper "Promethean" semantics. Personally, I don't care if that's accomplished with or without an official client library. The client library makes it easy to support proper semantics, but you can create broken semantics with the client library and proper one without one.
I haven't looked into too much detail here, which is why I hinted that @brian-brazil might want to tell you about them.
I don't feel strongly in which category we link linkerd. In doubt, let's just put it under "Other third-party utilities". That can't be wrong.

We need a new category here I think. It doesn't fit in 3rd party utilities as linkerd doesn't appear to be an instrumentation tool. I imagine over time we'll find many things that are instrumented with some other library, but also can expose metrics in the Prometheus format.

I haven't looked into too much detail here, which is why I hinted that @brian-brazil might want to tell you about them.

If you look at the linked scala file it's pretty clear. It's pulling from a Twitter Registry, sanitising metric names and manually writing the text format.
I'd like us to have a section for software that is doing Prometheus instrumentation in the recommended way, which is with our client libraries. "Directly instrumented software" seems like the right place for that. Right now the heading says "directly instrumented" and the copy says "exposes Prometheus metrics natively" which are different things which is where the confusion is.
Cadvisor should also move to the exporters as it's primarily proxying data from the kernel so it isn't directly instrumented.

Feel free to refactor the sections. I'll trust your judgement.

#749 rejigs this and add linkerd.

authors: beorn7 brian-brazil wmorgan

repo: prometheus/docs


text:
Notification/comment on test command success and failure

With the current Prow setup:
1./benchmark : A comment is posted before make deploy is run, this comment contains all information about the test. If something fails while make deploy is running prow posts a comment about the prowjob exiting with an error code.
2. /benchmark cancel : No comment is posted
With the new Github Actions setup:
Current comments:
1./benchmark : A comment is posted before make deploy is run, this comment contains all information about the test.
2. /benchmark cancel : A comment is posted before make clean is run. ( @krasi-georgiev recommends getting rid of this comment as we'll get a notification after 3 days anyway if this failed by the alertmanager)
ref https://github.com/prometheus/prombench/pull/248#issuecomment-520129011
I'd like to suggest a few more places for comments that  can make working with prombench from GitHub easier, this assumes the use of the StatefulSet implementation to run tests:
Github Actions with StatefulSet

/benchmark:  A comment is posted before make deploy is run, this comment contains all information about the test. Additionally, should contain the link to the deployment log for the statefulset in loki. (WIP)
change:

make deploy && echo 'deploy succeeded, now sleeping' && while sleep 86400; do :; done

to
if make deploy; then echo 'deploy succeeded, now sleeping'; while sleep 86400; do :; done; else make comment_deploy_failure; fi`

comment_deploy_failure is a Makefile target, which will call a script from /scripts directory which will post a comment to GitHub PR about that there was some failure in running make deploy

/benchmark cancel : No comment is posted

Some of these comments might be not necessary please provide you feedback and suggestions

/benchmark cancel : A comment is posted before make clean is run. ( @krasi-georgiev recommends getting rid of this comment as we'll get a notification after 3 days anyway if this failed by the alertmanager)

afer some discussion we will keep the comment to give feedvack that the cancellation has starter. This will remove a confusion like: "Did I type the comment properly", "Did the system detect the webhook" etc.

if make deploy; then echo 'deploy succeeded, now sleeping'; while sleep 86400; do :; done; else make comment_deploy_failure; fi`

lets wait for github actions a bit more as they should provide some form of feedback when a workflow failed.

https://help.github.com/en/articles/about-github-actions#notifications-for-workflow-runs
Its there in the docs to send enable notifications for gh actions. Even an option to send notifications for failed workflows only.
To enable https://help.github.com/en/articles/choosing-the-delivery-method-for-your-notifications#choosing-the-delivery-method-for-your-notifications-about-github-actions

Github Action issue to track commenting on failure:
https://github.community/t5/How-to-use-Git-and-GitHub/Github-Actions-Contexts-and-steps-if-conditionals-are-unusable/m-p/29669/highlight/true#M8294

closed by #287

authors: geekodour krasi-georgiev nikita-mk

repo: prometheus/prombench


text:
Add service discovery for OvhCloud

This PR adds a new service disocvery for Ovhcloud Bare Metal Cloud based on the work that has been done for Ionos and Scaleway.
The service discovery allows users to create scrape targets based on servers tied to an OVHcloud account.
Thank you for your time on this PR.
Answered https://github.com/prometheus/prometheus/pull/10775#issuecomment-1144080466
Signed-off-by: Marine Bal marine.bal@ovhcloud.com

Also, you can just push code to your branch without recreating a new pull request each time. Thanks!

In general, labels should be as close as possible to the fields the API
offers.
On 03 Jun 04:53, Arnoways wrote:

@Arnoways commented on this pull request.

+// CreateClient get client
+func (c SDConfig) CreateClient() (*ovh.Client, error) {

return ovh.NewClient(c.Endpoint, c.ApplicationKey, c.ApplicationSecret, c.ConsumerKey)
+}

+// NewDiscoverer new discoverer
+func (c SDConfig) NewDiscoverer(options discovery.DiscovererOptions) (discovery.Discoverer, error) {

return NewDiscovery(&c, options.Logger)
+}

+func init() {

discovery.RegisterConfig(&SDConfig{})
+}

+// ParseIPList Parse ip list to store on IPV4 and IPV6 on IPs type
+func ParseIPList(ipList []string) (*IPs, error) {
We use it to add ipv4 and ipv6 as meta in discovered labels so users can pick the one they want to use for scrapping.
--
Reply to this email directly or view it on GitHub:
https://github.com/prometheus/prometheus/pull/10802#discussion_r888873453
You are receiving this because you commented.
Message ID: @.***>

--
Julien Pivotto
O11y - https://o11y.eu/

For labels, we took the same api name with json tag by default, we only update it for 2-3 fields because one is on a sub-object and on object and it's duplicate
and on other one we have a typo into the api (fixed with V2 but not for now)

Hi @roidelapluie I updated the PR trying to remove the extra libraries and tidying the tests. Let me know what you think

Hello @roidelapluie , any chance you could take a new look at the modifications please?

Can we use https://pkg.go.dev/inet.af/netaddr and remove all the IP logic in the discovery?

Thanks!

authors: Arnoways Mama59 roidelapluie

repo: prometheus/prometheus


text:
ci: Add job to report build_all status

This should enable proper status reporting of matrix jobs for release branches. See also https://github.com/orgs/community/discussions/4324.
The branch protection rule(s) for release branches need to be changed too.

The idea is that GitHub's PR process gets stuck on the job, but a line saying needs.*.result will always work?
I haven't studied GitHub actions.

The branch protection rule(s) for release branches need to be changed too.

How would someone figure out what change is required?

How would someone figure out what change is required?

This PR introduces and additional job that needs the build_all job and it fails or succeeds based on the result list of all build_all matrix jobs, hence checking needs.*.result. We "manually" aggregate the status of the concurrent jobs.
side note I just noticed that the checks need a fix, we wan't to fail if build_all contains a single failure and only succeed of all jobs succeed. I'll fix that.
I think release branches currently have a status check against the Build for all architectures action. This is a matrix job running in 12 threads and github seems to lack a feature to aggregate and report the status correctly (see discussion link above). If that is correct (I can't actually check), this should be changed to check the status of the new build_all_status job.
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule
The relevant docs are here.
Changing the branch protection can also be done later, when everyone is convinced this new job reports as expected.

How to proceed here? This is way beyond my GH CI foo. @SuperQ maybe you have an opinion here?

I'd argue this change here by itself is benign. I merely adds a job that aggregates the status of previous jobs is depends on. We can merge this and monitor, that the new status job shows the correct behavior (green when all build_all matrix jobs are green, red when a single one fails).
Once we have confidence this does the right thing, enabling a branch protection rule is a separate step.
But I'm more then happy to have more eyes on this.

authors: bboreham beorn7 jan--f


text:
Discovery tests for updating target groups

This pr

Adds a test covering the case where a target providers sends updated versions of the same target groups and the system should reconcile to the latest version of each of the target groups
Refactors how input data is represented in the tests. It used to be literal declarations of necessary structs, now it is parsing yaml. Yaml declarations are half as long as the former. And these can be put in a fixture file
Adds a tiny bit of refactoring on test timeouts https://github.com/prometheus/prometheus/pull/3426/commits/10bad30ed799180ec65e1ea3c290bcf4d425e95f

For the second point, I think it is more developer friendly to read the yaml declarations from a fixture file. I'll work on it, drop a line if there are any opinions.

cc @brian-brazil @fabxc please have a look.

ping @brian-brazil , anything else to address in this pr?

Thanks for the comments (the useful ones 😛 ) @grobie. I added https://github.com/prometheus/prometheus/pull/3426/commits/099094dff75b10a039b85e6b53d86d138ee36e64 to address them.

I have couple of other additions in mind for these tests. It would be nice if this pr can be merged in before it gets too huge to review. ❤

Thanks!

authors: grandbora grobie


text:
when zooming in/out, we keep the pre-selected lines

Fix #7818 , add one more parameter needSaveLegendStatus to check if we need to keep the legend status. Now it'll only set to true when clicking on time range button (increase/decrease).
Signed-off-by: Luke Chen showuon@gmail.com

@juliusv , could you review this PR? Thanks.

Hi, thanks for submitting this! But I'm wondering, was there any more discussion after the last comment on https://github.com/prometheus/prometheus/issues/7818#issuecomment-682736613? Because I also was thinking the same thing as @roidelapluie, wondering whether it's worth the extra complexity to add this, since it's possible to turn off all series except some, by just clicking on the series name. And at least in the new UI, you can do that with multiple series by pressing Ctrl.
On a general note, this old UI is going away soon (yeah, for real now), so changes like this would be better made against the new React UI (under https://github.com/prometheus/prometheus/tree/master/web/ui/react-app). But it would be good to clear up the question above first, whether this is really needed.

@juliusv OK, I see. But in my opinion, although this old UI is going away soon, the old UI is still the entry point of Prometheus users for now. And if the enhancement makes sense and could make the user experience better, we should do it. Especially, this fix is not that complicated and ready for review now. Anyway, that's my opinion. I'll wait for the discussion. Thanks.

@juliusv do we want this?

I think we can add it since the patch is ready to go now. That's my opinion. What do you think @juliusv ?

Hi, sorry for dropping the ball on this. The React UI is the default by now, so things like this should go there in the future. However, when testing this for the old UI, I also found that it still has some unexpected behavior: when you zoom into a range that has a subset of the series a different range, and then go back to the bigger range, the bigger range will only have the subset selected, even though there was never any manual selection being done. I would expect that a superset in a larger range would always be shown, unless a user has explicitly manually selected only a subset of series. Things like that still make me wonder whether the feature is worth the mental complexity though.

Hi, sorry for dropping the ball on this. The React UI is the default by now, so things like this should go there in the future. However, when testing this for the old UI, I also found that it still has some unexpected behavior: when you zoom into a range that has a subset of the series a different range, and then go back to the bigger range, the bigger range will only have the subset selected, even though there was never any manual selection being done. I would expect that a superset in a larger range would always be shown, unless a user has explicitly manually selected only a subset of series. Things like that still make me wonder whether the feature is worth the mental complexity though.

@juliusv , ok, I'll close this PR. Thanks.

@juliusv , ok, I'll close this PR. Thanks.

authors: codesome juliusv showuon


text:
Document why OPENAI_API_KEY in getting started

I am looking into adopting promptfoo, and in the getting started step 3, randomly it asks for an OpenAI API key.
https://promptfoo.dev/docs/getting-started
Why is the OpenAI API key needed?  Can we document this (or add a link to the explanation) into the Getting Started instructions?

Is there some way we can have the "getting started" instructions not require OpenAI being set up?

Yes, if you aren't using GPT then you don't need to set your OpenAI API key!  promptfoo init creates a config that uses GPT by default, hence its inclusion in Getting Started.
Also worth noting that if you use any model-graded assert, you will have to override the LLM grader (and potentially the rubric prompt) to select a model other than GPT.

Thanks, I can contribute a docs PR for this shortly

I was in the docs anyway so I made an edit - feel free to add further clarification if you see a need :)

Just to confirm, is the default Getting Started supposed to use OpenAI's chat endpoint or completion endpoint?

It uses OpenAI's chat endpoint by default.

Thanks, I opened https://github.com/promptfoo/promptfoo-docs/pull/6 to upstream my learnings, thank you!

authors: jamesbraza typpo

repo: promptfoo/promptfoo

license: MIT


text:
Add link to Slack support

Need to add a link to be able to join the Support Slack after @pushkar adds.

@pushkar, what is the slack support link?


text:
not running propel with a propel.php config

I've found a issue. if you have a propel.php config file it will not work because he includes the config instead of the core file of propel
eg: ../../vendor/bin/propel   will execute the config file instead of propel itself
(this is annoying because it will not return anything)
I found renaming propel.php to propel.ini (the config)  did work.

Not sure about the cause, but I had a similar issue (propel.php not being used).
However, for me the workaround was renaming to "propel.inc" not "propel.ini".

authors: JASchilz spidfire

repo: propelorm/Propel


text:
Define all parameters supported by "Edit a set of TPP...

The puzzle 240-0a8671b5 from #240 has to be resolved:
https://github.com/proshin-roman/finapi-java-client/blob/4c115491c5fec39562fae8dabdbcac9adb214f3d/src/main/java/org/proshin/finapi/tppcredential/in/EditTppCredentialParameters.java#L21-L21
The puzzle was created by Roman Proshin on 26-Dec-19.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 240-0a8671b5 has disappeared from the source code, that's why I closed this issue.

repo: proshin-roman/finapi-java-client


text:
Pull requests are not updated when jenkins-ptcs-library is updated

When new version of jenkins-ptcs-library is released, old pull requests created by repository validator are not updated.
That branch should be updates so it updates the jenkins-ptcs-library directly to the latest version.

This should now be fixed.

repo: protacon/repository-validator


text:
🛑 dnslink.org is down

In 80a67bc, dnslink.org (https://dnslink.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: dnslink.org is back up in c228623 after 6 minutes.

repo: protocol/upptime-pln


text:
Add GEPA

Insert URLs to the project here: https://github.com/USEPA/GEPA

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All new projects listed will be posted on our Mastodon channel.

@nkruskamp @haclohman @burnettear

repo: protontypes/open-sustainable-technology


text:
Add clear message when topic creation fails

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
I changed to display the error message returned from the backend.
Is there anything you'd like reviewers to focus on?
It's my first pull request on this project so I'm happy If you give me a feedback.
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually - tried to create a topic twice
[ ] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[ ] My changes generate no new warnings (e.g. Sonar is happy)
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)
Topic creation when fails display 'Schema '

Now is displaying the error returned from the backend:

@Corlobin hey, thanks for your contribution!

authors: Corlobin Haarolean

repo: provectus/kafka-ui


text:
fix documentation

At https://pruvious.com/tutorial/01-project-setup
This line doesn't open the browser automatically.
To fix it: npm run dev -- -o instead of npm run dev -o

Fixed. Thank you.

repo: pruvious/pruvious


text:
Packet decoding will need to account for pump model

There are a lot of folks now with hardware that plan to talk to X22 pumps, which have about a dozen encoding differences across major packets. The most common one is when decoding insulin amounts, since the X22 and X23+ have different stroke sizes. However, there are other cases where bytes are in different offsets.
One approach that should work would be to create a family of PumpModel classes with an index by model string, and a family of Message classes to handle the decoding. MinimedPacket should continue to be agnostic to the intricacies of the message data and focus on RF encoding/decoding and validation.
Thoughts?

That makes sense; I have that separation in the https://github.com/ps2/minimed_rf library as well, and I'd like to keep them roughly in sync.

One thing I'd like to do differently than minimed_rf, is to have the message classes be aware of the first 5 bytes.  I plan to update minimed_rf message classes to be the same way

When separate message types have a common field type that is parsed in varying ways determined by pump model, then it makes sense for that decoding to be shared, and configurable by pump model.  I would think that there is still a single message type that can handle the various pumps.
But I might not be understanding what's common and what varies completely. We'd need to discuss specifics, I think, to get the best layout.  For now, I agree 100% on separating message semantics from the 4b6b encoding, crc calculation, and other rf packet details.

This issue was moved to ps2/rileylink_ios#1


text:
memory leak

Describe the bug
When using psalm with Laravel plugin I have, as I think, memory leak.
At least, when I run it with plugin, I have
psalm --no-cache
Scanning files...
PHP Fatal error:  Allowed memory size of 8589934592 bytes exhausted (tried to allocate 20480 bytes) in /var/www/vendor/laravel/framework/src/Illuminate/Support/Arr.php on line 300
PHP Fatal error:  Allowed memory size of 8589934592 bytes exhausted (tried to allocate 65536 bytes) in /var/www/vendor/sentry/sentry/src/Integration/FrameContextifierIntegration.php on line 56

when I run without plugin, it works fine
Impacted Versions
laravel/framework 5.8
vimeo/psalm 3.9
psalm/plugin-laravel 1.2.1
Can't give more info due to NDA.
Additional context
Add any other context about the problem here.
I can provide some other info (logs all dependencies) but only in private DM

Hey, please try to narrow it down a bit more - run with --debug to figure out what file it’s coming from, and see if running on just that file still produces the leak

:facepalm: my bad, I've made cyclic dependency, that's why it was not working

authors: muglug vladyslavstartsev

repo: psalm/psalm-plugin-laravel


text:
Refaktorované ovládání bojleru + nové senzory

Přidány nové senzory

battery_quality
battery_add_month
battery_add_year
battery_volt
battery_current
ac_in_aci_f
battery_temp
boiler_ssr1
boiler_ssr2
boiler_ssr3
boiler_manual_mode

Přidány/Refaktorovány nové služby pro ovládání CBB (bojler)

set_boiler_mode (refaktoring)
set_ssr_rele_1
set_ssr_rele_2
set_ssr_rele_3

Přidány nové senzory

battery_quality
battery_add_month
battery_add_year
battery_volt
battery_current
ac_in_aci_f
battery_temp
boiler_ssr1
boiler_ssr2
boiler_ssr3
boiler_manual_mode

Přidány/Refaktorovány nové služby pro ovládání CBB (bojler)

set_boiler_mode (refaktoring)
set_ssr_rele_1
set_ssr_rele_2
set_ssr_rele_3

Přidány nové senzory
battery_quality
battery_add_month
battery_add_year
battery_volt
battery_current
ac_in_aci_f
battery_temp
boiler_ssr1
boiler_ssr2
boiler_ssr3
boiler_manual_mode
Přidány/Refaktorovány nové služby pro ovládání CBB (bojler)
set_boiler_mode (refaktoring)
set_ssr_rele_1
set_ssr_rele_2
set_ssr_rele_3

Přidány nové senzory
battery_quality
battery_add_month
battery_add_year
battery_volt
battery_current
ac_in_aci_f
battery_temp
boiler_ssr1
boiler_ssr2
boiler_ssr3
boiler_manual_mode
Přidány/Refaktorovány nové služby pro ovládání CBB (bojler)
set_boiler_mode (refaktoring)
set_ssr_rele_1
set_ssr_rele_2
set_ssr_rele_3


text:
custom_optimizers and args do not work

Parenthesis in OptimizerFactory Row 129 not correctly set in version 1.2.2.
new Command($this->executable($options['command'], isset($options['args']) ? $options['args'] : array())))
to
new Command($this->executable($options['command']), isset($options['args']) ? $options['args'] : array()))
I try webp optimizing with cwebp.
Here some some option hints:
    'custom_optimizers' => array(
        'webp' => array(
            'command' => 'cwebp',
            'args' => array(
                '-quiet',
                '-m',
                6,
                '-pass',
                10,
                '-mt',
                '-o',
                $outputfile
            )
        )
    )

At the moment, the output option must be defined.
It will be nice to support webp directly.

Thanks for letting know. I've released 1.2.3 with the fix. The newest version (2.0.1) is not affected by this issue.
I will have a look later at webp, but if I add support for this format, it will be only in 2.0.x branch.

Thanks for the fast replay,
at the moment my software runs under php5.6. Only the 1.2.x brunch + custom_optimizers is possible to support webp.

authors: psliwa vitadisplays

repo: psliwa/image-optimizer


text:
Upgraded to work with ruby 3

We had a fork of this, so I figured I'd make some changes to it to work with ruby 3.  This is being used in RMD: https://github.com/psu-libraries/researcher-metadata/pull/485.  We probably don't want to go much longer using this fork though.  We may want to consider moving all our swagger stuff over to rswag (https://github.com/rswag/rswag)

lgtm, I do think a separate ticket to move to rswag might be good for the backlog!

authors: ajkiessl whereismyjetpack

repo: psu-libraries/apivore


text:
500 errors for ResourceController

If something is not a UUID, it should return a 404. Currently, it's throwing a 500 error.
WDLL

/resources/garbargelink.pdf returns 404 and not 500

I can't replicate this locally. It is raising ActiveRecord::RecordNotFound, which is correct. Need to investigate more...

repo: psu-stewardship/scholarsphere