The master branch version is not working

I just downloaded weave script from master branch and then launched the weave on 3 nodes.  These are my commands:
node1) IP <IP_ADDRESS>
weave reset && weave launch -password local123
weave expose <IP_ADDRESS>/8
node2) IP <IP_ADDRESS>
weave reset && weave launch -password local123 <IP_ADDRESS>
weave expose <IP_ADDRESS>/8
node3) IP <IP_ADDRESS>
weave reset && weave launch -password local123 <IP_ADDRESS>
weave expose <IP_ADDRESS>/8
After I ran those 3 weave containers I tried pinging each other on <IP_ADDRESS> and things don't connect.
The same above commands work on 0.9 version of weave.  Is there any change in master branch that breaks functionality?  I had revert back to 0.9 version from master branch to make things work.

I just tried the same test with current master and it seems to work for me.  Could you show the output of docker logs weave and weave status from all three hosts when it doesn't work?

node1) IP <IP_ADDRESS>
node2) IP <IP_ADDRESS>
weave reset && weave launch -password local123 <IP_ADDRESS>

Shouldn't that last IP address match the first one?

Glad you got it working. Let us know if there is anything we can do, e.g. improvements in the docs, to prevent others from making the same mistake.

Sorry my mistake of typing IP addresses of nodes.  I re-checked it my command to launch weave is correct.  Here is rundown again:
node1) IP: <IP_ADDRESS>
weave reset && weave launch -password local123
weave expose <IP_ADDRESS>/8
node2) IP: <IP_ADDRESS>
weave reset && weave launch -password local123 <IP_ADDRESS>
weave expose <IP_ADDRESS>/8
node3) IP: <IP_ADDRESS>
weave reset && weave launch -password local123 <IP_ADDRESS>
weave expose <IP_ADDRESS>/8
After this this is what happening:
From <IP_ADDRESS> I can ping both <IP_ADDRESS> & <IP_ADDRESS>
From <IP_ADDRESS> I can only get to <IP_ADDRESS> can't ping <IP_ADDRESS>
From <IP_ADDRESS> I can only get to <IP_ADDRESS> can't ping <IP_ADDRESS>
So the communication is only happening between nodes that are given in peer list.  Do I need to give all server ips in peer list?
The same set of commands work with 0.9 release.  So, wondering has anything changed in the behavior of latest in master branch?
node1: weave status
weave router git-245f74774513
Encryption on
Our name is 7a:43:d0:43:13:a2 (hotelsoft-local-core2)
Sniffing traffic on &{67 65535 ethwe d2:3a:80:dd:80:97 up|broadcast|multicast}
MACs:
d2:3a:80:dd:80:97 -> 7a:43:d0:43:13:a2 (2015-03-29 16:39:20.773363783 +0000 UTC)
56:a7:e8:b3:47:7d -> 7a:43:d0:43:13:a2 (2015-03-29 16:39:21.349195085 +0000 UTC)
7a:1b:f8:ee:24:13 -> 7a:1b:f8:ee:24:13 (2015-03-29 16:40:19.446616693 +0000 UTC)
02:42:0a:03:00:17 -> 7a:58:2c:b5:c9:a5 (2015-03-29 16:45:51.35488203 +0000 UTC)
7a:43:d0:43:13:a2 -> 7a:43:d0:43:13:a2 (2015-03-29 16:45:51.354968124 +0000 UTC)
02:42:0a:01:00:18 -> 7a:43:d0:43:13:a2 (2015-03-29 16:39:21.549314772 +0000 UTC)
de:fb:2e:14:91:1b -> 7a:1b:f8:ee:24:13 (2015-03-29 16:40:18.664957892 +0000 UTC)
02:42:0a:02:00:15 -> 7a:1b:f8:ee:24:13 (2015-03-29 16:40:56.973854131 +0000 UTC)
7a:58:2c:b5:c9:a5 -> 7a:58:2c:b5:c9:a5 (2015-03-29 16:44:47.457987487 +0000 UTC)
Peers:
Peer 7a:1b:f8:ee:24:13 (hotelsoft-local-core3) (v2) (UID<PHONE_NUMBER>1555944076)
   -> 7a:43:d0:43:13:a2 (hotelsoft-local-core2) [<IP_ADDRESS>:6783]
Peer 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4) (v2) (UID<PHONE_NUMBER>2730030560)
   -> 7a:43:d0:43:13:a2 (hotelsoft-local-core2) [<IP_ADDRESS>:6783]
Peer 7a:43:d0:43:13:a2 (hotelsoft-local-core2) (v10) (UID<PHONE_NUMBER>731662224)
   -> 7a:1b:f8:ee:24:13 (hotelsoft-local-core3) [<IP_ADDRESS>:46782]
   -> 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4) [<IP_ADDRESS>:53809]
Routes:
unicast:
7a:43:d0:43:13:a2 -> 00:00:00:00:00:00
7a:1b:f8:ee:24:13 -> 7a:1b:f8:ee:24:13
7a:58:2c:b5:c9:a5 -> 7a:58:2c:b5:c9:a5
7a:43:d0:43:13:a2 -> [7a:1b:f8:ee:24:13 7a:58:2c:b5:c9:a5]
Reconnects:

weavedns container is not present; have you launched it?

node2: weave status
weave router git-245f74774513
Encryption on
Our name is 7a:1b:f8:ee:24:13 (hotelsoft-local-core3)
Sniffing traffic on &{73 65535 ethwe ee:65:ff:5c:10:39 up|broadcast|multicast}
MACs:
02:42:0a:02:00:15 -> 7a:1b:f8:ee:24:13 (2015-03-29 16:48:21.997909619 +0000 UTC)
7a:43:d0:43:13:a2 -> 7a:43:d0:43:13:a2 (2015-03-29 16:48:21.998454897 +0000 UTC)
Peers:
Peer 7a:1b:f8:ee:24:13 (hotelsoft-local-core3) (v2) (UID<PHONE_NUMBER>1555944076)
   -> 7a:43:d0:43:13:a2 (hotelsoft-local-core2) [<IP_ADDRESS>:6783]
Peer 7a:43:d0:43:13:a2 (hotelsoft-local-core2) (v14) (UID<PHONE_NUMBER>731662224)
   -> 7a:1b:f8:ee:24:13 (hotelsoft-local-core3) [<IP_ADDRESS>:46782]
   -> 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4) [<IP_ADDRESS>:53809]
Peer 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4) (v2) (UID<PHONE_NUMBER>2730030560)
   -> 7a:43:d0:43:13:a2 (hotelsoft-local-core2) [<IP_ADDRESS>:6783]
Routes:
unicast:
7a:1b:f8:ee:24:13 -> 00:00:00:00:00:00
7a:43:d0:43:13:a2 -> 7a:43:d0:43:13:a2
7a:58:2c:b5:c9:a5 -> 7a:43:d0:43:13:a2
7a:1b:f8:ee:24:13 -> [7a:43:d0:43:13:a2]
Reconnects:

weavedns container is not present; have you launched it?

node3: weave status
weave router git-245f74774513
Encryption on
Our name is 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4)
Sniffing traffic on &{73 65535 ethwe c2:9e:2d:74:dc:2c up|broadcast|multicast}
MACs:
02:42:0a:03:00:17 -> 7a:58:2c:b5:c9:a5 (2015-03-29 16:51:35.51250232 +0000 UTC)
7a:58:2c:b5:c9:a5 -> 7a:58:2c:b5:c9:a5 (2015-03-29 16:44:47.454356183 +0000 UTC)
7a:43:d0:43:13:a2 -> 7a:43:d0:43:13:a2 (2015-03-29 16:51:35.523713025 +0000 UTC)
Peers:
Peer 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4) (v2) (UID<PHONE_NUMBER>2730030560)
   -> 7a:43:d0:43:13:a2 (hotelsoft-local-core2) [<IP_ADDRESS>:6783]
Peer 7a:43:d0:43:13:a2 (hotelsoft-local-core2) (v14) (UID<PHONE_NUMBER>731662224)
   -> 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4) [<IP_ADDRESS>:53809]
   -> 7a:1b:f8:ee:24:13 (hotelsoft-local-core3) [<IP_ADDRESS>:46782]
Peer 7a:1b:f8:ee:24:13 (hotelsoft-local-core3) (v2) (UID<PHONE_NUMBER>1555944076)
   -> 7a:43:d0:43:13:a2 (hotelsoft-local-core2) [<IP_ADDRESS>:6783]
Routes:
unicast:
7a:58:2c:b5:c9:a5 -> 00:00:00:00:00:00
7a:43:d0:43:13:a2 -> 7a:43:d0:43:13:a2
7a:1b:f8:ee:24:13 -> 7a:43:d0:43:13:a2
7a:58:2c:b5:c9:a5 -> [7a:43:d0:43:13:a2]
Reconnects:

weavedns container is not present; have you launched it?

node1: docker logs weave
weave 2015/03/29 16:39:20.739647 Command line options: map[iface:ethwe name:7a:43:d0:43:13:a2 nickname:hotelsoft-local-core2 wait:20]
weave 2015/03/29 16:39:20.739698 Command line peers: []
weave 2015/03/29 16:39:20.739853 Communication between peers is encrypted.
weave 2015/03/29 16:39:20.739896 Our name is 7a:43:d0:43:13:a2 (hotelsoft-local-core2)
weave 2015/03/29 16:39:20.773323 Sniffing traffic on &{67 65535 ethwe d2:3a:80:dd:80:97 up|broadcast|multicast}
weave 2015/03/29 16:39:20.773382 Discovered our MAC d2:3a:80:dd:80:97
weave 2015/03/29 16:39:21.071404 Discovered local MAC 7a:43:d0:43:13:a2
weave 2015/03/29 16:39:21.349204 Discovered local MAC 56:a7:e8:b3:47:7d
weave 2015/03/29 16:39:21.549325 Discovered local MAC 02:42:0a:01:00:18
weave 2015/03/29 16:40:10.137818 ->[<IP_ADDRESS>:36412] connection accepted
weave 2015/03/29 16:40:10.138561 ->[<IP_ADDRESS>:36412] completed handshake with 7a:7c:78:b4:d5:fd
weave 2015/03/29 16:40:10.138610 ->[7a:7c:78:b4:d5:fd]: connection added (new peer)
weave 2015/03/29 16:40:10.138872 ->[7a:7c:78:b4:d5:fd]: connection shutting down due to error: write tcp4 <IP_ADDRESS>:36412: connection reset by peer
weave 2015/03/29 16:40:10.138902 ->[7a:7c:78:b4:d5:fd]: connection deleted
weave 2015/03/29 16:40:10.138920 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:40:18.488656 ->[<IP_ADDRESS>:46782] connection accepted
weave 2015/03/29 16:40:18.489386 ->[<IP_ADDRESS>:46782] completed handshake with 7a:1b:f8:ee:24:13
weave 2015/03/29 16:40:18.489439 ->[7a:1b:f8:ee:24:13]: connection added (new peer)
weave 2015/03/29 16:40:18.491048 ->[7a:1b:f8:ee:24:13]: connection fully established
weave 2015/03/29 16:40:18.491738 EMSGSIZE on send, expecting PMTU update (IP packet was 60082 bytes, payload was 60074 bytes)
weave 2015/03/29 16:40:18.491769 ->[7a:1b:f8:ee:24:13]: Effective PMTU set to 1420
weave 2015/03/29 16:40:18.492664 ->[7a:1b:f8:ee:24:13]: Effective PMTU verified at 1420
weave 2015/03/29 16:40:18.664968 Discovered remote MAC de:fb:2e:14:91:1b at 7a:1b:f8:ee:24:13
weave 2015/03/29 16:40:19.446627 Discovered remote MAC 7a:1b:f8:ee:24:13 at 7a:1b:f8:ee:24:13
weave 2015/03/29 16:40:56.970476 ->[<IP_ADDRESS>:53809] connection accepted
weave 2015/03/29 16:40:56.971321 ->[<IP_ADDRESS>:53809] completed handshake with 7a:58:2c:b5:c9:a5
weave 2015/03/29 16:40:56.971368 ->[7a:58:2c:b5:c9:a5]: connection added (new peer)
weave 2015/03/29 16:40:56.972829 ->[7a:58:2c:b5:c9:a5]: connection fully established
weave 2015/03/29 16:40:56.973283 EMSGSIZE on send, expecting PMTU update (IP packet was 60082 bytes, payload was 60074 bytes)
weave 2015/03/29 16:40:56.973308 ->[7a:58:2c:b5:c9:a5]: Effective PMTU set to 1420
weave 2015/03/29 16:40:56.973863 Discovered remote MAC 02:42:0a:02:00:15 at 7a:1b:f8:ee:24:13
weave 2015/03/29 16:40:56.974197 ->[7a:58:2c:b5:c9:a5]: Effective PMTU verified at 1420
weave 2015/03/29 16:40:56.975542 ->[<IP_ADDRESS>:58742] connection accepted
weave 2015/03/29 16:40:56.975959 ->[<IP_ADDRESS>:58742] connection shutting down due to error during handshake: Already have connection to 7a:1b:f8:ee:24:13 at <IP_ADDRESS>:46782
weave 2015/03/29 16:40:57.164546 Discovered remote MAC 7a:58:2c:b5:c9:a5 at 7a:58:2c:b5:c9:a5
weave 2015/03/29 16:40:57.974667 Discovered remote MAC 02:42:0a:03:00:17 at 7a:58:2c:b5:c9:a5
weave 2015/03/29 16:40:57.976521 ->[<IP_ADDRESS>:58743] connection accepted
weave 2015/03/29 16:40:57.976949 ->[<IP_ADDRESS>:58743] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:41:04.022675 ->[<IP_ADDRESS>:58744] connection accepted
weave 2015/03/29 16:41:04.023170 ->[<IP_ADDRESS>:58744] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:41:12.536792 ->[<IP_ADDRESS>:58745] connection accepted
weave 2015/03/29 16:41:12.537400 ->[<IP_ADDRESS>:58745] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:41:29.010795 ->[<IP_ADDRESS>:58747] connection accepted
weave 2015/03/29 16:41:29.011344 ->[<IP_ADDRESS>:58747] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:41:48.145222 ->[<IP_ADDRESS>:58749] connection accepted
weave 2015/03/29 16:41:48.146006 ->[<IP_ADDRESS>:58749] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:42:11.238218 ->[<IP_ADDRESS>:58750] connection accepted
weave 2015/03/29 16:42:11.238699 ->[<IP_ADDRESS>:58750] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:42:24.032363 ->[<IP_ADDRESS>:36413] connection accepted
weave 2015/03/29 16:42:24.033094 ->[<IP_ADDRESS>:36413] completed handshake with 7a:7c:78:b4:d5:fd
weave 2015/03/29 16:42:24.033240 ->[7a:7c:78:b4:d5:fd]: connection added (new peer)
weave 2015/03/29 16:42:24.033449 ->[7a:7c:78:b4:d5:fd]: connection shutting down due to error: read tcp4 <IP_ADDRESS>:36413: connection reset by peer
weave 2015/03/29 16:42:24.033483 ->[7a:7c:78:b4:d5:fd]: connection deleted
weave 2015/03/29 16:42:24.033511 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:42:50.622023 ->[<IP_ADDRESS>:58751] connection accepted
weave 2015/03/29 16:42:50.622513 ->[<IP_ADDRESS>:58751] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:43:51.442699 ->[<IP_ADDRESS>:58752] connection accepted
weave 2015/03/29 16:43:51.443192 ->[<IP_ADDRESS>:58752] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:44:40.007793 ->[<IP_ADDRESS>:36414] connection accepted
weave 2015/03/29 16:44:40.008491 ->[<IP_ADDRESS>:36414] completed handshake with 7a:7c:78:b4:d5:fd
weave 2015/03/29 16:44:40.008578 ->[7a:7c:78:b4:d5:fd]: connection added (new peer)
weave 2015/03/29 16:44:40.008805 ->[7a:7c:78:b4:d5:fd]: connection shutting down due to error: EOF
weave 2015/03/29 16:44:40.008842 ->[7a:7c:78:b4:d5:fd]: connection deleted
weave 2015/03/29 16:44:40.008868 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:45:51.356166 ->[<IP_ADDRESS>:58753] connection accepted
weave 2015/03/29 16:45:51.356631 ->[<IP_ADDRESS>:58753] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:48:22.000501 ->[<IP_ADDRESS>:36415] connection accepted
weave 2015/03/29 16:48:22.001222 ->[<IP_ADDRESS>:36415] completed handshake with 7a:7c:78:b4:d5:fd
weave 2015/03/29 16:48:22.001309 ->[7a:7c:78:b4:d5:fd]: connection added (new peer)
weave 2015/03/29 16:48:22.001494 ->[7a:7c:78:b4:d5:fd]: connection shutting down due to error: read tcp4 <IP_ADDRESS>:36415: connection reset by peer
weave 2015/03/29 16:48:22.001531 ->[7a:7c:78:b4:d5:fd]: connection deleted
weave 2015/03/29 16:48:22.001554 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:48:22.003507 ->[<IP_ADDRESS>:58757] connection accepted
weave 2015/03/29 16:48:22.003923 ->[<IP_ADDRESS>:58757] connection shutting down due to error during handshake: Already have connection to 7a:1b:f8:ee:24:13 at <IP_ADDRESS>:46782
weave 2015/03/29 16:48:28.536291 ->[<IP_ADDRESS>:58758] connection accepted
weave 2015/03/29 16:48:28.536812 ->[<IP_ADDRESS>:58758] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:49:20.774414 Expired MAC d2:3a:80:dd:80:97 at 7a:43:d0:43:13:a2
weave 2015/03/29 16:50:20.774749 Expired MAC 56:a7:e8:b3:47:7d at 7a:43:d0:43:13:a2
weave 2015/03/29 16:50:20.774779 Expired MAC 7a:1b:f8:ee:24:13 at 7a:1b:f8:ee:24:13
weave 2015/03/29 16:50:20.774789 Expired MAC 02:42:0a:01:00:18 at 7a:43:d0:43:13:a2
weave 2015/03/29 16:50:20.774800 Expired MAC de:fb:2e:14:91:1b at 7a:1b:f8:ee:24:13
weave 2015/03/29 16:51:35.528015 ->[<IP_ADDRESS>:58761] connection accepted
weave 2015/03/29 16:51:35.528562 ->[<IP_ADDRESS>:58761] connection shutting down due to error during handshake: Already have connection to 7a:58:2c:b5:c9:a5 at <IP_ADDRESS>:53809
weave 2015/03/29 16:52:40.812407 ->[<IP_ADDRESS>:36416] connection accepted
weave 2015/03/29 16:52:40.813002 ->[<IP_ADDRESS>:36416] completed handshake with 7a:7c:78:b4:d5:fd
weave 2015/03/29 16:52:40.813050 ->[7a:7c:78:b4:d5:fd]: connection added (new peer)
weave 2015/03/29 16:52:40.813246 ->[7a:7c:78:b4:d5:fd]: connection shutting down due to error: read tcp4 <IP_ADDRESS>:36416: connection reset by peer
weave 2015/03/29 16:52:40.813295 ->[7a:7c:78:b4:d5:fd]: connection deleted
weave 2015/03/29 16:52:40.813329 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)

node: docker logs weave
weave 2015/03/29 16:40:08.885389 Command line options: map[iface:ethwe name:7a:1b:f8:ee:24:13 nickname:hotelsoft-local-core3 wait:20]
weave 2015/03/29 16:40:08.885442 Command line peers: [<IP_ADDRESS>]
weave 2015/03/29 16:40:08.885591 Communication between peers is encrypted.
weave 2015/03/29 16:40:08.885632 Our name is 7a:1b:f8:ee:24:13 (hotelsoft-local-core3)
weave 2015/03/29 16:40:08.922749 Sniffing traffic on &{73 65535 ethwe ee:65:ff:5c:10:39 up|broadcast|multicast}
weave 2015/03/29 16:40:08.922799 Discovered our MAC ee:65:ff:5c:10:39
weave 2015/03/29 16:40:08.923309 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:40:09.002418 Discovered local MAC 7a:1b:f8:ee:24:13
weave 2015/03/29 16:40:09.316366 Discovered local MAC de:fb:2e:14:91:1b
weave 2015/03/29 16:40:09.556459 Discovered local MAC 02:42:0a:02:00:15
weave 2015/03/29 16:40:11.928524 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 <IP_ADDRESS>:6783: no route to host
weave 2015/03/29 16:40:14.704632 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:40:14.934316 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 <IP_ADDRESS>:6783: no route to host
weave 2015/03/29 16:40:18.483758 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:40:18.485157 ->[<IP_ADDRESS>:6783] completed handshake with 7a:43:d0:43:13:a2
weave 2015/03/29 16:40:18.485295 ->[7a:43:d0:43:13:a2]: connection added (new peer)
weave 2015/03/29 16:40:18.486302 ->[7a:43:d0:43:13:a2]: connection fully established
weave 2015/03/29 16:40:18.486618 EMSGSIZE on send, expecting PMTU update (IP packet was 60082 bytes, payload was 60074 bytes)
weave 2015/03/29 16:40:18.486638 ->[7a:43:d0:43:13:a2]: Effective PMTU set to 1420
weave 2015/03/29 16:40:18.486987 ->[7a:43:d0:43:13:a2]: Effective PMTU verified at 1420
weave 2015/03/29 16:40:42.813892 Discovered remote MAC 7a:43:d0:43:13:a2 at 7a:43:d0:43:13:a2
weave 2015/03/29 16:40:56.969179 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:40:56.972155 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:42:24.029667 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:44:40.005016 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:48:21.997602 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:48:21.997732 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:48:21.999869 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:50:08.924698 Expired MAC ee:65:ff:5c:10:39 at 7a:1b:f8:ee:24:13
weave 2015/03/29 16:51:08.925017 Expired MAC 7a:1b:f8:ee:24:13 at 7a:1b:f8:ee:24:13
weave 2015/03/29 16:51:08.925050 Expired MAC de:fb:2e:14:91:1b at 7a:1b:f8:ee:24:13
weave 2015/03/29 16:52:40.809431 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)

node: docker logs weave
weave 2015/03/29 16:40:47.367906 Command line options: map[name:7a:58:2c:b5:c9:a5 nickname:hotelsoft-local-core4 wait:20 iface:ethwe]
weave 2015/03/29 16:40:47.367953 Command line peers: [<IP_ADDRESS>]
weave 2015/03/29 16:40:47.368096 Communication between peers is encrypted.
weave 2015/03/29 16:40:47.368136 Our name is 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4)
weave 2015/03/29 16:40:47.404609 Sniffing traffic on &{73 65535 ethwe c2:9e:2d:74:dc:2c up|broadcast|multicast}
weave 2015/03/29 16:40:47.404653 Discovered our MAC c2:9e:2d:74:dc:2c
weave 2015/03/29 16:40:47.405534 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:40:47.539034 Discovered local MAC 62:5b:7f:19:49:a4
weave 2015/03/29 16:40:48.337120 Discovered local MAC 02:42:0a:03:00:17
weave 2015/03/29 16:40:48.379782 Discovered local MAC 7a:58:2c:b5:c9:a5
weave 2015/03/29 16:40:50.411153 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 <IP_ADDRESS>:6783: no route to host
weave 2015/03/29 16:40:53.187266 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:40:53.417110 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 <IP_ADDRESS>:6783: no route to host
weave 2015/03/29 16:40:56.966598 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:40:56.967851 ->[<IP_ADDRESS>:6783] completed handshake with 7a:43:d0:43:13:a2
weave 2015/03/29 16:40:56.968003 ->[7a:43:d0:43:13:a2]: connection added (new peer)
weave 2015/03/29 16:40:56.968999 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:40:56.969105 ->[7a:43:d0:43:13:a2]: connection fully established
weave 2015/03/29 16:40:56.969776 EMSGSIZE on send, expecting PMTU update (IP packet was 60082 bytes, payload was 60074 bytes)
weave 2015/03/29 16:40:56.969798 ->[7a:43:d0:43:13:a2]: Effective PMTU set to 1420
weave 2015/03/29 16:40:56.970488 ->[7a:43:d0:43:13:a2]: Effective PMTU verified at 1420
weave 2015/03/29 16:40:57.971799 Discovered remote MAC 7a:43:d0:43:13:a2 at 7a:43:d0:43:13:a2
weave 2015/03/29 16:40:57.974044 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:41:04.017563 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:41:04.020613 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:41:12.531652 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:41:12.534354 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:41:29.005741 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:41:29.008577 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:41:48.140261 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:41:48.143155 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:42:11.232976 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:42:11.235660 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:42:24.030698 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:42:50.616835 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:42:50.619659 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:43:51.437504 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:43:51.440200 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:44:40.006014 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:45:51.350955 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:45:51.353622 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:48:21.998642 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)
weave 2015/03/29 16:48:28.531226 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:48:28.533894 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:50:47.414958 Expired MAC c2:9e:2d:74:dc:2c at 7a:58:2c:b5:c9:a5
weave 2015/03/29 16:51:35.512301 ->[<IP_ADDRESS>:6783] attempting connection
weave 2015/03/29 16:51:35.525634 ->[<IP_ADDRESS>:6783] connection shutting down due to error during handshake: Already have connection to 7a:43:d0:43:13:a2 at <IP_ADDRESS>:6783
weave 2015/03/29 16:51:47.415264 Expired MAC 62:5b:7f:19:49:a4 at 7a:58:2c:b5:c9:a5
weave 2015/03/29 16:52:40.810450 Removed unreachable Peer 7a:7c:78:b4:d5:fd () (v0) (UID<PHONE_NUMBER>025949613)

Ok, now I can reproduce it.  Bisecting...

Bisecting revealing the issue was introduced in d5eb76f32ec61cefbe6270759a46f25d4911f4ae
@kesavkolia: I've pushed a fix, could you try it (if you can get it, github seems to be under heavy attack right now).

I've uploaded new images, containing the fix, to the docker hub.

@kesavkolla: By the way, looking more closely in your weave status output, I see
Peers:
Peer 7a:1b:f8:ee:24:13 (hotelsoft-local-core3) (v2) (UID<PHONE_NUMBER>1555944076)
   -> 7a:43:d0:43:13:a2 (hotelsoft-local-core2) [<IP_ADDRESS>:6783]
Peer 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4) (v2) (UID<PHONE_NUMBER>2730030560)
   -> 7a:43:d0:43:13:a2 (hotelsoft-local-core2) [<IP_ADDRESS>:6783]
Peer 7a:43:d0:43:13:a2 (hotelsoft-local-core2) (v10) (UID<PHONE_NUMBER>731662224)
   -> 7a:1b:f8:ee:24:13 (hotelsoft-local-core3) [<IP_ADDRESS>:46782]
   -> 7a:58:2c:b5:c9:a5 (hotelsoft-local-core4) [<IP_ADDRESS>:53809]

which seems to suggest that the subnet <IP_ADDRESS>/16 is being used for the docker bridge (docker normally uses <IP_ADDRESS>/16 for its bridge, but it has a list of other addresses it will try).  Could you check with ip addr show docker0?  If <IP_ADDRESS>/16 is being used by the docker bridge, you should pick another subnet for the weave network, e.g.g <IP_ADDRESS>/16.
I don't think this is related to main issue you reported (as otherwise you would have no luck pinging <IP_ADDRESS> and <IP_ADDRESS> on node1).  But it might be a source of other issues.

Yes this is what my setup.  I'm using weave bridge as replacement for docker bridge.  So when I create any container they should automatically be available on weave network.  The host nodes has /8 subnet and containers will get /16 subnet.
I use DOCKER_OPTS=--fixed-cidr=<IP_ADDRESS>/16 --bridge=weave
The fixed-cidr changes on each node.
Is there any other way of doing this?

Hmm, did that work in 0.9.0?  The weave router container needs access to the weave bridge, but it also needs to be able to send and receive over the real network.  I think it's possible to achieve what you want in principle, but I'd be surprised if it works with the weave script in its current form.  I could be wrong on that though.
Thank you for reporting the original issue - it means we have fixed a serious bug.  Maybe you can confirm that what works in 0.9.0 now works in master, and open a new issue if you have problems using the weave bridge to replace the docker bridge?

Yes 0.9.0 always worked for me.  I thought this is a supported scenario to replace docker bridge with weave bridge.
I'll check the master branch to see if the original issue was fixed.

I validated this with new image from master and every thing works find.
Thanks for fixing the issue.


🐛 BUG: Unable to fetch a worker uploaded with Cloudflare API

Which Cloudflare product(s) does this pertain to?
Workers/Other
What version of Wrangler are you using?
2.16.0
What operating system are you using?
Windows
Describe the Bug
I have attempted to init a dashboard worker that I uploaded with cloudflare API. The worker contains three modules (an index.js and two supporting js files). The worker runs without issues.
The issue I have is that I can't fetch this worker with wrangler.
The command I used: wrangler init --from-dash test-worker
The error message: Expected only one entry in multipart response

This is a duplicate of this issue, work is planned to address this


Fix JUnit --tests behavior

Make parameterized tests work when --tests is used, and when the --tests argument matches a suite name, run the entire suite instead of displaying an error message that no tests matched the name.
Discussion at https://groups.google.com/forum/#!topic/gradle-dev/kmoJwBVGQHg

@AlexLandau Thank you for the pull request. I added my comments.

This change will also require an update to the design document at https://github.com/gradle/gradle/blob/master/design-docs/testing-improvements.md. I recommend you do it first so we can review test coverage before you start implementing it.

I've just gotten back to this.
To catch up these commits with the rest of the codebase, do you have a preference for rebase vs. merge? I'm not exactly sure how Github copes with them on PRs.

I think rebase is better.  If the PR gets screwy, we can close and open a new one.

I tried a rebase, but Github required a merge to keep pushing to the same junit-tests-behavior branch. It looks like that in turn messed up the commits list, so I'm just going to start a fresh PR.

The new, rebased pull request is #561.


Please Add the Made In Cuba Collection

Thank you for contributing! Please confirm this pull request meets the following requirements:

[X] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[X] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[X] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Curating a new topic or collection

[X] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[X] My folder contains a *.png image (if applicable) and index.md
[X] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

There are a lot of innovative open source projects being actively worked on in the island of Cuba. There are interesting hardware projects that arise due to the US Embargo on Cuba which requires the population to come up with innovative and unexpected uses for technology that should be shared with a wider audience. Here is but a small handful of curated projects that I would like to recommend be added to the Made in Cuba Collection.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

@lopezdp LGTM but there are failing tests, can you address those?

@BlakeWilliams thanks!

@BlakeWilliams can you provide an update on this? Looks like all checks are just waiting final approval, thanks!

Hi @lopezdp - this is merged now, but I wanted to let you know that at some point between you opening this PR and now, it looks like github.com/stepperUnipolar is no longer resolving - maybe this user changed their handle? I'm removing that one item in https://github.com/github/explore/pull/2367 to make CI green again, but feel free to open a new PR if you have their updated handle!

Hi @lopezdp - this is merged now, but I wanted to let you know that at some point between you opening this PR and now, it looks like github.com/stepperUnipolar is no longer resolving - maybe this user changed their handle? I'm removing that one item in #2367 to make CI green again, but feel free to open a new PR if you have their updated handle!

thanks for the help! unfortunately I dont know about unipolar :(

@deniseyu weird I dont see it in the collections on the explore tab... is there something else I should do?


Coda Daemon crashed - Testenet 3.3 Docker Crash Report

I sharing the crash report as suggested after the error, I was trying to run with the latest docker image:
docker run -d --name coda -p 8302:8302 -p 8303:8303 --restart always codaprotocol/coda-daemon:0.0.16-beta6 daemon -peer $SEED1
In macOS 10.15.4
coda_crash_report_2020-09-18_00-26-53.498373.tar.gz

"Exception":"(monitor.ml.Error\n  ((rpc_error (Connection_closed (\"EOF or connection closed\"))

This is the same error as provided in comments of https://github.com/CodaProtocol/coda/issues/6001

Closing as a dupe


⚠ Jenkins Plugins Artifactory has degraded performance

In bc33035, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1111 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 2af5510 after 1 hour, 17 minutes.


Implement upload es-next api (part of #240)

\cc @inikulin @AlexanderMoskovkin @VasilyStrelyaev

\r-

lgtm

@testcafe-build-bot \retest

lgtm

Just found a style issue (it relates to the previous PR but can be fixed here):
Missed 'Error' postfix in the upload error:
actionCanNotFindFileToUploadError:       'actionCanNotFindFileToUpload'

/r-

the same here

lgtm

lgtm


Cannot run definition tests: identifier React. Could not resolve name

I'm trying to update the argument types of a Jest method, but I can't run the definition tests properly, because of these weird errors. Note that my changes are completely unrelated to these errors, in fact my changes have nothing to do with Enzyme or React.
ERROR: jest_v20.x.x/flow_v0.39.x-
 * jest_v20.x.x/flow_v0.39.x- (flow-v0.53.0): Unexpected Flow errors(2):
   Error: 0-test_jest-v20.x.x.js:202
   202: const Dummy = () => <div />;
                            ^^^^^^^ identifier `React`. Could not resolve name

   Error: 0-test_jest-v20.x.x.js:203
   203: const wrapper = shallow(<Dummy />);
                                ^^^^^^^^^ identifier `React`. Could not resolve name

   Found 2 errors

   null

 * jest_v20.x.x/flow_v0.39.x- (flow-v0.53.1): Unexpected Flow errors(2):
   Error: 0-test_jest-v20.x.x.js:202
   202: const Dummy = () => <div />;
                            ^^^^^^^ identifier `React`. Could not resolve name

   Error: 0-test_jest-v20.x.x.js:203
   203: const wrapper = shallow(<Dummy />);
                                ^^^^^^^^^ identifier `React`. Could not resolve name

   Found 2 errors

   null

 * jest_v20.x.x/flow_v0.39.x- (flow-v0.54.0): Unexpected Flow errors(2):
   Error: 0-test_jest-v20.x.x.js:202
   202: const Dummy = () => <div />;
                            ^^^^^^^ identifier `React`. Could not resolve name

   Error: 0-test_jest-v20.x.x.js:203
   203: const wrapper = shallow(<Dummy />);
                                ^^^^^^^^^ identifier `React`. Could not resolve name

   Found 2 errors

   null

Any ideas?

Add import * as React from 'react' to the top of the test file. React typedefs are now native to flow.


OS X: naming and menu consistency with platform

Platform conventions indicate the application name should be Electron Mattermost.app, together with the app menu being Electron Mattermost.
Also, the Settings entry is to be separated from About <app-name>, labeled Preferences..., and have a CMD+, shortcut.
electron-mattermost:

Chrome:

Tied to #77, which solves the app name part.

Found out that menus are lacking standard entries on OS X, so standard shortcuts like CMD+W are not working.

Hi @lloeki, is there a straight forward way to add the shortcuts you mentioned?

Yes, just create appropriately named entries, and OS X will do some magic.
There's an example in Matter front code. Link pending.
On 22 Mar 2016 16:12, "it33"<EMAIL_ADDRESS>wrote:

Hi @lloeki https://github.com/lloeki, is there a straight forward way
to add the shortcuts you mentioned?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mattermost/desktop/issues/83#issuecomment-199858593

Here it is, in menu-template.js.  Just naming the things the right way makes OS X have the shortcuts, but they're included for Windows to behave. As for "Preferences...", it's lacking in the current code but naming it correctly shouldn't be a problem.

Maybe I had overlooked the separator.
Then, the wording was difficult for me when I had implemented the menu. (Both of "Preferences" and "Settings" become "設定" in Japanese...). On Windows and Linux, which is better?

Forgot to say that the Edit and Window entries are the one expected to be present on OS X.

@yuya-oc haha localisation sure is hard in many subtle ways :-)

A few missing shortcuts on OS-X:

Command-M Minimize Window
(optional) Alt-Command-Right Next (unread?) Channel? (Like Next Tab in Chrome)
(optional) Alt-Command-Left Prev (unread?) Channel? (Like Prev Tab in Chrome
already mentioned Command-, for Preferences

Are there any of those that I could help with a simple PR?

@leipert Command+, is added at v1.2.0. but the others are not yet. For PR, please see CONTRIBUTING.md.


lldb needs an easy way to specify python packages to be added

Issue description
I'm trying to use lldb for ghidra for debugging
This doesn't work as ghidra uses a python script on lldb, which requires the psutil module and fails to start debugging because of it
I thought if I override python3 for lldb to include the psutil module, it would include that python package for the lldb's scripting environment but that doesn't work as I thought
There is no indication on how to modify what python packages are available for lldb's scripting environment, and no comments on lldb.nix to show how to do this
It would be great if this is possible through overriding, so I'm able to run whatever python scripts for lldb
Steps to reproduce

Start lldb
Run the script command
import psutil
This gives the error ModuleNotFoundError: No module named 'psutil'

Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

system: "x86_64-linux"
host os: Linux 6.6.36, NixOS, 24.11 (Vicuna), 24.11.20240701.262a6fe
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.18.4
nixpkgs: /nix/store/6vwccppgzmn03wklp58k9fcndw2h7cwn-source

I apparently did everything but try creating a dev shell with the packages


related-key attack?

Hello.
I think there is a related-key attack in the way you produce Schnorr signatures.
https://github.com/mimblewimble/secp256k1-zkp/blob/7b7f3ec3f1fce7184bb79fea609e2b9f159c607e/src/modules/aggsig/main_impl.h#L49
sizeof(buf-1) = 8
sizeof(buf) - 1 = 32
so to my understanding you're copying only 8 bytes of the public key.
Therefore, if the signature
(s, e) is verified by H(_ || sG - eX) = e for public key X = xG
then, the signature
(s+ev, e) is verified by H(_ || (s+ev)G - e(X+vG)) = e for public key X + vG for any v in \ZZ_p for which X + vG has the same leading 64 bits of X.
Am I doing something wrong in here? Could you help me understand?

Thanks, and you're absolutely correct.. it's a slip and we have it tracked within the Grin issues list here: https://github.com/mimblewimble/grin/issues/1358
But good job finding it independently. We really appreciate having more eyes on this code, so if you come across anything further please don't hesitate to let us know.


Doesn't work for specific controller and action tracking with rails application.

Hi,
I tried to monitor the performance for specific controller and action with my rails application.
I did the configuration for web server agent and host agent, but I can see the warning "No language agents found yet" unfortunately.
And I tried to set for monitoring the specific controller and action performance in traceview initializer.
TraceView::Config[:bunnyconsumer][:controller] = <controller_name>
TraceView::Config[:bunnyconsumer][:action] = <action_name>
but in traceview dashboard, I see something like
No controller data found.
Getting controller and action data
The another thing works correctly.
If you let me know about what, for monitoring the specific controller and action, how I can configure the traceview initializer, I'd appreciate very much.
Thanks,
Dave
PS: my traceview.rb file is following.
AppNeta TraceView Initializer (for the traceview gem)
http://www.appneta.com/products/traceview/

More information on instrumenting Ruby applications can be found here:
https://support.appneta.com/cloud/installing-ruby-instrumentation
if defined?(TraceView::Config)
Tracing Mode determines when traces should be initiated for incoming requests.  Valid
options are always, through (when using an instrumented Apache or Nginx) and never.

If you're not using an instrumented Apache or Nginx, set this directive to always in
order to initiate tracing from Ruby.
TraceView::Config[:tracing_mode] = 'through'
Verbose output of instrumentation initialization
TraceView::Config[:verbose] = true
Logging of outgoing HTTP query args

This optionally disables the logging of query args of outgoing
HTTP clients such as Net::HTTP, excon, typhoeus and others.

This flag is global to all HTTP client instrumentation.

To configure this on a per instrumentation basis, set this
option to true and instead disable the instrumenstation specific
option log_args:

TraceView::Config[:nethttp][:log_args] = true
TraceView::Config[:excon][:log_args] = true
TraceView::Config[:typhoeus][:log_args] = true

TraceView::Config[:include_url_query_params] = true
Logging of incoming HTTP query args

This optionally disables the logging of incoming URL request
query args.

This flag is global and currently only affects the Rack
instrumentation which reports incoming request URLs and
query args by default.
TraceView::Config[:include_remote_url_params] = true
The TraceView Ruby client has the ability to sanitize query literals
from SQL statements.  By default this is disabled.  Enable to
avoid collecting and reporting query literals to TraceView.
TraceView::Config[:sanitize_sql] = false
Do Not Trace
These two values allow you to configure specific URL patterns to
never be traced.  By default, this is set to common static file
extensions but you may want to customize this list for your needs.

dnt_regexp and dnt_opts is passed to Regexp.new to create
a regular expression object.  That is then used to match against
the incoming request path.

The path string originates from the rack layer and is retrieved
as follows:

req = ::Rack::Request.new(env)
path = URI.unescape(req.path)

Usage:
TraceView::Config[:dnt_regexp] = ".(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|ttf|woff|svg|less)$"
TraceView::Config[:dnt_opts]   = Regexp::IGNORECASE

This will ignore all requests that end with the string lobster
regardless of case

Requests with positive matches (non nil) will not be traced.
See lib/traceview/util.rb: TraceView::Util.static_asset?

Rails Exception Logging

In Rails, raised exceptions with rescue handlers via
rescue_from are not reported to the TraceView
dashboard by default.  Setting this value to true will
report all raised exception regardless.

TraceView::Config[:report_rescued_errors] = true

By default, the curb instrumentation will not link
outgoing requests with remotely instrumented
webservers (aka cross host tracing).  This is because the
instrumentation can't detect if the independent libcurl
instrumentation is in use or not.

If you're sure that it's not in use/installed, then you can
enable cross host tracing for the curb HTTP client
here.  Set TraceView::Config[:curb][:cross_host] to true
to enable.

Alternatively, if you would like to install the separate
libcurl instrumentation, see here:
http://docs.appneta.com/installing-libcurl-instrumentation

TraceView::Config[:curb][:cross_host] = true

The bunny (Rabbitmq) instrumentation can optionally report
Controller and Action values to allow filtering of bunny
message handling in # the UI.  Use of Controller and Action
for filters is temporary until the UI is updated with
additional filters.

These values identify which properties of
Bunny::MessageProperties to report as Controller
and Action.  The defaults are to report :app_id (as
Controller) and :type (as Action).  If these values
are not specified in the publish, then nothing
will be reported here.

TraceView::Config[:bunnyconsumer][:controller] = :app_id #I tried to write the specific controller name
TraceView::Config[:bunnyconsumer][:action] = :type #and action name.

Resque Options

Set to true to disable Resque argument logging (Default: false)
TraceView::Config[:resque][:log_args] = false

Enabling/Disabling Instrumentation

If you're having trouble with one of the instrumentation libraries, they
can be individually disabled here by setting the :enabled
value to false:

TraceView::Config[:action_controller][:enabled] = true
TraceView::Config[:action_controller][:log_args] = true
TraceView::Config[:action_view][:enabled] = true
TraceView::Config[:active_record][:enabled] = true
TraceView::Config[:bunnyclient][:enabled] = true
TraceView::Config[:bunnyconsumer][:enabled] = true
TraceView::Config[:cassandra][:enabled] = true
TraceView::Config[:curb][:enabled] = true
TraceView::Config[:dalli][:enabled] = true
TraceView::Config[:delayed_jobclient][:enabled] = true
TraceView::Config[:delayed_jobworker][:enabled] = true
TraceView::Config[:excon][:enabled] = true
TraceView::Config[:em_http_request][:enabled] = true
TraceView::Config[:faraday][:enabled] = true
TraceView::Config[:grape][:enabled] = true
TraceView::Config[:httpclient][:enabled] = true
TraceView::Config[:memcache][:enabled] = true
TraceView::Config[:memcached][:enabled] = true
TraceView::Config[:mongo][:enabled] = true
TraceView::Config[:moped][:enabled] = true
TraceView::Config[:nethttp][:enabled] = true
TraceView::Config[:delayed_jobworker][:enabled] = true
TraceView::Config[:excon][:enabled] = true
TraceView::Config[:em_http_request][:enabled] = true
TraceView::Config[:faraday][:enabled] = true
TraceView::Config[:grape][:enabled] = true
TraceView::Config[:httpclient][:enabled] = true
TraceView::Config[:memcache][:enabled] = true
TraceView::Config[:memcached][:enabled] = true
TraceView::Config[:mongo][:enabled] = true
TraceView::Config[:moped][:enabled] = true
TraceView::Config[:nethttp][:enabled] = true
TraceView::Config[:redis][:enabled] = true
TraceView::Config[:resque][:enabled] = true
TraceView::Config[:rest_client][:enabled] = true
TraceView::Config[:sequel][:enabled] = true
TraceView::Config[:sidekiqclient][:enabled] = true
TraceView::Config[:sidekiqworker][:enabled] = true
TraceView::Config[:typhoeus][:enabled] = true

Enabling/Disabling Backtrace Collection

Instrumentation can optionally collect backtraces as they collect
performance metrics.  Note that this has a negative impact on
performance but can be useful when trying to locate the source of
a certain call or operation.

TraceView::Config[:action_controller][:collect_backtraces] = true
TraceView::Config[:action_view][:collect_backtraces] = true
TraceView::Config[:active_record][:collect_backtraces] = true
TraceView::Config[:bunnyclient][:collect_backtraces] = true
TraceView::Config[:bunnyconsumer][:collect_backtraces] = true
TraceView::Config[:cassandra][:collect_backtraces] = true
TraceView::Config[:curb][:collect_backtraces] = true
TraceView::Config[:dalli][:collect_backtraces] = true
TraceView::Config[:delayed_jobclient][:collect_backtraces] = true
TraceView::Config[:delayed_jobworker][:collect_backtraces] = true
TraceView::Config[:excon][:collect_backtraces] = true
TraceView::Config[:em_http_request][:collect_backtraces] = true
TraceView::Config[:faraday][:collect_backtraces] = true
TraceView::Config[:grape][:collect_backtraces] = true
TraceView::Config[:httpclient][:collect_backtraces] = true
TraceView::Config[:memcache][:collect_backtraces] = true
TraceView::Config[:memcached][:collect_backtraces] = true
TraceView::Config[:mongo][:collect_backtraces] = true
TraceView::Config[:moped][:collect_backtraces] = true
TraceView::Config[:nethttp][:collect_backtraces] = true
TraceView::Config[:redis][:collect_backtraces] = true
TraceView::Config[:resque][:collect_backtraces] = true
TraceView::Config[:rest_client][:collect_backtraces] = true
TraceView::Config[:sequel][:collect_backtraces] = true
TraceView::Config[:sidekiqclient][:collect_backtraces] = true
TraceView::Config[:sidekiqworker][:collect_backtraces] = true
TraceView::Config[:typhoeus][:collect_backtraces] = true
end

Hi @softcomet,
Is this a stand-alone Rails application? (e.g. No apache or nginx in front?)  If so you should set TraceView::Config[:tracing_mode] to :always.
# Tracing Mode determines when traces should be initiated for incoming requests. Valid
# options are always, through (when using an instrumented Apache or Nginx) and never.
#
# If you're not using an instrumented Apache or Nginx, set this directive to always in
# order to initiate tracing from Ruby.
TraceView::Config[:tracing_mode] = :always

The TraceView::Config[:bunnyconsumer][:controller] and TraceView::Config[:bunnyconsumer][:action] settings are just labels that used for filtering in the TraceView dashboard.  They won't affect if you see any language agents.
Let me know if this helps.  Another option is that you could submit a ticket to AppNeta support and they can look into your account dashboard for more targeted diagnostics.
https://tickets.appneta.com

Hey @softcomet - have you made any progress?  Let me know.  I'd like to help out if needed.

I'm going to close this out but if you ever want to revisit, please let me know!


Secure user

We should probably switch to using a system user without a shell (/usr/bin/nologin) to increase security. Also this is recommended by minio (https://github.com/minio/minio-service#guidelines)

It might also be worth creating it with system: true, and no home dir. Especially if we change the config to live in /etc/minio.


Repairing the Accuracy Loss of Large Numbers and Decimal

Repairing the Accuracy Loss of Large Numbers and Decimal

Hey @JesseWeb thanks for the commit. I'm sorry to accept your PR so late. I neglected this repository almost a year :(  and I'm catch up with all the things.
Hope you're doing well! good bye!


Codespaces lots of error - TypeScript

ADD ISSUE DESCRIPTION HERE
Version: 1.70.0
Commit: da76f93349a72022ca4670c1b84860304616aaa2
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Added Quantity functionality to Cart

Issue:
closes: #8
This PR does:
Now it will not show the duplicate entries instead it will update the quantity of an item.
Price will reflect according to quantity of items.
Also added buttons to increase or decrease quantity of an item.
Screenshot:
Before:

After:

with high level review this looks good.


-external library Apache felix. Changed coordinates to Maven. File na…

…me changed, adjusted. License Apache License v2.0. -notice.txt added based on NOTICE from Felix.
-checked Rat report; no license header in binaries-list (added)
-fixed version in -license.txt
-skimmed through the module, did not notice additional problems

Looks good - comment from #33 about the commit message applies here as well.

Merged this pull request:
https://git-wip-us.apache.org/repos/asf?p=incubator-netbeans.git;a=commit;h=3814587fcc8ae6712840b2d6c78126cb02b641e7


Find out what features are needed most

Hey, @Victorious3, do you have any feature requests?

sigh
So... when I was talking to @Strikingwolf, he said that I should simplify both my code and the external API, however, I am not sure how to do this, as this hasn't got many features yet.


Revert "Revert "Run docker fake intake test with new version of the fakeintake if mod…""

Reverts DataDog/datadog-agent#24586

/merge

/merge


IOU Distance - Recent address list flickers when clearing the address field

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/25974
Action Performed:
Precondition: Have several address in the recent address list.

Launch New Expensify app
Go to + > Request money > Distance > Start
Select an address
Tap on Start again
Highlight the entire address in the address field and delete it

Expected Result:
The recent address list does not flicker
Actual Result:
The recent address list flickers
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.59-4
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/c84b71ba-0c3a-4825-a84c-3b921e8aa8ff
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Not a blocker since it's behind a beta and this is a very minor detail

Also I'm not totally sure this is a bug, the text input changed so it re-rendered the search results. Going to close this


Error when doing SSR. path:/: Cannot read property '_currentElement' of null

I've been trying to deploy Nova to Galaxy, and although I can load the site, SSR is not enabled (at least judging from the source of the page) and I'm getting this error over and over in the logs:
2016-03-30 14:59:55+09:00TypeError: Cannot read property '_currentElement' of null
deh3
2016-03-30 14:59:55+09:00 at [object Object].ReactCompositeComponentMixin._updateRenderedComponent (/app/bundle/programs/server/npm/node_modules/react/lib/ReactCompositeComponent.js:559:52)
deh3
2016-03-30 14:59:55+09:00 at [object Object].ReactCompositeComponentMixin._performComponentUpdate (/app/bundle/programs/server/npm/node_modules/react/lib/ReactCompositeComponent.js:544:10)
deh3
2016-03-30 14:59:55+09:00 at [object Object].ReactCompositeComponentMixin.updateComponent (/app/bundle/programs/server/npm/node_modules/react/lib/ReactCompositeComponent.js:473:12)
deh3
2016-03-30 14:59:55+09:00 at [object Object].ReactCompositeComponentMixin.performUpdateIfNecessary (/app/bundle/programs/server/npm/node_modules/react/lib/ReactCompositeComponent.js:421:12)
deh3
2016-03-30 14:59:55+09:00 at Object.ReactReconciler.performUpdateIfNecessary (/app/bundle/programs/server/npm/node_modules/react/lib/ReactReconciler.js:102:22)
deh3
2016-03-30 14:59:55+09:00 at runBatchedUpdates (/app/bundle/programs/server/npm/node_modules/react/lib/ReactUpdates.js:129:21)
deh3
2016-03-30 14:59:55+09:00 at ReactReconcileTransaction.Mixin.perform (/app/bundle/programs/server/npm/node_modules/react/lib/Transaction.js:136:20)
deh3
2016-03-30 14:59:55+09:00 at ReactUpdatesFlushTransaction.Mixin.perform (/app/bundle/programs/server/npm/node_modules/react/lib/Transaction.js:136:20)
deh3
2016-03-30 14:59:55+09:00 at ReactUpdatesFlushTransaction.assign.perform (/app/bundle/programs/server/npm/node_modules/react/lib/ReactUpdates.js:86:38)
deh3
2016-03-30 14:59:55+09:00 at Object.flushBatchedUpdates (/app/bundle/programs/server/npm/node_modules/react/lib/ReactUpdates.js:147:19)

Any idea what could be causing it? I should add that the app works fine when I run it locally with the same MONGO_URL.

Oh also the db is hosted for free on MongoLab, so it's not very fast. Could SSR be timing out maybe?

Im getting this error also..  No luck figuring it out. @SachaG did you galaxy with any other mongo service and get it to work ?

I ended up getting this error locally as well so it's not related to Galaxy after all. Doesn't seem to affect the app too much though.
Also I haven't been able to run my app on Galaxy because of a memory leak, but I don't know if it's related or not.


Scrollbar is gone

Is it just me?  Is it just Linux?  I don't have a scrollbar in Oni anymore.

Same for me on Windows 10, using the latest commit on master.

Ah yes, this is a regression from some of the react / redux performance work. I have a fix for this, I'll push it up. Sorry about that!

Fixed by #599


why the new version the agent cant connect with chain？

like this

After some consideration, I've found that in the case of agents pre-implemented in LangFlow, they need to be initialized and passed to the AgentExecutor. During this process, the parameters include an LLM chain, which seems to cause issues when executing the flow. Due to this, I am also in the process of creating my own agents.


move fuzzers

Signed-off-by: Ville Aikas<EMAIL_ADDRESS>We currently ship fuzzers in our binaries, this is hoping to remove the last bits of them. Note that I did not inline them into the roundtrip_test because I was thinking that if downstream wants to test them, they can continue to do so.
Addresses:
https://github.com/knative/eventing/issues/4398
https://github.com/knative/serving/issues/9725

With this change, when I bring into eventing (my own branch), we now see:
vaikas@vaikas-a01 eventing % go build ./cmd/controller/main.go
vaikas@vaikas-a01 eventing % go tool nm -size  main  | grep fuzz | grep knative.dev
vaikas@vaikas-a01 eventing %

But the Google fuzzers are still there. But progress:
vaikas@vaikas-a01 eventing % go tool nm -size  main  | grep fuzz
 143dbe0         32 T github.com/google/gofuzz.(*Continue).ExpFloat64
 143dc00         32 T github.com/google/gofuzz.(*Continue).Float32
 143dc20         32 T github.com/google/gofuzz.(*Continue).Float64
 143dc40        128 T github.com/google/gofuzz.(*Continue).Fuzz

Also, down another 13kB ;)
Previously when moved the eventing fuzzers away, our resulting binary was:
61103260
vaikas@vaikas-a01 eventing % ls -l main
-rwxr-xr-x  1 vaikas  staff  61089612 Oct 27 13:26 main

vaikas@vaikas-a01 mink % echo '61103260 61089612 - p' | dc
13648

UT failed with:
false}}; new config &{knative.dev/serving testComponent opencensus<PHONE_NUMBER> <nil> <nil> localhost:12345 false 0 false   {   false}}
    --- FAIL: TestMetricsExport/OpenCensus (4.04s)
        resource_view_test.go:439: Timeout reading input
        resource_view_test.go:445: Unexpected OpenCensus exports (-want +got):
              []metrics.metricExtract(Inverse(Sort, []string{
              	"knative.dev/serving/testComponent/global_export_counts<>:2",
              	"knative.dev/serving/testComponent/resource_global_export_count<>:2",
              	`knative.dev/serving/testComponent/testing/value<project="p1",rev`...,
            - 	`knative.dev/serving/testComponent/testing/value<project="p1",revision="r2">:1`,
              }))
    logger.go:130: 2020-10-27T11:42:23.560Z	INFO	metrics/exporter.go:155	Flushing the existing exporter before setting up the new exporter.
    logger.go:130: 2020-10-27T11:42:23.562Z	INFO	metrics/stackdriver_exporter.go:203	Created Opencensus Stackdriver exporter with config &{knative.dev/serving testComponent stackdriver<PHONE_NUMBER> 0x22f01a0 <nil>  false 0 true knative.dev/serving/testComponent custom.googleapis.com/knative.dev/serving/testComponent {   false}}
    logger.go:130: 2020-10-27T11:42:23.562Z	INFO	metrics/exporter.go:168	Successfully updated the metrics exporter; old config: &{knative.dev/serving testComponent opencensus<PHONE_NUMBER> <nil> <nil> localhost:12345 false 0 false   {   false}}; new config &{knative.dev/serving testComponent stackdriver<PHONE_NUMBER> 0x22f01a0 <nil>  false 0 true knative.dev/serving/testComponent custom.googleapis.com/knative.dev/serving/testComponent {   false}}
FAIL

I hae a hard time it's related to this, is this flaky test?

/test pull-knative-pkg-unit-tests

Failed again with this:
    --- FAIL: TestMetricsExport/OpenCensus (4.03s)
        resource_view_test.go:439: Timeout reading input
        resource_view_test.go:445: Unexpected OpenCensus exports (-want +got):
              []metrics.metricExtract(Inverse(Sort, []string{
              	"knative.dev/serving/testComponent/global_export_counts<>:2",
              	"knative.dev/serving/testComponent/resource_global_export_count<>:2",
              	`knative.dev/serving/testComponent/testing/value<project="p1",rev`...,
            - 	`knative.dev/serving/testComponent/testing/value<project="p1",revision="r2">:1`,
              }))
    logger.go:130: 2020-10-27T11:50:08.694Z	INFO	metrics/exporter.go:155	Flushing the existing exporter before setting up the new exporter.
    logger.go:130: 2020-10-27T11:50:08.695Z	INFO	metrics/stackdriver_exporter.go:203	Created Opencensus Stackdriver exporter with config &{knative.dev/serving testComponent stackdriver<PHONE_NUMBER> 0x22f01a0 <nil>  false 0 true knative.dev/serving/testComponent custom.googleapis.com/knative.dev/serving/testComponent {   false}}
    logger.go:130: 2020-10-27T11:50:08.695Z	INFO	metrics/exporter.go:168	Successfully updated the metrics exporter; old config: &{knative.dev/serving testComponent opencensus<PHONE_NUMBER> <nil> <nil> localhost:12345 false 0 false   {   false}}; new config &{knative.dev/serving testComponent stackdriver<PHONE_NUMBER> 0x22f01a0 <nil>  false 0 true knative.dev/serving/testComponent custom.googleapis.com/knative.dev/serving/testComponent {   false}}
FAIL

/test pull-knative-pkg-unit-tests


Docs feature request: When should Fields be used?

Fields is the only part of the documentation I've noticed, where the use case is not particularly explained - it is mostly clear this feature shouldn't be used!
It is perhaps this non-clarity that led a developer on my project to use Fields to achieve conditional disabling of form fields even though this use case alone can be covered by formValueSelector as mentioned in #1960, or in the docs example. (Further, they also looped to render a bunch of Field components inside Fields - that's another story, but) I do think the documentation could be more clear here about the 'raison d'être' for Fields.
If I understand correctly, I'd wonder if for many people, the following may be a sufficient Fields-like implementation:
connect(state, ownProps) => (
  ownProps.names.reduce((acc, name) => {
    acc[name] = selector(state, name)
    return acc
  },
  {})
)
// (+ corresponding lifecycle methods).

Why does Fields exist? How (often) does it differ in practice from providing inter-field value-awareness as in the above example? Might the above case be worthwhile to add to the docs (essentially a props configurable version of the existing example)?

Going to close this one out. To anyone searching the issues, this would be my advice:
Fields is powerful because it gives you everything. This is ok for small, trivial cases, e.g. combining 2 fields and one error label, but generally, if the use cases are larger than that, the problem can most likely be re-expressed in another way and you should re-architect your components.
Examples:
If you are looking to Fields because you want:

to do conditional field disabling => use getFormValues selector and Field instead.
you want all your fields to have similar wrapping (which requires meta) => use an HOC to wrap all your components (outside of the component definition).
One small area of your form has say 2 input values, but otherwise is essentially one input component (e.g. say departure date, return date) => Fields can be a great option here. The performance won't be an issue.

Thanks for that, @danielrob!


Set $RINGO_HOME in Homebrew package

The RINGO_HOME environment variable is important for installing packages with ringo-admin. It must be present to run Ringo smoothly.

Afais it's already correctly set, that's the content of /usr/local/bin/ringo after brew install ringojs:
#!/bin/bash
RINGO_HOME="/usr/local/Cellar/ringojs/2.0.0_1/libexec" JAVA_HOME="${JAVA_HOME:-/usr/local/opt/openjdk/libexec/openjdk.jdk/Contents/Home}" exec "/usr/local/Cellar/ringojs/2.0.0_1/libexec/bin/ringo"  "$@"


[LW-10833] - Shared wallet schema and examples

Description
This pull request introduces a comprehensive JSON schema for the creation of shared wallets, along with relevant examples. The schema is designed to facilitate the coordination of transactions in a shared wallet environment by defining a clear structure for the JSON files exchanged between cosigners.
Changes Made
JSON Schema for Shared Wallet Creation:
•	A new JSON schema has been defined to structure the creation of shared wallets.
•	The schema includes definitions for version, metadata, participants, and NativeScript.
Schema Details:
•	Version: Specifies the schema version.
•	Metadata: Contains information such as the creation date, notes, the creator’s public key, and the target chain ID.
•	Participants: Lists the participants in the shared wallet, including their names and corresponding Ed25519KeyHash.
•	NativeScript: Defines the script structure, which can include ScriptAll, ScriptAny, or ScriptNOfK, specifying the conditions under which the shared wallet transactions are valid.
Motivation
The introduction of this schema aims to standardize the process of creating and managing shared wallets within the Cardano ecosystem. By providing a clear and validated structure for the necessary JSON files, we aim to enhance interoperability, reduce errors, and streamline the coordination of transactions between cosigners.

Allure Report
allure-report-publisher generated test report!

smokeTests: ✅ test report for 3f975734

passed
failed
skipped
flaky
total
result

Total
33
0
0
0
33
✅


Custom marker icon on csv?

Is there any way to specify custom marker as defined in csv?
The feature already available in:
https://github.com/joker-x/Leaflet.geoCSV
http://joker-x.github.io/Leaflet.geoCSV/example/icons/index.html

Nope, as documented, custom layers are possible but aren't specific to any file format.


Move set owner to null

Bug report
While upgrading our application with the latest Docker files, we encountered a few issues:

A change of behavior where the object is no longer updated. This is cover in issues #359 and #427. While a comment mentions that "conceptually objects are immutable", functionally speaking, they are moved. A philosophical question one would argue but the function is called moved, not remove + upload. This change of behavior breaks our trigger functions but we could deal with it.

What really concern us in this issue is moving an existing file. With the upload call, the owner field is correctly associated to the user of the supabase client. However, the move call set the owner field to null. For this, we have no workaround and shall be treated as a bug.

[x] I confirm this is a bug with Supabase, not with my own application.

[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
When using supabase.storage.from(...).move, the owner field is set to null.
To Reproduce
This is how to reproduce the bug
await Promise.all(files.map( async file => {
  Promise.resolve()
  .then(async() => {
    const { data, error } = await supabaseClient
      .storage.from('kb_document_assets')
      .upload(
          `staging/${user.id}/${file.name}`,
          file
        )
    console.log('upload', data, error)
    return data
  })
  .then(async(upload) => {
    const { data, error } = await supabaseClient
      .storage.from('kb_document_assets')
      .move(
          upload.path,
          upload.path+'.test'
        )
    console.log('move', data, error)
  })
}))

From the studio console, the owner field is now null.
Expected behavior
The owner field should be associated with the Supabase client authenticated user.
System information
Our packages.json file includes
{...
    "@supabase/auth-helpers-nextjs": "^0.9.0",
    "@supabase/auth-helpers-react": "^0.4.2",
    "@supabase/ssr": "^0.1.0",
    "@supabase/supabase-js": "^2.39.3",
...}

Here are the container image versions:

supabase/studio:20240101-8e4a094
kong:2.8.1
supabase/gotrue:v2.132.3
postgrest/postgrest:v12.0.1
supabase/realtime:v2.25.50
supabase/storage-api:v0.43.11
supabase/postgres-meta:v0.75.0
supabase/postgres:<IP_ADDRESS>

Additional context
We are using the file storage backend.
I do not think my policy is to blame, it is also working fine with the previous version (around march 2023):
CREATE POLICY "Project assets are administered with document access."
  ON "storage"."objects"
  AS PERMISSIVE FOR ALL TO public
  USING (
    bucket_id = 'kb_document_assets' and auth.uid() IS NOT NULL
  )
  WITH CHECK (
    bucket_id = 'kb_document_assets' and auth.uid() IS NOT NULL
  );

This is now fixed


Suggested reword in 01_IntelligentPerformance.md for sql2019lab

https://github.com/microsoft/sqlworkshops/blob/rgward/sql2019lab/01_IntelligentPerformance.md
Suggested reword in 01_IntelligentPerformance.md
In the guide for getting set up with Azure Data Studio notebooks, the instructions say
"Use the File menu to open up the iqp_tablevariabledeferred.ipynb notebook and go through all the steps."
I might instead recommend something like….
'Use the File > Open Folder menu to open up the folder sql2019lab. Now, in Azure Data Studio, you can select the piece of paper icon on the left-hand taskbar to navigate through the folder. As you go through the labs, you can find the .ipynb files in their respective folders (e.g. the notebook file for 01_IntelligentPerformance is in sql2019lab/01_IntelligentPerformance/iqp/iqp_tablevariabledeferred.ipynb)."
Why?
That way, in the following labs, they don't have to keep opening each file, they can just navigate using the built in file explorer.
@rgward

Great suggestion. I've used your suggestion and made changes like this for Module 1, 3, and 4,  Please pull latest from rgward branch and let me know is this works. If you agree, then please close out this issue

Nice! I like the screenshot too.  One thing -
"open up the iqp_tablevariabledeferred.ipynb notebook and go through all the steps> You can now use Azure Data Studio explorer to open up a notebook or script without exiting the tool." just a ">" typo instead of a period in Module 1.

Feel free to close the issue after you see the note about ">" typo. Wasn't sure if I closed it if you would still get the notification. Thanks.

Crud, I thought I caught those. I had them fixed in 3 and 4 but not 1. Thanks for the catch. Fixed now so closing


Dates in filenames are recognized as Due Dates

Dear @roovo first of all thank you for the great work, I really like using it to build a combination of bullet journaling and getting things done in Obsidian :)
I use Daily notes which have simply a YYYY-MM-DD formatted date as filename.
I collect all kind of notes and tasks in these daily notes. Some tasks have a due date assigned others do not and are e.g. tagged "#somewhen".
CardBoard seems to assign the date from the filename to the tasks without date, which renders it rather useless for me currently as the whole today section is spammed with tasks that actually have no date and are simply recorded to do them maybe sometime in the future.
I use the current version of your plugin and additionally the Tasks Plugin, as well as the Dataview Plugin.
Example:
In a file named 2023-02-02:
- [ ] Task 1 #projectA #next 📅 2023-02-10
- [ ] Task 2 #projectA #somewhen

TaskBoard shows them like this (on the 1st of Feb.)

Ah just realized I apparently was searching for the wrong keywords. It is already in progress for 0.7.2 (#106 )
But now it is a bug, so it might get a high priority? 😁
So anyway:

Hiya - and thanks ....yep - hope to look at this over the weekend.  My plan is to:

add an option for date boards to ignore filename dates
make it so if you put @due(none) on the line of a task it will ignore the date for that single task.

Not sure if I'll have time to get it finished this weekend, but I'll do my best and it shouldn't be too much after if I don't :)
Thanks again.  I'll leave this issue open till I've done it so you can keep track easily!

current plan is to:

add an option to global settings to not use daily note file names when setting the due date for tasks. I was initially thinking of doing this on a per-board basis, but that could lead to cards appearing on different boards with different due dates which doesn't feel desirable.
allow https://github.com/Due(none) to be placed on a task line to nullify the due date derived from the file name. This is needed for drag and drop so that a task in a daily note can be moved to the undated column.

This makes sense to me :)

...and version 0.7.2 is now out which supports this :)  There's a new global setting, plus I've added support for @due(none).  Any issues with it, just let me know.  Many thanks :)

Works like a charm, tank you!


Support GraphQL via AppSync

Thoughts?  Some of it can be done via Terraform but GraphQL is more application code than infrastructure.
Any plans to have plugins/extensions to Apex?

I haven't tried AppSync yet but I love the sound of it in general, hard to say if it would fit well in here or not but hopefully I'll have some time to investigate that in the next few months

Maybe helpful: https://github.com/sid88in/serverless-appsync-plugin


Strange javascript resources

Just logging this before I filter them out from my crawl:
 WARN | 404 http://localhost:3000/assets/js/vendor/%29.revokeObjectURL%28file
 WARN | 404 http://localhost:3000/assets/js/vendor/blob
 WARN | 404 http://localhost:3000/assets/js/vendor/%29.createObjectURL%28blob

Generated by this file:
https://github.com/eligrey/FileSaver.js/blob/master/FileSaver.js
It appears to me that possibly this is an error with the discover resources logic for javascript files.

@cgiffard's philosophy has been to keep simplecrawler's discovery mechanism "dumb", with the reasoning that it's better for the crawler to make a few junk requests than for it to miss some stuff. So by default, the discoverResources method will pick up some garbage, the idea is to make it easy to replace this logic with more a more advanced discovery function, tailored for the dev's specific needs.
If there is a specific, non-huge improvement to one of the default discoverRegex's, feel free to submit a PR, otherwise, maybe the way to go in your case would be to override the discoverResources method? When I've worked with simplecrawler, I've had a lot of success using cheerio to parse pages and do a more refined extraction of resources!

Thanks, I just got a feel for that from reading the base href issue.
Now I have my pattern matching support in place, it's pretty easy for me to ignore these sorts of things without implementing discoverResources.
Cheers for the tip on cheerio, looks quite nice :)
Closing as expected behaviour.

For the record it looks like these patterns:
        /\s?url\((["']).*?\1\)/ig,
        /\s?url\([^"'].*?\)/ig,

For CSS I imagine, I think we could remove the i flag and be safe, it then wouldn't match the junk in this issue and I don't know of anyone that uppercases url() in CSS files and likely uppercase is invalid CSS anyhow (I would have to check).
What do you think?

Spec is quite specific:
https://www.w3.org/TR/CSS2/syndata.html#uri
I know css selectors are case-insensitive but I think we could be safe to remove those i flags, @cgiffard - what do you think?

Just confirmed that removing the i flag does indeed prevent those junk requests.

There are actually lots of inline JS scripts around which have code like openURL("http://foo/bar.txt"). That regex is designed to catch those — the philosophy being that overly broad matching (and then filtering) is better than missing resources.
It was fascinating to see the outcome of this philosophy at work when scanning inside binary files (like Microsoft Office documents) actually yielded real URL results that wouldn't have been found otherwise (and a whole lot of junk, but I figured it was a reasonable tradeoff.)
I'm inclined to leave the regex match as it is, but I'd welcome discussion.

That's fine with me, thanks for the clarification.
Would it not make sense then for simplecrawler to provide some discoverResources strategies rather than have developers constantly re-inventing the wheel? These could be external npm packages.
For example, I think my use case is likely the most common, I am only interested in valid links within the HTML and CSS documents.
Question: what would be the best way to disable discovering resources in javascript files without writing a custom discoverResources?

Or alternatively a separate pattern for the scenario you describe and then expose an API for modifying (adding and deleting) from the default list of patterns?
That would solve this issue for me without the need to write discoverResources which seems like overkill for this scenario.

Maybe named patterns in an object that is later flattened to an array?

Good suggestion, and please feel absolutely welcome to provide a discoverResources function that can be published as an external module. Then you could do something as simple as:
crawler.discoverResources = require("nice-link-discovery");

(Or similar.)

Or alternatively a separate pattern for the scenario you describe and then expose an API for modifying (adding and deleting) from the default list of patterns?

Maybe I'm misunderstanding what you mean here, but the discoverRegex array is public and documented, so operating on that array would be the API for modifying the list of discovery patterns :)

Question: what would be the best way to disable discovering resources in javascript files without writing a custom discoverResources?

crawler.supportedMimeTypes and crawler.downloadUnsupported can be used to avoid downloading javascript resources. If you'd rather download the files, but not look for resources in them, you could either listen for the discoverycomplete event, check the queueItem's Content-Type and mutate the resources array as you want, or you could monkey patch the discoverResources method with a method that only calls the original method when the Content-Type is the one you want, or you could swap out the entire discoverResources method (it's quite a simple method, really).

It's my preference to consider the current code complete for this use case, so I'm closing this issue. Feel free to reopen it if you vehemently disagree. :)

No worries for me, I'll implement discoverResources (later). Thanks for your time.


App Service Architecture v0.2

Develop app workflow:
1. Create a new app

Click create button
Create or select a repo (An empty repo storage without index.yaml is able to be registered to OpenPitrix)
Upload app config package, validate automatically in the background. The package will be uploaded to the repo automatically and generate the first version of the app.
Developer can download the package.

2. Create a new app version in an exist app.

Show the repo which cannot be changed.
List all the exist app version on the left side.
Upload app config package, generate new version when validate succeeded.

Publish app workflow:
app.status: draft/active/suspended/deleted
app_version.status: draft/submitted/passed/rejected/active/suspended/deleted

If an app_version's status is active, the app is active

active means the app is published to public or private market.

If publish app version to public market need admin to review, else if publish app version to private market, the app version's status change to active immediately.

API for user:

DescribeApps
DescribeAppVersions

API for developer:

ModifyAppVersion
SubmitAppVersion
CancelAppVersion
ReleaseAppVersion
DeleteAppVersion

API for admin:

PassAppVersion
RejectAppVersion
SuspendAppVersion

App version status diagram:

Link


Better MD editor

https://github.com/marktext/muya
This project is awesome all around.
Muya is the best embeddable md editor out there.
2 * awesome = ? -> 😊 :+1:

You can try out the marktext app to check it's UX and look and feel. Muya is an outfactoring of the MD editor.

Interesting! Currently we have an Ace binding implemented which is boring but well trod.
I see it says - "Muya is still under development and should not be used for production" ... OpenMemex is guilty of overcharging our novelty budget as is :) but I'll check out marktext app and see how it feels.

If I had to guess, marktext might be already using muya. Or shortly might. So "not in production" might be a bit of an expectation management thing rather than being accurate : 😊

Cool - I think feasibility might come down to how easy it the API makes it to integrate a rust binding. Ace turned out to be relatively gentle even for a non-rust expert like myself (still pre-alpha, see https://github.com/austinvhuang/openmemex/blob/master/frontend/src/ace.rs and https://github.com/austinvhuang/openmemex/blob/master/frontend/static/ace_bindings.js for both sides of the FFI).
Would be happy to take a PR if you or anyone is interested in taking a stab too. Not sure if you're in the discord already but feel free to come chat more there https://discord.gg/mGy29Smv4g


.input-group must not contain extraneous children

An .input-group can only have exactly 2 or 3 direct children. These children must be a .form-control preceded and/or followed by an addon.
Refs https://github.com/twbs/bootstrap/issues/16540

@cvrebert is the 2 / 3 children due to 1 input + 1–2 possible .input-group-addon or is there a different reason for this?

Yes, except the add-on can also be an .input-group-btn (and maybe some other possibility; check the input group docs).

Do we even need to confirm .form-control and .input-group-* elements are in the children, even though it's trivial?
Furthermore, I think the cases of too few and too many might need to be separate lint checks.
var validElements = ['.input-group-btn', '.input-group-addon', '.form-control'].join(',');
var childrenLength = $('.input-group').children().not(validElements).length;

if (childrenLength > 3) {
  return '`.input-group` must not contain extraneous children. These children must be a `.form-control` preceded or followed by an addon.';
}

if (childrenLength < 2) {
  return '`.input-group` must contain at least two children. These children must be a `.form-control` preceded or followed by an addon.';
}


Refresh the Zipkin observability tutorial

Description
Please explain the changes you've made
Based on https://github.com/dapr/quickstarts/issues/932 I have made minor issues to the observability tutorial.
Issue reference
We strive to have all PRs being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
#932
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] The quickstart code compiles correctly
[ ] You've tested new builds of the quickstart if you changed quickstart code
[x] You've updated the quickstart's README if necessary
[ ] If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

For completeness, I successfully ran through the tutorial with Dapr 1.13 on Kubernetes.

@holopin-bot @pdebruin Thanks Pieter!


[web] wierd stuff in amount column in charts

1E0?

Could be due to disabling of assistive technologies? Wild guess

Or maybe the fact that i upgraded jfreechart

no idea why it got like this, but after rechecking, its gone. Closing


Are we moving towards including error messages in response body?

I thought we were moving away from including any errors in the response body, but all encoders provided by erraux involve marshalling the error as cause into the response body:
default behavior:
https://github.com/xmidt-org/httpaux/blob/9f219068a591cf61a2c8deb156240876d76c9cef/erraux/encoder.go#L299-L305
As encoder:
https://github.com/xmidt-org/httpaux/blob/9f219068a591cf61a2c8deb156240876d76c9cef/erraux/encoder.go#L172-L173
https://github.com/xmidt-org/httpaux/blob/9f219068a591cf61a2c8deb156240876d76c9cef/erraux/encoder.go#L162
Is encoder:
https://github.com/xmidt-org/httpaux/blob/9f219068a591cf61a2c8deb156240876d76c9cef/erraux/encoder.go#L59
https://github.com/xmidt-org/httpaux/blob/9f219068a591cf61a2c8deb156240876d76c9cef/erraux/encoder.go#L112
Is this the plan for our API responses moving forward?

It was, at one point, our collective deliberate decision to remove bodies from any HTTP errors.  This was largely in part to train our users to look at response codes rather than error bodies in any form when things went sideways.  Unless this decision has changed, we shouldn't change the behavior of the software as it is deployed in our environment.  If this behavior is easily changed via configuration, I'm all for adding the feature.
Ultimately though, this is a pointy hat boss decision.

Perhaps the confusion is due to the fact that this repo is in xmidt-org?  My intention was for this to be a general purpose library, not something specific to the xmidt or webpa servers.  Would it make sense to move this library somewhere else?
I get (but was not part of the collective) that we do this on xmidt.  I would disagree that we want to ban all response bodies on errors on any project.  We should train our clients to read and adhere to the specification.
An example of an error response body being useful is scrivener.  It returns a 400 to indicate that the client did not send the correct name/value pairs for a template.  But which names were missing?  Scrivener indicates that in the response body.  If scrivener were not allowed to return a response body, then a client wouldn't be able to take remedial action which would likely include resorting to slack or filing a ticket.  The engineer implementing the codepath to hydrate a template won't always be on the same team as the content producer who authored the template.
Headers are inappropriate to communicate errors, as indicated by the RFC.  Among other reasons, headers are restricted to 7-bit ASCII and the error may include Unicode values.

Yeah, I'd vote for making it configurable as well. It'll help to at least start adopting the library and grow from there.
FYI: Argus is reporting error messages through a header today but we can change that in later versions. We control the messages though and so far it's all ASCII.

What's a scrivener?  ;-)
@johnabass : I agree with you on all points.  I just want to make sure we don't change existing behavior.  Making the behavior configurable would satisfy both goals.

I'm in favor of making it configurable as well.  @JC000 summarized my position pretty well here: https://github.com/xmidt-org/httpaux/issues/36#issuecomment-811570460
While "SHOULD" is well meaning, when failure responses start containing payloads, consumers of the API may start decoding them & using them.  The payload becomes a poorly documented enforced API as sorts.  It becomes more fun when content-type and assorted accept headers also force the payload to be something you may not want.

To clarify my "dislike" ... I don't like getting "noise" defects because one layer of a system returns an 400 error as applicatoin/json with JSON vs. another section of code (maybe something we don't control) returns a simple text string for a different 400 error.  If we can normalize so the same response & format/etc can be more uniformly supported - great, I'm all for that.

One other thing we might need to watch out for in our services is sending unfiltered errors to clients with information we don't want to expose, like in this argus issue:
https://github.com/xmidt-org/argus/issues/30


Assertion error on ingestion

thread 'tokio-runtime-worker' panicked at src/state/mod.rs:1004:17:
assertion `left == right` failed
  left: Some(37271)
 right: Some(37261)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace```

https://github.com/Granola-Team/mina-indexer/blob/main/rust/src/state/mod.rs#L1004

Do we have evidence that this happens with consistent db versions?

I'll add some more context to start

No, this could indeed have been due to failure to update database versions.

See also #1246

@Isaac-DeFrain I'm comfortable closing this in favour of #1246, for now. Unless you know what is wrong from the code (you can see that the assertion should indeed not always hold), then I suggest closing.


Some visualization layers need to have a pop up for useability

Some of the visualization layers are unusable without their pop-up information. The pop up fields are listed at the bottom of their links. Is this completely impossible for the tool to do?

Baseline Fish Habitat
Upstream habitat

From Slack discussion with Ryan:
as for whether we can implement them - I don't see that fitting in, as there is too much vector data to query over the API at one time
we could look into making them clickable: user clicks on the green, triggers an API request for which feature is at that point (well, tiny bbox) and return the values
however, we're looking at 4+ hours of work.
Another option - they host on MapBox and use vector tiles
Pros: No feature limit like ESRI API, also fast and light-weight (no additional calls needed)
Cons: Subject to same crappy missing bits that we see on some of our barrier layers.
and would need to be updated in Mapbox, instead of pulling directly from service.

Jocelyn will try to get shapefiles from client; Ryan will try to pull in while working on other visualization stuff.

Response from Brett:
"As far as the BFH and the Upstream Habitat layers, I’m not sure the pop-ups are absolutely necessary.  They are reference layers which show stream reaches of known and potential anadromy.  I’d prefer to leave them as being sourced directly from the existing REST endpoints for now and skip the pop-ups.  Please let me know if you have concerns with this approach."


Unable to install plugin

Hi,
I've done the following to use this plugin, however, the old plugin is used(this) instead of yours, is this as expected?

cordova plugin rm cordova-plugin-wkwebviewxhrfix
cordova plugin add https://github.com/AraHovakimyan/cordova-plugin-wkwebviewxhrfix

App -> platforms -> ios -> App -> plugins

Would need your advice on this, thank you.

Hi @benjamincxw
I think that behavior is bug npm. For me works correctly.
I can only suggest options that can solve this problem.
You can check the package.json file in your project, maybe this file still contains a record containing the plugin name old still.

Also If your project has the file package-lock.json, try to delete this file and then install it again, this file will be generated again.
Maybe the problem is due to the fact that there are still entries in the old form in this file.

If it helps please let me know.

Hi @benjamincxw
I think that behavior is bug npm. For me works correctly.
I can only suggest options that can solve this problem.
You can check the package-lock.json file in your project, maybe this file still contains a record containing the plugin name old still.

If your project has the file package-lock.json, try to delete this file and then install it again, this file will be generated again.
Maybe the problem is due to the fact that there are still entries in the old form in this file.

If it helps let me know
Thanks.

Try to use this fork
cordova plugin add https://github.com/IsraelHikingMap/cordova-plugin-wkwebviewxhrfix
Please let me know if this approach will help you to fix your issue.
Based on discussion
https://github.com/AraHovakimyan/cordova-plugin-wkwebviewxhrfix/issues/5#issuecomment-1162193487


discussion(docker): Build envd own base images

We are using docker.io/python:3.8 as default image for CPU. But it is too large.
Maybe we can refer to https://github.com/aws/aws-lambda-base-images to set up our own base python image.

I am closing the issue since we decided to use the docker hub currently.


Assert all #[wasm_bindgen] attributes are used by default

An off-by-default option for this was introduced in https://github.com/rustwasm/wasm-bindgen/pull/1055, and it's a breaking change to turn it on, so this tracks enabling it eventually!

This one can probably be closed now too.

Closing it as per previous comment


Error when viewing external freight customers

Reported by Robert Halvarsson.

Fixed in release 1.6.8.


chore: delete command namespace

:bug: Fixes bug where deleting by name fails if current path has no initialized function.
:gift: Adds namespace test to delete command
:broom: Moves namespace flag into delete command for

Better help text
Easier testing

:broom: Sets static default namespace for flag to "default"

/kind techdebt

@lkingland unit test running with current main merged in are failing.

Assert need adjustment and/or you need also rebase.

/approve
/lgtm

@lance PTAL

/lgtm

/approve

/lgtm
/approve


encoding/json: Add Encoder.Indent

This is a feature request for encoding/json post-Go 1.2

It would be great if json.Encoder had an Indent method like xml.Encoder does. Currently
the only way to get indented JSON is to use MarshalIndent but that requires an
intermediate []byte.

+1 !

Any word on this? I might take a stab at since I need it at the moment.

Stab away.

any news here? I would also need it :+1:

No news.

I'm going to try to do this for 1.7.


Updated changelog and fixed toxiproxy docs

@dvlato did you say merging the CHANGELOG back to master could cause some issues with automated release script?


fix: convertToArray handle undefined cases

This bug was introduced in the version 2.0.21.
Since loops are expecting an array to iterate, it throws an error when you try to iterate undefined
The change just ensure undefined or any other nully value is treated properly
convertToArray(undefined)  → []

Hi @Kikobeats,
Thanks so much for catching this and creating a PR!
Merged & published to npm in version 2.0.22.

Thanks a lot!


Privacy Issue with Sandstorm Edition - Export

When exporting an image from the Sandstorm version of draw.io, the output URL is https://exp.draw.io/ImageExport4/export
This presents a security issue and breach of usual Sandstorm standards, where all I/O should happen to/from the Sandstorm Server.
To reproduce:
File >> Export As >> Advanced
Export and select "Open in new window"
The export is shown originating from the exp.draw.io domain

@zeigerpuppy What browser are you using?
I discussed this issue with David during app review, and I believe he said that it "shouldn't" process externally on Chrome or Firefox. (I was testing on Edge.)

The Advanced dialog uses the external service, while the direct export options in the menu use client-side image generation in Chrome, Firefox and Edge.

I believe the ideal situation would be that for a self-hosted install of draw.io (whether Sandstorm or otherwise), ideally it should offer a warning dialog when exporting data to an external service. Presumably of course, with the option to skip the warning in the future.

@zeigerpuppy Why are you using the Advanced image export and not on of the direct export options btw?

I usually use the advanced export when needing to set the resolution of a PNG export


Throw exact error when failing to fetch extension lists

Describe your suggested feature
Two part suggestion:

Be able to specify which custom repo is failing to fetch extension list
Be able to specify what the exact http error is, if any. Failing to fetch ext list could be a 429 or some other error and it's kinda difficult to ascertain what/where went wrong
1.5. Add an extra rate limit to github network client to avoid getting ratelimited while fetching from all custom repos

Other details
Still tryna figure out why my tachisy fails to fetch extension list. A VPN always works so I think knowing http error code + which custom repo failed might help in that.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.9.3.
[X] I will fill out all of the requested information in this form.

To add to this (instead of making a separate request): The app stops checking other (custom) repo for extension lists if one of them fails. The error currently doesn't really tell which custom repo failed


Spelling mistake

cnc-installation.yaml has spelling mistake. Networking is spelling Netwroking. Tried to edit myself but dont have permissions to this repo.
Eric

@ericrife fixed, thank you
https://github.com/NVIDIA/cloud-native-core/blob/master/playbooks/cnc-installation.yaml#L400