Scope 0.11.1 doesn't track fastdp connections from weave 1.4

Weave 1.4 includes an intermediate bridge so that conntrack (and in turn Scope) can track connections made in Weave through fast data path ( https://github.com/weaveworks/weave/pull/1712 )
However, the demo in the weave ECS guide doesn't show connections between httpservers and data producers (which happen with weave), only between the internet and httpservers:

Related: https://github.com/weaveworks/weave/issues/1577

I have repeated the original test of the conntrack fix with Scope 0.11.1 and Net 1.4.0:

This test was performed using two Ubuntu 15.04 VMs (3.19.0-23-generic) provisioned from weave/test/Vagrantfile and uses the reproduction script provided in weaveworks/weave#1577.

Thanks @awh.  Just to confirm this is in fact working, could you try with scope launch --probe.conntrack false?
@2opremio pls grab a report if the hosts are still about.

Here's the report: https://gist.github.com/2opremio/e76005d3f8c642f36f05
The machines are running a recent kernel
$ uname -a
Linux ip-172-31-0-11 4.1.13-19.30.amzn1.x86_64 #1 SMP Fri Dec 11 03:42:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

And the intermediate bridges seem to be there:
$ ifconfig | grep vethwe-
vethwe-bridge Link encap:Ethernet  HWaddr FA:D3:F1:17:3D:CD
vethwe-datapath Link encap:Ethernet  HWaddr 2A:20:98:B2:5F:B6

could you try with scope launch --probe.conntrack false?

Well, that confirms that edge was indeed coming from conntrack.

the intermediate bridges seem to be there

Does sudo conntrack -E -p tcp yield expected connection events?

@fons you're containers don't have weave IP address (or mac addresses).  Did you start scope before weave?  Could you post the output of docker logs weavescope please?

Does sudo conntrack -E -p tcp yield expected connection events?

Yep, when repeatedly curl an httpserver container from my machine, this results in connections to the dataproducers. This is reflected by conntrack.
$ weave status dns | grep httpserver
httpserver   <IP_ADDRESS>       d466a21b8789 72:9e:17:8b:87:2b
httpserver   <IP_ADDRESS>       7c3a973f73c0 a6:14:ab:cd:af:6f
httpserver   <IP_ADDRESS>       225bc820b4c0 ce:4d:a8:89:e2:a5
$ weave status dns | grep dataproducer
dataproducer <IP_ADDRESS>       5186a1435fe5 72:9e:17:8b:87:2b
dataproducer <IP_ADDRESS>       f0332ea4cb41 a6:14:ab:cd:af:6f
dataproducer <IP_ADDRESS>       42840fd5d7b6 ce:4d:a8:89:e2:a5
$ sudo yum install conntrack
[...]
$ sudo conntrack -E -p tcp -d <IP_ADDRESS>
    [NEW] tcp      6 120 SYN_SENT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38739 dport=4540 [UNREPLIED] src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38739
 [UPDATE] tcp      6 60 SYN_RECV src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38739 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38739
 [UPDATE] tcp      6 432000 ESTABLISHED src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38739 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38739 [ASSURED]
 [UPDATE] tcp      6 120 FIN_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38739 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38739 [ASSURED]
 [UPDATE] tcp      6 60 CLOSE_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38739 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38739 [ASSURED]
 [UPDATE] tcp      6 30 LAST_ACK src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38739 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38739 [ASSURED]
 [UPDATE] tcp      6 120 TIME_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38739 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38739 [ASSURED]
    [NEW] tcp      6 120 SYN_SENT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38741 dport=4540 [UNREPLIED] src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38741
 [UPDATE] tcp      6 60 SYN_RECV src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38741 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38741
 [UPDATE] tcp      6 432000 ESTABLISHED src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38741 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38741 [ASSURED]
 [UPDATE] tcp      6 120 FIN_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38741 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38741 [ASSURED]
 [UPDATE] tcp      6 30 LAST_ACK src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38741 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38741 [ASSURED]
 [UPDATE] tcp      6 120 TIME_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38741 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38741 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38534 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38534 [ASSURED]
    [NEW] tcp      6 120 SYN_SENT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38747 dport=4540 [UNREPLIED] src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38747
 [UPDATE] tcp      6 60 SYN_RECV src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38747 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38747
 [UPDATE] tcp      6 432000 ESTABLISHED src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38747 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38747 [ASSURED]
 [UPDATE] tcp      6 120 FIN_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38747 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38747 [ASSURED]
 [UPDATE] tcp      6 30 LAST_ACK src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38747 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38747 [ASSURED]
 [UPDATE] tcp      6 120 TIME_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38747 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38747 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38535 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38535 [ASSURED]
^Cconntrack v1.4.0 (conntrack-tools): 21 flow events have been shown.
[ec2-user@ip-172-31-0-11 ~]$ sudo conntrack -E -p tcp -d <IP_ADDRESS>
    [NEW] tcp      6 120 SYN_SENT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38185 dport=4540 [UNREPLIED] src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38185
 [UPDATE] tcp      6 60 SYN_RECV src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38185 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38185
 [UPDATE] tcp      6 432000 ESTABLISHED src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38185 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38185 [ASSURED]
 [UPDATE] tcp      6 120 FIN_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38185 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38185 [ASSURED]
 [UPDATE] tcp      6 60 CLOSE_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38185 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38185 [ASSURED]
 [UPDATE] tcp      6 30 LAST_ACK src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38185 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38185 [ASSURED]
 [UPDATE] tcp      6 120 TIME_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38185 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38185 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=37974 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=37974 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=37976 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=37976 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=37979 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=37979 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=37980 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=37980 [ASSURED]
    [NEW] tcp      6 120 SYN_SENT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38193 dport=4540 [UNREPLIED] src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38193
 [UPDATE] tcp      6 60 SYN_RECV src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38193 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38193
 [UPDATE] tcp      6 432000 ESTABLISHED src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38193 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38193 [ASSURED]
 [UPDATE] tcp      6 120 FIN_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38193 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38193 [ASSURED]
 [UPDATE] tcp      6 60 CLOSE_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38193 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38193 [ASSURED]
 [UPDATE] tcp      6 30 LAST_ACK src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38193 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38193 [ASSURED]
 [UPDATE] tcp      6 120 TIME_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=38193 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=38193 [ASSURED]
^Cconntrack v1.4.0 (conntrack-tools): 18 flow events have been shown.
$ sudo conntrack -E -p tcp -d <IP_ADDRESS>
    [NEW] tcp      6 120 SYN_SENT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44790 dport=4540 [UNREPLIED] src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44790
 [UPDATE] tcp      6 60 SYN_RECV src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44790 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44790
 [UPDATE] tcp      6 432000 ESTABLISHED src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44790 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44790 [ASSURED]
 [UPDATE] tcp      6 120 FIN_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44790 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44790 [ASSURED]
 [UPDATE] tcp      6 60 CLOSE_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44790 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44790 [ASSURED]
 [UPDATE] tcp      6 30 LAST_ACK src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44790 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44790 [ASSURED]
 [UPDATE] tcp      6 120 TIME_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44790 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44790 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44580 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44580 [ASSURED]
    [NEW] tcp      6 120 SYN_SENT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44792 dport=4540 [UNREPLIED] src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44792
 [UPDATE] tcp      6 60 SYN_RECV src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44792 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44792
 [UPDATE] tcp      6 432000 ESTABLISHED src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44792 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44792 [ASSURED]
 [UPDATE] tcp      6 120 FIN_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44792 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44792 [ASSURED]
 [UPDATE] tcp      6 30 LAST_ACK src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44792 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44792 [ASSURED]
 [UPDATE] tcp      6 120 TIME_WAIT src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44792 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44792 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44587 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44587 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44588 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44588 [ASSURED]
[DESTROY] tcp      6 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=44589 dport=4540 src=<IP_ADDRESS> dst=<IP_ADDRESS> sport=4540 dport=44589 [ASSURED]
^Cconntrack v1.4.0 (conntrack-tools): 17 flow events have been shown.

@fons you're containers don't have weave IP address (or mac addresses). Did you start scope before weave? Could you post the output of docker logs weavescope please?

$ docker logs weavescope
<probe> 2015/12/17 16:38:59 probe starting, version 0.11.1, ID 69d328f551512825
<probe> 2015/12/17 16:38:59 publishing to: <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>
<app> 2015/12/17 16:38:59 app starting, version 0.11.1, ID 3fcfc699bb0228df
<app> 2015/12/17 16:38:59 listening on :4040
<probe> 2015/12/17 16:38:59 Error fetching app details: Get http://<IP_ADDRESS>:4040/api: dial tcp <IP_ADDRESS>:4040: getsockopt: connection refused
<probe> 2015/12/17 16:38:59 Control connection to <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:38:59 Error fetching app details: Get http://<IP_ADDRESS>:4040/api: dial tcp <IP_ADDRESS>:4040: getsockopt: connection refused
<probe> 2015/12/17 16:38:59 Error fetching app details: Get http://<IP_ADDRESS>:4040/api: dial tcp <IP_ADDRESS>:4040: getsockopt: connection refused
<probe> 2015/12/17 16:38:59 Publish loop for <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:38:59 docker container: collecting stats for 0115360f10c6a0461482ff022881ed7d0bae0c9be0809d497c5768aa157dcf49
<probe> 2015/12/17 16:38:59 docker container: collecting stats for 96de65f6c7dce265abcd6dd4a6119a054aec4ce315d12819171be94761111404
<probe> 2015/12/17 16:39:03 docker container: collecting stats for 59ffda8847cd80595ba7a85d6d09a86447f8164deaf3f8670a73e886dc5ef24d
<probe> 2015/12/17 16:39:05 docker container: error reading event, did container stop? read unix @->/var/run/docker.sock: use of closed network connection
<probe> 2015/12/17 16:39:05 docker container: stopped collecting stats for 59ffda8847cd80595ba7a85d6d09a86447f8164deaf3f8670a73e886dc5ef24d
<probe> 2015/12/17 16:39:07 docker container: collecting stats for e74e74676f4aec4eafd78cdfffa10534a5fdc95acb5c6902ad81860251968871
<probe> 2015/12/17 16:39:07 docker container: error reading event, did container stop? read unix @->/var/run/docker.sock: use of closed network connection
<probe> 2015/12/17 16:39:07 docker container: stopped collecting stats for e74e74676f4aec4eafd78cdfffa10534a5fdc95acb5c6902ad81860251968871
<probe> 2015/12/17 16:39:09 docker container: collecting stats for 3e6c5c0c2e710136e6719f7d688684216125ba8bccf5f91b783839972fce5f3e
<probe> 2015/12/17 16:39:09 Control connection to <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:39:09 Control connection to <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:39:09 Control connection to <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:39:09 Publish loop for <IP_ADDRESS>:4040 exiting
<probe> 2015/12/17 16:39:09 Closing control connection to <IP_ADDRESS>:4040
<probe> 2015/12/17 16:39:09 Closing control connection to <IP_ADDRESS>:4040
<probe> 2015/12/17 16:39:09 Control connection to <IP_ADDRESS>:4040 exiting
<probe> 2015/12/17 16:39:10 docker container: error reading event, did container stop? read unix @->/var/run/docker.sock: use of closed network connection
<probe> 2015/12/17 16:39:10 docker container: stopped collecting stats for 0115360f10c6a0461482ff022881ed7d0bae0c9be0809d497c5768aa157dcf49
<probe> 2015/12/17 16:39:10 Publish loop for <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:39:10 Publish loop for <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:39:10 Publish loop for <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:39:11 docker container: collecting stats for 702b953bc0bd3c28914637522534cc25568762fc88bb4545a9b484bebb3df94d
<probe> 2015/12/17 16:39:11 docker container: collecting stats for 4216d8e33fbbce4540ed635bde733c4fba1d9d0b9d3af943db3356291fa1f04e
<probe> 2015/12/17 16:39:12 docker container: error reading event, did container stop? read unix @->/var/run/docker.sock: use of closed network connection
<probe> 2015/12/17 16:39:12 docker container: stopped collecting stats for 702b953bc0bd3c28914637522534cc25568762fc88bb4545a9b484bebb3df94d
<probe> 2015/12/17 16:39:16 docker container: collecting stats for acec0ea1014c3e025102a97a163d570298164b3ef76ba6035872cfc957beaa1c
<probe> 2015/12/17 16:39:16 docker container: collecting stats for 4bdaec5aabb5ab1c3a6e53d1eb3e15661737b226a78ecc3127fbe0f6f1b18f73
<probe> 2015/12/17 16:39:16 docker container: error reading event, did container stop? read unix @->/var/run/docker.sock: use of closed network connection
<probe> 2015/12/17 16:39:16 docker container: stopped collecting stats for 4bdaec5aabb5ab1c3a6e53d1eb3e15661737b226a78ecc3127fbe0f6f1b18f73
<probe> 2015/12/17 16:39:47 docker container: collecting stats for 7c3a973f73c0523601e82b8eb87e0d4591e3171351b6523841b960cce5f1c96e
<probe> 2015/12/17 16:39:47 docker container: collecting stats for f0332ea4cb41463bfc615649db74101c4437a6174a0b83405618b689300b0f5e
<probe> 2015/12/17 16:39:48 docker container: collecting stats for d6e6fcdc225feb73639e638157d7835f2ed3db0bdddfbb627e967cd1cfe0351a
<probe> 2015/12/17 16:39:48 docker container: error reading event, did container stop? read unix @->/var/run/docker.sock: use of closed network connection
<probe> 2015/12/17 16:39:48 docker container: stopped collecting stats for d6e6fcdc225feb73639e638157d7835f2ed3db0bdddfbb627e967cd1cfe0351a
<probe> 2015/12/17 16:39:50 docker container: collecting stats for 23936b16209bdb0c4c2391a031ad2e2df420e5d9a5957458eedf4eccd2be9a75
<probe> 2015/12/17 16:39:50 docker container: error reading event, did container stop? read unix @->/var/run/docker.sock: use of closed network connection
<probe> 2015/12/17 16:39:50 docker container: stopped collecting stats for 23936b16209bdb0c4c2391a031ad2e2df420e5d9a5957458eedf4eccd2be9a75
<probe> 2015/12/17 16:49:10 docker container: collecting stats for 250d04ce1763f739bfc88b382d30350881ab821100f0c24c4fa9b3c278e6173f
<probe> 2015/12/17 16:49:10 docker container: stopped collecting stats for 250d04ce1763f739bfc88b382d30350881ab821100f0c24c4fa9b3c278e6173f
<probe> 2015/12/17 16:49:36 docker container: collecting stats for 49a4bd162d6b8e355b9e43a353069976c8dbfc93491db75f55bcc6317566b038
<probe> 2015/12/17 16:49:36 docker container: stopped collecting stats for 49a4bd162d6b8e355b9e43a353069976c8dbfc93491db75f55bcc6317566b038
<probe> 2015/12/17 16:49:43 docker container: collecting stats for 751d059871c5f3457b59c9d0c5e00a38e72fe7204f6473152bb57101ac8d9555
<probe> 2015/12/17 16:49:43 docker container: stopped collecting stats for 751d059871c5f3457b59c9d0c5e00a38e72fe7204f6473152bb57101ac8d9555
<probe> 2015/12/17 16:54:50 docker container: collecting stats for 29caaeb35f3cbf49dc1f48018b024e1233aa0ca6c0b28316361f6a1906c40739
<probe> 2015/12/17 16:54:50 docker container: stopped collecting stats for 29caaeb35f3cbf49dc1f48018b024e1233aa0ca6c0b28316361f6a1906c40739

@fons it should print something like:
vagrant@vagrant-ubuntu-vivid-64:~/src/github.com/weaveworks/scope/experimental/multitenant$ docker logs weavescope
Exposing host to weave network.
<IP_ADDRESS>
Weave container detected at <IP_ADDRESS>, Docker bridge at <IP_ADDRESS>
<probe> 2015/12/17 13:45:42 probe starting, version 1ef6006, ID 344e6a5cec61ea05
<app> 2015/12/17 13:45:42 app starting, version 1ef6006, ID 812c78e5e043398
<probe> 2015/12/17 13:45:42 publishing to: localhost:4040, scope.weave.local:4040
<app> 2015/12/17 13:45:42 listening on :4040

This suggests scope was brought up before weave, or it failed to detect weave in some other way.  @awh you're off the hook.

After rebooting scope, the logs show
$ docker logs weavescope
Exposing host to weave network.
<IP_ADDRESS>
Weave container detected at <IP_ADDRESS>, Docker bridge at <IP_ADDRESS>
<probe> 2015/12/17 16:59:32 probe starting, version 0.11.1, ID 339104be00cc6398
<probe> 2015/12/17 16:59:32 publishing to: <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>
<app> 2015/12/17 16:59:32 app starting, version 0.11.1, ID 4ac02287b14914bf
<app> 2015/12/17 16:59:32 listening on :4040
<probe> 2015/12/17 16:59:32 Control connection to <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:59:32 docker container: collecting stats for ffa24c478e15a515124f6ae79b45a12681de310b3d199a479f12ce2020f32c32
<probe> 2015/12/17 16:59:32 Publish loop for <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:59:32 docker container: collecting stats for 7c3a973f73c0523601e82b8eb87e0d4591e3171351b6523841b960cce5f1c96e
<probe> 2015/12/17 16:59:32 Control connection to <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:59:32 Publish loop for <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:59:32 docker container: collecting stats for f0332ea4cb41463bfc615649db74101c4437a6174a0b83405618b689300b0f5e
<probe> 2015/12/17 16:59:32 Control connection to <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:59:32 docker container: collecting stats for acec0ea1014c3e025102a97a163d570298164b3ef76ba6035872cfc957beaa1c
<probe> 2015/12/17 16:59:32 Publish loop for <IP_ADDRESS>:4040 starting
<probe> 2015/12/17 16:59:32 docker container: collecting stats for 4216d8e33fbbce4540ed635bde733c4fba1d9d0b9d3af943db3356291fa1f04e
<probe> 2015/12/17 16:59:32 docker container: collecting stats for 3e6c5c0c2e710136e6719f7d688684216125ba8bccf5f91b783839972fce5f3e

This seems to suggest that scope now sees the weave network
Exposing host to weave network.
<IP_ADDRESS>
Weave container detected at <IP_ADDRESS>, Docker bridge at <IP_ADDRESS>

Did you start scope before weave?

Scope is guaranteed tot start after Weave due to https://github.com/weaveworks/integrations/blob/master/aws/ecs/packer/to-upload/scope.conf#L19
However, it could be Scope still launches too early, before Scope can recognize the weave network. So this seems another occurrence of https://github.com/weaveworks/scope/issues/510
Now I can see one connection to a dataproducer, but I am still missing two:

Here's the report: https://gist.github.com/2opremio/0086436fb831e82dc562

Pls check the logs on the other two machines contain the "Weave container detected at" line.

You are right after restarting scope in those other two machines, everything works as expected.  This is another instance of #510


[MB-5798] Migration to load zip3_distances data

Description
This PR adds a secure (and local obfuscated) migration for loading zip3-to-zip3 distance data into the zip3_distances table which will be used in pricing.  PR #5432 created the table and related objects.
See the design doc for this work to understand more about the approach taken.
Reviewer Notes

This is a large set of records; is there any way to speed up this load?  It currently takes about 5 seconds locally but YMMV.  I expect that to be a good bit longer when I test this on experimental after initial PR review.

Setup

db_dev_migrate to make sure local migration works fine.
make run_prd_migrations (or replace prd with stg or exp for those environments) to make sure secure migration works fine.
Compare the results in zip3_distances and verify that the real migration reflects the data from the CSV and the obfuscated migration is randomized (see design doc for a link to the data file and details about randomization).

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
Design Doc

Messages

:book:
:link: MB-5798

  Generated by :no_entry_sign: dangerJS against 45cc84d9b49da1e827835be01aa3ec1fcf1e4000

I did some testing and was able to speed up the data load by 50% or so (at least locally) by dropping the indexes and restoring them after the load was done.  Hopefully that helps in the deployed environments too.

Question about maintenance: Is this a table we'll have to keep "up to date"? Just something to think about when this might change?

I don't anticipate that this data set will change very often, but we could have some updates if new zip3s appear or new roads result in a different mileage.  That said, I believe the ultimate goal is to use a web service instead of this static data, so hopefully it's not a problem we'll have to worry about eventually.

As for the time it takes, since we don't have active users using the system, I'm kinda like meh... but if this is something that we need to do in the future, we might want to look at the insert speed/locking.

I spent some time this morning researching/testing ways to speed it up and the big one is to use COPY like we're already doing.  But dropping/recreating the indexes was another one and that helped quite a bit (about 50% locally).  I'm interested to see how long this takes in experimental when I test it (waiting to do that last after getting a couple of reviews).
I think our biggest speed-up overall for migrations is going to be to 1) figure out a way to squash them since we build up a lot of old things that we turn around and tear down, and 2) get rid of some past data loads of performance data if we're allowed to.  If we squash migrations, I'd like to try the drop/restore indexes trick I did here to see how much that helps overall.
Thanks for reviewing!


Interface to change Vertex Properties

Instead of (or, in addition to) the keyboard shortcuts to adjust vertex properties, having an interface to adjust vertex properties could be helpful.
RM Proposed this mockup:

A few things to decide:

Should we remove vertex Property information from the toolbar? It's getting pretty busy up there...

If we did that, we could just render the property information when highlighting a vertex

If you select a vertex by clicking on it, should we present the user with a mouse-driven interface similar to the mockup? OR should it be on hover? Hover might be a pain if there are multiple contol points close together...

Currently starting to think that we might hold off on this till a later version... want to just get 1.2 released.
All this info is currently in the toolbar and can be changed via keyboard shortcuts.
This would be a cool enhancement, but might not get done for 1.2

I'm good with postponing.  Maybe 1.3.
I can update godot asset library with the current modifications this month.
I would like to make an updated video to show off the updates and attach to
the asset library.
On Sun, Mar 8, 2020, 8:17 PM Ryan Lloyd<EMAIL_ADDRESS>wrote:

Currently starting to think that we might hold off on this till a later
version... want to just get 1.2 released.
All this info is currently in the toolbar and can be changed via keyboard
shortcuts.
This would be a cool enhancement, but might not get done for 1.2
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/remorse107/rmsmartshape2d/issues/13?email_source=notifications&email_token=ABY6AUM6LPD3UYFFF6FAQ2LRGRGT5A5CNFSM4LDP5YZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOFH4BY#issuecomment-596278791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABY6AUPGHLJS23Q5PWDAJ3DRGRGT5ANCNFSM4LDP5YZA
.


Cost-Efficient Gradient Boosting (GreedyMiser) for XGBoost

I'm interested in having support for cost-efficient gradient boosting in XGBoost. Glossing over non-essential details, CEBG is the application of a GreedyMiser-like strategy to second-order XGBoost-style optimization. LightGBM has support for this under parameters beginning with "cegb" (see https://lightgbm.readthedocs.io/en/latest/Parameters.html)
To summarize the idea, we maintain a set of indicator variables indicating whether each feature has already been used somewhere in the forest that has been trained. Whenever a new feature that has not yet been used anywhere in the forest is being considered for a split, it has to pay a penalty (that can be specified per-feature, or is the same for all features) that can be seen as lowering the gain of the split. The goal is to nudge the tree towards re-using features it has already used, unless the unused features result in significantly better splits.
The purpose of this feature is to enable the training of models that are parsimonious in terms of how many features they use. In industry, models using thousands of features are not uncommon, but many of the features likely have low importance and could be removed without much impact. Models that use fewer features are cheaper to serve in production and require smaller payloads, reducing networking and data marshaling costs.
There are many ways to do feature selection, including methods that are done independently of the model, but XGBoost itself is a decent feature selection algorithm. Therefore one approach to feature selection can look like this: 1) train an XGBoost model on all features; 2) get the feature importance; 3) train another XGBoost model with only the top K features; 4) check that the new model is not much worse than the model having all the features. However, this feature selection strategy is not ideal, because highly-correlated but important features are likely to all be used during training. With the proposed feature-use penalty, if features A and B are correlated, and only A has been used thus far, then B will only be used if gain(best split of B) > gain(best split of A) + penalty_term. So, training with this feature turns XGBoost into a more powerful feature selector based on a fairly theoretically-sound basis: a feature is admitted when it provides a contribution to reducing loss than cannot be captured by existing features.
I want to get feedback on this idea:

If I were to contribute this change, and it could be done neatly in the code, would it be accepted?
Is there any reason this would be especially difficult to implement? It is straightforward to implement in a naive sequential implementation of XGBoost learning, but I'm not sure if having something like indicator variables would prove difficult in a distributed context.

Thank you for raising the issue and for the very nice summary. I will look into the paper (I think I read it before but couldn't recall).

If I were to contribute this change, and it could be done neatly in the code, would it be accepted?

I think so. Will update this once I go through the paper and see if there's an easy way to do it, at least for one tree method and for one hardware architecture.

Is there any reason this would be especially difficult to implement?

I can't answer that until I fully understand the algorithm.

Just to clarify, the CEGB paper actually implements three kinds of cost penalties:

a penalty for the evaluation time taken to evaluate each tree
a penalty for the first time a feature is used in evaluating a given row
a penalty for the first time a feature is used while constructing a tree

I'm only proposing to implement the last of these three. The first one was designed to trade off tree depth and evaluation speed (but in practice XGBoost inference is pretty fast, so I don't think it's needed), and the second one only makes sense if features are fetched as-needed as a model is being evaluated (only if used in a path that's taken in a tree).
The third one, the penalty for the first time a feature is used in tree construction, should be the simplest and the one I think has the most value, so it is the only one I'm proposing to implement. I figure almost all systems that do inference with XGBoost compute all the features used up-front without attempting to determine which features are strictly needed because they appear on a path that will be taken.


Sw1745 trace check condor ver

Since I was tooling around in condor_ce_trace, I noticed a few things with pylint so decided to fix them.

Looks good to me!


new config for tags

This change enables publishing to bintray via a git tag by adding a new workflow.

Can you explain in the description what this does?

@tylerbrandt done

build


SSL Letsencrypt

Checklist

Please read the setup instructions
Please read the FAQ

What is troubling you?
Clear and concise description of what you're trying to do and what isn't working for you
i have NPM in my vm on proxmox, i  got issue after i change my public ip to new provider, i can't generate new ssl,
it's say "internal server error"
can you help me, sorry for my english

any solution? I am having the same issue


tree not working (Error: Cannot find module 'biojs-io-newick')

Running snippets/tree reports the following exception.
Error: Cannot find module 'biojs-io-newick'

I seem to be able to work around this error by including msa-tnt and biojs-io-newick as regular modules (browserify) rather than the current async msa.g.package.loadPackages. Suggests the problem is down to the loading, not the modules themselves, but I haven't got much further than that.
Note: the correct files do seem to be included:
GET /node_modules/msa-tnt/build/bundle.js - 304 Not Modified - 2.3 MB
GET /node_modules/biojs-io-newick/build/biojs-io-newick.min.js - 304 Not Modified - 6.7 KB

However, it looks like msa-tnt is the full bundle that contains everything (i.e. it includes its own version of msa). At best, it looks like a redundancy that could be made slightly more efficient. At worst, this looks like it could make the universe collapse in a mess of meta-recursion.
Is it better to leave msa-tree as the container/adaptor for the components msa and tnt?

However, it looks like msa-tnt is the full bundle that contains everything (i.e. it includes its own version of msa).

Yep the adapter is horrible.

At worst, this looks like it could make the universe collapse in a mess of meta-recursion.

I agree.

Is it better to leave msa-tree as the container/adaptor for the components msa and tnt?

msa-tnt has historic reasons. David and I tried to find a nice way to combine biojs components which failed because components need to have some common API.
Imho the (best) way to move forward is

to have a small loader that uses the cdn js builds, but can be customized. the logic should be as simple as currently:
try to load async if variables is not there), but allow the user to specify his/her own paths and detect global variables

loadPackage("tnt") -> cdn.bio.sh/tnt/... || ./tnt.js

The tree adapter should be included directly as msa plugin - it can then bootstrap the tree and set events. AFAIK https://github.com/daviddao/exelixis already includes the newick parser, but tnt.tree is the original component and is still maintained and updated. Currently the main problem is that the msa-tnt component has the assumption that it has to construct both components.

msa-tnt has historic reasons. David and I tried to find a nice way to combine biojs components which failed because components need to have some common API.

Thanks - I figured that might be the case. I'm currently working on an app that combines components - I figured I would use this as a template, but sounds like there might be better examples?

David and I tried to find a nice way to combine biojs components which failed because components need to have some common API.

Is it worth choosing a particular MVC framework (e.g. Backbone) and getting people to inherit from a plugin view?
Anyway, ignoring for a moment whether this should be using msa-tnt, the original issue was that the dynamic loading of packages in msa didn't appear to be working ("Error: Cannot find module 'biojs-io-newick'"). Seems that dynamic loading is going to be useful in lots of places - I'm happy to invest time understanding/fixing if this still seems the best way of doing things.

Is it worth choosing a particular MVC framework (e.g. Backbone) and
getting people to inherit from a plugin view?

Yes absolutely. Backbone is probably the easiest, however it has its limitations. I think currently in the msa a) it's quite tricky to see where events come from and b) to extend/overwrite existing views.
That being said - I still want to modularize the msa and imho the best way to go forward is to split it up into multiple web components. You should be able to observe this progress over the next weeks.
Yes dynamic loading is important as we want to ship a slim package that can be extended. I will reply to the color issue later. Sorry that this got lost.
On May 10, 2016 6:06:30 PM GMT+03:00, Ian Sillitoe<EMAIL_ADDRESS>wrote:

msa-tnt has historic reasons. David and I tried to find a nice way to
combine biojs components which failed because components need to have
some common API.

Thanks - I figured that might be the case. I'm currently working on an
app that combines components - I figured I would use this as a
template, but sounds like there might be better examples?

David and I tried to find a nice way to combine biojs components
which failed because components need to have some common API.

Is it worth choosing a particular MVC framework (e.g. Backbone) and
getting people to inherit from a plugin view?
Anyway, ignoring for a moment whether this should be using
msa-tnt, the original issue was that the dynamic loading of
packages in msa didn't appear to be working ("Error: Cannot find
module 'biojs-io-newick'"). Seems that dynamic loading is going to be
useful in lots of places - I'm happy to invest time
understanding/fixing if this still seems the best way of doing things.

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/wilzbach/msa/issues/122#issuecomment-218187105

No problem.
I was going to prepare a separate PR without any mention of d3 - happy to
postpone that until there's a good answer for the dynamic loading.
On 10 May 2016 at 16:58, Sebastian Wilzbach<EMAIL_ADDRESS>wrote:

Is it worth choosing a particular MVC framework (e.g. Backbone) and
getting people to inherit from a plugin view?

Yes absolutely. Backbone is probably the easiest, however it has its
limitations. I think currently in the msa a) it's quite tricky to see where
events come from and b) to extend/overwrite existing views.
That being said - I still want to modularize the msa and imho the best way
to go forward is to split it up into multiple web components. You should be
able to observe this progress over the next weeks.
Yes dynamic loading is important as we want to ship a slim package that
can be extended. I will reply to the color issue later. Sorry that this got
lost.
On May 10, 2016 6:06:30 PM GMT+03:00, Ian Sillitoe <
<EMAIL_ADDRESS>wrote:

msa-tnt has historic reasons. David and I tried to find a nice way to
combine biojs components which failed because components need to have
some common API.

Thanks - I figured that might be the case. I'm currently working on an
app that combines components - I figured I would use this as a
template, but sounds like there might be better examples?

David and I tried to find a nice way to combine biojs components
which failed because components need to have some common API.

Is it worth choosing a particular MVC framework (e.g. Backbone) and
getting people to inherit from a plugin view?
Anyway, ignoring for a moment whether this should be using
msa-tnt, the original issue was that the dynamic loading of
packages in msa didn't appear to be working ("Error: Cannot find
module 'biojs-io-newick'"). Seems that dynamic loading is going to be
useful in lots of places - I'm happy to invest time
understanding/fixing if this still seems the best way of doing things.

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/wilzbach/msa/issues/122#issuecomment-218187105

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/wilzbach/msa/issues/122#issuecomment-218204511

--
Ian Sillitoe | Senior Research Fellow
CATH Manager | www.cathdb.info
University College London | 627 Darwin, Gower Street, WC1E 6BT

related to #150

Should be fixed with #150 - a proper solution however would be only to load tnt and put the msa-tnt adapter code into the msa viewer.


Error when the server send unexpected messages

If an unexpected message is received from the server the controller will stop with the reason {:protocol_violation, {:unexpected_package_from_remote, package}} where package is the unexpected package. The implementer can then log it or do whatever.

Pull Request Test Coverage Report for Build 392

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 86.401%

Totals

Change from base Build 389:
0.1%

Covered Lines:
521

Relevant Lines:
603

💛  - Coveralls


Themes don't update codeblocks, so they look a little blinding in night mode

This doesn't update codeblocks, so they look a little blinding in night mode:

Could we fix that?
Originally posted by @jyn514 in https://github.com/rust-lang/docs.rs/pull/1116#issuecomment-716594541

places with code blocks:

/about/builds: https://docs.rs/about/builds
Source pages: https://docs.rs/crate/libmtp-rs/0.7.1/source/Cargo.toml
Crate readmes: https://docs.rs/crate/lapin/1.4.3


Update oauth2.gemspec

Change the dependency to rack to be less than 3 in order to work with rails 5

There seem to be some PR's open for this already


Unable to see / add peers inside a configuration: TypeError: '<' not supported between instances of 'int' and 'str'

Describe The Problem
Installed the dashboard service on top of an existing wireguard server with multiple peers. I'm unable to see anything inside of the configuration. The log file shows a traceback: TypeError: '<' not supported between instances of 'int' and 'str'
Expected Error / Traceback
Please provide the error traceback here

[22/Jun/2021 20:20:37] "GET /get_config/wg0 HTTP/1.1" 500 -
[2021-06-22 20:20:59,820] ERROR in app: Exception on /get_config/wg0 [GET]
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 2447, in wsgi_app
response = self.full_dispatch_request()
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1952, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1821, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python3.6/site-packages/flask/_compat.py", line 39, in reraise
raise value
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1950, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1936, in dispatch_request
return self.view_functionsrule.endpoint
File "dashboard.py", line 406, in get_conf
"peer_data": get_peers(config_name),
File "dashboard.py", line 186, in get_peers
result = sorted(result, key=lambda d: d['status'])
TypeError: '<' not supported between instances of 'int' and 'str'
To Reproduce
Please provide how you run the dashboard
Home page shows Wg0. When selecting Wg0 returns blank page with navigation on left still visible. Can activate / deactivate the interface.
OS Information:

OS: CentOS Linux release 8.3.2011
Python Version: 3.6.8

Sample of your .conf file
[Interface]
Address = <IP_ADDRESS>/24
SaveConfig = true
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o ens32 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o ens32 -j MASQUERADE
ListenPort = <Listen port>
PrivateKey = <Private Key here>

[Peer]
PublicKey = <Public Key here>
AllowedIPs = <IP_ADDRESS>/32
Endpoint = <Client Generated>

[Peer]
PublicKey = <Public Key here>
AllowedIPs = <IP_ADDRESS>/32
Endpoint = <Client Generated>

[Peer]
PublicKey = <Public Key here>
AllowedIPs = <IP_ADDRESS>/32
Endpoint = <Client Generated>

Please provide a sample of your configuration file that you are having problem with. You can replace your public key and private key to ABCD...

[Account]
username = ABCD
password = ABCD
[Server]
wg_conf_path = /etc/wireguard
app_ip = <IP_ADDRESS>
app_port = 10086
auth_req = true
version = v2.0

Hi! Could you please provide the .json file created under wireguard-dashboard/db please? It seems like the database file is causing the problem. You can remove any private information such as IP address, but please leave the status key unchanged. Thank you!

Thanks for getting back to me!
Here is a sample of the file since we have a lot of peers. The only fields I have changed are ID to protect the public keys and the private IP addresses.
{"_default":      {         "1":          {             "id": "<Peer Public Key>", "name": "", "total_receive": 0, "total_sent": 0, "total_data": 0, "endpoint": "<Peer IP Address>", "status": "stopped", "latest_handshake": "(None)", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "2":          {             "id": "<Peer Public Key>", "name": "", "total_receive": 0, "total_sent": 0, "total_data": 0, "endpoint": "<Peer IP Address>", "status": "stopped", "latest_handshake": "(None)", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "3":          {"             id": "<Peer Public Key>", "name": "", "total_receive": 11.0934, "total_sent": 303.8359, "total_data": 314.9293, "endpoint": "<Peer IP Address>", "status": "stopped", "latest_handshake": "(None)", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "4":          {                "id": "<Peer Public Key>", "name": "", "total_receive": 0, "total_sent": 0, "total_data": 0, "endpoint": "<Peer IP Address>", "status": "stopped", "latest_handshake": "(None)", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "5":          {                "id": "<Peer Public Key>", "name": "", "total_receive": 0, "total_sent": 0, "total_data": 0, "endpoint": "<Peer IP Address>", "status": "stopped", "latest_handshake": "(None)", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "6":          {             "id": "<Peer Public Key>", "name": "", "total_receive": 0.556, "total_sent": 3.1699, "total_data": 3.7259, "endpoint": "<Peer IP Address>", "status": "running", "latest_handshake": "0:00:09", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "7":          {             "id": "<Peer Public Key>", "name": "", "total_receive": 15.4949, "total_sent": 260.1104, "total_data": 275.6053, "endpoint": "<Peer IP Address>", "status": "running", "latest_handshake": "0:01:38", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "8":          {             "id": "<Peer Public Key>", "name": "", "total_receive": 0, "total_sent": 0, "total_data": 0, "endpoint": "<Peer IP Address>", "status": "stopped", "latest_handshake": "(None)", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "9":          {             "id": "<Peer Public Key>", "name": "", "total_receive": 0, "total_sent": 0, "total_data": 0, "endpoint": "<Peer IP Address>", "status": "stopped", "latest_handshake": "(None)", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         },          "10":          {             "id": "<Peer Public Key>", "name": "", "total_receive": 0, "total_sent": 0, "total_data": 0, "endpoint": "(none)", "status": "stopped", "latest_handshake": "(None)", "allowed_ip": "<IP_ADDRESS>/32", "traffic": []         }

Your database file seems normal, if you remove it and restart the dashboard, does it work or is still not working?

Also did you have any content other than wireguard configuration in the .conf file? like comments

Removing it and restarting the dashboard did not work. There is a Post Up and Post Down iptables entry in the conf file for the server. I spun up a test system running Ubuntu 18.04.5 and copied the conf over. I was running into the same issue until I removed the Post Up and Post Down sections. I'm guessing that is it? I changed:
[Interface] Address = <IP_ADDRESS>/24 SaveConfig = true PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o ens32 -j MASQUERADE PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o ens32 -j MASQUERADE ListenPort = <Listen port> PrivateKey = <Private Key here>
to
[Interface] Address = <IP_ADDRESS>/24 SaveConfig = true ListenPort = <Listen port> PrivateKey = <Private Key here>
Deleted the db json file, restarted the dashboard, and toggled the tunnel off then on.

This is weird, because for myself is using post up and down too, but the dashboard is running no problem. and our configuration looks similar. I will look into this problem and will try to fix it. Thank you for telling me this problem!

Thank you for your help!
Quick update, the peers appear while the tunnel is off but while it is active the peers do not load. This on the test system.

would you mind telling me does your current user have privilege to execute wg show?

I'm using the default admin user from the ini file. I haven't modified any permissions whatsoever. Having said that, I removed a bunch of entries from the conf file ~80 down to 3 and now the dashboard is running as expected. Could it be a memory issue? Seemed like the dashboard would get hosed up when I tried to look at the peers.

Hmmmmm that might be an issue, I'm gonna test it on my side since i'm just using it with 10 or less peers

Sounds good, top isn't showing a bunch of utilization but the web page seems to be timing out.

Quick follow up.
The error is not present in the test machine logs. I'm guessing it has to do with the OS or how I setup the other machine.
The web interface works perfectly when the tunnel is not active but begins to become unresponsive when the tunnel is active.
I think this has to do with the larger number of peers our config file has. When reducing the number of peers to under ten the website works as expected.
I'm gonna close the issue out since it has been fixed by changing to the required OS.

Hi! Thank you for replying back, I'm gonna re-open this bug report since is gonna remind me to fix it lol. I'm gonna test on multiple OS and also simulate more peers running and figure out what is going on ;)

Bug fixed on the newest release ;) Running 80+ peers now should be fine, please file another bug report if it is still causing bug in the newest version :)


Swift 3 Compatibility ?

hi there,
is this library compatible with swift 3 && Xcode 8 or need an update ?

Hi @arsanjani it's on my todo list, the update will be hopefully this weekend.

@arsanjani the release is ready: 2.0.0


inner page links don't work on chrome (mobile & windows)

I'm having trouble getting inner page links in the navbar to work in Chrome
(eg.

Foo

)
Works fine in Firefox.  I'm using jQuery/bootstrap.  No error; just nothing happens.

Do you have a link?

Please provide a preview. Impossible for anyone to troubleshoot without it.

Sorry - The page was in a logged in area - not easy to share - and now I've removed the menu; I'm going to try something else.
I assume that inner page links USUALLY work?
Thank you for your time; I'll close this issue.

codepen.com - paste your code there and you can give us preview. I do not believe it will work with anchor links, which I believe is what you are referencing. I say this because Y scroll is disabled when the menu is revealed.

ic.  You may want to mention that.  I did mean anchor links when I said
inner page links.
As I said;they were working in FF.
I think the line of code that I pasted is probably sufficient; if anchor
links are not expected to work.  Good job though; it's one of the best
swipe capable menus I've seen.  Just not quite what I need.
On Sun, Jan 3, 2016 at 8:03 PM Derek Stevenson<EMAIL_ADDRESS>wrote:

codepen.com - paste your code there and you can give us preview. I do not
believe it will work with anchor links, which I believe is what you are
referencing. I say this because Y scroll is disabled when the menu is
revealed.
—
Reply to this email directly or view it on GitHub
https://github.com/Mango/slideout/issues/145#issuecomment-168576175.

@hardlynoticable I have nothing to do with this plugin. I recently started using it and I love how simple and lightweight it is compared to some of the other plugins out there.
Let me test this on my mobile framework and I'll report back with my findings for you.

I just tested and it works just fine in the newest versions of chrome, firefox and microsoft edge.
This is what I used when testing and I made sure to place the anchor at the bottom of the page.

Testing 123

Testing


Support emissive texture and color in default shader

As proposed in the libgdx contributions forum I have implemented support for emissive texture and color in the default shader.
The change is trivial.
A test class was also added (I am not sure about the naming conventions of test classes, if there is any).

Further testing has shown a missing change:
default.vertex.glsl should start with:
#if defined(diffuseTextureFlag) || defined(specularTextureFlag) || defined(emissiveTextureFlag)
#define textureFlag

Unfortunately I do not know whether I can modify this pull request (probably not) or whether I would need to create a new pull request.

You can squash all changes into a single commit following this https://eli.thegreenplace.net/2014/02/19/squashing-github-pull-requests-into-a-single-commit

Looks great, thanks!


julec: fix help function to print formatted string

Description
Fixed incorrect behavior of the help function for julec.

Checklist

[x] A description of the changes in this PR is mentioned above.
[ ] All the new and existing tests pass.
[x] The code follows the code style and conventions of the project.
[x] No plagiarized, duplicated, or repetitive code that has been directly copied from another source.
[x] I have read the whole Contributing Guidelines of the project and its resources/related pages.

Screenshots (if any)

Original
Updated

Note to reviewers

You, as a member, don't have to fork the repo. You should be able to create a branch.


Rename methodtime branch to rc2.0 (release candidate 2.0)

fyi @emilydriano @robynstuart  methodtime has been renamed to rc2.0-methodtime


Revisit mongodb uniqueness constraint on secondary indexes

MongoDB allows us to enforce uniqueness on secondary indexes.
This could helps us in removing some checks from the validation code when using mongodb.
Moreover we would be required to use it on the id depending on how we handle #992

This was already done.
We do have unique indexes for some keys in the backlog and votes collection.


startup script (.bat) file required for windows #1

Closes #1

Creating a new pull request as it referes to incorrect issue


Is there some shorthand for listing multiple language fallback tags?

Hi, is there some similar syntax to Wikidata's "wikibase:language" array parameter, to have multiple language-title fallbacks?
SERVICE wikibase:label { bd:serviceParam wikibase:language "de,en,es,nl". }

My query currently looks like the one below, but I would like to check ~100 language-tag fallbacks (so the output will always show some title for niche/local topics):
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wd: <http://www.wikidata.org/entity/>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX geof: <http://www.opengis.net/def/function/geosparql/>
SELECT ?anything ?name ?dist ?location WHERE {
  ?anything wdt:P625 ?location .
  ?anything rdfs:label ?name .
  FILTER (LANG(?name) = "de") .
  BIND (geof:distance(?location, "POINT(10.85 48.00)") AS ?dist)
  FILTER (?dist <= 101)
}
ORDER BY ASC(?dist)
LIMIT 10

Thanks for the wonderful Qlever project!

@waldenn The standard way to do this in SPARQL is as follows (note that in QLever there is no need for the LIMIT 10, computing the full result is just as efficient):
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wd: <http://www.wikidata.org/entity/>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX geof: <http://www.opengis.net/def/function/geosparql/>
SELECT ?anything ?name ?dist ?location WHERE {
  ?anything wdt:P625 ?location .
  BIND (geof:distance(?location, "POINT(10.85 48.00)") AS ?dist)
  FILTER (?dist <= 101)
  OPTIONAL { ?anything rdfs:label ?name FILTER (LANG(?name) = "de") }
  OPTIONAL { ?anything rdfs:label ?name FILTER (LANG(?name) = "en") }
  OPTIONAL { ?anything rdfs:label ?name FILTER (LANG(?name) = "es") }
  OPTIONAL { ?anything rdfs:label ?name FILTER (LANG(?name) = "nl") }
}
ORDER BY ASC(?dist)

QLever query: https://qlever.cs.uni-freiburg.de/wikidata/2uz4dy
The main reason why Blazegraph has a special SERVICE for names is because a query like the above would take forever with Blazegraph. Of course, the solution with OPTIONAL is not practical when you have very many different fallbacks. However, I wonder how often that is really needed in practice.

Thanks for this! I will create a list of OPTIONALs like that and experiment more with that SPARQL end-point.
I use/need this fallback-title functionality often in my project (https://conze.pt), to always try to show labels for topics. Many (more obscure) entities only have Wikidata labels in a few languages. So when you list those items and only see some Wikidata Qid, it reduces the user experience. Eg. when browsing in English-mode, I would rather see some German-title for the list of topics, than only a Qid.

One thing that I want to add:
a long chain of such optionals would require some time for each query.
If you always have exactly the same order of desired languages for your application one could precompute the chain of optionals and pin it to the cache (The query for the "canonical label" of each entity according to your specified order).
This of course would require either setting up your own QLever instance, or asking us nicely to at least for experimentation purposes do this for you.
Unfortunately we don't have precomputed results that are stored on disk yet, so this would require some RAM.
A query that computes such a result could look like this
Unfortunately we currently cannot compute it, as the initial rdfs:label + DISTINCT takes too much RAM, but we will have someone working on this in the next few months.


r/cloudstack_instance: Add user_data_base64

Allows the use of base64gzip() for large templates (>32k)
Fixes a bug where removal of user_data resulted in an error (user_data too short)

in our provider we accept both under the same key and check base64/gzip if the content looks like cloud-init or multi-part. Using plain text makes it much easier to read/update from it.
https://github.com/exoscale/terraform-provider-exoscale/blob/v0.9.36/exoscale/resource_compute.go#L1001-L1028

Agree, let's keep gzipping out of scope for this one.


Link to Github discussion boards

Can add more links elsewhere in the docs if needed in due course. merging in.


[3.4 RC2] Using NodePath with certain default values shows an error in editor

Godot version
3.4 RC2
System information
Windows 11 x64
Issue description
If you try to use an exported NodePath variable with a default value of "", NodePath("") or NodePath() the editor will throw an error when trying to use a node that uses that variable:

ERROR: (Node not found: "" (relative to "/root/EditorNode/@@592/@@593/@@601/@@603/@@607/@@611/@@612/@@613/@@629/@@630/@@639/@@640/@@6275/@@6109/@@6110/@@6111/@@6112/@@6113/Control/Panel").)
   at: (scene/main/node.cpp:1325)

Is something very similar to when you try to use a node in a tool script.
This error doesn't breaks the editor or the game, but this was working on 3.3
Steps to reproduce

Create a node and attach this script

export(NodePath) var ReferenceNode_path:NodePath = NodePath("") # Fails with "" || NodePath() || NodePath("")

onready var reference_node:Node = get_node(ReferenceNode_path) as Node

func custom_function() -> void:
	reference_node # <- Try using any of its properties after running the game

Minimal reproduction project
Thanks to eons on discord helping me to replicate this issue:
project.zip

I reproduced this error on linux x64 when editor try to suggest autocomplete options.

This error doesn't breaks the editor or the game
It doesn't break, but substantially affects the overall performance of the editor, as in large project I'm working on right now it's flooding the output with this kind of errors. Thanks for the repro steps!

This error doesn't breaks the editor or the game, but this was working on 3.3

Can you check again?
I just tried and I can reproduce the bug, but for me it happens the same in 3.4 RC 2, 3.3.4-stable, 3.3-stable and even 3.2-stable. So it doesn't appear to be a regression.

MRP doesn't trigger ERROR: (Node not found: "" (relative to "/root/EditorNode/@@592/@@593/@@601/@@603/@@607/@@611/@@612/@@613/@@629/@@630/@@639/@@640/@@6275/@@6109/@@6110/@@6111/@@6112/@@6... type of error. Also I don't think that the MRP shows any bug. ERROR: (Node not found: "" (relative to "/root/Node").) is expected behaviour for empty path and I confirm that it happens the same in 3.3.4 and 3.3.3. So maybe my issue is something different as it happens only in 3.4/custom builds from 3.x.

I've bisected what causes my problem and it's this PR https://github.com/godotengine/godot/pull/49491 that triggers "Node not found" errors. It's most probably related to tool scripts in my project, but I don't have the MRP yet.

CC @pycbouh

Sorry, I don't understand what problem is being reported. Like @akien-mga, I can reproduce the problem described in the OP with the attached MPR in both 3.4 RC2 and 3.3 stable.
@Listwon What exactly did you track down to be caused by the aforementioned PR? Can you provide a test project and the steps that only trigger the "Node not found" error in 3.4, but not in 3.3? Because the MRP attached by @AnidemDex triggers the error in either version (and indeed is the expected behavior, I think, like you yourself mention).

The MRP was actually not reproduce the bug that @AnidemDex and @Listwon both seem to experience. The MRP covers only a normal error that happens from misusing the API in a script, while the "bug" here seems to be a misuse of the API in the editor code itself, hence the  relative to "/root/EditorNode/@@592/@@593/@@601/@@603/@@607/@@611/@@612/@@613/@@629/@@630/@@639/@@640/@@6275/@@6109/@@6110/@@6111/@@6112/@@6113/Control/Panel" part.
But indeed we need a way to reproduce the bug to solve it.

here seems to be a misuse of the API in the editor code itself

Probably true, but I've seen such paths reported by the editor before, and well, this MRP does the same in 3.3.

So if there is a regression, something not yet determined is causing it.

Oh I couldn't reproduce this error with the MRP, I only get the script error when running the project, nothing in the editor itself (even when setting them as tool scripts).

I just followed instructions that said to use the reference somehow, so I've added .name, and it throws those messages when trying to come up with auto-complete suggestions.

@pycbouh I'm trying to find it right now and prepare the MRP. What I found so far is that one of the scripts loaded by EditorResourcePicker::_get_allowed_types() (checked with VS debugger) on project loading tries to preload scenes in const Dictionary like this:
const SCENES:Dictionary = {
	"scene1":preload("res://preloaded_scene.tscn")
}

and I get Node not found errors. If I try to open one of those scenes, I'm flooded with cascade of similar errors

This error doesn't breaks the editor or the game, but this was working on 3.3

Can you check again?
I just tried and I can reproduce the bug, but for me it happens the same in 3.4 RC 2, 3.3.4-stable, 3.3-stable and even 3.2-stable. So it doesn't appear to be a regression.

here seems to be a misuse of the API in the editor code itself

Probably true, but I've seen such paths reported by the editor before, and well, this MRP does the same in 3.3.
[an image goes here]
So if there is a regression, something not yet determined is causing it.

Can reproduce on 3.3, wich is... weird. Someone on discord said that wasn't able to reproduce it on 3.3.4. I guess I have to replicate that by myself before opening this issue.
So, have I to close this issue? Modify its title?
Sorry for the problems in advance

So, have I to close this issue? Modify its title?

@AnidemDex I think what you've highlighted is an existing problem, but a problem nonetheless. If the problem you describe is the same as I noticed and it's related to the auto-completion, we can adjust the title/descripting in the OP and keep it open. Unless this is a duplicate.
However, @Listwon's report seems to be about something new. That probably deserves a new issue report so that we can properly track it and hopefully fix for the next 3.4 RC.

@Listwon's issue might be related to daa0977c68faa7b1be3dc3838c07dcdf23cd790e / #52126.

I'm still struggling to prepare the good MRP. It is of course related to NodePath issues, but also to EditorResourcePicker. The thing is - in project with over 600 scripts EditorResourcePicker::_get_allowed_types() loads them to check classes inheritance. One problem is - it's triggered multiple times automatically during project import (probably because of some tileset tool scripts updates in background). So it slows everything down unnecessarily by itself. The next problem is, every time I click on the Node with script attached, there is a hiccup, because it reloads all scripts again. While these scripts (~600) are loaded, they preload scenes and some of them have Viewports. Because of some issue with NodePath or other related issues, there are errors about incorrect NodePath. NodePath is correct on the scene itself, but maybe if it's preloaded from within the script, loaded by EditorResourcePicker::_get_allowed_types() or more precisely EditorNode::get_editor_data().script_class_is_parent(E->get(), base)), it lacks some context?

One problem is - it's triggered multiple times automatically during project import (probably because of some tileset tool scripts updates in background). So it slows everything down unnecessarily by itself.

The results are cached after the first run, so it shouldn't contribute to the slow down when it's the same base types. See https://github.com/godotengine/godot/pull/51211

@AnidemDex Errors with auto-complete are caused by user code. It fails trying to get the reference to the object, because it tries to execute get_node() to get the value from a node path which is in this case invalid. If you use get_node_or_null() instead, there are no more errors. I'm not sure if anything can be changed in the engine to address that, because it fails on executing the code that the user wrote.


Canceled

Issue Id: 46c256b6-02af-58e5-9a53-493a958e2915Versions - 0.10.8Stack Error: Canceled    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/jrieken.vscode-omnisharp/out/omnisharpServer.js:235:31 /vs/base/common/callbackList.ts#L63:26 (CallbackList.invoke)/vs/base/common/event.ts#L107:26 (Emitter.fire)/vs/base/common/cancellation.ts#L42:18 (MutableToken.cancel)/vs/base/common/cancellation.ts#L83:31 (CancellationTokenSource.cancel)    at DiagnosticsProvider._validateProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/jrieken.vscode-omnisharp/out/features/diagnosticsProvider.js:149:37)     at emitOne (events.js:82:20)    at EventEmitter.emit (events.js:169:7)    at StdioOmnisharpServer.OmnisharpServer._fireEvent (/Applications/Visual Studio Code.app/Conten

Should this go to telemetry?

this is tracked on the C# side now


Using TM1py connection, anyway I can see the Context on Pulse/TM1Top

Describe what did you try to do with TM1py
We may have many TM1py scripts running at the same time on the server, at the moment, they are not able to identify the purpose when reading it from TM1Top or Pulse.
Describe what's not working the way you expect
Didn't get the expected result? Describe:

Similar to Arc for TM1, we can pass some description to further describe the action when running scripts via TM1py.

Version

TM1py [1.3.1]
TM1 Server Version: [11.7]

Hi Tat
I have TM1 server version 11.5 on my laptop and I am able to see TM1Py in the session context when running  a script so maybe it is related to TM1 server version 11.7.  I can also confirm at a client I am working on they are able to see this in the context for TM1 server version 11.4.

Hi @jbeanz23,
I think @tatwong wants a custom context that he can set rather a generic one for all TM1Py connections.

Oh, my bad :)

Hi @tatwong,
when you instantiate the TM1Service, you can pass the optional argument session_context with the value that you would like to see in Pulse, TM1top.
here is a sample:
https://github.com/cubewise-code/tm1py-samples/blob/master/Administration/session_custom_context.py


Update devise.zh-CN.yml

连续退出两次会出现翻译缺失：
translation missing: zh-CN.devise.sessions.user.already_signed_out
修改了一下_devise.zh-CN.yml_文件

Current coverage is 95.97%

Merging #608 into master will not affect coverage as of 6dd156d

@@            master    #608   diff @@
======================================
  Files          102     102
  Stmts         4278    4278
  Branches         0       0
  Methods          0       0
======================================
  Hit           4106    4106
  Partial          0       0
  Missed         172     172

Review entire Coverage Diff as of 6dd156d

Powered by Codecov. Updated on successful CI builds.


Add intents.

Hi again,
I notice that music and playlist files are not registered to play under fplay on my system. I.e. when I choose a mp3, ogg, pls, m3u... using the cyanogenmod file browser, under the open with menu fplay is not listed.
This is kind of a rare use case, but it is useful on websites like soma.fm where you are given a pls file, which android just dumps in the Download directory. It would be neat if when clicking the file (or the notification that the file has finished downloading), that the file either opened in fplay or the menu appears asking which app to open in, fplay being an option.
I don't know much about Android development (I've written a total of zero lines of android code to date), but I think you just need to register an intent?
Thanks

Hi Carlos,
I don't know if you have some time to work on FPlay anymore, but if you have, I will really appreciate the same thing vext01 asked for : being able to make FPlay the default player !
Another thing : if you want a french translator, I may help you with pleasure !
Thank you.

Hi Soudain!
Sorry for the delay :cry: I have not received this message in my e-mail, and therefore, I failed to reply to you on time.
Well... As you can see, I already added that feature in version 1.42 :wink:
As for the French translation..... Fantastic!!!! Your help will be really welcome :smile:
Drop me an email!!!
Regards!!!


New version of ReachabilityAnalysis

Failing test:
ERROR: LoadError: LoadError: MethodError: no method matching TMJets21b(; orderT=10, orderQ=2, abs_tol=1.0e-10)

I think this is unrelated.

Codecov Report

Merging #61 (1878a7c) into master (6dbd83a) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #61   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          44      44
  Lines         659     663    +4
======================================
- Misses        659     663    +4

Impacted Files
Coverage Δ

src/utils.jl
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


SP-1155 - Add SonarQube #minor

Codecov Report

Merging #117 (3d4d50a) into main (8e668f9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   53.25%   53.25%
=======================================
  Files           4        4
  Lines         169      169
=======================================
  Hits           90       90
  Misses         67       67
  Partials       12       12

Continue to review full report at Codecov.

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


Issue6

Hello,
Implementing ESLint was strait forward. I matched the configuration file to your indentation style in .eslintrc.json. Only noteworthy thing is the recommended eslint default rule file did not like any console output, so I overwrote that setting to "warn" instead of "error". You will need to do another npm install to get the ESLint module.

@ermarinz Thanks for the contribution


remove unused code from peak files

remove large chunks of unused code from peak files

resolved with commit 57cffbb73fb08daa59de35d1448b87f812f6be27


[BUG] Error trying to run qTsConverter

Describe the bug

Hi, trying to run qTsConverter gives me the following error message:

QQmlApplicationEngine failed to load component
qrc:/main.qml:4:1: plugin cannot be loaded for module "QtQuick.Controls": Cannot protect module QtQuick.Controls 2 as it was never registered

To Reproduce
Steps to reproduce the behavior:

Start qTsConverter

Expected behavior

normally running program :)

Desktop (please complete the following information):

Arch Linux
qTsConverter version: 4.3.4 (problem also occurs with current GIT version)
QT version: 5.15.2

This is probably a wrong config of Qt in your system... I will try on an arch machine :)

Thanks for investigating :) this is a freshly set up system, I didn’t do anything Qt-specific, so maybe it’s related to recent Qt package updates (I used qTsConverter successfully before on another Arch system a few months back).


Missing icon shopping-bag

First of all thank you for your amazing work.
I was looking for shopping-bag icon but i can't found it in Vue2 library

Vue 2 version is no longer maintained.


Make it better

Use some docker!

Hello @dolanor
Docker is a great tool but it's a little bit overkill for a static website no ?

Since I didn't want to have a lot of dev libs on my box to add the bépo layout, I prefered to dev for this project directly in docker.
And I thought others might use it too.
Also, it was a way to try it out on online labs but I had to build it directly there because the automated build didn't work on arm.
 Merci qui ? :shipit:


Update Node modules

Replaced the deprecated gulp-uglifyJS with gulp-uglify, as per the following warning message it was giving out:
npm WARN deprecated<EMAIL_ADDRESS>Since gulp-sourcemaps now works, use gulp-uglify instead
While I was there I also updated Bower as it was also complaining of being a few releases behind and added sourcemaps to the JavaScript compression process.
If this is accepted I'll push it out to the other apps.

:+1:

Sourcemaps: :cool:


Remove phuml

I don't see any references to it here and it prevents me from removing a script in the Aiai-repo.

Should be fine right? @christiansipola


Run Nova action on button click

NovaButton can be a very nice shortcut way to use Nova actions. Instead of selecting a row and selecting an action from the drop-down menu, just click on a NovaButton. So is it possible to run a pre-defined action by clicking a NovaButton?

duplicate https://github.com/dillingham/nova-button/issues/18
I agree but just dont want to flood the markup with a bunch of form fields for each row


chore: Remove Field < and <= support from Brillig

Problem
See convo with Kev:
Essentially it was:
pub enum BinaryFieldOp {
    Add,
    Sub,
    Mul,
    Div,
    Cmp(Comparison),
}
Where we implement comparison for Field operations
In Noir we don't implement < and > for Field operations because technically fields are not ordered

Happy Case
Just a single Equals opcode for BinaryFieldOp. Also refactor Int to be similar (collapse Comparison type)
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
Yes
Support Needs
No response

Closed by https://github.com/noir-lang/acvm/pull/328


Proposed EOF reinstatement.

Precedence: C, C++, Go, and Java all return EOFs as error codes when
the stream ends.  Java includes higher-level APIs that return nulls,
about as close to the current Rust implementation as can be, given the
language differences.
Precedence: Win32 APIs and Windows-based stuff in general tends to
return 'success' and an indicator that it read 0 bytes when such calls
fail.  Well, mostly.  Asynchronous calls are weird, and if you supply
one of the parameters that is commonly null, then Win32's "ReadFile"
will actually start to give you EOFs.
Personally, I have a strong preference for using EOFs a la "the C way"
everywhere.  Rust being sold as a systems programming language makes me
expect this kind of behavior.  Hearing that the IO reforms are trying
to simplify and not implement the union of things between platforms
again implies to me that this will work in the "standard" way.
To be honest, I'm not sure I even like this.  It seems strange that we have
read_to_end and read_to_string, and furthermore that read statically
takes a &mut [u8].  Why don't these methods take an iterator (or is it a
Cursor in this nomenclature?) and the specifics of whether that goes into a
u8 slice or a Vec or a String or a user-implemented-type-T get handled
by the iterator implementation?
Also, side bug fixed: write was returning a uint, but apparently usize is the
new uint.

For what it's worth, the returning of 0 on EOF is similar in style to standard posix apis. Not sure we should really be looking at Win32 as an example of what to do in API design ("Well, mostly." doesn't inspire confidence).
The use of slices is for efficiency purposes, if iterators were used most read impls would need to allocate memory internally, perform a syscall, and then write the data into the provided iterator. At least an extra copy, and potentially quite a bit of iterator overhead.

C's getlineexplicitly returns EOF, which is what spawned the initial confusion and PR motivation.
We probably agree w.r.t. win32; just trying to be thorough.
I guess I would expect that the slice implementation would decay into a pointer under the hood and the implementation would thus get to read directly into it.  If this isn't conceivable, first I'd cry, then I'd agree with you.

Thanks for this RFC!
Note that the method signatures have now all been updated to return usize on success, as suggested here. I think this addresses the most important concern raised by this RFC: there is a now a uniform way to detect and handle EOF throughout new IO. So this RFC has already been partially implemented.
The other proposal of the RFC is to produce a separate notion of EOF error after the first time a zero byte result is returned. This seems problematic for a few reasons:

It means code must be prepared to handle two varieties of EOF-signaling results, which undoes much of the motivation for using a 0 return to signal EOF.

EOF is not always a permanent state, so the contract wouldn't always make sense.

It relies on a somewhat subtle contract, which again was one of the problems we were trying to get away from in old_io.

Note that in particular, with the current IO setup, it works well to use try! to handle "actual" errors, and then look at the byte count to decide whether you're done.
With all of that said, and the signature change already in place, I'm going to close out this RFC. Thanks again for bringing these issues to the community's attention!


Update zsh quickstart and awesome-zsh-plugins entries

Copyright Assignment

[x] This document is covered by the MIT License, and I agree to contribute this PR under the terms of the license.

Things to look out for
Make sure that if your notes field in any additions/updates you make to the YAML files in the _data directory contains any : characters that the entire field is quoted as shown below:
Valid:
foo: "bar: baz"

Invalid:
foo: bar: baz

♥


whoami API query should return user's roles

Schema update: make Organization in the User graphql type nullable
Update whoami resolver and make the organization Optional
Add UI-relevant permissions to the whoami user response

Done!


Disabled json checking on server side.

Fixed method invocation on client side.

Codecov Report

Merging #253 (9895b1d) into dev (e7043be) will increase coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              dev     #253      +/-   ##
==========================================
+ Coverage   11.95%   11.97%   +0.02%
==========================================
  Files         223      223
  Lines        5322     5312      -10
  Branches      878      875       -3
==========================================
  Hits          636      636
+ Misses       4608     4598      -10
  Partials       78       78

Impacted Files
Coverage Δ

...otlin/tools/aqua/bgw/net/client/BoardGameClient.kt
0.00% <0.00%> (ø)

...ools/aqua/bgw/net/server/service/MessageService.kt
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


librdkafka.dylib not found on osx.

Hi,
I've followed the instructions for linux and they wrok perfectly. -adding LD_LIBRARY_PATH...-
Now we have another box running osx and the library are not found:
defining LD_LIBRARY_PATH and osx DYLD_xxxx  variables neither resolves the problem.
when issued brew install librdkafka the version 1.6.0 is installed. Then found and a version error is happening.
Which is the current version of librdkafka used by the extension?
and any suggestion to solve the problem?
Thanks

Hi did you find dll or native library under the bin/runtime directory?

It is because of the mac os runtime protection. https://stackoverflow.com/questions/35568122/why-isnt-dyld-library-path-being-propagated-here.
I tested my mac, in my case, brew upgrade openssl solved the problem. (no need to add DYLD_xxx) I found the workaround on the issue of https://github.com/confluentinc/confluent-kafka-dotnet/issues/778#issuecomment-464129983

@TsuyoshiUshio I'm getting the same issue on the Mac M1.  openssl does not seems to solve this issue. Any workaround?

Hi @rkbalu
I don't have M1 mac, so that I can't test it, however, how about this.
$ brew install librdkafka

@TsuyoshiUshio - Thanks for quick response. But, still failing though! I can see the library under the bin after the build.

Other investigation is  do the command. (adopt the pass that you have the librdkafka.so) and find missing library.
ldd ~/.nuget/packages/librdkafka.redist/0.11.6/runtimes/linux-x64/native/librdkafka.so

It shows the dependency and you might find what is missing.

just adding some info here - as I'm experiencing the same issue.
M1 Mac isnt supported natively by both librdkafka and confluent.kafka
https://github.com/confluentinc/confluent-kafka-dotnet/issues/1707
https://github.com/edenhill/librdkafka/issues/3546

@shrohilla  I am still facing this issue on Apple M1 max.
I have the latest extension bundle installed:
/Users/ankur.gupta/.azure-functions-core-tools/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/4.0.2
&
.Net version is 7

confluentinc/confluent-kafka-dotnet#1707 (comment)

Thanks ! That have worked for me :)


KASAN example

According to https://www.microsoft.com/en-us/security/blog/2023/01/26/introducing-kernel-sanitizers-on-microsoft-platforms/, Kernel AddressSanitizer (KASAN) is available on Windows for kernel-mode. However, there is very limited documentation as to how to use it. It would be nice to have an example detailing the way to build a driver with KASAN support.

In addition to the sample, it would be extremely helpful if the documentation described, specifically, how KASAN differs from/adds to the already existing Driver Verifier (which does very efficient pool overrun checking as well as use-after-free checks) and stack overrun checking.
Why would a KM dev want to use KASAN if I already have Verifier enabled?  Can they co-exist? Do they interact? What are the costs/benefits/tradeoffs.

Huge shoutout to @JohnMcSandwich for making the KASAN scenario work for 3rd party device drivers and even providing a sample.
To provide a high-level answer to Peter's question:

DV and KASAN are complimentary.
DV is "lightweight" (as you do not need to special compile) whereas KASAN requires a special compilation
DV can only "see" what goes on "on the edge" of the driver whereas KASAN can intercept "inside" of a driver.  (Exception to this: DV does have special treatment of memory manager / IRQL style checks where we bug check based on page violations rather than based on the specific bug in the driver itself (so bugcheck based on a symptom rather than necessarily at the immediate point of failure).
DV has tons of driver specific rules.  KASAN is focused on generic memory checks.

I know what you really want is a more comprehensive and data driven answer. I don't have that.
I bet there are many other angles, but that's my 2 cents...
Jakob
References:

https://www.microsoft.com/en-us/security/blog/2023/01/26/introducing-kernel-sanitizers-on-microsoft-platforms/
https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/kasan
https://github.com/microsoft/Windows-driver-samples/blob/main/tools/kasan/samples/KasanDemo-WDM/README.md


Put a check indicator on View -> Toggle Word Wrap

Issue Type: Feature Request
I can never tell if I have word wrap enabled by looking at View -> Toggle Word Wrap. Which is strange because right next to it, you have Show Breadcrumbs, Show Minimap, etc. which all have checks that indicate whether or not that feature is turned on.
Lets be consistent. Show the state of whether or not word wrap is enabled for the editor with a check.
VS Code version: Code 1.54.3 (2b9aebd5354a3629c3aba0a5f5df49f43d6689f8, 2021-03-15T11:57:12.728Z)
OS version: Darwin x64 20.3.0

/duplicate of #62307


K8s 1.17 - Coredns stuck in "Updating" state in cluster with windows node.

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Create a custom cluster with AWS with:
1 Linux etcd/control node
1 linux worker
3 windows worker nodes
AMI
AMI ID: ami-0bce54f2d5686d6c3
Name: windows-1903-docker-1903-ssh
Region: us-west-1
Provision the linux nodes first.
Wait for the cluster to become available before provisioning the windows node.
Result:
coredns is stuck upgrading:

coredns view:

Error seen in pod:

Node count appears to be off:

Each windows worker is correctly labeled as a worker:

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
v2.3-head commit a21dd0bab
Installation option (single install/HA):
single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Kubernetes version (use kubectl version): v1.17.0-rancher1-2
Network Provider: flannel
Windows Support: Enabled
Cloud Provider: Amazon

Could your fix related to coredns in RKE be applied to this use case? @superseb

@kinarashah Think the autoscaler labels should inclue beta.kubernetes.io/os=linux as well so it doesn't count Windows nodes as schedulable nodes?

@kinarashah Think the autoscaler labels should include beta.kubernetes.io/os=linux as well so it doesn't count Windows nodes as schedulable nodes?

yeah, we need linux label as well

The bug fix is verified with Rancher server rancher\rancher:v2.3-head version 9243de496
Core DNS is functional.

Tags in the windows worker node:
beta.kubernetes.io/os = windows
kubernetes.io/os = windows

Tags in the linux worker node:
beta.kubernetes.io/os = linux
kubernetes.io/os = linux

The bug fix is verified with Rancher server rancher\rancher:master-head version 88fcc20ad
Core DNS is functional.

Tags in the windows worker node:
beta.kubernetes.io/os = windows
kubernetes.io/os = windows

Tags in the linux worker node:
beta.kubernetes.io/os = linux
kubernetes.io/os = linux


Introduce startup probe in AWS sources' adapters

Closes #418
Prevents sources from becoming ready if the provided credentials aren't valid, or if the provided resource doesn't exist.
As a side effect, allows running all these adapters as long-running Knative Services in Google Cloud Run (because poking port 8080 will now return a response).

@antoineco this is on my list for tonight/tomorrow to test in GCR

looks like we are missing Performance Insights source

SNS is intentionally excluded because :
The SNS source is multi-tenant, so the logic of the startup probe is different and more involved: it needs to read the informer's lister, and verify that a HTTP handler was registered for each AWSSNSSource in the namespace. I drafted the logic here, regardless that source won't run outside of Kubernetes (so, no Cloud Run),

@JeffNeff I added a probe to the Performance Insights source in 982902ab..617ce146.


feat(network): db executor support for data types with a new trait

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

#1789  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nagmo-starkware and the rest of your teammates on  Graphite


Add metadata for kubernetes owner objects

Description of Changes
Adds additional keys to the resource object for parent objects to fully identify a pod. For example, for pods that are part of a service, it adds service name, and for pods that are part of a replicaset, it adds a replicaset name as well as the parent deployment name.
Example new resource block:
 "resource": {
    "k8s.cluster.name": "",
    "k8s.deployment.name": "nozzle",
    "k8s.namespace.name": "cabin",
    "k8s.namespace.uid": "0fe5f4fb-503f-457b-b0f9-72c1d6cea97c",
    "k8s.pod.name": "nozzle-6d8ccd7ccb-wcqcd",
    "k8s.pod.uid": "8914e221-464b-4e95-91bd-43251e0d670a",
    "k8s.replicaset.name": "nozzle-6d8ccd7ccb"
  },

Please check that the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Add a changelog entry (for non-trivial bug fixes / features)
[x] CI passes

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.8103806
-0.06895006
126.5951
-0.64816284

1
5000
6.3277917
+0.13804626
136.99286
+1.2805786

1
10000
12.379519
-0.24152756
143.55429
-0.19894409

1
50000
59.77547
-1.6923676
177.54782
-0.37149048

1
100000
117.69599
+0.43736267
230.66891
-3.7389526

10
100
2.4483256
+0.0689652
130.0524
-0.5247803

10
500
7.189876
+0.72426605
138.5066
+1.0490417

10
1000
13.758407
-0.2590208
144.03516
-3.8438873

10
5000
66.46669
-3.006218
184.21822
-0.01171875

10
10000
127.003136
-2.1156387
231.81465
+8.273834

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.7069255
-0.17240512
128.17026
+0.9269943

1
5000
5.8449388
-0.34480667
134.78758
-0.9246979

1
10000
11.998708
-0.62233925
145.31007
+1.556839

1
50000
58.501423
-2.9664154
173.49501
-4.424301

1
100000
115.63444
-1.6241913
232.12527
-2.2825928

10
100
2.3621502
-0.017210245
131.28583
+0.7086487

10
500
7.0348277
+0.5692177
136.78893
-0.66864014

10
1000
14.103932
+0.086504936
145.64143
-2.2376099

10
5000
65.08747
-4.385437
181.42618
-2.8037567

10
10000
126.827705
-2.291069
242.17888
+18.638062


Profiler fails to compile BPF filters on WLAN Pi 2.1.2

Describe the bug
Profiler fails to launch and throws a scapy exception:
scapy.error.Scapy_Exception: Failed to compile filter expression type mgt subtype probe-req or type mgt subtype auth or type mgt subtype assoc-req or type mgt subtype reassoc-req (-1)

To Reproduce
Steps to reproduce the issue.
Launch profiler like sudo profiler from a WLAN Pi terminal running 2.1.2.
Expected behavior
Profiler shouldn't crash.
Debug output
wlanpi@wlanpi:~$ sudo profiler
[sudo] password for wlanpi:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Starting a fake AP using wlan0mon on channel 36 (5180)

Getting started:

 - Associate your Wi-Fi client to *our* SSID: WLAN Pi
 - Enter any random password to connect
 - Authentication will fail, which is OK
 - We should receive an association request to 78:d2:94:2c:05:47
 - Results are then saved locally and printed on the shell
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2023-11-08 15:42:51,151 [INFO] fakeap.py: starting beacon transmissions
2023-11-08 15:42:51,409 [ERROR] fakeap.py: we had a problem creating BPF filters on L2socket/wlan0mon
Traceback (most recent call last):
  File "/opt/wlanpi/pipx/venvs/profiler/lib/python3.9/site-packages/profiler/fakeap.py", line 385, in __init__
    sniff(
  File "/opt/wlanpi/pipx/venvs/profiler/lib/python3.9/site-packages/scapy/sendrecv.py", line 1263, in sniff
    sniffer._run(*args, **kwargs)
  File "/opt/wlanpi/pipx/venvs/profiler/lib/python3.9/site-packages/scapy/sendrecv.py", line 1127, in _run
    sniff_sockets[L2socket(type=ETH_P_ALL, iface=iface,
  File "/opt/wlanpi/pipx/venvs/profiler/lib/python3.9/site-packages/scapy/arch/linux.py", line 497, in __init__
    attach_filter(self.ins, filter, self.iface)
  File "/opt/wlanpi/pipx/venvs/profiler/lib/python3.9/site-packages/scapy/arch/linux.py", line 166, in attach_filter
    bp = compile_filter(bpf_filter, iface)
  File "/opt/wlanpi/pipx/venvs/profiler/lib/python3.9/site-packages/scapy/arch/common.py", line 156, in compile_filter
    raise Scapy_Exception(
scapy.error.Scapy_Exception: Failed to compile filter expression type mgt subtype probe-req or type mgt subtype auth or type mgt subtype assoc-req or type mgt subtype reassoc-req (-1)
2023-11-08 15:42:51,425 [INFO] fakeap.py: try running with --no_bpf_filters
2023-11-08 15:42:52,221 [WARNING] fakeap.py: beacon(): network is down or no such device (wlan0mon) ... exiting ...

Software and hardware:

OS: Debian 11 bullseye
Hardware: NEO2
Profiler Version: 1.0.15

The scapy exception failing to compile filters is due to a problem with the version of libpcap shipped in 2.1.2 (libpcap0.8:arm64 1.10.0-2).
This can be resolved on a WLAN Pi running 2.1.2 by installing a newer version of libpcap (libpcap0.8=1.10.3-1~bpo11+1). Thanks @adriangranados for the find.
scapy.error.Scapy_Exception: Failed to compile filter expression type mgt subtype probe-req or type mgt subtype auth or type mgt subtype assoc-req or type mgt subtype reassoc-req (-1)
2023-11-08 15:42:51,425 [INFO] fakeap.py: try running with --no_bpf_filters
2023-11-08 15:42:52,221 [WARNING] fakeap.py: beacon(): network is down or no such device (wlan0mon) ... exiting ...
wlanpi@wlanpi:~$ sudo apt-get install libpcap0.8=1.10.3-1~bpo11+1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  libpcap0.8
1 upgraded, 0 newly installed, 0 to remove and 79 not upgraded.
Need to get 157 kB of archives.
After this operation, 14.3 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye-backports/main arm64 libpcap0.8 arm64 1.10.3-1~bpo11+1 [157 kB]
Fetched 157 kB in 0s (421 kB/s)
(Reading database ... 65451 files and directories currently installed.)
Preparing to unpack .../libpcap0.8_1.10.3-1~bpo11+1_arm64.deb ...
Unpacking libpcap0.8:arm64 (1.10.3-1~bpo11+1) over (1.10.0-2) ...
Setting up libpcap0.8:arm64 (1.10.3-1~bpo11+1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u6) ...
wlanpi@wlanpi:~$ sudo profiler

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Starting a fake AP using wlan0mon on channel 36 (5180)

Getting started:

 - Associate your Wi-Fi client to *our* SSID: WLAN Pi
 - Enter any random password to connect
 - Authentication will fail, which is OK
 - We should receive an association request to 78:d2:94:2c:05:47
 - Results are then saved locally and printed on the shell
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2023-11-08 15:44:27,708 [INFO] fakeap.py: starting beacon transmissions


add on demand tool

Makes sense to me, and makes the readers a little more automatic. I think I like the term "on demand" more than "adhoc", not sure which term you wanted to settle on.
Feels like there's room to think about how caching could work in future PRs too!

makes sense! I think i like on demand too, will revise