Kubernetes Weave Net Deployment Onto AKS Cluster: Suspect Encryption Not Occuring Between Nodes - Xpost from Slack per request

Hello,
This is regarding my inquiry on Slack.
I am attempting to measure a Kubernetes AKS cluster performance with and without encryption using Weave Net. Originally I followed the Integrating Kubernetes via the Addon instructions and encryption showed enabled. I ran all my tests using the containers I created; these tests included unencrypted, FastDp encryption, and Sleeve encryption. When I plotted the results from the test, all the results are approximately the same so I don't believe encryption was occurring.
I used tcpdump on the VMs to monitor the data, and the testing is not going through the Weave Net ports 6783/6784 (depending on Sleeve or FastDp) and do not appear to be encrypting. When I run weave ps on each VM the containers do not show attached to the exposed weave network; the IPs for the containers deployed using Kubernetes attach to the cluster vnet. I tried attaching the containers and then they are unreachable outside of the host node.
What you expected to happen?
I expected performance to drop due to encryption between the nodes
What happened?

Assume that the data is not routing through Weave network and is not encrypting.
How to reproduce it?

This file contains a good amount of information of how I deploy Weave Net in the cluster along with the weave status. This example is in Sleeve mode. The activity for all nodes port 6783 is included:
terminal-output.txt
Anything else we need to know?

Using Azure Kubernetes Service (ASK) cluster
Created cluster using the basic commands:
az aks create
--resource-group myResourceGroup
--name myAKSCluster
--node-count 3
--enable-addons monitoring
I am launching two simple pods using this configuration:
test-pods.txt
The memory allocation is to ensure the pods go to separate nodes.
Versions:

$ weave version
weave script 2.5.2
weave 2.5.2

$ docker version
Client:
 Version:           3.0.3
 API version:       1.40
 Go version:        go1.11.4
 Git commit:        48bd4c6d
 Built:             Wed Jan 23 16:17:56 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          3.0.4
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.11.4
  Git commit:       8ecd530
  Built:            Fri Jan 25 01:45:38 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.2
  GitCommit:<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce
 runc:
  Version:          1.0.0-rc6+dev
  GitCommit:        96ec2177ae841256168fcf76954f7177af9446eb
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

$ uname -a
Linux aks-nodepool1-52804781-x 4.15.0-1051-azure #56-Ubuntu SMP Thu Jul 4 23:10:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.8", GitCommit:"a89f8c11a5f4f132503edbc4918c98518fd504e3", GitTreeState:"clean", BuildDate:"2019-04-23T04:41:47Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}

Logs:
$ kubectl get pods --all-namespaces -o wide | grep weave
kube-system   weave-net-g8vn5    2/2       Running   0          3h        <IP_ADDRESS>     aks-nodepool1-52804781-0
kube-system   weave-net-ggpm5    2/2       Running   0          3h        <IP_ADDRESS>     aks-nodepool1-52804781-1
kube-system   weave-net-w8mj7    2/2       Running   0          3h        <IP_ADDRESS>     aks-nodepool1-52804781-2

$ kubectl logs -n kube-system weave-net-g8vn5 weave
INFO: 2019/07/30 16:08:50.836510 Command line options: map[db-prefix:/weavedb/weave-net host-root:/host nickname:aks-nodepool1-52804781-0 port:6783 conn-limit:100 expect-npc:true ipalloc-range:<IP_ADDRESS>/12 metrics-addr:<IP_ADDRESS>:6782 docker-api: ipalloc-init:consensus=3 name:56:cb:66:88:4d:72 datapath:datapath no-dns:true no-fastdp:true http-addr:<IP_ADDRESS>:6784]
INFO: 2019/07/30 16:08:50.836601 weave  2.5.2
INFO: 2019/07/30 16:08:50.967258 Bridge type is bridge
INFO: 2019/07/30 16:08:50.967275 Communication between peers via untrusted networks is encrypted.
INFO: 2019/07/30 16:08:51.003303 Our name is 56:cb:66:88:4d:72(aks-nodepool1-52804781-0)
INFO: 2019/07/30 16:08:51.003332 Launch detected - using supplied peer list: [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]
INFO: 2019/07/30 16:08:51.097825 Checking for pre-existing addresses on weave bridge
INFO: 2019/07/30 16:08:51.120849 [allocator 56:cb:66:88:4d:72] No valid persisted data
INFO: 2019/07/30 16:08:51.144033 [allocator 56:cb:66:88:4d:72] Initialising via deferred consensus
INFO: 2019/07/30 16:08:51.144223 Sniffing traffic on vethwe-pcap (via pcap)
INFO: 2019/07/30 16:08:51.199453 Listening for HTTP control messages on <IP_ADDRESS>:6784
INFO: 2019/07/30 16:08:51.199787 Listening for metrics requests on <IP_ADDRESS>:6782
INFO: 2019/07/30 16:08:51.199944 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:51.200049 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:51.200104 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:51.200352 ->[<IP_ADDRESS>:46067] connection accepted
INFO: 2019/07/30 16:08:51.200760 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 :0-><IP_ADDRESS>:6783: connect: connection refused
INFO: 2019/07/30 16:08:51.200913 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 :0-><IP_ADDRESS>:6783: connect: connection refused
INFO: 2019/07/30 16:08:51.201234 ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/07/30 16:08:51.201384 ->[<IP_ADDRESS>:46067|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/07/30 16:08:51.771377 [kube-peers] Added myself to peer list &{[{b2:52:b9:fc:57:2b aks-nodepool1-52804781-2} {56:cb:66:88:4d:72 aks-nodepool1-52804781-0} {7a:7e:3f:46:2f:19 aks-nodepool1-52804781-1}]}
DEBU: 2019/07/30 16:08:51.781384 [kube-peers] Nodes that have disappeared: map[]
INFO: 2019/07/30 16:08:52.242290 ->[<IP_ADDRESS>:45759] connection accepted
INFO: 2019/07/30 16:08:52.243701 ->[<IP_ADDRESS>:45759|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection ready; using protocol version 2
INFO: 2019/07/30 16:08:52.243841 overlay_switch ->[7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)] using sleeve
INFO: 2019/07/30 16:08:52.243969 ->[<IP_ADDRESS>:45759|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection added (new peer)
INFO: 2019/07/30 16:08:52.260557 ->[<IP_ADDRESS>:55893] connection accepted
INFO: 2019/07/30 16:08:52.260897 ->[<IP_ADDRESS>:45759|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection fully established
INFO: 2019/07/30 16:08:52.261079 EMSGSIZE on send, expecting PMTU update (IP packet was 60052 bytes, payload was 60044 bytes)
INFO: 2019/07/30 16:08:52.262369 sleeve ->[<IP_ADDRESS>:6783|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: Effective MTU verified at 1414
INFO: 2019/07/30 16:08:52.263998 ->[<IP_ADDRESS>:55893|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection ready; using protocol version 2
INFO: 2019/07/30 16:08:52.264076 overlay_switch ->[b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)] using sleeve
INFO: 2019/07/30 16:08:52.264093 ->[<IP_ADDRESS>:55893|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection added (new peer)
INFO: 2019/07/30 16:08:52.267203 EMSGSIZE on send, expecting PMTU update (IP packet was 60052 bytes, payload was 60044 bytes)
INFO: 2019/07/30 16:08:52.267290 ->[<IP_ADDRESS>:55893|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection fully established
INFO: 2019/07/30 16:08:52.267752 sleeve ->[<IP_ADDRESS>:6783|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: Effective MTU verified at 1414
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
DEBU: 2019/07/30 16:08:52.447418 registering for updates for node delete events
INFO: 2019/07/30 18:20:59.116327 ->[<IP_ADDRESS>:50296] connection accepted
INFO: 2019/07/30 18:21:02.055728 ->[<IP_ADDRESS>:50296] connection shutting down due to error during handshake: failed to receive remote protocol header: EOF
INFO: 2019/07/30 18:21:04.263151 ->[<IP_ADDRESS>:50338] connection accepted
INFO: 2019/07/30 18:21:05.188089 ->[<IP_ADDRESS>:50338] connection shutting down due to error during handshake: failed to receive remote protocol header: EOF

-------------------------------------------

$ kubectl logs -n kube-system weave-net-ggpm5 weave
DEBU: 2019/07/30 16:08:50.705600 [kube-peers] Checking peer "7a:7e:3f:46:2f:19" against list &{[{b2:52:b9:fc:57:2b aks-nodepool1-52804781-2} {56:cb:66:88:4d:72 aks-nodepool1-52804781-0} {7a:7e:3f:46:2f:19 aks-nodepool1-52804781-1}]}
INFO: 2019/07/30 16:08:50.898208 Command line options: map[datapath:datapath expect-npc:true name:7a:7e:3f:46:2f:19 host-root:/host ipalloc-init:consensus=3 metrics-addr:<IP_ADDRESS>:6782 nickname:aks-nodepool1-52804781-1 no-dns:true no-fastdp:true db-prefix:/weavedb/weave-net http-addr:<IP_ADDRESS>:6784 ipalloc-range:<IP_ADDRESS>/12 conn-limit:100 docker-api: port:6783]
INFO: 2019/07/30 16:08:50.898388 weave  2.5.2
INFO: 2019/07/30 16:08:52.003913 Re-exposing <IP_ADDRESS>/12 on bridge "weave"
INFO: 2019/07/30 16:08:52.025232 Bridge type is bridge
INFO: 2019/07/30 16:08:52.025253 Communication between peers via untrusted networks is encrypted.
INFO: 2019/07/30 16:08:52.069834 Our name is 7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)
INFO: 2019/07/30 16:08:52.069905 Launch detected - using supplied peer list: [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]
INFO: 2019/07/30 16:08:52.174017 Checking for pre-existing addresses on weave bridge
INFO: 2019/07/30 16:08:52.174363 weave bridge has address <IP_ADDRESS>/12
INFO: 2019/07/30 16:08:52.184192 [allocator 7a:7e:3f:46:2f:19] Initialising with persisted data
INFO: 2019/07/30 16:08:52.184333 Sniffing traffic on vethwe-pcap (via pcap)
INFO: 2019/07/30 16:08:52.229551 Listening for HTTP control messages on <IP_ADDRESS>:6784
INFO: 2019/07/30 16:08:52.229785 Listening for metrics requests on <IP_ADDRESS>:6782
INFO: 2019/07/30 16:08:52.240831 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:52.241043 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:52.241128 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:52.241339 ->[<IP_ADDRESS>:55787] connection accepted
INFO: 2019/07/30 16:08:52.242379 ->[<IP_ADDRESS>:6783|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/07/30 16:08:52.242941 ->[<IP_ADDRESS>:55787|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/07/30 16:08:52.243347 ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: connection ready; using protocol version 2
INFO: 2019/07/30 16:08:52.243567 overlay_switch ->[56:cb:66:88:4d:72(aks-nodepool1-52804781-0)] using sleeve
INFO: 2019/07/30 16:08:52.243664 ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: connection added (new peer)
INFO: 2019/07/30 16:08:52.245933 EMSGSIZE on send, expecting PMTU update (IP packet was 60052 bytes, payload was 60044 bytes)
INFO: 2019/07/30 16:08:52.246086 ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: connection fully established
INFO: 2019/07/30 16:08:52.246344 sleeve ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: Effective MTU verified at 1414
INFO: 2019/07/30 16:08:52.260509 ->[<IP_ADDRESS>:6783|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection ready; using protocol version 2
INFO: 2019/07/30 16:08:52.260672 overlay_switch ->[b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)] using sleeve
INFO: 2019/07/30 16:08:52.260693 ->[<IP_ADDRESS>:6783|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection added (new peer)
INFO: 2019/07/30 16:08:52.261823 ->[<IP_ADDRESS>:51349] connection accepted
INFO: 2019/07/30 16:08:52.264297 ->[<IP_ADDRESS>:51349|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection ready; using protocol version 2
INFO: 2019/07/30 16:08:52.264389 overlay_switch ->[b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)] using sleeve
INFO: 2019/07/30 16:08:52.264463 ->[<IP_ADDRESS>:51349|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection shutting down due to error: Multiple connections to b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2) added to 7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)
INFO: 2019/07/30 16:08:52.292231 EMSGSIZE on send, expecting PMTU update (IP packet was 60052 bytes, payload was 60044 bytes)
INFO: 2019/07/30 16:08:52.292407 ->[<IP_ADDRESS>:6783|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection fully established
INFO: 2019/07/30 16:08:52.292661 sleeve ->[<IP_ADDRESS>:6783|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: Effective MTU verified at 1414
INFO: 2019/07/30 16:08:52.332979 Discovered remote MAC 56:cb:66:88:4d:72 at 56:cb:66:88:4d:72(aks-nodepool1-52804781-0)
INFO: 2019/07/30 16:08:52.607060 Discovered remote MAC 26:53:eb:eb:5d:4c at 56:cb:66:88:4d:72(aks-nodepool1-52804781-0)
INFO: 2019/07/30 16:08:52.820559 [kube-peers] Added myself to peer list &{[{b2:52:b9:fc:57:2b aks-nodepool1-52804781-2} {56:cb:66:88:4d:72 aks-nodepool1-52804781-0} {7a:7e:3f:46:2f:19 aks-nodepool1-52804781-1}]}
DEBU: 2019/07/30 16:08:52.839389 [kube-peers] Nodes that have disappeared: map[]
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
DEBU: 2019/07/30 16:08:53.003271 registering for updates for node delete events
INFO: 2019/07/30 18:21:15.432489 ->[<IP_ADDRESS>:35562] connection accepted
INFO: 2019/07/30 18:21:17.069344 ->[<IP_ADDRESS>:35562] connection shutting down due to error during handshake: failed to receive remote protocol header: EOF

-------------------------------------------

$ kubectl logs -n kube-system weave-net-w8mj7 weave
DEBU: 2019/07/30 16:08:50.750623 [kube-peers] Checking peer "b2:52:b9:fc:57:2b" against list &{[{b2:52:b9:fc:57:2b aks-nodepool1-52804781-2} {56:cb:66:88:4d:72 aks-nodepool1-52804781-0} {7a:7e:3f:46:2f:19 aks-nodepool1-52804781-1}]}
INFO: 2019/07/30 16:08:50.924102 Command line options: map[db-prefix:/weavedb/weave-net ipalloc-init:consensus=3 docker-api: expect-npc:true name:b2:52:b9:fc:57:2b conn-limit:100 nickname:aks-nodepool1-52804781-2 metrics-addr:<IP_ADDRESS>:6782 no-dns:true no-fastdp:true port:6783 datapath:datapath host-root:/host http-addr:<IP_ADDRESS>:6784 ipalloc-range:<IP_ADDRESS>/12]
INFO: 2019/07/30 16:08:50.924152 weave  2.5.2
INFO: 2019/07/30 16:08:52.054438 Re-exposing <IP_ADDRESS>/12 on bridge "weave"
INFO: 2019/07/30 16:08:52.076624 Bridge type is bridge
INFO: 2019/07/30 16:08:52.076658 Communication between peers via untrusted networks is encrypted.
INFO: 2019/07/30 16:08:52.119146 Our name is b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)
INFO: 2019/07/30 16:08:52.119189 Launch detected - using supplied peer list: [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]
INFO: 2019/07/30 16:08:52.179896 Checking for pre-existing addresses on weave bridge
INFO: 2019/07/30 16:08:52.181216 weave bridge has address <IP_ADDRESS>/12
INFO: 2019/07/30 16:08:52.195761 [allocator b2:52:b9:fc:57:2b] Initialising with persisted data
INFO: 2019/07/30 16:08:52.195935 Sniffing traffic on vethwe-pcap (via pcap)
INFO: 2019/07/30 16:08:52.252588 Listening for HTTP control messages on <IP_ADDRESS>:6784
INFO: 2019/07/30 16:08:52.253131 Listening for metrics requests on <IP_ADDRESS>:6782
INFO: 2019/07/30 16:08:52.263816 ->[<IP_ADDRESS>:43633] connection accepted
INFO: 2019/07/30 16:08:52.264157 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:52.264359 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:52.264529 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/07/30 16:08:52.265181 ->[<IP_ADDRESS>:43633|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection ready; using protocol version 2
INFO: 2019/07/30 16:08:52.265397 overlay_switch ->[7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)] using sleeve
INFO: 2019/07/30 16:08:52.265543 ->[<IP_ADDRESS>:43633|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection added (new peer)
INFO: 2019/07/30 16:08:52.266955 ->[<IP_ADDRESS>:53749] connection accepted
INFO: 2019/07/30 16:08:52.268033 EMSGSIZE on send, expecting PMTU update (IP packet was 60052 bytes, payload was 60044 bytes)
INFO: 2019/07/30 16:08:52.268189 ->[<IP_ADDRESS>:43633|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection fully established
INFO: 2019/07/30 16:08:52.268470 sleeve ->[<IP_ADDRESS>:6783|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: Effective MTU verified at 1414
INFO: 2019/07/30 16:08:52.268527 ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: connection ready; using protocol version 2
INFO: 2019/07/30 16:08:52.268827 overlay_switch ->[56:cb:66:88:4d:72(aks-nodepool1-52804781-0)] using sleeve
INFO: 2019/07/30 16:08:52.268888 ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: connection added (new peer)
INFO: 2019/07/30 16:08:52.269419 ->[<IP_ADDRESS>:53749|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/07/30 16:08:52.269640 ->[<IP_ADDRESS>:6783|b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/07/30 16:08:52.269879 ->[<IP_ADDRESS>:6783|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection ready; using protocol version 2
INFO: 2019/07/30 16:08:52.270051 overlay_switch ->[7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)] using sleeve
INFO: 2019/07/30 16:08:52.270176 ->[<IP_ADDRESS>:6783|7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1)]: connection shutting down due to error: Multiple connections to 7a:7e:3f:46:2f:19(aks-nodepool1-52804781-1) added to b2:52:b9:fc:57:2b(aks-nodepool1-52804781-2)
INFO: 2019/07/30 16:08:52.270497 EMSGSIZE on send, expecting PMTU update (IP packet was 60052 bytes, payload was 60044 bytes)
INFO: 2019/07/30 16:08:52.270805 ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: connection fully established
INFO: 2019/07/30 16:08:52.272272 sleeve ->[<IP_ADDRESS>:6783|56:cb:66:88:4d:72(aks-nodepool1-52804781-0)]: Effective MTU verified at 1414
INFO: 2019/07/30 16:08:52.337826 Discovered remote MAC 56:cb:66:88:4d:72 at 56:cb:66:88:4d:72(aks-nodepool1-52804781-0)
INFO: 2019/07/30 16:08:52.611951 Discovered remote MAC 26:53:eb:eb:5d:4c at 56:cb:66:88:4d:72(aks-nodepool1-52804781-0)
INFO: 2019/07/30 16:08:52.861366 [kube-peers] Added myself to peer list &{[{b2:52:b9:fc:57:2b aks-nodepool1-52804781-2} {56:cb:66:88:4d:72 aks-nodepool1-52804781-0} {7a:7e:3f:46:2f:19 aks-nodepool1-52804781-1}]}
DEBU: 2019/07/30 16:08:52.871163 [kube-peers] Nodes that have disappeared: map[]
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
DEBU: 2019/07/30 16:08:53.014772 registering for updates for node delete events
INFO: 2019/07/30 18:16:20.698572 ->[<IP_ADDRESS>:55816] connection accepted
INFO: 2019/07/30 18:16:27.993655 ->[<IP_ADDRESS>:55816] connection shutting down due to error during handshake: failed to receive remote protocol header: EOF
INFO: 2019/07/30 18:17:29.633665 ->[<IP_ADDRESS>:56268] connection accepted
INFO: 2019/07/30 18:17:39.634087 ->[<IP_ADDRESS>:56268] connection shutting down due to error during handshake: received incomplete remote protocol header (6 octets instead of 7): [10 116 101 115 116 10]; error: read tcp4 <IP_ADDRESS>:6783-><IP_ADDRESS>:56268: i/o timeout
INFO: 2019/07/30 18:17:51.848974 ->[<IP_ADDRESS>:56428] connection accepted
INFO: 2019/07/30 18:17:53.426623 ->[<IP_ADDRESS>:56428] connection shutting down due to error during handshake: failed to receive remote protocol header: EOF
INFO: 2019/07/30 18:18:14.652123 ->[<IP_ADDRESS>:56580] connection accepted
INFO: 2019/07/30 18:18:16.434132 ->[<IP_ADDRESS>:56580] connection shutting down due to error during handshake: failed to receive remote protocol header: EOF
INFO: 2019/07/30 18:21:09.702413 ->[<IP_ADDRESS>:35404] connection accepted
INFO: 2019/07/30 18:21:10.896978 ->[<IP_ADDRESS>:35404] connection shutting down due to error during handshake: failed to receive remote protocol header: EOF

Network:

$ ip route
# From one of the VMs
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/12 dev weave  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/16 dev eth0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/24 dev cbr0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS> via <IP_ADDRESS> dev eth0
<IP_ADDRESS> via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/16 dev docker0  proto kernel  scope link  src <IP_ADDRESS> linkdown

# From container on that VM
# If I manually do 'weave attach' for the container it shows the ethwe network, but not as default
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/24 dev eth0  proto kernel  scope link  src <IP_ADDRESS>

$ ip -4 -o addr
# From one of the VMs
1: lo    inet <IP_ADDRESS>/8 scope host lo\       valid_lft forever preferred_lft forever
2: eth0    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth0\       valid_lft forever preferred_lft forever
4: docker0    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0\       valid_lft forever preferred_lft forever
10: cbr0    inet <IP_ADDRESS>/24 scope global cbr0\       valid_lft forever preferred_lft forever
41: weave    inet <IP_ADDRESS>/12 brd <IP_ADDRESS> scope global weave\       valid_lft forever preferred_lft forever

$ sudo iptables-save
# From one of the VMs
# Generated by iptables-save v1.6.0 on Tue Jul 30 19:07:40 2019
*filter
:INPUT ACCEPT [154:242683]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [162:30708]
:DOCKER - [0:0]
:DOCKER-ISOLATION-STAGE-1 - [0:0]
:DOCKER-ISOLATION-STAGE-2 - [0:0]
:DOCKER-USER - [0:0]
:KUBE-EXTERNAL-SERVICES - [0:0]
:KUBE-FIREWALL - [0:0]
:KUBE-FORWARD - [0:0]
:KUBE-SERVICES - [0:0]
:WEAVE-NPC - [0:0]
:WEAVE-NPC-DEFAULT - [0:0]
:WEAVE-NPC-EGRESS - [0:0]
:WEAVE-NPC-EGRESS-ACCEPT - [0:0]
:WEAVE-NPC-EGRESS-CUSTOM - [0:0]
:WEAVE-NPC-EGRESS-DEFAULT - [0:0]
:WEAVE-NPC-INGRESS - [0:0]
-A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes externally-visible service portals" -j KUBE-EXTERNAL-SERVICES
-A INPUT -j KUBE-FIREWALL
-A INPUT -i weave -j WEAVE-NPC-EGRESS
-A FORWARD -i weave -m comment --comment "NOTE: this must go before \'-j KUBE-FORWARD\'" -j WEAVE-NPC-EGRESS
-A FORWARD -o weave -m comment --comment "NOTE: this must go before \'-j KUBE-FORWARD\'" -j WEAVE-NPC
-A FORWARD -o weave -m state --state NEW -j NFLOG --nflog-group 86
-A FORWARD -o weave -j DROP
-A FORWARD -i weave ! -o weave -j ACCEPT
-A FORWARD -o weave -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -m comment --comment "kubernetes forwarding rules" -j KUBE-FORWARD
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A OUTPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A OUTPUT -j KUBE-FIREWALL
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN
-A KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
-A KUBE-FORWARD -m comment --comment "kubernetes forwarding rules" -m mark --mark 0x4000/0x4000 -j ACCEPT
-A KUBE-FORWARD -s <IP_ADDRESS>/16 -m comment --comment "kubernetes forwarding conntrack pod source rule" -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A KUBE-FORWARD -d <IP_ADDRESS>/16 -m comment --comment "kubernetes forwarding conntrack pod destination rule" -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A WEAVE-NPC -m state --state RELATED,ESTABLISHED -j ACCEPT
-A WEAVE-NPC -d <IP_ADDRESS>/4 -j ACCEPT
-A WEAVE-NPC -m physdev --physdev-out vethwe-bridge --physdev-is-bridged -j ACCEPT
-A WEAVE-NPC -m state --state NEW -j WEAVE-NPC-DEFAULT
-A WEAVE-NPC -m state --state NEW -j WEAVE-NPC-INGRESS
-A WEAVE-NPC-DEFAULT -m set --match-set weave-Rzff}h:=]JaaJl/G;(XJpGjZ[ dst -m comment --comment "DefaultAllow ingress isolation for namespace: kube-public" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-P.B|!ZhkAr5q=XZ?3}tMBA+0 dst -m comment --comment "DefaultAllow ingress isolation for namespace: kube-system" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-!|3TBtLLt=xOR(J}vJXEQlrws dst -m comment --comment "DefaultAllow ingress isolation for namespace: testperf" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-;rGqyMIl1HN^cfDki~Z$3]6!N dst -m comment --comment "DefaultAllow ingress isolation for namespace: default" -j ACCEPT
-A WEAVE-NPC-EGRESS -m state --state RELATED,ESTABLISHED -j ACCEPT
-A WEAVE-NPC-EGRESS -m physdev --physdev-in vethwe-bridge --physdev-is-bridged -j RETURN
-A WEAVE-NPC-EGRESS -m addrtype --dst-type LOCAL -j RETURN
-A WEAVE-NPC-EGRESS -d <IP_ADDRESS>/4 -j RETURN
-A WEAVE-NPC-EGRESS -m state --state NEW -j WEAVE-NPC-EGRESS-DEFAULT
-A WEAVE-NPC-EGRESS -m state --state NEW -m mark ! --mark 0x40000/0x40000 -j WEAVE-NPC-EGRESS-CUSTOM
-A WEAVE-NPC-EGRESS -m state --state NEW -m mark ! --mark 0x40000/0x40000 -j NFLOG --nflog-group 86
-A WEAVE-NPC-EGRESS -m mark ! --mark 0x40000/0x40000 -j DROP
-A WEAVE-NPC-EGRESS-ACCEPT -j MARK --set-xmark 0x40000/0x40000
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-41s)5vQ^o/xWGz6a20N:~?#|E src -m comment --comment "DefaultAllow egress isolation for namespace: kube-public" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-41s)5vQ^o/xWGz6a20N:~?#|E src -m comment --comment "DefaultAllow egress isolation for namespace: kube-public" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -m comment --comment "DefaultAllow egress isolation for namespace: kube-system" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -m comment --comment "DefaultAllow egress isolation for namespace: kube-system" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-}ZB~iZ6;2|u5m[r}.Ia*;K_Gu src -m comment --comment "DefaultAllow egress isolation for namespace: testperf" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-}ZB~iZ6;2|u5m[r}.Ia*;K_Gu src -m comment --comment "DefaultAllow egress isolation for namespace: testperf" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-s_+ChJId4Uy_$}G;WdH|~TK)I src -m comment --comment "DefaultAllow egress isolation for namespace: default" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-s_+ChJId4Uy_$}G;WdH|~TK)I src -m comment --comment "DefaultAllow egress isolation for namespace: default" -j RETURN
COMMIT
# Completed on Tue Jul 30 19:07:40 2019
# Generated by iptables-save v1.6.0 on Tue Jul 30 19:07:40 2019
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [11:722]
:POSTROUTING ACCEPT [0:0]
:DOCKER - [0:0]
:KUBE-MARK-DROP - [0:0]
:KUBE-MARK-MASQ - [0:0]
:KUBE-NODEPORTS - [0:0]
:KUBE-POSTROUTING - [0:0]
:KUBE-SEP-B4ABR3NA4JKKWXRE - [0:0]
:KUBE-SEP-CAOZVPADEBLUVUHZ - [0:0]
:KUBE-SEP-CET6LPM3WOAFUU5V - [0:0]
:KUBE-SEP-DFG7WZISOSWQK72A - [0:0]
:KUBE-SEP-DNU2VU3I33BHLVVR - [0:0]
:KUBE-SEP-OVZMS5RMXCYJ77AR - [0:0]
:KUBE-SEP-RQJGIMR7APXJ2TJM - [0:0]
:KUBE-SEP-WF67KY7XYO2UQEIZ - [0:0]
:KUBE-SERVICES - [0:0]
:KUBE-SVC-BJM46V3U5RZHCFRZ - [0:0]
:KUBE-SVC-ERIFXISQEP7F7OF4 - [0:0]
:KUBE-SVC-LC5QY66VUV2HJ6WZ - [0:0]
:KUBE-SVC-NPX46M4PTMTKRN6Y - [0:0]
:KUBE-SVC-TCOU7JCQXEZGVUNU - [0:0]
:KUBE-SVC-XGLOHA7QRQ3V22RZ - [0:0]
:WEAVE - [0:0]
-A PREROUTING -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A OUTPUT ! -d <IP_ADDRESS>/8 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -m comment --comment "kubernetes postrouting rules" -j KUBE-POSTROUTING
-A POSTROUTING -s <IP_ADDRESS>/16 ! -o docker0 -j MASQUERADE
-A POSTROUTING ! -d <IP_ADDRESS>/16 -m comment --comment "kubenet: SNAT for outbound traffic from cluster" -m addrtype ! --dst-type LOCAL -j MASQUERADE
-A POSTROUTING -j WEAVE
-A DOCKER -i docker0 -j RETURN
-A KUBE-MARK-DROP -j MARK --set-xmark 0x8000/0x8000
-A KUBE-MARK-MASQ -j MARK --set-xmark 0x4000/0x4000
-A KUBE-POSTROUTING -m comment --comment "kubernetes service traffic requiring SNAT" -m mark --mark 0x4000/0x4000 -j MASQUERADE
-A KUBE-SEP-B4ABR3NA4JKKWXRE -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-B4ABR3NA4JKKWXRE -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:443
-A KUBE-SEP-CAOZVPADEBLUVUHZ -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-CAOZVPADEBLUVUHZ -p udp -m udp -j DNAT --to-destination <IP_ADDRESS>:53
-A KUBE-SEP-CET6LPM3WOAFUU5V -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-CET6LPM3WOAFUU5V -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:53
-A KUBE-SEP-DFG7WZISOSWQK72A -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-DFG7WZISOSWQK72A -p udp -m udp -j DNAT --to-destination <IP_ADDRESS>:53
-A KUBE-SEP-DNU2VU3I33BHLVVR -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-DNU2VU3I33BHLVVR -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:53
-A KUBE-SEP-OVZMS5RMXCYJ77AR -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-OVZMS5RMXCYJ77AR -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:443
-A KUBE-SEP-RQJGIMR7APXJ2TJM -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-RQJGIMR7APXJ2TJM -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:9090
-A KUBE-SEP-WF67KY7XYO2UQEIZ -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-WF67KY7XYO2UQEIZ -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:8082
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "default/kubernetes:https cluster IP" -m tcp --dport 443 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "default/kubernetes:https cluster IP" -m tcp --dport 443 -j KUBE-SVC-NPX46M4PTMTKRN6Y
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/heapster: cluster IP" -m tcp --dport 80 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/heapster: cluster IP" -m tcp --dport 80 -j KUBE-SVC-BJM46V3U5RZHCFRZ
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p udp -m comment --comment "kube-system/kube-dns:dns cluster IP" -m udp --dport 53 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p udp -m comment --comment "kube-system/kube-dns:dns cluster IP" -m udp --dport 53 -j KUBE-SVC-TCOU7JCQXEZGVUNU
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp cluster IP" -m tcp --dport 53 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp cluster IP" -m tcp --dport 53 -j KUBE-SVC-ERIFXISQEP7F7OF4
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/kubernetes-dashboard: cluster IP" -m tcp --dport 80 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/kubernetes-dashboard: cluster IP" -m tcp --dport 80 -j KUBE-SVC-XGLOHA7QRQ3V22RZ
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/metrics-server: cluster IP" -m tcp --dport 443 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/metrics-server: cluster IP" -m tcp --dport 443 -j KUBE-SVC-LC5QY66VUV2HJ6WZ
-A KUBE-SERVICES -m comment --comment "kubernetes service nodeports; NOTE: this must be the last rule in this chain" -m addrtype --dst-type LOCAL -j KUBE-NODEPORTS
-A KUBE-SVC-BJM46V3U5RZHCFRZ -j KUBE-SEP-WF67KY7XYO2UQEIZ
-A KUBE-SVC-ERIFXISQEP7F7OF4 -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-DNU2VU3I33BHLVVR
-A KUBE-SVC-ERIFXISQEP7F7OF4 -j KUBE-SEP-CET6LPM3WOAFUU5V
-A KUBE-SVC-LC5QY66VUV2HJ6WZ -j KUBE-SEP-B4ABR3NA4JKKWXRE
-A KUBE-SVC-NPX46M4PTMTKRN6Y -j KUBE-SEP-OVZMS5RMXCYJ77AR
-A KUBE-SVC-TCOU7JCQXEZGVUNU -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-CAOZVPADEBLUVUHZ
-A KUBE-SVC-TCOU7JCQXEZGVUNU -j KUBE-SEP-DFG7WZISOSWQK72A
-A KUBE-SVC-XGLOHA7QRQ3V22RZ -j KUBE-SEP-RQJGIMR7APXJ2TJM
-A WEAVE -s <IP_ADDRESS>/12 -d <IP_ADDRESS>/4 -j RETURN
-A WEAVE ! -s <IP_ADDRESS>/12 -d <IP_ADDRESS>/12 -j MASQUERADE
-A WEAVE -s <IP_ADDRESS>/12 ! -d <IP_ADDRESS>/12 -j MASQUERADE
COMMIT
# Completed on Tue Jul 30 19:07:40 2019
# Generated by iptables-save v1.6.0 on Tue Jul 30 19:07:40 2019
*security
:INPUT ACCEPT [241464:138432857]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [308112:119898566]
-A OUTPUT -d <IP_ADDRESS>/32 -p tcp -m owner --uid-owner 0 -j ACCEPT
-A OUTPUT -d <IP_ADDRESS>/32 -p tcp -m conntrack --ctstate INVALID,NEW -j DROP
COMMIT
# Completed on Tue Jul 30 19:07:40 2019

Thanks for the detailed problem report.

Using Azure Kubernetes Service (ASK) cluster

I don't know that platform, but managed Kubernetes offerings will come with their own pod network.  Do Azure provide a way to disable their network in favour of Weave Net?
Kubernetes can only use one pod network per cluster, and there is (generally speaking) zero support to remove one and replace with another.

Hi Bryan,
I actually have opened a ticket yesterday with Microsoft to see if they can inform me of any restrictions that may be blocking me and to see if I can get access to configure the Kubelets. The AKS cluster is totally managed by Azure; I will inquire when I hear back from support.
When I was performing the Integrating Kubernetes via the Addon steps and it said that "Weave Net can be installed onto your CNI-enabled Kubernetes cluster" I checked to see if the AKS cluster was CNI-enabled; from what I read in some articles it should be. Anyway, I decided to see if I can check the configuration; I figured out how to read the Kubelet commands that get deployed, and discovered that the --network-plugin command line option shows in the system logs to be set to kubenet instead of cni, and I am expecting this may be an issue. For reference: Kubernetes Network Plugins
This configuration is the last thing I can think of to try since I can not custom build every aspect of the cluster. Hopefully Azure will be able to assist in changing the Kubelets. I'll update when I get some information from Azure. Do you think that the CNI configuration may be the issue?

If AKS supports removing their native networking then configuration would be the issue. But it’s possibke that it just won’t work with a different CNI plugin. I don’t know.

Update: I heard back from Azure, and there is no way to configure the Kubelet(s) other than creating a new cluster. I created a new cluster and passed in the --network-plugin cni parameter to see if that would work; it still defaulted to the --network-plugin="kubenet" according to the system logs. I tested the performance again, and nothing is going through the Weave Net ports. There is not any special configuration that they know of that I can do other than passing in arguments upon cluster creation, and they do not have any reference material on implementing Weave Net with their service.
I am going to have to say that Weave Net is not compatible with AKS at this point in time. Thank you for all your help!

Update: For anyone interested, I was able to get Weave Net to operate within AKS last week. When creating the cluster the argument --network-plugin azure needs to be passed into the az aks create command. This will set the Kubelet configuration to --network-plugin=cni and will point to /etc/cni/net.d on the VMs. Information on setting that up can be found here.
These steps must be done on each VM in the cluster that you want Weave Net to operate on:

SSH into the VM
Install Weave
Navigate to /etc/cni/net.d and inside that directory you will see a configuration file for Azure and one for Weave Net.
Move/remove the Azure config file.
Exit the VM and repeat steps 1-5 on each VM; proceed to step 6 when ready.
Launch Weave Net
When the Weave Net pods are running, delete all user pods/deployments/services using kubectl delete all --all. This will restart the Kubernetes service and anything created afterwards should attach to the Weave Net; use kubectl get pods -o wide to verify they are on the Weave Net subnet.

I was able to run all my performance tests on the containers. This setup is not stable at this time!!! If Weave Net decides to switch from FastDp to Sleeve mode due to unknown routes, it crashes the whole subnet and the containers can not longer communicate. I ran into this issue when performing TCP throughput tests while exponentially increasing the packet size from 1B to 1GiB; it failed at different values that have all been greater than or equal to 1MiB. I only had a successful test when I allocated more RAM to the VM (8GB to 16GB), and it only passed once.
Side note: If deciding to modify the VM resources, make sure to delete the Weave Net Daemonset. I upgraded all the VMs while it was running and then all the AKS managed pods were attaching to the Weave Net. When I had to relaunch Weave Net after the crash, no containers would attach because Weave Net was not running and then they would not when I relaunched Weave Net. I had to create new VMs to attach back to the cluster's network and delete the others.
Hope this helps someone.

@kthompsonpros have you found a CNI encryption scheme that works on AKS?

Sorry, I have not further investigated this. It was a research project I was assigned during an internship.


⚠ Bofrost.fr has degraded performance

In e5ab438, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 868 ms

Resolved: Bofrost.fr performance has improved in 3d60b8e after 13 minutes.


[Bug] SkyWalking Java agent okhttp plugin Wrong url used to create span #8695

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[ ] Update the CHANGES log.

Please fix CI and make sure the plugin tests could verify this case. Also, you should add a full description about what is bug scenario, and why this could fix it.

It is better if you have verified cases in https://github.com/apache/skywalking-java/tree/main/test/plugin/scenarios/okhttp-scenario. And add this unsupported scenario into that cases with new expected spans.

It is better if you have verified cases in https://github.com/apache/skywalking-java/tree/main/test/plugin/scenarios/okhttp-scenario. And add this unsupported scenario into that cases with new expected spans.

This is the sequence diagram of the synchronous call, with the new interceptor in red. You can see that the original interceptor was intercepted twice
这是同步调用的时序图 ,红色部分为这次新增的拦截器 .可以看到原先的是拦截了两次。
Using the chain of responsibility pattern to process requests and allowing the user to customize interceptors allowing the user to rewrite requests interceptors fall into two further categories
okhttp使用责任链模式处理请求。并且允许用户自定义拦截器。允许用户重写重新请求。拦截器又被分为两类。官方说明

I think agent interception should be at least after the user can customize the application of interceptors
我认为agent拦截至少应该在用户可以自定义的应用拦截器之后


LAGGING

OK. Please do not close this because I get what you are saying.
Closing word_counter did half the job.
The other half can't be done.
I did all of your suggestions, none work.
Currently, it is half-lag:
I can control it but response speed is still super slow.
(for the word counter maybe try manual refresh, not auto)
Closing themes didn't work.
Still, I kept it closed just in case.
Any other possibilities?
Add on conflicts?
Mac causing problems?
My disc space?

What is happening?
Lagging
What should be happening?
Shouldn't lag
Operating system/browser name & version:
App version,
notion-enhancer and/or notion-repackaged version:
Newest (0.11.0)
notion-enhancer configuration (enabled/disabled mods and their settings):
I have fontchooser, tray, tabs, view scale, scroll to top, indentation lines, bypass preview, and truncated titles on.

Anyone?

yeah, nothing I can do about this without real or specific diagnosis of the problem (e.g. #87)
¯_(ツ)_/¯
github issues are for reporting specific bugs, not for asking for support with a personal usage issue. reopening/creating similar issues will result in them being closed, because "lag" is not a fixable bug when it doesn't have a known source.

I had the same problem. I disabled each extension one by one until it stopped lagging, I assume you have already tried this but just in case, I recommend doing it, it might be an unexpected extension. For me it ended up being a combination of outliner and word counter. Very unexpected.
Major lag spikes would happen as outliner loaded in and it continued to stutter even after the page was loaded. Disabling one fixed half the lag, disabling the other fixed the other half. It now works as expected. I am on a very different much more beefy system though so your mileage may vary.

I tried with every file and only big files caused problems.
FIX: smaller files.

On Mar 16, 2022, at 4:47 PM, ReiTheMartianCat @.*** @.***>> wrote:
I had the same problem. I disabled each extension one by one until it stopped lagging, I assume you have already tried this but just in case, I recommend doing it, it might be an unexpected extension. For me it ended up being a combination of outliner and word counter. Very unexpected.
Major lag spikes would happen as outliner loaded in and it continued to stutter even after the page was loaded. Disabling one fixed half the lag, disabling the other fixed the other half. It now works as expected. I am on a very different much more beefy system though so your mileage may vary.
—
Reply to this email directly, view it on GitHub https://github.com/notion-enhancer/repo/issues/84#issuecomment-1068875696, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXPVCEYJBTYM4UHE3FDQNX3VAGNYVANCNFSM5PBDVBRQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.


DCP RFC

See the README.md... I'll add a few comments along the way, too.

@yurishkuro awesome comments, thank you! I did a few tiny quick/easy things, but I don't have time right now for the more thoughtful/deep changes, esp around PivotTracing-like ContextIDs, tags, service identification, and so forth.
I will try to get to those before Monday in any case.
Thanks again,
Ben

RFC part two is in a separate PR: https://github.com/opentracing/api-golang/pull/2/files

(Since PR #2 was actually a diff against the changes/rfc branch, that merge has affected this PR (#1), and I will now merge it into master)


Example doesn't work

Report a bug
What did you do?
I downloaded the zip file from GitHub and opened the Segmentio.xcworkspace file inside the Example folder.
What did you expect to happen?
I expected to see the example running in the Simulator.
What happened instead?
An issue appears when compiling and can't run the application. The issue is in the class ExampleViewController.swift, line 95, inside the function: fileprivate func segmentioOptions() -> SegmentioOptions. The error says: "Expression type 'SegmentioOptions' is ambiguous without more context"
Your Environment

[x] Swift version: the one in the example project.
[x] iOS version: last version
[x] Device: simulator
[x] Xcode version: 8.1

Thanks in advance!

Hi
I can load Segmentio from branch issues_fixes with fixes for Segmentio's core and example

Thanks @houze2311 for your fast response! The example works great using that branch!
Best regards!


Fix a broken link to the developer manual

Previous one from https://ydf.readthedocs.io/en/latest/contributing.html led to 404 on Github.

Thank you for this fix, I will merge it ASAP


Does anyone have an example on how to map a simple string into a complex type?

I am trying to map a string to a complex type. A string that represents an account number. The complex type will have a a formatted acc no as provide below.
"account": {
            "id": null,
            "accountNumberFormatted": null
        },

the boundry will eventually become json as above.

If your source/target type can be JObject instead of string,  you can use Json plugin.
Or if you have specific destination type, then you can use MapWith
TypeAdapterConfig<string, ComplexType>.NewConfig()
            .MapWith(str => JsonConvert.DeserializeObject<ComplexType>(str));

But if you would like to map string from/to generic complex type, you might need to create custom adapter. Pls see JsonAdapter as an example.


⚠ T:Riza Api has degraded performance

In 0f9c18e, T:Riza Api (https://infra.triza.dev/api) experienced degraded performance:

HTTP code: 200
Response time: 4296 ms

Resolved: T:Riza Api performance has improved in bdcea03.


SourceDirectory environment variable expansion

Please add an example how to use SourceDirectory with environment variables. Neither $(..), %..% or $.. works.
And please add a list of available environment variables available. I see a ROLEROOT variable but nothing else, I need a source path variable. Thank you

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

ID: 64044dfc-c8af-b5da-8c91-a9eebdc9d1a0
Version Independent ID: f512610d-417b-22a3-a415-9ee57b5fc72f
Content: Azure Cloud Services Def. WebRole Schema
Content Source: articles/cloud-services/schema-csdef-webrole.md
Service: cloud-services
GitHub Login: @jpconnock
Microsoft Alias: jeconnoc

@SeriousM Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

CC @cynthn

Any updates on this issue?

#reassign: @MicahMcKittrick-MSFT

We are currently cleaning up old issues and closing out items that are greater than 90 days old. If an issue is still present, please open a new feedback item on the document so we can prioritize correctly.
#please-close


returning does not work properly with Bulk()

The following code does not return the data from the table. It returns data from the CTE
database.DB.NewUpdate().
		Model(&OrderItem).
		ExcludeColumn("order_id", "created_at").
		Value("updated_at", "CURRENT_TIMESTAMP").
		Bulk().
		Returning("*").
		Exec(ctx)

Instead the following works properly.
database.DB.NewUpdate().
		Model(&OrderItem).
		ExcludeColumn("order_id", "created_at").
		Value("updated_at", "CURRENT_TIMESTAMP").
		Bulk().
		Returning("order_item.*").
		Exec(ctx)

This is not a problem with Bun. Thats how postgres works. Do you think the second solution should be the default behavior for Bun as it makes sense?  Also, time.Time  type is always treated as timestamptz in SQL query. But I want this to be timestamp. How to enforce this behavior?

Do you think the second solution should be the default behavior for Bun as it makes sense?

Perhaps, but Bun does not rewrite the SQL provided by the user because it is too complex and fragile.

Also, time.Time type is always treated as timestamptz in SQL query. But I want this to be timestamp.

You can change the SQL type via tag fields: type:timestamp.

See bulk-update and timestamptz vs timestamp


First pull request attempt: Test.branch

Per instructions from Seth, created a test branch with changes to the Accounts, Jet User Guide and Niagara User Guide files.

Per @elisabethpatterson, this PR is old, and no longer needed.


[BUG] Same issues as #129 using rconfix release

Where bugs related
I am having the same issue as reported in #129
Describe the bug
I have get5 + splewis apistats on the game server and the rcon-fix get5 binary and when attempting to create match I get "2020/06/20 23:16:11 JSON Unmarshal error: invalid character 'L' after top-level value
[GIN] 2020/06/20 - 23:16:11 | 500 |   27.918197ms |    <IP_ADDRESS> | POST     /api/v1/match/create
Error #01: Error reading get5_web_avaliable response"
Screenshots

Desktop (please complete the following information):

Server OS: Centos 8.2.2004
Go version: 1.13.4
Browser: Chrome
Browser Version: 83.0.4103.106

Thanks for the report! are you using latest build(https://github.com/FlowingSPDG/get5-web-go/releases/tag/v0.1.2-rconfix) ?
actually I committed a lot of changes after v0.1.2 so I can't look into it now.
perhaps you may disable SRCDS logs(log off) to suppress logs and let API parse correctly.

Thanks for the reply!

Thanks for the report! are you using latest build(https://github.com/FlowingSPDG/get5-web-go/releases/tag/v0.1.2-rconfix) ?
I am using the latest 0.1.2-rconfix.
actually I committed a lot of changes after v0.1.2 so I can't look into it now.
perhaps you may disable SRCDS logs(log off) to suppress logs and let API parse correctly.
in which config file is this value, I can't seem to find it?

Will be fixed on v0.2.0.


Z-Wave thermostat no longer shows target temperature

Home Assistant release (hass --version):
0.27.0
Python release (python3 --version):
3.4.2
Component/platform:
Climate
Description of problem:
Z-Wave Thermostat (CT 100) no longer shows target temperature (instead displays 'null').  See screenshot.
Expected:
Z-Wave Thermostat should show the temperature as before (<0.27.0).
Problem-relevant configuration.yaml entries and steps to reproduce:
groups:
  thermostat:
    # No longer shows target temperature; is always 'null'.  Still possible to set temperature, I believe.
    - climate.2gig_technologies_ct100_thermostat_usa_cooling_1_4

Add a Z-Wave thermostat to your groups (if needed)
Note that the target temperature displays 'null'

Additional info:

Closing, looks like @turbokongen already fixed it in this commit: https://github.com/home-assistant/home-assistant/commit/17a57d3b47ea9058e2fb0d81e16b50dc28885ef0
Thanks!


Next.js fixes

Fixes Next.js SSR
Fixes Next.js image optimization

Fixes:

https://github.com/firebase/firebase-tools/issues/5977
https://github.com/firebase/firebase-tools/issues/5915
possibly a few other issues exhibiting EADDR* errors and crashes of the node runtime


Prl 2145 legal representation

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRL-2145
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

creating a new PR for testing


New cards variation (layout with 1 large card half screen and 4 smaller cards)

Can be seen on landing pages.

Eg missing on https://main--helix-sportsmagazine--headwirecom.hlx.page/golf-news-tour


Filter continuous values from logbook

Description:
This change filters events events from the logbook generated for continuous values. With weather forecast as an example, a new event is shown in the logbook every 15 minutes. This continuous data is much easier to view in the history line chart, and clutters the logbook view.

I agree with this change. Can you add a unit test to verify that sensors are no longer being reported?

Test is in!

Bueno 🐬


Feature request - Where callback with condition

This code works with Boolean(options.keyword) === true
  const result= await db
    .selectFrom('table')
    .selectAll()
    .where('title', 'is not', null)
    .where(qb => {
      if (options.keyword) {
        return qb
          .orWhere('title', 'like', `%${options.keyword}%`)
          .orWhere('tags', 'like', `%${options.keyword}%`);
      }
      return qb;
    })
    .execute()

The generated SQL is correct.
SELECT *
FROM   `table`
WHERE  `title` IS NOT NULL
       AND ( `title` LIKE "%test%"
              OR `tags` LIKE "%test%" )

But failed with  Boolean(options.keyword) === false, it will raise no where methods called insided a group callback.
So I tried with if() method
  const result = await db
    .selectFrom('table')
    .selectAll()
    .where('title', 'is not', null)
    .if(Boolean(options.keyword), qb =>
      qb
        .orWhere('title', 'like', `%${toSimple(options.keyword)}%`)
        .orWhere('tags', 'like', `%${toSimple(options.keyword)}%`)
    )
    .execute()

But the generated SQL is error
SELECT *
FROM   `table`
WHERE  `title` IS NOT NULL
        OR `title` LIKE "%test%"
        OR `tags` LIKE "%test%"

Can we return undefined in where callback in this situation?

We shouldn't allow undefined to be returned. If we did, forgetting to return the query builder would compile but produce the wrong result. We probably could just remove the error and ignore query builders with no method calls.
But for now, there are multiple ways to fix this:
  const result = await db
    .selectFrom('table')
    .selectAll()
    .where('title', 'is not', null)
    .if(Boolean(options.keyword), qb =>
      qb.where(qb =>
        .orWhere('title', 'like', `%${toSimple(options.keyword)}%`)
        .orWhere('tags', 'like', `%${toSimple(options.keyword)}%`)
    ))
    .execute()

  let qb = db
    .selectFrom('table')
    .selectAll()
    .where('title', 'is not', null)

 if (options.keyword) {
  qb = qb
    .orWhere('title', 'like', `%${toSimple(options.keyword)}%`)
    .orWhere('tags', 'like', `%${toSimple(options.keyword)}%`)
 }

const result = await qb.execute()

Thank you! Or just return qb.where(db.raw('1=1'))

We probably could just remove the error and ignore query builders with no method calls.

Turns out this can't be easily done. It would require too many changes compared to the impact on usability.


How to use goindex on my VPS without cloudflare workers?

According to the author, still not support yet


SimpleForm styles

This gem is the best one I have found so far (and I have tried nearly all similar ones).  However, your styles overwrite simple_form styles...  For example .pwdcalc_simple replaces simple_forms .form-control class.  If I get time Ill fork and try to submit a PR.

That sounds great!


Is there a document about telemetry or health check?

In the config, there is some configuration about health check, but it seem to be no working. Or how can i know if it is healthy or unhealthy ?

cluste health check config is working. if it is configured, mosn will send tcp dial to check whether the upstream host is healthy.
see code in: pkg/upstream/healthcheck


upgrade to latest dependencies (#2964)

bumping knative.dev/pkg c889c5b...2f55fe0:

2f55fe0 Fix potential slowloris attack (# 2682)
8d1efe1 Update community files (# 2683)
4a80605 Add health checks (# 2671)
33e6b88 fix: reconcilerImpl.updateStatus calculates state difference in debug mode only (# 2678)
bumping knative.dev/reconciler-test e459729...e707ddf:
e707ddf upgrade to latest dependencies (# 475)
662cd0d Update community files (# 473)
e906aa6 Allow testing with istio enabled (# 466)

Signed-off-by: Knative Automation<EMAIL_ADDRESS>

/retest

OCF Webhook is merging this PR


Update Posts “goodbye-2023-welcome-2024”

Automatically generated by Netlify CMS

👷 Deploy Preview for shiny-babka-998c7e processing.

Name
Link

🔨 Latest commit
da86ecb6d5e95653bcab71c69ebf50a24d540818

🔍 Latest deploy log
https://app.netlify.com/sites/shiny-babka-998c7e/deploys/659beaaa8791b700085dde47


Self Signed CA Certificate error when connect to rancher server

We have self CA, and when I try to connect to rancher server, I've got an error
➜  ~ rancherssh site
Searching for container site
Failed to communicate with rancher API: Get https://rancho.test.env/v1/containers/?kind=container&name_like=site&state=running: x509: certificate signed by unknown authority

Hi,
I solved this issue on MacOS :

Download certificate from the browser
Open the Keychain Access tool
Import the certificate
Open it and expand the Trust section
Select Always Trust
Retry rancherssh my-container


Account selection for Fox Farming and LPs glitchy when more than two accounts

Overview
If there are more than two Eth accounts, when trying to select a different account in the Fox Farming or ETH/FOX LP, the drop down menu goes glitchy and makes it hard to select an account.
References and additional details

Log into release.shapeshift.com and connect to wallet that supports multi account (testing on Release 1.117.0, PR: https://github.com/shapeshift/web/pull/2481)
In the Accounts page, add 2x ETH accounts
Navigate to Defi page and select the Fox Farming or LP card
Select deposit or withdraw and try to select a different account.
Notice the drop down menu moves around and makes it hard to select a different account.

https://user-images.githubusercontent.com/100157997/196812110-5d77b8ef-5523-4b78-ac24-f6c7576e7b86.mp4
Acceptance Criteria
Accounts should be easy to select from drop down menu
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

@MBMaria this still valid?

This has been fixed now @0xdef1cafe . no longer glitching


Consider support yaml aliases

Some yaml files are organizing as the following, could you please consider to support that ?
Like the followling from the official documentation https://pyyaml.org/wiki/PyYAMLDocumentation
Aliases
Note that PyYAML does not yet support recursive objects.
Using YAML you may represent objects of arbitrary graph-like structures. If you want to refer to the same object from different parts of a document, you need to use anchors and aliases.
Anchors are denoted by the & indicator while aliases are denoted by ``. For instance, the document
left hand: &A
name: The Bastard Sword of Eowyn
weight: 30
right hand: *A
expresses the idea of a hero holding a heavy sword in both hands.
PyYAML now fully supports recursive objects. For instance, the document
&A [ *A ]
will produce a list object containing a reference to itself.

Hi Yablon, can you show a more concrete example of a yaml file that does not work right now with OmegaConf?
I am not sure what you are trying to represent.

@omry Yes, thank you for your reply !
I have 2 yaml files.
test_1.yaml
sample_rate: &SR !!int "4000"
sample_rate_test: *SR

test_2.yaml
sample_rate: &SR !!int "8000"

but when I merge the 2 files using omegaconf,
a = OmegaConf.load('test_1.yaml')
b = OmegaConf.load('test_2.yaml')
c = OmegaConf.merge(a, b)
print(c)

I got this
{'sample_rate': 8000, 'sample_rate_test': 4000}

What I expected is I got all the variables with the same aliases changed.
I think if you support the merge method, it is reasonable to support the above usage.
Thank you!

The problem is that PyYAML resolves the aliases when you load each individual file.
luckily, OmegaConf does support this functionality through interpolations:
file1:
a: 10
b:
   a: 20

file1:
a1 : ${a}
b1 : ${b.a}

c1 = OmegaConf.load('file1.yaml')
c2 = OmegaConf.load('file2.yaml')
c = OmegaConf.merge(a, b)
# will print as is
print(c.pretty())

# will print with values resolved.
print(c.pretty(resolve=True))

@omry That is great !
However, I think maybe I didn't express myself well.
I usually use a yaml config file as an instead of tf.contrib.training.HParams for now.
The yaml config file is usually a little bit complicated, and contains many items.
For simplicity, I usually write two yaml files when training. One is the big yaml config file, the other is a small file that may contain many nodes. When training, I will read the big yaml config file first and the replace the variables in the big file with the variables in the small file.
In that way, my training history is saved with not so many efforts.
But the problem is that, some aliases in the big file, can't changed once for all with the variable in small files. For a long time I  have considered how to resolve this, until I see your awesome omegaconf. That's why I give the examples above.
In the end, I want to replace variables that has aliases all with another value. Is that possilbe with omegaconf ?
By the way, I found lists variables read using omegaconf don't support list operations.
like the following,
a = OmegaConf.load('config.yaml')
b = a.some_list + [1]

will throw an error, can that be fixed ?
Thank you!

Hi Yablon,
Thanks for sharing more context. I am happy to hear you are using OmegaConf for machine learning. it was actually created with a machine learning use case in mind.
Firstly, since you already know about OmegaConf, spend some time going through the documentation of what OmegaConf can do.
I then strongly suggest that you look at Hydra which builds on OmegaConf to make it even more powerful and good to use for complex use cases like ML.
Hydra make it easy to compose configurations with OmegaConf in a way that is most likely powerful enough to do what you need to do.
It also offers other useful features (parameter sweeps, tab completion and more).
Your explanation of the specific problem you are facing is not good enough for me to understand yet. it's best to show with a small example what the problem is.
About your other problem with list: it is a known issue, OmegaConf list is not really a list and primitive list does not like adding itself with it.
You can work around it by doing:
a = OmegaConf.load('config.yaml')
b = OmegaConf.create([1]) + a.some_list

Feel free to ask followup questions. you can also join the chat (see chat link in README for this project), I can answer more questions about both there.

Thank you @omry
Sorry for my low level of English language, what makes you confused.
I write an example like example
Hydra seems to be a big repository, and I will go through it later.

A few notes about your repo:

Stop using yaml anchors with OmegaConf, they do not work well when you combine different configs.
You don't need to declare the type  like max_wav_value: !!float "32768.0",  This would be just fine: max_wav_value: 32768.0

Try something like this (with OmegaConf interpolation):
all_config.yaml:
sampling_rate: 8000.0

feature_extract:
  sample_rate: ${sampling_rate}

train.yaml:
sampling_rate: 16000.0

base = OmegaConf.load("all_config.yaml")
traincfg = OmegaConf.load("train.yaml")
config = OmegaConf.merge(base, traincfg) # first base, then traincfg
print(config.pretty(resolve=True))

This should print something like (I didn't test):
sampling_rate: 16000.0
feature_extract:
  sample_rate: 16000.0

And really, please spend 20 minutes to go through the Hydra tutorial. It will really make your life easier to switch to it.

@omry Thank you for your example, it is very helpful. I will learn Hydra.


Grammar issue in README

"Carl's Introduction to Tokio to the crate."
I believe that the "to the crate" should be removed.

Thanks for the report (and sorry for the huge delay in response). The README has been rewritten since this issue.


feat(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1140

Questions ?
Please refer to the Backport tool documentation


xRDSessionDeployment, xRDServer: fixes

Pull Request (PR) description
Fixes issues found in resources.
This Pull Request (PR) fixes the following issues

Fixes #47
Fixes #50
Task list

[X] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[X] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Hi Johan,
Retry. Again there are more files changed then should be. Problem is that i get presented with untracked or changed files when downloading the xRemoteDesktopSessionHost 'clean' on my machine. Which is very....odd. You can see which ones they are; first commit. When is test other repo's (sqlServerDsc for instance), i have no issues...
Other commits are just a recap of previous work.

@peppekerstens Ah, that's because they were committed with the wrong line encoding, with the .gitattributes file fixes!
@ld0614 since you are a maintainer of this repository, could you possible send in a PR merging in the offending files with the correct line encoding?
Just clone to a new folder and you should see files to stage into a PR.

@peppekerstens btw you haven't done anything wrong. The wrong line encodings were there from the beginning. 🙂

appveyor build faillure seems to be unrelated to the code (time-out due to hang on certificate error) can you  please re-initiate a build?

Now that #57 has been merged, could you try to rebase from the remote's dev branch head and force push to update the PR (and trigger another build)?


what are the commands

i dont understand how you even make it send anything, cant find the commands

The commands are defined here

K, thanks! Thought it was slash commands


GPMDP entry in windows 10 volume mixer is misformatted

Windows 10
Unable to adjust the applications volume in the windows sound mixer panel. Display of the item is cut off and does not display the volume bar. Random clicking in the empty space will eventually let you adjust the invisible slider.
Right click system volume icon, open volume mixer. Find the entry listed as:
Go
Musi
It will have no volume slider. Pic attached.

I can confirm this issue is present for me, On older versions and the newest version.

Did some playing around and was able to get the gpmdp entry to not be the last entry and the display is still incorrect.

This is actually a bug in electron / windows that we are experiencing.  I raised this with electron here https://github.com/atom/electron/issues/4838  and they put the blame firmly on a buggy win32 API.
Not much I can do here but wait for Microsoft or Electron to fix.  Sorry guys.


Support for DPOR

Does P# support DPOR now?
Can you please point me to how I can use it?

Hi Ankush, to enable it you need to pass the /sch:dpor (DPOR) or /sch:rdpor (randomized-DPOR) when invoking the PSharpTester.exe tool.
I think using randomized-DPOR is better, as we found it to perform much better than the purely DFS-based one. Sadly we did not have much time to seriously evaluate these strategies yet (because we run out of time as Paul's internship was finishing), but we think they will be very useful (at least as part of a portfolio of strategies). Any feedback is highly appreciated!
Perhaps @paulthomson can advise more regarding this feature (but I think he is on holidays right now!).

Thanks Pantazis, few more questions.
What is the difference between randomized-dpor and dpor?
Can you please point me to a P# sample where DPOR based search finishes exploring all the executions.
I would like to play around with that sample and would like to then see how DPOR performs for some of the P to P# samples.

I think the main difference between randomized and non-randomized DPOR, is that the randomized DPOR will randomly choose to reverse some races while exploring a program in a DFS manner. Due to the extra bit of randomness, this could lead the scheduler to explore potentially more interesting schedules, whereas the DFS-DPOR might only explore a specific part of the schedule-space or get stack in a loop and not be able to escape (similar to a regular DFS scheduler).
I am not sure if we have a specific sample (besides very trivial programs) were DPOR managed to finish exploring all executions. @paulthomson do you have any sample to suggest?


Without any changes, an error occurred using the seata-server.bat -p 19212 -m file command

seata version 1.1.0
jdk version 13
Without any changes, an error occurred using the seata-server.bat -p 19212 -m file command
[0.003s] [warning] [gc] -Xloggc is deprecated.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit

@cielswift some jvm params not support in high jdk version, please  remove the deprecated param from seata-server.bat  and restart.

手动建个 logs 目录

create logs folder under seata-server

thanks,but why release package contains the floder...


Feature/primitive constant

I finished my work supporting primitive constants. String,Boolean, Integer, Float and Double constants now supported. Hopefully you like my changes.
Changes:

I add a new lexer test suite that allows me to easily check my regular expressions.
addConstant member to ast
adjust parser and lexer

known Issues:

valid floating point values without leading digits (e.g. .45f) are not supported. There is a missmacth with strings like org**.f**ranca.examples. .f is match. I want to improve this later
no type casting in constant expression, e.g. const Float f1 = 123, is invalid syntax. Curently I'm not sure that it makes sense to support a C-like type casting, e.g.
const UInt32 u1 = true --> Value is 1
const Float f1 = 123 --> value is 123.0
const Float f1 =<PHONE_NUMBER>44d  --> forbidden decrease precision????

What is your opinion?

I fix all of the issue. Please could you check my changes again. Thank you


THROTTLED not handled? May be I need to configure RateLimits

Hi, I have read about this great library that RateLimits are "under control".
I am doing a simply test:
do {
    $request = $api->graph($q);
    print_r($request['body']['container']['extensions']['cost']['throttleStatus']);
    echo('
');
    print_r($request['errors']);
    echo('
');
    flush () ;
    ob_flush ();
} while (true);

But after a while, I am getting this ERROR
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 820 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 738 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 663 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 590 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 526 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 454 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 372 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 298 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 230 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 157 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 89 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 17 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 53 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 73 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )

I understand that it will be very difficult to control what is the cost of the query before doing it.
So I have decrease the limit to 5 (even 1), and also 500 (just in case I am thinking the other way round)
I use this
$options->setGraphLimit('5');

And check with
echo 'RATE: ' . $options->getGraphLimit();
echo '
';

In all cases I am getting the same error, sometimes the api gets a THROTTLED error.
What I am doing wrong?
RATE: 1
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 835 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 754 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 685 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 606 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 530 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 459 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 390 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 318 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 236 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 166 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 84 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 8 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 38 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 54 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 76 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 0 [restoreRate] => 50 )

Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 21 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 49 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 76 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 92 [restoreRate] => 50 )
Array ( [0] => Array ( [message] => Throttled [extensions] => Array ( [code] => THROTTLED [documentation] => https://help.shopify.com/api/graphql-admin-api/graphql-admin-api-rate-limits ) ) )
Array ( [maximumAvailable] => 1000 [currentlyAvailable] => 8 [restoreRate] => 50 )

Ah, yes this may be a bug in the lookup of the lastCost, will check into this.

@ortegafernando Update your composer to use dev-master, and give it a try, if all is well now I will release a patch. But in checking, you're right... the graph limits get pushed in as a nested array. My tests we're using a flat array which is why it was not caught.

Hi, I have also found an error in the calculation of sleep.
microtime function returns the time WITH microseconds, and not "IN" microseconds.
currentTime and lastTime are in seconds.
timeDiff is also in seconds, so I don't understand this part:
if ($timeDiff < 1000000 && $lastCost > $pointsEverySecond) {
            // Less than a second has passed and the cost is over the limit
            $td->sleep(1000000 - $timeDiff);
            return true;
        }

May be is this option better?:
        $overCost = $lastCost - ($timeDiff * $pointsEverySecond);
        if ($overCost > 0){
            //lastCost is more than "estimated recovered cost" (time * recover rate) AND leftCost is less than our limit
            $td->sleep($overCost/$pointsEverySecond * 1000000);  //calls usleep($microseconds);
            return true;
        }

I have check it and it seems to be safe not to waste your graphQL points.
What do you think?
NOTE: It could be possible also to define in options a value until it we dont need to begin to sleep. (sorry for my english). I mean something like this: "As we have 1000 points in Shopify, we only begin to sleep when we are above 500 points:"
        ..........

        // Get the last request cost
        /** @var int $lastCost */
        $lastCost = $ls->get($api->getSession());

        $leftCost = isset($lastCost[0]['left']) ? $lastCost[0]['left'] : 0;
        $lastCost = isset($lastCost[0]['actualCost']) ? $lastCost[0]['actualCost'] : 0;

        if ($lastTime === 0 || $lastCost === 0) {
            // This is the first request, nothing to do
            return false;
        }

        // How many points can be spent every second and time difference
        $pointsEverySecond = $api->getOptions()->getGraphLimit();
        $timeDiff = $currentTime - $lastTime;

        $overCost = $lastCost - ($timeDiff * $pointsEverySecond);
        if (($overCost > 0) && $leftCost < 500) {
            //lastCost is more than "estimated recovered cost" (time * recover rate) AND leftCost is less than our limit
            $td->sleep($overCost/$pointsEverySecond * 1000000);  //calls usleep($microseconds);
            return true;
        }
        return false;

I hope your answer and thinking about it, thanks a lot.

@ortegafernando Its designed to be very basic so someone can implement their own. Have configurable limits would be a more inclusive thing I'd leave up to the developer to handle themselves.
However, if you have a fix for the microtime issue and the new calculation there, you're welcome to submit a PR to contribute it :)

What do you thing about this PR?:
https://github.com/osiset/Basic-Shopify-API/pull/91

I think this has been fixed on master. But alas, it was re-published under the same version number which makes updating a real pain. Can you (@osiset) publish master as a new version?

The release wasnt pushed, a patch will go out tomorrow for it

v10.0.2 is out to correct the microtime issue and enable ability to enable/disable internal limiter.

v10.0.2 is out to correct the microtime issue and enable ability to enable/disable internal limiter.

Hi, sorry, but may 10.0.2 version will be published next hours/days ? Just now I can't see it.
Thanks.


Fuel Tanks Plus and Color Coded Canisters feature integration

Both of the mods "Fuel Tanks Plus" and "Color Coded Canisters" now (optionally) cooperate with each other for color-switching. They work independently, but to get the most out of them, they should be installed together. They should probably have a "suggest" or "recommend" rule, in both directions.
Am I right in assuming that "recommend" is stronger than "suggest" (like a default "yes", or something)? If there's a difference between the two, I would probably do this:
FTP "suggests" CCC (for a more consistent art style)
CCC "recommends" FTP (since it has an optional feature that requires FTP)

Am I right in assuming that "recommend" is stronger than "suggest" (like a default "yes", or something)?

Exactly right, recommends are default yes while suggests are default no.

Perfect, thanks.


Disable ExportAPI

Because we are going to constantly change the API surface of this library, we should disable the ExportAPI feature and enable it back closer to GA.
To disable, add <GenerateAPIListing>false</GenerateAPIListing> to https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/tables/Azure.Data.Tables/src/Azure.Data.Tables.csproj
and run eng\scripts\Export-API.ps1
As an example: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/formrecognizer/Azure.AI.FormRecognizer/src/Azure.AI.FormRecognizer.csproj#L8

FYI @meanjeekim


keep getting broken copy

it wont tell me why im getting a broken copy. it just says to delete it and try again or put stuff in the exclusions but i dont know what i should exclude.

When you click the optimize button and it only produces a broken copy it means the optimizer crashed somewhere. There should be some errors in the console if that happens, if you send me what they say I can try to fix it.


Unable to follow complex export blocks

Input code
/** @module myModule */

export {
  default as SomePropName,
  SomeOtherExport1,
  SomeOtherExport2,
} from './someOtherFile'

Expected behavior
I should see SomePropName, SomeOtherExport1 and SomeOtherExport2 (with proper typings) as member of myModule
Current behavior
I see nothing
Your environment

Software
Version

JSDoc
latest

Node.js
latest

npm
latest

Operating system
macOS

I'm also having this struggle, I cannot seem to figure out how to define a named export at all.

@Twipped looking at the state of this repo i'm afraid we're left with no solution. good luck 👌


Exposes timeslot index to agent stat samplers

Agent stat samplers need timeslot index to tell if a data point is the start of jvm life cycle or is the first timeslot when there is not previous data point.
related to #2345

Current coverage is 40.25% (diff: 71.42%)

Merging #2408 into master will increase coverage by <.01%

@@             master      #2408   diff @@
==========================================
  Files          1630       1630
  Lines         57134      57135     +1
  Methods       11109      11109
  Messages          0          0
  Branches       7873       7873
==========================================
+ Hits          22993      22998     +5
+ Misses        34141      34137     -4
  Partials          0          0

Powered by Codecov. Last update 4e4b675...f04cb01


Lizard Spock Game

Description 📜
It's the same as a Rock Paper Scissor game with lizard Spock
Fixes #632

Type of change 📝
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this
[x] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Optional) 📸

https://user-images.githubusercontent.com/73753957/164223704-df87f765-c217-4959-942c-8147662a47bd.mp4

@khushi-purwar Review


Bolt ActionController::API if it is defined

This is something where we should have some tests to ensure the API controller behaves like the traditional controllers with Strongbolt. Do you mind adding a test for that under spec/controllers/?

Yeah, I'm planning to sort it out rails in addition to rails '>= 5.0' support (specs are failed on rails '> 4.2') sometime next week.

My problem reported in issue #33 was resolved when I try solution from PR #37.
My rails-api only (Rails 4.2.x - I'm using rails-api gem) is using strongbolt and it works as described.


fix: axios dependeabot alert

Note: it doesn't appear that we support proxy functionality within botbuilder, so I don't think this is a high priority issue deserving patch releases.

Pull Request Test Coverage Report for Build 463970766

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 84.42%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

libraries/adaptive-expressions/src/triggerTrees/trigger.ts
2
61.63%

Totals

Change from base Build 462134831:
-0.01%

Covered Lines:
17650

Relevant Lines:
19979

💛  - Coveralls

Pull Request Test Coverage Report for Build 463970766

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 84.42%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

libraries/adaptive-expressions/src/triggerTrees/trigger.ts
2
61.63%

Totals

Change from base Build 462134831:
-0.01%

Covered Lines:
17650

Relevant Lines:
19979

💛  - Coveralls

Fixes #3173

Fixes #3173


feat: initial module implementation

Description
Initial module implementation for the Service to Service authorization module.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
module implementation with capability to create service to service authorization policies, cbr rules, and ability to scope those rules to a cbr zone
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

Here are the CRA failures from the previous run, this is only failing due to the COS instance that is provisioned in the example, updated the CRA ignore to skip these as this does not pertain to the module itself.
Ignore rules: []
234 skipped SCC Rules
3 Relevant SCC Rules
2 failed SCC Rules reported & found in Terraform resource(s):
Rule ID rule-8cbd597c-7471-42bd-9c88-36b2696456e9 : Check whether Cloud Object Storage network access is restricted to a specific IP range
	Found in:
		resource_address:module.cos_instance.ibm_cos_bucket.cos_bucket1[0]
Rule ID rule-c97259ee-336d-4c5f-b436-1868107a9558 : Check whether Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)
	Found in:
		resource_address:module.cos_instance.ibm_cos_bucket.cos_bucket1[0]

/run pipeline

/run pipeline

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Updated the three SQLite modules to support short file paths

As it turns out SQLite's connection string doesn't like short file paths (i.e. .\database\db.sqlite).  I made a few small modifications and tested them (with and without Pester) and now I can lazily feed in a database path using .<path>.

Awesome, thanks for adding this!


My npx prisma generate didn't work

Hi, I try to get along with the tutorial and I got stuck when creating a database and generating Prisma Client.

My OS is windows. Any help would be appreciate it!
Thank you!

@tashasyarifah, please see here for the solution:
https://github.com/prisma/prisma/issues/6508#issuecomment-919483693

@Bizzle-Dapp okay thanks for the reference. Gonna check them!


Game aborts if ONE column is full.

The game is aborted when 1 column is full. I will try to fix it by myself, but I don't know if I have time.

Fixed by help from ChatGPT


Node JS version too tightly defined

The nodejs version in package.json is locked to ~4.2.0 which is too tightly coupled when ^4.2.0 should be fine.
Following the installation guidelines on nodejs.org ends up installing 4.4.0 which should be fine.
Locking to 4.2.x makes contributing unnecessarily difficult

Fixed with https://github.com/silverstripe/silverstripe-framework/pull/5180


beeswarm corrupts Explanation object

Reproduction:
import xgboost
import shap

X, y = shap.datasets.boston()
model = xgboost.XGBRegressor().fit(X, y)
explainer = shap.Explainer(model)
shap_values = explainer(X)

First see the valid summary:
shap.summary_plot(shap_values, max_display=10)

Now use beeswarm with truncated list:
shap.plots.beeswarm(shap_values, max_display=2)

Now the summary graph is corrupted:
shap.summary_plot(shap_values, max_display=10)

Notice how the 2nd row (sum of features) corrupted the summary plot ^

I can confirm that beeswarm function changes the shap.values array.

I have also noticed this.  A little debugging shows it's happening in these lines in _beeswarm.py
    # see how many individual (vs. grouped at the end) features we are plotting
    if num_features < len(values[0]):
        num_cut = np.sum([len(orig_inds[feature_order[i]]) for i in range(num_features-1, len(values[0]))])
        values[:,feature_order[num_features-1]] = np.sum([values[:,feature_order[i]] for i in range(num_features-1, len(values[0]))], 0)

A workaround is to use copy.deepcopy(shap_values) before passing them into beeswarm

Closing, also duplicate of #1970


[spring-xsuaa] Configuring the Runtime Environment

Hi,
We are using spring-xsuaa 2.11.5 and we are doing auto wiring for XsuaaServiceConfiguration.
 @Autowired private XsuaaServiceConfiguration xsuaaServiceConfiguration;
We use a CF environment in our production but we are running PR Build and tests on Kubernetes envrionment which contains the setup of CF environment.  And this leads to bean creation failure.
Do we have option to choose/define the environment to be used for configuration ?
Thanks & Regards,
Harishankar D

Hi @harishankard
Auto configuration with XsuaaServiceConfiguration should work in K8s envrionment, in case these preconditions are met:
https://github.com/SAP/cloud-security-xsuaa-integration/blob/main/spring-xsuaa/README.md#mega-service-configuration-in-kuberneteskyma-environment.
Otherwise you may need to overwrite the xsuaaServiceConfiguration bean, have you already tried that?
Kind regards,
Nena

Hi @nenaraab ,
Here in our case this is was working fine with the spring-xsuaa version when it lesser than 2.10. But with recent update we see the XsuaaServicePropertySourceFactory  picks K8 environment and our environment for applications contains VCAP_SERVICES and VCAP_APPLICATIONS in the structure of CF. This leads to error  Cannot verify with online token key, uaadomain is null and results in 401.
Note: We just use k8s to run our CI tests and mimic the CF environment.
Regards,
Harishankar D

Hi @harishankard,
In library the K8s environment is detected by checking, if the environment variable KUBERNETES_SERVICE_HOST exists, so in your case it resolves to K8s environment.
Would it be possible to delete this environment variable in your test container before you run the test?
Kind Regards,
Liga

Closing due to inactivity


No connections via IPv4 under Ubuntu Linux

Expected Behavior
I want to run testrpc on a server and connect to it using IPv4 from my client. Starting it via testrpc should spawn a process that listens on port 8545 for IPv4.
Current Behavior
If I run testrpc the server only listens to port 8545 for the IPv6 protocol. No connection via IPv4 is possible.
Here is the output of netstat -tulpn |grep 8545:
tcp6       0      0 :::8545                :::*                    LISTEN      16568/node
Possible Solution
This could be related to https://github.com/nodejs/node-v0.x-archive/issues/9195
Your Environment

Version used: EthereumJS TestRPC v2.1.0
Server type and version: node v6.2.0, npm 3.8.9
Operating System and version: Ubuntu 14.04 LTS 64 bit

I've added a --hostname parameter which you can use to set the port the server listens on. This is on master, but will go out with the next release. This should solve your issue.
I'm going to close this ticket, but please reopen if it doesn't work for you. Cheers!

Many thanks. That's exactly what I have been looking for.

--port  will override the default 8545 port setting


Switch to lefthook

Ditch Husky in favor of https://github.com/Arkweid/lefthook. In the future we can split the tests more, eg. only run xo when something is changed in js files or prevent the tests from running when .md files are changed.

Maybe we should set it up like you said in this PR? Or you want to tackle this later?

Lefthook doesn't behave like I would expect, looking into that
The failing tests are caused by changes in my package lockfile which I haven't pushed yet

It doesn't seem to work good here.
Even though I modified postcss.js and lint failed, the commit proceeded just fine. Also, it does seem slow like the previous solution.

@XhmikosR, I've split the hooks now. It's also possible to pass a variable to mocha if only a specific style needs to be checked.
Not sure if we should run things in parallel?

Also, it seems something runs twice. This is from my small test:
RUNNING HOOKS GROUP: pre-commit

  EXECUTE > lint-js
(SKIP. NO FILES FOR INSPECTING)

  EXECUTE > lint-less
(SKIP. NO FILES FOR INSPECTING)

  EXECUTE > lint-sass
(SKIP. NO FILES FOR INSPECTING)

  EXECUTE > test-all
(SKIP. NO FILES FOR INSPECTING)

  EXECUTE > test-less
(SKIP. NO FILES FOR INSPECTING)

  EXECUTE > test-postcss
(SKIP. NO FILES FOR INSPECTING)

  EXECUTE > test-sass
(SKIP. NO FILES FOR INSPECTING)

  EXECUTE > test-stylus
(SKIP.  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>xo script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!       Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>xo script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\xmr\AppData\Roaming\npm-cache\_logs\2019-08-06T14_33_16_238Z-debug.log
ERROR: "xo" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>lint: `npm-run-all --parallel xo stylelint`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\xmr\AppData\Roaming\npm-cache\_logs\2019-08-06T14_33_16_387Z-debug.log
npm ERR! Test failed.  See above for more details.
[lefthook 783ddbe] test
 1 file changed, 1 insertion(+)

Success (7984 ms @ 06/08/2019 17:33:16)

Lefthook seemed to slow things down if we're doing changes in different files. Gonna ditch the idea of using git hooks in favor of CircleCI tests.


[#152144657] Fix cred rotation in envs with valid TLS certs

What
In persistent environments, which have valid TLS certificates, having
CF_SKIP_SSL_VALIDATION unset meant that uaac was passed a quoted empty
string as an argument and failed with Too many command line parameters given.
I unquoted the argument to uaac target to avoid this happening.
How to review
Code review. I've run it in my dev env, for what it's worth
Who can review
Anyone but @bleach

:+1: Will merge when Travis is green.

Reviewer race condition 😆


Change root behaviour: relative to current directory if a relative path is defined

Hi there! First of all, thanks for the nice and simple solution! 😄
Now, my use case is that I open a bunch of microservices, each in a folder and run them in development mode.

The situation I have faced is that each developer can have the repository checked out in a different path, so for root we can not use anything. Initially, I configured that as root: . expecting it to work, as itermocil is executed from the repository itself, but itermocil relies on the iTerm behaviour. If the profile is configured to open new tabs in $HOME, it does not work because the . does not point to the repository, just to ., which in that case is the home directory.
I wanted first to discuss the implementation so that if wanted, I could open a PR then.
My proposal is, if root starts with a dot ., make cd move relatively to where itermocil has been invoked, and if it is an absolute path, then just go there.

This is a great idea and is particularly valuable when working in a team.
There are increasingly more monorepo setups where one has to run half a dozen services and these have to be setup at startup time. It's time consuming and error prone.
Would love to be able to use iTermocil in this use case as every repo is at a different location.
As a plus, I feel like this is a great opportunity to grow iTermocil's user base (and perhaps number of contributors!) because it has a viral growth component. If I add it to my team's repo, and it saves everybody a lot of time, the people on the team are all going to end up using iTermocil as well.


New package: XFloats.jl v0.1.0

Registering package: XFloats.jl
Repository: https://github.com/JeffreySarnoff/XFloats.jl
Created by: @JeffreySarnoff
Version: v0.1.0
Commit: 9b479a24d6a0564f4066a4ab6d7180920a9b093c
Reviewed by: @JeffreySarnoff
Reference: https://github.com/JeffreySarnoff/XFloats.jl/commit/9b479a24d6a0564f4066a4ab6d7180920a9b093c#commitcomment-34584164
Release notes:

new package: highly performant and precise small floats

bad .toml entry please delete this in favor of https://github.com/JuliaRegistries/General/pull/2529


pullSecrets added to helm chart

Description
There are some cases that needs pull secrets for getting image from a local restricted registry.
Type of change

[X] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[X] Helm chart template output was checked

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Hi @hbahadorzadeh , once the Contributor License Agreement is completed, i think this PR is good to merge. Will you be able to rebase and respond to CLA? many thanks.

@hbahadorzadeh Since there has been no action on this PR, we'll close.  Please re-open if we need to reconsider.


Introduce Pull Request Reviewers

Introduces a generated set of code owners to ensure a good contribution experience.
For more details/timelines (internal): go/codeowners

@confluentinc/api please take action to review and merge this pull request.
For more details/timelines see: go/codeowners
Note: This pull request and subsequent comments are automatically generated