text:
Joining a node into a weave network when the node already has a defined weave interface does not cause any reconfiguration, causing pods to become unrouteable

What you expected to happen?
When adding new nodes into a weave network I expect them to be assigned a unique IP for the weave bridge interface. I also expect to be able to perform weave reset from within a weavenet container.
What happened?
This is on a kubernetes cluster consisting of 4 nodes (1 control and 3 workers). weavenet is installed as the CNI.
I had a node that already had a weave interface defined and I added it to an existing weave network cluster, weave reached quorum and made links successfully between all nodes, however it did not notice that two nodes shared the same IP address. This meant that routing traffic to any pods living on either of those nodes resulted in 50/50 failure rate.
How to reproduce it?
Create a single node K8S cluster (node 1), by installing kubernetes, and installing weave as the CNI.
kubeadm init
kubeadm apply -f (deployment file for weave: image: weaveworks/weave-kube:2.5.0 & host network : true)
All pods go to RUNNING state and see the weave interface when you run 'ifconfig weave'
Repeat on another node (node 2)
Note: Both nodes default to weave bridge IP: 10.32.0.1
Bring node 2 down and clean it:
kubeadm reset
Use the join command on node 2 to join the existing cluster.
On node 1:
kubeadm token create --print-join-command
On node 2:

kubectl get nodes - will confirm that node 2 has joined the cluster.
ifconfig weave on both nodes confirms that they both have the same IP address still.
Log in to the weave container to verify that weavenet connections have been made:
$ sudo kubectl exec -ti -nkube-system weave-net-stfns -c weave sh
/home/weave # ./weave --local status
    Version: 2.5.0 (version 2.6.0 available - please upgrade!)

    Service: router
   Protocol: weave 1..2
       Name: 72:a0:a9:f7:52:26(node1)
 Encryption: disabled

PeerDiscovery: enabled
Targets: 1
Connections: 2 (1 established, 1 failed)
Peers: 2 (with 2 established connections)
TrustedSubnets: none
    Service: ipam
     Status: ready
      Range: 10.32.0.0/12

DefaultSubnet: 10.32.0.0/12
/home/weave # ./weave --local status connections
<- 10.250.130.7:56006    established fastdp a2:37:ac:ae:1d:ef(node2) mtu=1376
-> 10.250.130.2:6783     failed      cannot connect to ourself, retry: never
From this point onwards you can validate (using something like kuberang) that connectivity into pods within the weave network from outside the network (e.g. node 1 or node 2, or any upstream network connected node) is unstable and will result in timeouts/failures. Eventually it causes coredns to crash.
Anything else we need to know?
Tests have been run on VMWare and AWS EC2. In both cases this is a Kubernetes cluster.
We do not install weave binary into the command line of the node. It should only run as a container. Installing weave and running weave reset from the command line of the node itself is a workaround we shouldn't be using. Note: I can not seem to find a way of running weave reset from within the weave-net container - otherwise I might use that as part of process of decommissioning a node.
Versions:
/home/weave # ./weave --local version
weave 2.5.0
$ sudo docker version
Client:
Version:           18.09.5
API version:       1.39
Go version:        go1.10.8
Git commit:        e8ff056
Built:             Thu Apr 11 04:43:34 2019
OS/Arch:           linux/amd64
Experimental:      false
Server: Docker Engine - Community
Engine:
Version:          18.09.5
API version:      1.39 (minimum version 1.12)
Go version:       go1.10.8
Git commit:       e8ff056
Built:            Thu Apr 11 04:13:40 2019
OS/Arch:          linux/amd64
Experimental:     false
$ uname -a
Linux node2 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
$ sudo kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:32:14Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

## Logs:

$ sudo kubectl logs -n kube-system weave-net-zqd49 weave
DEBU: 2019/12/05 11:27:55.957155 [kube-peers] Checking peer "a2:37:ac:ae:1d:ef" against list &{[{72:a0:a9:f7:52:26 node1}]}
Peer not in list; removing persisted data
INFO: 2019/12/05 11:27:56.404358 Command line options: map[docker-api: nickname:node2 no-dns:true datapath:datapath ipalloc-range:10.32.0.0/12 http-addr:127.0.0.1:6784 ipalloc-init:consensus=2 name:a2:37:ac:ae:1d:ef conn-limit:100 db-prefix:/weavedb/weave-net metrics-addr:0.0.0.0:6782 port:6783 expect-npc:true host-root:/host]
INFO: 2019/12/05 11:27:56.404670 weave  2.5.0
INFO: 2019/12/05 11:27:56.412281 failed to create weave-test-commentf7c03267; disabling comment support
INFO: 2019/12/05 11:27:56.495587 Re-exposing 10.32.0.1/12 on bridge "weave"
INFO: 2019/12/05 11:27:56.523625 Bridge type is bridged_fastdp
INFO: 2019/12/05 11:27:56.523699 Communication between peers is unencrypted.
INFO: 2019/12/05 11:27:56.540895 Our name is a2:37:ac:ae:1d:ef(node2)
INFO: 2019/12/05 11:27:56.541031 Launch detected - using supplied peer list: [10.250.130.2 10.250.130.7]
INFO: 2019/12/05 11:27:56.576822 Checking for pre-existing addresses on weave bridge
INFO: 2019/12/05 11:27:56.577274 weave bridge has address 10.32.0.1/12
INFO: 2019/12/05 11:27:56.604256 [allocator a2:37:ac:ae:1d:ef] No valid persisted data
INFO: 2019/12/05 11:27:56.623474 [allocator a2:37:ac:ae:1d:ef] Initialising via deferred consensus
INFO: 2019/12/05 11:27:56.623763 Sniffing traffic on datapath (via ODP)
INFO: 2019/12/05 11:27:56.624668 ->[10.250.130.2:6783] attempting connection
INFO: 2019/12/05 11:27:56.625159 ->[10.250.130.7:6783] attempting connection
INFO: 2019/12/05 11:27:56.625840 ->[10.250.130.7:54862] connection accepted
INFO: 2019/12/05 11:27:56.628366 ->[10.250.130.7:6783|a2:37:ac:ae:1d:ef(node2)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/12/05 11:27:56.628842 ->[10.250.130.7:54862|a2:37:ac:ae:1d:ef(node2)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/12/05 11:27:56.629407 ->[10.250.130.2:6783|72:a0:a9:f7:52:26(node1)]: connection ready; using protocol version 2
INFO: 2019/12/05 11:27:56.629738 overlay_switch ->[72:a0:a9:f7:52:26(node1)] using fastdp
INFO: 2019/12/05 11:27:56.629862 ->[10.250.130.2:6783|72:a0:a9:f7:52:26(node1)]: connection added (new peer)
INFO: 2019/12/05 11:27:56.630495 Listening for HTTP control messages on 127.0.0.1:6784
INFO: 2019/12/05 11:27:56.631031 Listening for metrics requests on 0.0.0.0:6782
INFO: 2019/12/05 11:27:56.649937 ->[10.250.130.2:6783|72:a0:a9:f7:52:26(node1)]: connection fully established
ERRO: 2019/12/05 11:27:56.649985 [allocator] address 10.32.0.1/12 is owned by other peer 72:a0:a9:f7:52:26 (node1)
INFO: 2019/12/05 11:27:56.674291 EMSGSIZE on send, expecting PMTU update (IP packet was 60028 bytes, payload was 60020 bytes)
INFO: 2019/12/05 11:27:56.675557 sleeve ->[10.250.130.2:6783|72:a0:a9:f7:52:26(node1)]: Effective MTU verified at 1438
INFO: 2019/12/05 11:27:57.165663 [kube-peers] Added myself to peer list &{[{72:a0:a9:f7:52:26 node1} {a2:37:ac:ae:1d:ef node2}]}
DEBU: 2019/12/05 11:27:57.195294 [kube-peers] Nodes that have disappeared: map[]
10.44.0.0
INFO: 2019/12/05 11:27:57.347081 Weave version 2.6.0 is available; please update at https://github.com/weaveworks/weave/releases/download/v2.6.0/weave
10.250.130.2
10.250.130.7
DEBU: 2019/12/05 11:27:57.462869 registering for updates for node delete events

<!-- Anything interesting or unusual output by the below, potentially relevant, commands?
$ journalctl -u docker.service --no-pager | grep -vi info
-- Logs begin at Thu 2019-12-05 10:26:21 UTC, end at Thu 2019-12-05 11:48:59 UTC. --
Dec 05 10:26:39 node1 systemd[1]: Starting Docker Application Container Engine...
Dec 05 10:26:42 node1 dockerd[1455]: time="2019-12-05T10:26:42.678121878Z" level=warning msg="Using pre-4.0.0 kernel for overlay2, mount failures may require kernel update" storage-driver=overlay2
Dec 05 10:26:48 node1 systemd[1]: Started Docker Application Container Engine.
Dec 05 10:27:18 node1 systemd[1]: Stopping Docker Application Container Engine...
Dec 05 10:27:18 node1 systemd[1]: Stopped Docker Application Container Engine.
Dec 05 10:27:18 node1 systemd[1]: Starting Docker Application Container Engine...
Dec 05 10:27:19 node1 dockerd[3858]: time="2019-12-05T10:27:19.039945350Z" level=warning msg="Using pre-4.0.0 kernel for overlay2, mount failures may require kernel update" storage-driver=overlay2
Dec 05 10:27:21 node1 systemd[1]: Started Docker Application Container Engine.

$ journalctl -u kubelet --no-pager
Last message in journal is just as node is joining (and get pods now shows everything as running).
Dec 05 11:27:54 node2 kubelet[30502]: W1205 11:27:54.919085   30502 cni.go:213] Unable to update cni config: No networks found in /etc/cni/net.d
Dec 05 11:27:55 node2 kubelet[30502]: W1205 11:27:55.349741   30502 watcher.go:87] Error while processing event ("/sys/fs/cgroup/devices/libcontainer_31035_systemd_test_default.slice": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/devices/libcontainer_31035_systemd_test_default.slice: no such file or directory
Dec 05 11:27:55 node2 kubelet[30502]: E1205 11:27:55.818583   30502 kubelet.go:2169] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

$ kubectl get events
- Nothing unusual.
25m         Normal   NodeReady                 node/node2   Node node2 status is now: NodeReady
$ date
Thu Dec  5 11:53:51 UTC 2019
-->

## Network:

node 1
$ sudo ip route
default via 10.250.130.1 dev eth0 proto static metric 100
10.32.0.0/12 dev weave proto kernel scope link src 10.32.0.1
10.250.0.0/16 dev eth0 proto kernel scope link src 10.250.130.2 metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
$ sudo ip -4 -o addr
1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
2: eth0    inet 10.250.130.2/16 brd 10.250.255.255 scope global noprefixroute eth0\       valid_lft forever preferred_lft forever
3: docker0    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0\       valid_lft forever preferred_lft forever
6: weave    inet 10.32.0.1/12 brd 10.47.255.255 scope global weave\       valid_lft forever preferred_lft forever
$ sudo iptables-save
Generated by iptables-save v1.4.21 on Thu Dec  5 11:43:24 2019
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [25:1516]
:POSTROUTING ACCEPT [25:1516]
:DOCKER - [0:0]
:KUBE-MARK-DROP - [0:0]
:KUBE-MARK-MASQ - [0:0]
:KUBE-NODEPORTS - [0:0]
:KUBE-POSTROUTING - [0:0]
:KUBE-SEP-3DU66DE6VORVEQVD - [0:0]
:KUBE-SEP-PNP333KAQDYB2H5R - [0:0]
:KUBE-SEP-S4MK5EVI7CLHCCS6 - [0:0]
:KUBE-SEP-SWLOBIBPXYBP7G2Z - [0:0]
:KUBE-SEP-SZZ7MOWKTWUFXIJT - [0:0]
:KUBE-SEP-UJJNLSZU6HL4F5UO - [0:0]
:KUBE-SEP-ZCHNBYOGFZRFKYMA - [0:0]
:KUBE-SERVICES - [0:0]
:KUBE-SVC-ERIFXISQEP7F7OF4 - [0:0]
:KUBE-SVC-JD5MR3NA4I4DYORP - [0:0]
:KUBE-SVC-NPX46M4PTMTKRN6Y - [0:0]
:KUBE-SVC-TCOU7JCQXEZGVUNU - [0:0]
:OUTPUT_direct - [0:0]
:POSTROUTING_ZONES - [0:0]
:POSTROUTING_ZONES_SOURCE - [0:0]
:POSTROUTING_direct - [0:0]
:POST_public - [0:0]
:POST_public_allow - [0:0]
:POST_public_deny - [0:0]
:POST_public_log - [0:0]
:PREROUTING_ZONES - [0:0]
:PREROUTING_ZONES_SOURCE - [0:0]
:PREROUTING_direct - [0:0]
:PRE_public - [0:0]
:PRE_public_allow - [0:0]
:PRE_public_deny - [0:0]
:PRE_public_log - [0:0]
:WEAVE - [0:0]
-A PREROUTING -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -m comment --comment "kubernetes postrouting rules" -j KUBE-POSTROUTING
-A POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE
-A POSTROUTING -j WEAVE
-A DOCKER -i docker0 -j RETURN
-A KUBE-MARK-DROP -j MARK --set-xmark 0x8000/0x8000
-A KUBE-MARK-MASQ -j MARK --set-xmark 0x4000/0x4000
-A KUBE-POSTROUTING -m comment --comment "kubernetes service traffic requiring SNAT" -m mark --mark 0x4000/0x4000 -j MASQUERADE
-A KUBE-SEP-3DU66DE6VORVEQVD -s 10.32.0.3/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-3DU66DE6VORVEQVD -p udp -m udp -j DNAT --to-destination 10.32.0.3:53
-A KUBE-SEP-PNP333KAQDYB2H5R -s 10.250.130.2/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-PNP333KAQDYB2H5R -p tcp -m tcp -j DNAT --to-destination 10.250.130.2:6443
-A KUBE-SEP-S4MK5EVI7CLHCCS6 -s 10.32.0.3/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-S4MK5EVI7CLHCCS6 -p tcp -m tcp -j DNAT --to-destination 10.32.0.3:53
-A KUBE-SEP-SWLOBIBPXYBP7G2Z -s 10.32.0.2/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-SWLOBIBPXYBP7G2Z -p tcp -m tcp -j DNAT --to-destination 10.32.0.2:9153
-A KUBE-SEP-SZZ7MOWKTWUFXIJT -s 10.32.0.2/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-SZZ7MOWKTWUFXIJT -p udp -m udp -j DNAT --to-destination 10.32.0.2:53
-A KUBE-SEP-UJJNLSZU6HL4F5UO -s 10.32.0.2/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-UJJNLSZU6HL4F5UO -p tcp -m tcp -j DNAT --to-destination 10.32.0.2:53
-A KUBE-SEP-ZCHNBYOGFZRFKYMA -s 10.32.0.3/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-ZCHNBYOGFZRFKYMA -p tcp -m tcp -j DNAT --to-destination 10.32.0.3:9153
-A KUBE-SERVICES -d 10.96.0.10/32 -p udp -m comment --comment "kube-system/kube-dns:dns cluster IP" -m udp --dport 53 -j KUBE-SVC-TCOU7JCQXEZGVUNU
-A KUBE-SERVICES -d 10.96.0.10/32 -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp cluster IP" -m tcp --dport 53 -j KUBE-SVC-ERIFXISQEP7F7OF4
-A KUBE-SERVICES -d 10.96.0.1/32 -p tcp -m comment --comment "default/kubernetes:https cluster IP" -m tcp --dport 443 -j KUBE-SVC-NPX46M4PTMTKRN6Y
-A KUBE-SERVICES -d 10.96.0.10/32 -p tcp -m comment --comment "kube-system/kube-dns:metrics cluster IP" -m tcp --dport 9153 -j KUBE-SVC-JD5MR3NA4I4DYORP
-A KUBE-SERVICES -m comment --comment "kubernetes service nodeports; NOTE: this must be the last rule in this chain" -m addrtype --dst-type LOCAL -j KUBE-NODEPORTS
-A KUBE-SVC-ERIFXISQEP7F7OF4 -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-UJJNLSZU6HL4F5UO
-A KUBE-SVC-ERIFXISQEP7F7OF4 -j KUBE-SEP-S4MK5EVI7CLHCCS6
-A KUBE-SVC-JD5MR3NA4I4DYORP -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-SWLOBIBPXYBP7G2Z
-A KUBE-SVC-JD5MR3NA4I4DYORP -j KUBE-SEP-ZCHNBYOGFZRFKYMA
-A KUBE-SVC-NPX46M4PTMTKRN6Y -j KUBE-SEP-PNP333KAQDYB2H5R
-A KUBE-SVC-TCOU7JCQXEZGVUNU -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-SZZ7MOWKTWUFXIJT
-A KUBE-SVC-TCOU7JCQXEZGVUNU -j KUBE-SEP-3DU66DE6VORVEQVD
-A WEAVE -s 10.32.0.0/12 -d 224.0.0.0/4 -j RETURN
-A WEAVE ! -s 10.32.0.0/12 -d 10.32.0.0/12 -j MASQUERADE
-A WEAVE -s 10.32.0.0/12 ! -d 10.32.0.0/12 -j MASQUERADE
COMMIT
Completed on Thu Dec  5 11:43:24 2019
Generated by iptables-save v1.4.21 on Thu Dec  5 11:43:24 2019
*mangle
:PREROUTING ACCEPT [482665:278017281]
:INPUT ACCEPT [482649:278013893]
:FORWARD ACCEPT [4:490]
:OUTPUT ACCEPT [471570:90210128]
:POSTROUTING ACCEPT [471574:90210618]
:FORWARD_direct - [0:0]
:INPUT_direct - [0:0]
:OUTPUT_direct - [0:0]
:POSTROUTING_direct - [0:0]
:PREROUTING_ZONES - [0:0]
:PREROUTING_ZONES_SOURCE - [0:0]
:PREROUTING_direct - [0:0]
:PRE_public - [0:0]
:PRE_public_allow - [0:0]
:PRE_public_deny - [0:0]
:PRE_public_log - [0:0]
-A PREROUTING -j PREROUTING_direct
-A PREROUTING -j PREROUTING_ZONES_SOURCE
-A PREROUTING -j PREROUTING_ZONES
-A INPUT -j INPUT_direct
-A FORWARD -j FORWARD_direct
-A OUTPUT -j OUTPUT_direct
-A POSTROUTING -j POSTROUTING_direct
-A PREROUTING_ZONES -i eth0 -g PRE_public
-A PREROUTING_ZONES -g PRE_public
-A PRE_public -j PRE_public_log
-A PRE_public -j PRE_public_deny
-A PRE_public -j PRE_public_allow
COMMIT
Completed on Thu Dec  5 11:43:24 2019
Generated by iptables-save v1.4.21 on Thu Dec  5 11:43:24 2019
*security
:INPUT ACCEPT [482651:278016725]
:FORWARD ACCEPT [4:490]
:OUTPUT ACCEPT [471584:90211104]
:FORWARD_direct - [0:0]
:INPUT_direct - [0:0]
:OUTPUT_direct - [0:0]
-A INPUT -j INPUT_direct
-A FORWARD -j FORWARD_direct
-A OUTPUT -j OUTPUT_direct
COMMIT
Completed on Thu Dec  5 11:43:24 2019
Generated by iptables-save v1.4.21 on Thu Dec  5 11:43:24 2019
*raw
:PREROUTING ACCEPT [482665:278017281]
:OUTPUT ACCEPT [471570:90210128]
:OUTPUT_direct - [0:0]
:PREROUTING_ZONES - [0:0]
:PREROUTING_ZONES_SOURCE - [0:0]
:PREROUTING_direct - [0:0]
:PRE_public - [0:0]
:PRE_public_allow - [0:0]
:PRE_public_deny - [0:0]
:PRE_public_log - [0:0]
-A PREROUTING -j PREROUTING_direct
-A PREROUTING -j PREROUTING_ZONES_SOURCE
-A PREROUTING -j PREROUTING_ZONES
-A OUTPUT -j OUTPUT_direct
-A PREROUTING_ZONES -i eth0 -g PRE_public
-A PREROUTING_ZONES -g PRE_public
-A PRE_public -j PRE_public_log
-A PRE_public -j PRE_public_deny
-A PRE_public -j PRE_public_allow
COMMIT
Completed on Thu Dec  5 11:43:24 2019
Generated by iptables-save v1.4.21 on Thu Dec  5 11:43:24 2019
filter
:INPUT ACCEPT [2623:467665]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [2730:559392]
:DOCKER - [0:0]
:DOCKER-ISOLATION-STAGE-1 - [0:0]
:DOCKER-ISOLATION-STAGE-2 - [0:0]
:DOCKER-USER - [0:0]
:FORWARD_IN_ZONES - [0:0]
:FORWARD_IN_ZONES_SOURCE - [0:0]
:FORWARD_OUT_ZONES - [0:0]
:FORWARD_OUT_ZONES_SOURCE - [0:0]
:FORWARD_direct - [0:0]
:FWDI_public - [0:0]
:FWDI_public_allow - [0:0]
:FWDI_public_deny - [0:0]
:FWDI_public_log - [0:0]
:FWDO_public - [0:0]
:FWDO_public_allow - [0:0]
:FWDO_public_deny - [0:0]
:FWDO_public_log - [0:0]
:INPUT_ZONES - [0:0]
:INPUT_ZONES_SOURCE - [0:0]
:INPUT_direct - [0:0]
:IN_public - [0:0]
:IN_public_allow - [0:0]
:IN_public_deny - [0:0]
:IN_public_log - [0:0]
:KUBE-EXTERNAL-SERVICES - [0:0]
:KUBE-FIREWALL - [0:0]
:KUBE-FORWARD - [0:0]
:KUBE-SERVICES - [0:0]
:OUTPUT_direct - [0:0]
:WEAVE-NPC - [0:0]
:WEAVE-NPC-DEFAULT - [0:0]
:WEAVE-NPC-EGRESS - [0:0]
:WEAVE-NPC-EGRESS-ACCEPT - [0:0]
:WEAVE-NPC-EGRESS-CUSTOM - [0:0]
:WEAVE-NPC-EGRESS-DEFAULT - [0:0]
:WEAVE-NPC-INGRESS - [0:0]
-A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes externally-visible service portals" -j KUBE-EXTERNAL-SERVICES
-A INPUT -j KUBE-FIREWALL
-A INPUT -i weave -j WEAVE-NPC-EGRESS
-A FORWARD -i weave -m comment --comment "NOTE: this must go before '-j KUBE-FORWARD'" -j WEAVE-NPC-EGRESS
-A FORWARD -o weave -m comment --comment "NOTE: this must go before '-j KUBE-FORWARD'" -j WEAVE-NPC
-A FORWARD -o weave -m state --state NEW -j NFLOG --nflog-group 86
-A FORWARD -o weave -j DROP
-A FORWARD -i weave ! -o weave -j ACCEPT
-A FORWARD -o weave -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -m comment --comment "kubernetes forwarding rules" -j KUBE-FORWARD
-A FORWARD -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A OUTPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A OUTPUT -j KUBE-FIREWALL
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN
-A KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
-A KUBE-FORWARD -m conntrack --ctstate INVALID -j DROP
-A KUBE-FORWARD -m comment --comment "kubernetes forwarding rules" -m mark --mark 0x4000/0x4000 -j ACCEPT
-A WEAVE-NPC -m state --state RELATED,ESTABLISHED -j ACCEPT
-A WEAVE-NPC -d 224.0.0.0/4 -j ACCEPT
-A WEAVE-NPC -m physdev --physdev-out vethwe-bridge -j ACCEPT
-A WEAVE-NPC -m state --state NEW -j WEAVE-NPC-DEFAULT
-A WEAVE-NPC -m state --state NEW -j WEAVE-NPC-INGRESS
-A WEAVE-NPC-DEFAULT -m set --match-set weave-P.B|!ZhkAr5q=XZ?3}tMBA+0 dst -m comment --comment "DefaultAllow ingress isolation for namespace: kube-system" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-Rzff}h:=]JaaJl/G;(XJpGjZ[ dst -m comment --comment "DefaultAllow ingress isolation for namespace: kube-public" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-]B(W?)t*z5O17G044[gUo#$l dst -m comment --comment "DefaultAllow ingress isolation for namespace: kube-node-lease" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-;rGqyMIl1HN^cfDki~Z$3]6!N dst -m comment --comment "DefaultAllow ingress isolation for namespace: default" -j ACCEPT
-A WEAVE-NPC-EGRESS -m state --state RELATED,ESTABLISHED -j ACCEPT
-A WEAVE-NPC-EGRESS -m physdev --physdev-in vethwe-bridge -j RETURN
-A WEAVE-NPC-EGRESS -d 224.0.0.0/4 -j RETURN
-A WEAVE-NPC-EGRESS -m state --state NEW -j WEAVE-NPC-EGRESS-DEFAULT
-A WEAVE-NPC-EGRESS -m state --state NEW -m mark ! --mark 0x40000/0x40000 -j WEAVE-NPC-EGRESS-CUSTOM
-A WEAVE-NPC-EGRESS -m state --state NEW -m mark ! --mark 0x40000/0x40000 -j NFLOG --nflog-group 86
-A WEAVE-NPC-EGRESS -m mark ! --mark 0x40000/0x40000 -j DROP
-A WEAVE-NPC-EGRESS-ACCEPT -j MARK --set-xmark 0x40000/0x40000
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -m comment --comment "DefaultAllow egress isolation for namespace: kube-system" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -m comment --comment "DefaultAllow egress isolation for namespace: kube-system" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-41s)5vQ^o/xWGz6a20N:~?#|E src -m comment --comment "DefaultAllow egress isolation for namespace: kube-public" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-41s)5vQ^o/xWGz6a20N:~?#|E src -m comment --comment "DefaultAllow egress isolation for namespace: kube-public" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-sui%gZ}{kX~oZgI_Ttqp=Dp src -m comment --comment "DefaultAllow egress isolation for namespace: kube-node-lease" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-sui%gZ}{kX~oZgI_Ttqp=Dp src -m comment --comment "DefaultAllow egress isolation for namespace: kube-node-lease" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-s+ChJId4Uy$}G;WdH|~TK)I src -m comment --comment "DefaultAllow egress isolation for namespace: default" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-s+ChJId4Uy$}G;WdH|~TK)I src -m comment --comment "DefaultAllow egress isolation for namespace: default" -j RETURN
COMMIT
Completed on Thu Dec  5 11:43:24 2019
Node 2
$ sudo ip route
default via 10.250.130.1 dev eth0 proto static metric 100
10.32.0.0/12 dev weave proto kernel scope link src 10.32.0.1
10.250.0.0/16 dev eth0 proto kernel scope link src 10.250.130.7 metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
$ sudo ip -4 -o addr
1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
2: eth0    inet 10.250.130.7/16 brd 10.250.255.255 scope global noprefixroute eth0\       valid_lft forever preferred_lft forever
3: docker0    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0\       valid_lft forever preferred_lft forever
6: weave    inet 10.32.0.1/12 brd 10.47.255.255 scope global weave\       valid_lft forever preferred_lft forever
6: weave    inet 10.44.0.0/12 brd 10.47.255.255 scope global secondary weave\       valid_lft forever preferred_lft forever
$ sudo iptables-save
Generated by iptables-save v1.4.21 on Thu Dec  5 11:46:34 2019
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [1:60]
:POSTROUTING ACCEPT [1:60]
:DOCKER - [0:0]
:KUBE-MARK-DROP - [0:0]
:KUBE-MARK-MASQ - [0:0]
:KUBE-NODEPORTS - [0:0]
:KUBE-POSTROUTING - [0:0]
:KUBE-SEP-3DU66DE6VORVEQVD - [0:0]
:KUBE-SEP-PNP333KAQDYB2H5R - [0:0]
:KUBE-SEP-S4MK5EVI7CLHCCS6 - [0:0]
:KUBE-SEP-SWLOBIBPXYBP7G2Z - [0:0]
:KUBE-SEP-SZZ7MOWKTWUFXIJT - [0:0]
:KUBE-SEP-UJJNLSZU6HL4F5UO - [0:0]
:KUBE-SEP-ZCHNBYOGFZRFKYMA - [0:0]
:KUBE-SERVICES - [0:0]
:KUBE-SVC-ERIFXISQEP7F7OF4 - [0:0]
:KUBE-SVC-JD5MR3NA4I4DYORP - [0:0]
:KUBE-SVC-NPX46M4PTMTKRN6Y - [0:0]
:KUBE-SVC-TCOU7JCQXEZGVUNU - [0:0]
:OUTPUT_direct - [0:0]
:POSTROUTING_ZONES - [0:0]
:POSTROUTING_ZONES_SOURCE - [0:0]
:POSTROUTING_direct - [0:0]
:POST_public - [0:0]
:POST_public_allow - [0:0]
:POST_public_deny - [0:0]
:POST_public_log - [0:0]
:PREROUTING_ZONES - [0:0]
:PREROUTING_ZONES_SOURCE - [0:0]
:PREROUTING_direct - [0:0]
:PRE_public - [0:0]
:PRE_public_allow - [0:0]
:PRE_public_deny - [0:0]
:PRE_public_log - [0:0]
:WEAVE - [0:0]
-A PREROUTING -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -m comment --comment "kubernetes postrouting rules" -j KUBE-POSTROUTING
-A POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE
-A POSTROUTING -j WEAVE
-A DOCKER -i docker0 -j RETURN
-A KUBE-MARK-DROP -j MARK --set-xmark 0x8000/0x8000
-A KUBE-MARK-MASQ -j MARK --set-xmark 0x4000/0x4000
-A KUBE-POSTROUTING -m comment --comment "kubernetes service traffic requiring SNAT" -m mark --mark 0x4000/0x4000 -j MASQUERADE
-A KUBE-SEP-3DU66DE6VORVEQVD -s 10.32.0.3/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-3DU66DE6VORVEQVD -p udp -m udp -j DNAT --to-destination 10.32.0.3:53
-A KUBE-SEP-PNP333KAQDYB2H5R -s 10.250.130.2/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-PNP333KAQDYB2H5R -p tcp -m tcp -j DNAT --to-destination 10.250.130.2:6443
-A KUBE-SEP-S4MK5EVI7CLHCCS6 -s 10.32.0.3/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-S4MK5EVI7CLHCCS6 -p tcp -m tcp -j DNAT --to-destination 10.32.0.3:53
-A KUBE-SEP-SWLOBIBPXYBP7G2Z -s 10.32.0.2/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-SWLOBIBPXYBP7G2Z -p tcp -m tcp -j DNAT --to-destination 10.32.0.2:9153
-A KUBE-SEP-SZZ7MOWKTWUFXIJT -s 10.32.0.2/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-SZZ7MOWKTWUFXIJT -p udp -m udp -j DNAT --to-destination 10.32.0.2:53
-A KUBE-SEP-UJJNLSZU6HL4F5UO -s 10.32.0.2/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-UJJNLSZU6HL4F5UO -p tcp -m tcp -j DNAT --to-destination 10.32.0.2:53
-A KUBE-SEP-ZCHNBYOGFZRFKYMA -s 10.32.0.3/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-ZCHNBYOGFZRFKYMA -p tcp -m tcp -j DNAT --to-destination 10.32.0.3:9153
-A KUBE-SERVICES -d 10.96.0.10/32 -p udp -m comment --comment "kube-system/kube-dns:dns cluster IP" -m udp --dport 53 -j KUBE-SVC-TCOU7JCQXEZGVUNU
-A KUBE-SERVICES -d 10.96.0.10/32 -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp cluster IP" -m tcp --dport 53 -j KUBE-SVC-ERIFXISQEP7F7OF4
-A KUBE-SERVICES -d 10.96.0.10/32 -p tcp -m comment --comment "kube-system/kube-dns:metrics cluster IP" -m tcp --dport 9153 -j KUBE-SVC-JD5MR3NA4I4DYORP
-A KUBE-SERVICES -d 10.96.0.1/32 -p tcp -m comment --comment "default/kubernetes:https cluster IP" -m tcp --dport 443 -j KUBE-SVC-NPX46M4PTMTKRN6Y
-A KUBE-SERVICES -m comment --comment "kubernetes service nodeports; NOTE: this must be the last rule in this chain" -m addrtype --dst-type LOCAL -j KUBE-NODEPORTS
-A KUBE-SVC-ERIFXISQEP7F7OF4 -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-UJJNLSZU6HL4F5UO
-A KUBE-SVC-ERIFXISQEP7F7OF4 -j KUBE-SEP-S4MK5EVI7CLHCCS6
-A KUBE-SVC-JD5MR3NA4I4DYORP -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-SWLOBIBPXYBP7G2Z
-A KUBE-SVC-JD5MR3NA4I4DYORP -j KUBE-SEP-ZCHNBYOGFZRFKYMA
-A KUBE-SVC-NPX46M4PTMTKRN6Y -j KUBE-SEP-PNP333KAQDYB2H5R
-A KUBE-SVC-TCOU7JCQXEZGVUNU -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-SZZ7MOWKTWUFXIJT
-A KUBE-SVC-TCOU7JCQXEZGVUNU -j KUBE-SEP-3DU66DE6VORVEQVD
-A WEAVE -s 10.32.0.0/12 -d 224.0.0.0/4 -j RETURN
-A WEAVE ! -s 10.32.0.0/12 -d 10.32.0.0/12 -j MASQUERADE
-A WEAVE -s 10.32.0.0/12 ! -d 10.32.0.0/12 -j MASQUERADE
COMMIT
Completed on Thu Dec  5 11:46:34 2019
Generated by iptables-save v1.4.21 on Thu Dec  5 11:46:34 2019
*mangle
:PREROUTING ACCEPT [380540:260841992]
:INPUT ACCEPT [380522:260838121]
:FORWARD ACCEPT [4:490]
:OUTPUT ACCEPT [369211:68123116]
:POSTROUTING ACCEPT [369215:68123606]
:FORWARD_direct - [0:0]
:INPUT_direct - [0:0]
:OUTPUT_direct - [0:0]
:POSTROUTING_direct - [0:0]
:PREROUTING_ZONES - [0:0]
:PREROUTING_ZONES_SOURCE - [0:0]
:PREROUTING_direct - [0:0]
:PRE_public - [0:0]
:PRE_public_allow - [0:0]
:PRE_public_deny - [0:0]
:PRE_public_log - [0:0]
-A PREROUTING -j PREROUTING_direct
-A PREROUTING -j PREROUTING_ZONES_SOURCE
-A PREROUTING -j PREROUTING_ZONES
-A INPUT -j INPUT_direct
-A FORWARD -j FORWARD_direct
-A OUTPUT -j OUTPUT_direct
-A POSTROUTING -j POSTROUTING_direct
-A PREROUTING_ZONES -i eth0 -g PRE_public
-A PREROUTING_ZONES -g PRE_public
-A PRE_public -j PRE_public_log
-A PRE_public -j PRE_public_deny
-A PRE_public -j PRE_public_allow
COMMIT
Completed on Thu Dec  5 11:46:34 2019
Generated by iptables-save v1.4.21 on Thu Dec  5 11:46:34 2019
*security
:INPUT ACCEPT [380520:260840697]
:FORWARD ACCEPT [4:490]
:OUTPUT ACCEPT [369224:68124016]
:FORWARD_direct - [0:0]
:INPUT_direct - [0:0]
:OUTPUT_direct - [0:0]
-A INPUT -j INPUT_direct
-A FORWARD -j FORWARD_direct
-A OUTPUT -j OUTPUT_direct
COMMIT
Completed on Thu Dec  5 11:46:34 2019
Generated by iptables-save v1.4.21 on Thu Dec  5 11:46:34 2019
*raw
:PREROUTING ACCEPT [380540:260841992]
:OUTPUT ACCEPT [369211:68123116]
:OUTPUT_direct - [0:0]
:PREROUTING_ZONES - [0:0]
:PREROUTING_ZONES_SOURCE - [0:0]
:PREROUTING_direct - [0:0]
:PRE_public - [0:0]
:PRE_public_allow - [0:0]
:PRE_public_deny - [0:0]
:PRE_public_log - [0:0]
-A PREROUTING -j PREROUTING_direct
-A PREROUTING -j PREROUTING_ZONES_SOURCE
-A PREROUTING -j PREROUTING_ZONES
-A OUTPUT -j OUTPUT_direct
-A PREROUTING_ZONES -i eth0 -g PRE_public
-A PREROUTING_ZONES -g PRE_public
-A PRE_public -j PRE_public_log
-A PRE_public -j PRE_public_deny
-A PRE_public -j PRE_public_allow
COMMIT
Completed on Thu Dec  5 11:46:34 2019
Generated by iptables-save v1.4.21 on Thu Dec  5 11:46:34 2019
filter
:INPUT ACCEPT [62:15062]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [46:7368]
:DOCKER - [0:0]
:DOCKER-ISOLATION-STAGE-1 - [0:0]
:DOCKER-ISOLATION-STAGE-2 - [0:0]
:DOCKER-USER - [0:0]
:FORWARD_IN_ZONES - [0:0]
:FORWARD_IN_ZONES_SOURCE - [0:0]
:FORWARD_OUT_ZONES - [0:0]
:FORWARD_OUT_ZONES_SOURCE - [0:0]
:FORWARD_direct - [0:0]
:FWDI_public - [0:0]
:FWDI_public_allow - [0:0]
:FWDI_public_deny - [0:0]
:FWDI_public_log - [0:0]
:FWDO_public - [0:0]
:FWDO_public_allow - [0:0]
:FWDO_public_deny - [0:0]
:FWDO_public_log - [0:0]
:INPUT_ZONES - [0:0]
:INPUT_ZONES_SOURCE - [0:0]
:INPUT_direct - [0:0]
:IN_public - [0:0]
:IN_public_allow - [0:0]
:IN_public_deny - [0:0]
:IN_public_log - [0:0]
:KUBE-EXTERNAL-SERVICES - [0:0]
:KUBE-FIREWALL - [0:0]
:KUBE-FORWARD - [0:0]
:KUBE-SERVICES - [0:0]
:OUTPUT_direct - [0:0]
:WEAVE-NPC - [0:0]
:WEAVE-NPC-DEFAULT - [0:0]
:WEAVE-NPC-EGRESS - [0:0]
:WEAVE-NPC-EGRESS-ACCEPT - [0:0]
:WEAVE-NPC-EGRESS-CUSTOM - [0:0]
:WEAVE-NPC-EGRESS-DEFAULT - [0:0]
:WEAVE-NPC-INGRESS - [0:0]
-A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes externally-visible service portals" -j KUBE-EXTERNAL-SERVICES
-A INPUT -j KUBE-FIREWALL
-A INPUT -i weave -j WEAVE-NPC-EGRESS
-A FORWARD -i weave -m comment --comment "NOTE: this must go before '-j KUBE-FORWARD'" -j WEAVE-NPC-EGRESS
-A FORWARD -o weave -m comment --comment "NOTE: this must go before '-j KUBE-FORWARD'" -j WEAVE-NPC
-A FORWARD -o weave -m state --state NEW -j NFLOG --nflog-group 86
-A FORWARD -o weave -j DROP
-A FORWARD -i weave ! -o weave -j ACCEPT
-A FORWARD -o weave -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -m comment --comment "kubernetes forwarding rules" -j KUBE-FORWARD
-A FORWARD -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A OUTPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A OUTPUT -j KUBE-FIREWALL
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN
-A KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
-A KUBE-FORWARD -m conntrack --ctstate INVALID -j DROP
-A KUBE-FORWARD -m comment --comment "kubernetes forwarding rules" -m mark --mark 0x4000/0x4000 -j ACCEPT
-A WEAVE-NPC -m state --state RELATED,ESTABLISHED -j ACCEPT
-A WEAVE-NPC -d 224.0.0.0/4 -j ACCEPT
-A WEAVE-NPC -m physdev --physdev-out vethwe-bridge -j ACCEPT
-A WEAVE-NPC -m state --state NEW -j WEAVE-NPC-DEFAULT
-A WEAVE-NPC -m state --state NEW -j WEAVE-NPC-INGRESS
-A WEAVE-NPC-DEFAULT -m set --match-set weave-P.B|!ZhkAr5q=XZ?3}tMBA+0 dst -m comment --comment "DefaultAllow ingress isolation for namespace: kube-system" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-Rzff}h:=]JaaJl/G;(XJpGjZ[ dst -m comment --comment "DefaultAllow ingress isolation for namespace: kube-public" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-]B(W?)t*z5O17G044[gUo#$l dst -m comment --comment "DefaultAllow ingress isolation for namespace: kube-node-lease" -j ACCEPT
-A WEAVE-NPC-DEFAULT -m set --match-set weave-;rGqyMIl1HN^cfDki~Z$3]6!N dst -m comment --comment "DefaultAllow ingress isolation for namespace: default" -j ACCEPT
-A WEAVE-NPC-EGRESS -m state --state RELATED,ESTABLISHED -j ACCEPT
-A WEAVE-NPC-EGRESS -m physdev --physdev-in vethwe-bridge -j RETURN
-A WEAVE-NPC-EGRESS -d 224.0.0.0/4 -j RETURN
-A WEAVE-NPC-EGRESS -m state --state NEW -j WEAVE-NPC-EGRESS-DEFAULT
-A WEAVE-NPC-EGRESS -m state --state NEW -m mark ! --mark 0x40000/0x40000 -j WEAVE-NPC-EGRESS-CUSTOM
-A WEAVE-NPC-EGRESS -m state --state NEW -m mark ! --mark 0x40000/0x40000 -j NFLOG --nflog-group 86
-A WEAVE-NPC-EGRESS -m mark ! --mark 0x40000/0x40000 -j DROP
-A WEAVE-NPC-EGRESS-ACCEPT -j MARK --set-xmark 0x40000/0x40000
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -m comment --comment "DefaultAllow egress isolation for namespace: kube-system" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -m comment --comment "DefaultAllow egress isolation for namespace: kube-system" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-41s)5vQ^o/xWGz6a20N:~?#|E src -m comment --comment "DefaultAllow egress isolation for namespace: kube-public" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-41s)5vQ^o/xWGz6a20N:~?#|E src -m comment --comment "DefaultAllow egress isolation for namespace: kube-public" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-sui%gZ}{kX~oZgI_Ttqp=Dp src -m comment --comment "DefaultAllow egress isolation for namespace: kube-node-lease" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-sui%gZ}{kX~oZgI_Ttqp=Dp src -m comment --comment "DefaultAllow egress isolation for namespace: kube-node-lease" -j RETURN
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-s+ChJId4Uy$}G;WdH|~TK)I src -m comment --comment "DefaultAllow egress isolation for namespace: default" -j WEAVE-NPC-EGRESS-ACCEPT
-A WEAVE-NPC-EGRESS-DEFAULT -m set --match-set weave-s+ChJId4Uy$}G;WdH|~TK)I src -m comment --comment "DefaultAllow egress isolation for namespace: default" -j RETURN
COMMIT
Completed on Thu Dec  5 11:46:34 2019

@nnaisbitt please note that performing weave reset is the recommended way if you are planning to join nodes that were previously running weave
https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-installation

We do not install weave binary into the command line of the node. It should only run as a container. Installing weave and running weave reset from the command line of the node itself is a workaround we shouldn't be using.

There is no alternative way at the moment. There is open issue for what you are looking for https://github.com/weaveworks/weave/issues/3321

Understood. But still I'm surprised that weavenet performs all connection handshakes successfully, when in this state.
I look forward to seeing that functionality.
Thanks.

authors: murali-reddy nnaisbitt


text:
keyframe-effect-constructor.js:128 Uncaught TypeError: Failed to execute 'animate' on 'Element': 'function (a){return a}' is not a valid value for easing

In Chrome 52 (Stable) this is the warning...
Specifying animation easing as a function is deprecated and all support will be removed in M54, around October 2016, at which point this will throw a TypeError. This warning may have been triggered by the Web Animations or Polymer polyfills. See http://crbug.com/601672 for details.
In Chrome 54 (dev) as of last week, this now throws a TypeError and breaks any Polymer application that relies on a neon-animation component.
keyframe-effect-constructor.js:128 Uncaught TypeError: Failed to execute 'animate' on 'Element': 'function (a){return a}' is not a valid value for easing     at Object.b.newUnderlyingAnimationForKeyframeEffect (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:16:7609)     at b.Animation._rebuildUnderlyingAnimation (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:15:31941)     at b.Animation (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:15:30984)     at b.AnimationTimeline._play (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:15:30111)     at Object.b.newUnderlyingAnimationForGroup (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:16:12228)     at b.Animation._rebuildUnderlyingAnimation (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:15:32144)     at b.Animation (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:15:30984)     at b.AnimationTimeline._play (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:15:30111)     at b.AnimationTimeline.play (https://dev.com/assets/bower_components/web-animations-js/web-animations-next-lite.min.js:15:30306)     at HTMLElement._runAnimationEffects (https://dev.com/assets/bower_components/neon-animation/neon-animation-runner-behavior.html:62:32)b.newUnderlyingAnimationForKeyframeEffect @ keyframe-effect-constructor.js:128_rebuildUnderlyingAnimation @ web-animations-next-animation.js:86b.Animation @ web-animations-next-animation.js:35_play @ timeline.js:48b.newUnderlyingAnimationForGroup @ group-constructors.js:189_rebuildUnderlyingAnimation @ web-animations-next-animation.js:90b.Animation @ web-animations-next-animation.js:35_play @ timeline.js:48play @ timeline.js:65_runAnimationEffects @ neon-animation-runner-behavior.html:62playAnimation @ neon-animation-runner-behavior.html:87show @ (index):1672(anonymous function) @ (index):628(anonymous function) @ webcomponents-lite.min.js:12

Can be fixed by pulling in any of these versions...
https://github.com/web-animations/web-animations-js/tree/2.2.0
https://github.com/web-animations/web-animations-js/tree/2.1.5
https://github.com/web-animations/web-animations-js/tree/2.0.1
https://github.com/web-animations/web-animations-js/tree/1.0.8
Please close this issue.

source: gharchive/issue

repo: web-animations/web-animations-next

license_type: permissive

license_source: bigquery


text:
System Info
System:
OS: macOS 13.2
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 10.66 GB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 14.21.3 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 6.14.18 - /usr/local/bin/npm
Browsers:
Chrome: 111.0.5563.64
Safari: 16.3
Details
在 builtins.html.template 中使用绝对路径时，如果路径包含中文字符，就会报错

Reproduce link
No response
Reproduce Steps

npx rspack serve

相对路径是没问题的

我马上修复一下哈～

authors: JSerFeng dingff

repo: web-infra-dev/rspack

license: MIT

license_source: github-api


text:
hexoid crashes if imported using commonjs

System Info
System:
OS: macOS 13.3.1
CPU: (10) arm64 Apple M1 Pro
Memory: 404.19 MB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
npm: 8.19.2 - ~/node_modules/.bin/npm
Browsers:
Chrome: 113.0.5672.126
Edge: 113.0.1774.35
Safari: 16.4
npmPackages:
@rspack/cli: 0.1.11 => 0.1.11
@rspack/core: 0.1.11 => 0.1.11
@rspack/dev-server: ~0.1.0 => 0.1.11
@rspack/plugin-minify: ~0.1.0 => 0.1.11
Details
https://www.npmjs.com/package/hexoid is delivered as:
CommonJS: dist/index.js
ES Module: dist/index.mjs
UMD: dist/index.min.js
When it is consumed through CommonJS, it crashes at runtime.
When it is consumed through EMS, it works fine
Compilation output
ESM
(function() {
var __webpack_modules__ = {
"56": function (module, exports, __webpack_require__) {
"use strict";
Object.defineProperty(exports, "__esModule", {
    value: true
});
Object.defineProperty(exports, "default", {
    enumerable: true,
    get: function() {
        return _default;
    }
});
var IDX = 256, HEX = [];
while(IDX--)HEX[IDX] = (IDX + 256).toString(16).substring(1);
function _default(len) {
    len = len || 16;
    var str = '', num = 0;
    return function() {
        if (!str || num === 256) {
            str = '';
            num = (1 + len) / 2 | 0;
            while(num--)str += HEX[256 * Math.random() | 0];
            str = str.substring(num = 0, len - 2);
        }
        return str + HEX[num++];
    };
}
},
"821": function (module, exports, __webpack_require__) {
"use strict";
Object.defineProperty(exports, "__esModule", {
    value: true
});
var _56 = __webpack_require__.ir(__webpack_require__("56"));
const toID = (0, _56.default)();
toID();
},

}

CommonJS
var __webpack_modules__ = {
"56": function (module, exports, __webpack_require__) {
"use strict";
Object.defineProperty(exports, "__esModule", {
    value: true
});
Object.defineProperty(exports, "default", {
    enumerable: true,
    get: function() {
        return _default;
    }
});
var IDX = 256, HEX = [];
while(IDX--)HEX[IDX] = (IDX + 256).toString(16).substring(1);
function _default(len) {
    len = len || 16;
    var str = '', num = 0;
    return function() {
        if (!str || num === 256) {
            str = '';
            num = (1 + len) / 2 | 0;
            while(num--)str += HEX[256 * Math.random() | 0];
            str = str.substring(num = 0, len - 2);
        }
        return str + HEX[num++];
    };
}
},
"821": function (module, exports, __webpack_require__) {
const hexoid = __webpack_require__("56");
const toID = hexoid();
toID();
},

}

Reproduce link
No response
Reproduce Steps
This will crash at runtime:
const hexoid = require('hexoid');

const toID = hexoid();
toID(); //=> '52032fedb951da00'

This works
import hexoid from 'hexoid';

const toID = hexoid();
toID(); //=> '52032fedb951da00'

actually both of the import | require are bundling the module entrypoint(dist/index.mjs), and since dist/index.mjs only exports default, so you need to do
const hexoid = require('hexoid').default

this is the same behavior as webpack, and you can check the source code here https://github.com/webpack/webpack/blob/main/lib/config/defaults.js#L1259.
I'm not sure whether default behavior is right, since esbuild takes another approach( main over module when target = node). @alexander-akait may know why webpack design this way.

Thanks for the fast reply @hardfist
Webpack and Rspack behave differently. The compiled code does not crash at runtime when built using Webpack.
My understanding is that Rspack bundles the module entrypoint(dist/index.mjs) while webpack uses the common js one (dist/index.js).
Webpack output:
/******/ (() => { // webpackBootstrap
/******/ 	var __webpack_modules__ = ([
/* 0 */,
/* 1 */
/***/ ((module) => {

var IDX=256, HEX=[];
while (IDX--) HEX[IDX] = (IDX + 256).toString(16).substring(1);

module.exports = function (len) {
	len = len || 16;
	var str='', num=0;
	return function () {
		if (!str || num === 256) {
			str=''; num=(1+len)/2 | 0;
			while (num--) str += HEX[256 * Math.random() | 0];
			str = str.substring(num=0, len-2);
		}
		return str + HEX[num++];
	};
}

/***/ })
/******/ 	]);

Rspack:
var __webpack_modules__ = {
"56": function (module, exports, __webpack_require__) {
"use strict";
Object.defineProperty(exports, "__esModule", {
    value: true
});
Object.defineProperty(exports, "default", {
    enumerable: true,
    get: function() {
        return _default;
    }
});
var IDX = 256, HEX = [];
while(IDX--)HEX[IDX] = (IDX + 256).toString(16).substring(1);
function _default(len) {
    len = len || 16;
    var str = '', num = 0;
    return function() {
        if (!str || num === 256) {
            str = '';
            num = (1 + len) / 2 | 0;
            while(num--)str += HEX[256 * Math.random() | 0];
            str = str.substring(num = 0, len - 2);
        }
        return str + HEX[num++];
    };
}
},
"821": function (module, exports, __webpack_require__) {
const hexoid = __webpack_require__("56");
const toID = hexoid();
console.log(toID());
},

}

@antoinepairet  what webpack version do you use?

https://github.com/web-infra-dev/rspack-repro maybe you can provide demo using rspack repro template, so we can compare the result of rspack and webpack

Does rspack support https://github.com/lukeed/hexoid/blob/master/package.json#L6? Based on output rspack takes ESM version, but when you use const hexoid = require('hexoid'); we should take commonjs version (webpack takes it)

Does rspack support https://github.com/lukeed/hexoid/blob/master/package.json#L6? Based on output rspack takes ESM version, but when you use const hexoid = require('hexoid'); we should take commonjs version (webpack takes it)

we support exports field but hexiod doesnt use exports field https://www.npmjs.com/package/hexoid?activeTab=code

it seems packagejson is the same between github and npm

it seems packagejson is the same between github and npm

You probably meant "NOT the same"
https://www.npmjs.com/package/hexoid?activeTab=code does not use exports field in package.json
while https://github.com/lukeed/hexoid/blob/master/package.json#L6 has it
Rspack and webpack behave differently in this case.

The difference between webpack and rspack is that rpack uses the ESM version and webpack uses commonjs, because there is no exports in published package, I see only these things:
"module": "dist/index.mjs",
"main": "dist/index.js",

So my question - @antoinepairet What is the target - node or web?

Rspack breaks when all dependencies are bundled: config.externals = [].
The reproduction scenario is available here: https://github.com/rosahealth/rspack-is-awesome
It is an Nx workspace with 1 project and 3 configs to build or serve the project:

using Rspack without config.externals
using Rspack with config.externals
using webpack

➜  rspack-is-awesome git:(main) ✗ diff rspack.config.js rspack.broken-config.js
9a10,11
>   config.externals = []; // <-- This is what makes it crash at runtime
>
➜  rspack-is-awesome git:(main)

Here is the content of rspack.broken-config.js (@alexander-akait the target is node):
const { composePlugins, withNx } = require('@nrwl/rspack');

module.exports = composePlugins(withNx(), (config) => {
  config.devtool = false;
  config.optimization = {
    ...config.optimization,
    minimize: false,
  };

  config.externals = []; // <-- This is what makes it crash at runtime

  config.target = ['node', 'es2015'];
  config.output = {
    ...config.output,
    chunkFormat: 'commonjs',
  };

  return config;
});

Let me know if you need more info.

@antoinepairet your demo is kind of too complex, so I made the minimal demo using rspack-repro template https://github.com/hardfist/rspack-webpack-crash, and you can see both rspack and webpack result crash at runtime.

so rspack and webpack behaves the same way

The difference between webpack and rspack is that rpack uses the ESM version and webpack uses commonjs, because there is no exports in published package, I see only these things:
"module": "dist/index.mjs",
"main": "dist/index.js",

So my question - @antoinepairet What is the target - node or web?
@alexander-akait  webpack will also pick the module field over main field even when target set to node, am I wrong?

Our logic:

for web (and web related) targets - ["browser", "module", "main"]
for node ["module", "main"]

So yes

@alexander-akait @hardfist Thank you for the follow-up 🙌🏻
Next time I will create the reproduction using the rspack template 👍🏻
I will create an issue on the hexoid repo to add the exports in the package.json on npm.

@alexander-akait @hardfist Thank you for the follow-up 🙌🏻 Next time I will create the reproduction using the rspack template 👍🏻
I will create an issue on the hexoid repo to add the exports in the package.json on npm.

since it's not a bug of rspack, gonna close the issue

authors: alexander-akait antoinepairet hardfist


text:
refactor: css-extract using parseMeta to store css info

Summary
css-extract uses additionalData to parse necessary data to Rust, but additionalData can be removed by other user's plugin, so it's not safe.
Now we introduce a new internal field for passing data, other loaders cannot modify it

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

Would you please add a test just to avoid regressions?

Would you please add a test just to avoid regressions?

Done

source: gharchive/pull-request

authors: JSerFeng h-a-n-a


text:
Show error msg for failed TXs

For now when TX gets reverted, it's still considered as a "success" request for the react-query lib and we show green success tx notification.
Let's look into the ways to detect if the TX was actually reverted or not. Maybe parse the response object and see some status there?


text:
feature: Working on ENSAvatar

Overview:
ENS or Ethereum Naming Service has avatars attached to the addresses on mainnet. Instead of just using blockie we can have this as an avatar in web3uikit
What I would build:
I would integrate  ENSAvatars as a component to be used as a basic avatar if they have one and have blockies as a backup if the consumer does not have an ENS Avatar.This can be an image or a gif.for example vitalik.eth gives this gif:

Reference:

https://ensdomains.github.io/ens-avatar/
https://docs.ens.domains/ens-improvement-proposals/ensip-12-avatar-text-records

Closed by #689


text:
Multiplayer: 404 avatar

  | _mapUrl | @ | runtime.js:617
-- | -- | -- | --
  | (anonymous) | @ | runtime.js:642
  | _mapScript | @ | runtime.js:633
  | _mapUrl | @ | runtime.js:620
  | async function (async) |   |
  | _mapUrl | @ | runtime.js:617
  | _loadScript | @ | runtime.js:664
  | (anonymous) | @ | runtime.js:1221
  | runtime.loadFile | @ | runtime.js:1251
  | (anonymous) | @ | world.js:363
  | async function (async) |   |
  | (anonymous) | @ | world.js:360
  | (anonymous) | @ | world.js:66
  | r | @ | yjs.js:57
  | We | @ | yjs.js:77
  | rn | @ | yjs.js:77
  | value | @ | yjs.js:77
  | (anonymous) | @ | yjs.js:77
  | r | @ | yjs.js:57
  | e | @ | yjs.js:77
  | Ft | @ | yjs.js:77
  | Ee | @ | yjs.js:77
  | Ue | @ | yjs.js:77
  | Ae | @ | yjs.js:77
  | (anonymous) | @ | xrrtc.js:182

https://github.com/TheNexusCity/webaverse-app/issues/1

Since avatar wearing and switching is working, I think we can close this @0reo

authors: DavinciDreams avaer lalalune

repo: webaverse/app


text:
299 refactor dashboard

title: Issue #299  | [TASK]: Refactor dashboard

Discord Username: @dekomori_sanae09
What type of PR is this? (select all that apply)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 🚧 Breaking Change
[x] 🧑💻 Code Refactor
[ ] 📝 Documentation Update

Description
There are a lot of changes.

Renamed files to camel case.
Added components folder inside dashboard page.
It shows basic stats like races participated, snippets created, rank(for now its set to 1).
the top progress bars become a scrollable elemt in small screen/ mobile screens.
It has 2 tabs for races and snippets.

Next Steps

[ ] Add other graphs like accuracy cpm performance
[ ] Add data-table in snippets tab

Related Tickets & Documents

Related Issue #299
Closes #

QA Instructions, Screenshots, Recordings
Small demo:
https://github.com/webdevcody/code-racer/assets/95468529/c5e207b6-1f64-46fb-810f-647826def8de

UI accessibility concerns?
It is mobile responsive.

Added/updated tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

It looks a bit pissed on the mobile screens. Could you remove the scroll area and make the cards be in a column?

 It looks a bit pissed on the mobile screens. Could you remove the scroll area and make the cards be in a column?

ok will work on it and the scrolling too

repo: webdevcody/code-racer


text:
fixes tests / 32bit+64bit detection / download cache

This fixes many tests.
This removes the special handling of 64bit only for linux.
Cheers Lars
P.S: would be nice, if you can make a release, if you are fine with that.

The download tests are very flaky, plz test it on your machine. We should change from many integration tests to much less.

Thanks! If you want I could give you access to this repo if you want to be a co-maintainer?
Unfortunately the phantomjs drivers fails since bitbucket probably dislikes the many downloads. Though the errors don't really say exactly what is goes wrong.
Yes the test should not be that integration heavy, your right. The HttpClient should probably be mocked somehow. Maybe wrapped in a class that could be replaced by a mocked implementation in the tests.
Maybe you have a better idea?
Though don't have time to work on this right now though. Feel free to fix it somehow!
I'll do a release immediately!

By the way does the phantomjs drivers work without errors when using this plugin normally?

Okey I missed that you changed the 64bit check.
I'm not sure that the downloaded driver should be 64bit for internetexplorer driver if the OS is 64bit. The default internetexplorer version used on Windows 7 and 8 is 32bit. Windows 10 seems to use 64bit.
I guess phantomjs driver should be based on the OS bit version?
Any thoughts?

we should have a test case for windows. So we can be sure.

If you want I could give you access to this repo if you want to be a co-maintainer?

Would be nice. But anyway I'll prefer to have a code review by you.

By the way does the phantomjs drivers work without errors when using this plugin normally?

It worked for me. But these tests I'll do again later.


text:
Build failure when building example application Android image

I have generated the example app by following the get started documentation.
The build for the Android platform fails with the following stacktrace :
root@a743d391cae2:~/webfx-example# webfx build -m
[INFO] -------------< com.dooapp:webfx-example-application-gluon >-------------
[INFO] Building WebFXExample 1.0.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- gluonfx-maven-plugin:1.0.16:build (default-cli) @ webfx-example-application-gluon ---
[INFO] Scanning for projects...
[INFO]
[INFO] -------------< com.dooapp:webfx-example-application-gluon >-------------
[INFO] Building WebFXExample 1.0.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] >>> gluonfx-maven-plugin:1.0.16:compile (default-cli) > process-classes @ webfx-example-application-gluon >>>
[INFO]
[INFO] --- maven-enforcer-plugin:3.1.0:enforce (enforce-maven) @ webfx-example-application-gluon ---
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @ webfx-example-application-gluon ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ webfx-example-application-gluon ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] <<< gluonfx-maven-plugin:1.0.16:compile (default-cli) < process-classes @ webfx-example-application-gluon <<<
[INFO]
[INFO]
[INFO] --- gluonfx-maven-plugin:1.0.16:compile (default-cli) @ webfx-example-application-gluon ---
Feb 28, 2023 9:33:17 AM com.gluonhq.substrate.util.Logger logSevere
SEVERE: Process install native-image failed with result: 3
Check the log files under null
And please check https://docs.gluonhq.com/ for more information.
Feb 28, 2023 9:33:17 AM com.gluonhq.substrate.util.Logger logInfo
INFO: Logging process [install native-image] to file: /root/webfx-example/webfx-example-application-gluon/target/gluonfx/log/process-install native-image-1677576797076.log
java.io.IOException: Error installing native-image at: /root/.webfx/cli/graalvm/graalvm-svm-java17-linux-gluon-22.1.0.1-Final/lib/installer
Please, use gu to install native-image running the following command:
$GRAALVM_HOME/bin/gu --jvm install native-image
	at com.gluonhq.substrate.model.InternalProjectConfiguration.getGraalVMBinPath(InternalProjectConfiguration.java:590)
	at com.gluonhq.substrate.model.InternalProjectConfiguration.getGraalVersion(InternalProjectConfiguration.java:126)
	at com.gluonhq.substrate.model.InternalProjectConfiguration.checkGraalVMVersion(InternalProjectConfiguration.java:468)
	at com.gluonhq.substrate.SubstrateDispatcher.<init>(SubstrateDispatcher.java:381)
	at com.gluonhq.NativeBaseMojo.createSubstrateDispatcher(NativeBaseMojo.java:159)
	at com.gluonhq.NativeCompileMojo.execute(NativeCompileMojo.java:53)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
	at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:370)
	at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:351)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:215)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:171)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:163)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:298)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:960)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:293)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:196)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
[INFO] Total time:  3.051 s
[INFO] Finished at: 2023-02-28T09:33:17Z
[INFO] ------------------------------------------------------------------------
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
[ERROR] Failed to execute goal com.gluonhq:gluonfx-maven-plugin:1.0.16:compile (default-cli) on project webfx-example-application-gluon: Error: Error installing native-image at: /root/.webfx/cli/graalvm/graalvm-svm-java17-linux-gluon-22.1.0.1-Final/lib/installer
[ERROR] Please, use gu to install native-image running the following command:
[ERROR] $GRAALVM_HOME/bin/gu --jvm install native-image
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

The issue seems related to the installation of the native-image component of GraalVM. The logs of gu are below :
root@a743d391cae2:~/webfx-example# $GRAALVM_HOME/bin/gu --jvm install native-image
Downloading: Component catalog from www.graalvm.org
Could not load channel https://www.graalvm.org/component-catalog/graal-updater-component-catalog.properties: Unsupported GraalVM version: 22.1.0.1, platform linux/amd64
Error: Unsupported GraalVM version: 22.1.0.1, platform linux/amd64

I'm not sure whether it's an issue with webfx-cli or with the GraalVM Gluon fork. I did not find any related information to this issue. Any idea how to fix that ?
Note : I'm running the build from a Docker container, using the maven:3.8.7-eclipse-temurin-19-focal image.

Thanks for reporting this.
The issue was a mistake in the way the WebFX CLI determines the GraalVM home (the structure of the downloaded file can be very different depending on the OS). It tries to find the first /bin/ folder in the structure and then returns the parent folder as the home folder. It works in general, but in your case, it was finding /lib/installer/bin before /bin/ and therefore was passing /root/.webfx/cli/graalvm/graalvm-svm-java17-linux-gluon-22.1.0.1-Final/lib/installer instead of /root/.webfx/cli/graalvm/graalvm-svm-java17-linux-gluon-22.1.0.1-Final/ as the GraalVM home to Gluon. I think I fixed the problem by sorting all those bin folders before returning the first element (it was not sorted before).
Anyway you can get the fix by running webfx bump cli.
Let me know if that fixes your issue.

Thanks, the issue is fixed now!

authors: amischler salmonb

repo: webfx-project/webfx-cli


text:
WebGPU Samples page cannot load due to missing main.js

The previously available file at https://webgpu.github.io/webgpu-samples/main.js is missing after a recent deployment.

Could be due to the recent requirement bump to Node v20. Maybe a redeploy would help?

FWIW I've just merged https://github.com/webgpu/webgpu-samples/commit/79485ded481e57610c977b94937f9764f84fd6ff and it didn't help.
I guess something is broken. @greggman Can you have a look?

Looks OK now, guessing it was fixed by #465?

authors: beaufortfrancois iwoplaza kainino0x

repo: webgpu/webgpu-samples


text:
Inconsistencies in data if reference sample is changed

II was sent to this page:
https://storage.googleapis.com/demos.webmproject.org/webp/cmp/2024_01_25/index.html#ref=AVIF+speed+6&matcher_ssim=off&ploty=encoded_size
We're comparing for the same source image and the same SSIMULACRA2.
With WebP chosen as reference:

of codec
encoded size
encoded time
decoding time

AVIF speed 6
-29.2%
+457.0%
+170.7%

JPEG XL effort 7
-26.4%
+300.3%
+239.5%

WebP method 4
-
-
-

compared to WebP method 4
With JPEG XL chosen as reference:

of codec
encoded size
encoded time
decoding time

AVIF speed 6
+1.1%
+51.7%
+16.1%

JPEG XL effort 7
-
-
-

WebP method 4
+35.8%
-75.0%
-70.5%

compared to JPEG XL effort 7
With AVIF chosen as reference:

of codec
encoded size
encoded time
decoding time

AVIF speed 6
-
-
-

JPEG XL effort 7
-1.0%
-34.1%
-13.9%

WebP method 4
+41.2%
-82.0%
-63.1%

compared to AVIF speed 6

If WebP is the reference, then AVIF is 2.8 percentage point smaller than JPEG XL.
If JPEG XL is the reference, then AVIF is 1.1 percentage point bigger than JPEG XL.
If AVIF is chosen as the reference, JPEG XL is 1.0 percentage point smaller than AVIF.

So, 2. and 3. are relatively consistent with each other, but 1. is not.
What can explain this inconsistency? Data points are not from the same source if we change reference point?

Hi Robert-André, thank you for your interest in Codec-Compare and for your work on the framework that was used for previous comparisons.

What can explain this inconsistency?

In the Codec-Compare interface, I was careful not to imply anything more than what the filtered data points show. So the interface only shows:

If WebP is the reference, then AVIF is ~2.8 percentage point smaller than JPEG XL~ 1.41 times smaller than WebP.
If JPEG XL is the reference, then AVIF is 1.1 percentage point bigger than JPEG XL.
If AVIF is chosen as the reference, JPEG XL is 1.0 percentage point smaller than AVIF.

Data points are not from the same source if we change reference point?

The matched AVIF/WebP data points and the matched JPEG XL/WebP data points are not the same set in 1. Comparing codecs based on that can be inconsistent.
Since that was misleading, I uploaded default presets with only two codecs in the latest batch (except in the "All codecs at all efforts" preset which is convenient to experts). This way no one is tempted to compare apples with oranges.
An alternative would be to filter out the data points that are not used by all codecs but this often ends up in too few data points to get meaningful results.

Oh ok my bad, I misread the data then!
Sidenote, On https://storage.googleapis.com/demos.webmproject.org/webp/cmp/2024_03_25/index.html, it says it is version 0.2.2, are the sources available for it too?
Thanks a lot for your great tool!

version 0.2.2, are the sources available for it too?

Yes: https://github.com/webmproject/codec-compare/pull/9
I just did not create a release for that version as the changes were minor.

authors: eclipseo y-guyon

repo: webmproject/codec-compare


text:
Example using Zend Expressive

Do you know of an example that works with Zend Expressive? He tried, but it works

None that I am aware of

As of version 0.10.0 there is a PSR-7 compatible standard server. It should be possible to use it as is with Zend Expressive.

FYI, this is the integration I came up with. It could be cleaner, but at least it is simple. The middleware itself look like:
<?php

declare(strict_types=1);

namespace Application\Action;

use Application\Api\Schema;
use GraphQL\Doctrine\DefaultFieldResolver;
use GraphQL\GraphQL;
use GraphQL\Server\StandardServer;
use Interop\Http\ServerMiddleware\DelegateInterface;
use Interop\Http\ServerMiddleware\MiddlewareInterface;
use Psr\Http\Message\ServerRequestInterface;
use Zend\Diactoros\Response\JsonResponse;

class GraphQLAction implements MiddlewareInterface
{
    public function process(ServerRequestInterface $request, DelegateInterface $delegate)
    {
        GraphQL::setDefaultFieldResolver(new DefaultFieldResolver());

        $schema = new Schema();
        $server = new StandardServer([
            'schema' => $schema,
            'queryBatching' => true,
            'debug' => true,
        ]);

        $parsedBody = json_decode($request->getBody()->getContents(), true);
        $request = $request->withParsedBody($parsedBody);
        $response = $server->executePsrRequest($request);

        return new JsonResponse($response);
    }
}

Configure it in config/autoload/dependencies.global.php:
return [
    'dependencies' => [
        'invokables' => [
            GraphQLAction::class => GraphQLAction::class,
        ],
    ],
];

And declare a route in config/routes.php:
$app->post('/graphql', Application\Action\GraphQLAction::class, 'graphql');

@PowerKiKi Why you shouldn't need following lines:
$parsedBody = json_decode($request->getBody()->getContents(), true);
$request = $request->withParsedBody($parsedBody);

They seem redundant as server should already do it (if Content-Type header in the request is application/json).
Following should work as is (if something doesn't work, then it is probably a bug):
public function process(ServerRequestInterface $request, DelegateInterface $delegate)
{
    $schema = new Schema();
    $server = new StandardServer([
        'schema' => $schema,
        'queryBatching' => true,
        'debug' => true,
        'fieldResolver' => new DefaultFieldResolver()
    ]);
    $response = $server->executePsrRequest($request);
    return new JsonResponse($response);
}

Also there is complementary project https://github.com/phps-cans/psr7-middleware-graphql

Thanks for mentioning psr7-middleware-graphql, I wasn't aware of it.
The parsing of JSON is necessary in my case, otherwise parsedBody is empty and the server will fail to decode json from non-parsed body. I was surprised by this behavior as I was expecting it would work out of the box as you described. Would you want me to open an issue for that ?

If parsedBody is empty, then it is a bug. Will appreciate if you open an issue for it. But are you sure Content-Type header is set properly to application/json in your case?

authors: PowerKiKi benjamingb vladar

repo: webonyx/graphql-php

license: mit


text:
CLA IP Policy

Hi,
What happens now?
The CLA agreement doesn't seem to link to the IP Policy correctly. It shows
 [JS Foundation IP Policy]({{ site.url }}{{ site.baseurl }}/pdf/ip-policy.pdf).

What should happen?
The CLA agreement should link to the correct IP policy. Googling shows this IP Policy -> JS Foundation
Could you guys please fix it? :)

Thank you for reporting this. The CLA document actually isn't stored at this repo as far as I know. I think this issue maybe should be moved elsewhere.
@d3viant0ne do you typically manage this? Should I move this issue to a webpack-contrib repo like this one or this one?
cc @webpack/core-team

The CLA & it's associated bot is a service provided & hosted by the JSFoundation.

Ok so then it looks like maybe I need to move this issue here then? Will do so momentarily, but if there's a better place let me know.

Moved to JSFoundation/cla-assistant#7

authors: d3viant0ne maheshpec skipjack


text:
Fix typo in 'Under the hood' page

This PR fixes a typo in 'under the hood' page of the docs.

Please sign the CLA

Thanks!

authors: GnsP anshumanv montogeek


text:
feat: #5105 add pathname at the end of dropdown language url

Added pathname to keep the consistency of reading while changing language.
Closes https://github.com/webpack/webpack.js.org/issues/5105

Really nice feature. However there is one problem, say I'm browsing /concepts/plugins/#usage and want to check the respective Chinese version, clicking the button would bring me to chinese-site/concepts/plugins/ instead of chinese-site/concepts/plugins/#usage.
I think we should retain the URI fragment as well, just like how we did when changing the version of webpack documentation:

Here's the code https://github.com/webpack/webpack.js.org/blob/master/src/components/Sidebar/Sidebar.jsx#L25 just in case you want to take a look.

Btw, can you sign cla here https://cla.js.foundation/webpack/webpack.js.org?pullRequest=5108?

@chenxsan I've signed! 😀

Really nice feature. However there is one problem, say I'm browsing /concepts/plugins/#usage and want to check the respective Chinese version, clicking the language button would bring me to chinese-site/concepts/plugins/ instead of chinese-site/concepts/plugins/#usage.
I think we should retain the URI fragment as well, just like how we did when changing the version of webpack documentation:

Here's the code https://github.com/webpack/webpack.js.org/blob/master/src/components/Sidebar/Sidebar.jsx#L25 just in case you want to take a look.

Good catch! what if I pass location.hash as a prop to use it on Navigation?

I just found a bug in the current implementation.
Here's how to reproduce:
Open https://webpack-js-org-git-fork-cs09g-feature-issue-bdc88a-webpack-docs.vercel.app/concepts/entry-points/#multi-page-application, then change the version. You'll see the URI fragment is missing.

@chenxsan Hmm, the hash is missing. Is that based on the last commit on this PR? Or is something different on the build with on localhost?

We have this preview https://github.com/webpack/webpack.js.org/pull/5108#issuecomment-867109431 synced with the latest commit of current pull request, so the preview should be up to date.
The build is actually a server-side rendered first, then hydrated on client-side app. So, yes, it's not the same as the dev one on localhost.

@chenxsan I've pushed one more commit after the preview generated. I guess it's fine with the next deployment. check this out. https://webpack-js-org-1ozc7s86g-webpack-docs.vercel.app/

Neither does it work. You can open https://webpack-js-org-1ozc7s86g-webpack-docs.vercel.app/concepts/entry-points/#multi-page-application to inspect.
But I did notice the discrepancy here:

The href prop in React virtual DOM is up to date, however the real DOM is stale.
So the problem could be hash is client side only, and it's not hydrated on client side causing the issue. How about handling it with useEffect?

I got it. I could check this out with `yarn build-test' on localhost. By the way, It's a class component. It needs to be refactored.

@cs09g Seems the CLA is not signed, can you double check?

@chenxsan I did. Some of my commits pushed as different emails with Github. Should I re-commit with the email that I signed in CLA?

@chenxsan I did. Some of my commits pushed as different emails with Github. Should I re-commit with the email that I signed in CLA?

Yeah, the bot is not that smart to handle it.

@chenxsan Thanks for the warm review!


text:
Update hmr-react.md

small commit :) one extra line)

Can you sign the CLA? Good to go after that.

@bebraw , ah, sorry, i'm new here... I hope now I did it right.

It's cool. Thanks. 👍

authors: BorodinDemid bebraw


text:
How to deal with variables in class DependenciesBlock in Webpack 5

Hi,
I'm trying to learn Webpack internals in order to upgrade worker-plugin to Webpack 5 support.
Actually it leverages on Webpack v4 ParserHelpers methods:

toConstantDependency
addParsedVariableToModule

The first is present also in Webpack v5 JavascriptParserHelpers but the second is not. I followed the source code and stumbled into the DependenciesBlock class
The DependenciesBlock class features a this.variables = [] property in Webpack v4 which is missing in the constructor method in Webpack v5.
The same applies to the addVariable method which is present in DependenciesBlock for Webpack v4 but not for Webpack v5. This specific method is the one that is called by the addParsedVariableToModule in Webpack v4 ParserHelpers.
I would like to know if there's a beaten path to follow for this particular update case from Webpack v4 to Webpack v5?
Thanks :100: for the awesome lib!!!

These variables were removed.
You should use InitFragments instead.

Depending on the use case you may be able to use one of the core dependency classes for that.

Or try always using HarmonyImportSpecifierDependency instead of branching

Thanks a lot @sokra! Checking them out

Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks!

authors: evilebottnawi lanceschi sokra

repo: webpack/webpack


text:
Use CommonsChunkPlugin twice on one page

As part of our caching strategy, I have set up a configuration where we have two instances of CommonsChunkPlugin: one for vendor scripts; one for common app code. Now we want to include both on every page. But the generated vendor.js and commons.js each include the webpack runtime, which doesn't work.
Is there a way to remove the runtime from one of those bundles, or is there a different correct way to do this?

I have two instances of CommonsChunkPlugin : vendor and common.
webpack.conf:
var entry = {
        profile: [ './app/frontend/javascripts/profile/main.es6'],
        projects: [ './app/frontend/javascripts/projects/main.es6'],
        // the vendor entry point
        vendor: ['babel-polyfill', 'lodash', 'jquery']
    };

    var plugins = [
        new webpack.optimize.CommonsChunkPlugin("common", 'common' + (options.longTermCaching ? '-[chunkhash].js' : '.js'), ['projects', 'profile']),
        new webpack.optimize.CommonsChunkPlugin("vendor", 'vendor' + (options.longTermCaching ? '-[chunkhash].js' : '.js' ), ['common', 'vendor'], Infinity)
    ];

The webpack runtime is only present into the vendor bundle and I can use them like this :
  <script src="[...]/assets/vendor.js"></script>
  <script src="[...]/assets/common.js"></script>
  <script src="[...]/assets/profile.js"></script>

I hope this will help you (I don't know if it is the correct way to do it but it seems to work)

Is there a way to remove the runtime from one of those bundles, or is there a different correct way to do this?

@andrewbranch You can do it the way @fredericgrati does it. One of the Plugins should have the name of the other commons chunk in the chunks property.

I'm a little confused but that seems to work nicely. Thanks!

authors: andrewbranch fredericgrati sokra


text:
Support 'overrides' option for bower.json

This example can't support bower overrides options.
http://webpack.github.io/docs/usage-with-bower.html
bower overrides spec is here.
https://github.com/bower/bower/issues/585
Now I take file by foo/dist/foo.min.js for work arround. Browserify and https://github.com/ck86/main-bower-files support it.

Closing as the issue has moved to here: https://github.com/lpiepiora/bower-webpack-plugin/issues/21 Thanks!

authors: mizchi shama


text:
hot module reload causing Maximum call stack size exceeded

Do you want to request a feature or report a bug?
report a bug

What is the current behavior?
following the HMR Guide
devServer.hot: true and plugins contains new webpack.HotModuleReplacementPlugin().
When my webpack config has both of these changes I get a seemingly infinite loop. console details
If the current behavior is a bug, please provide the steps to reproduce.
follow the guide linked above, change some code in print.js

What is the expected behavior?
That the code is reloaded without an error.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

see https://github.com/webpack/webpack-dev-server/issues/87

Same thing here, removing the plugin
new webpack.HotModuleReplacementPlugin()
from the webpack config seems to fix the issue and hot reloading still seems to work

Closing due to inactivity. Please test with latest version webpack and webpack-dev-server and feel free to reopen if still regressions. Also i recommend migrate on webpack-serve Thanks!

authors: Aequitas737 evilebottnawi flazz sokra


text:
fix(schema): Added "binaries" to issueTypes

The current schema identifies binaries as invalid when adding it the the knip config for include or exclude, however it is a valid option.

Thanks @fnannestad! Now I see "unresolved" was also missing, which I'll add. Have a great day 🌞

authors: fnannestad webpro

repo: webpro/knip

license: ISC


text:
Add handlebars partials support

I needed to separate several entities/resources structures in different files to proper organization and reuse, so I modified my local copy of dummy-json.js to be able to register Handlebars.partials(). I think that it would be nice if it was available to everyone, since it register partials is one of the main features of Handlebars.

Thanks for this! Really nice addition.

You're welcome :)
2015-08-02 7:04 GMT-03:00 Matt Sweetman notifications@github.com:

Thanks for this! Really nice addition.
—
Reply to this email directly or view it on GitHub
https://github.com/webroo/dummy-json/pull/4#issuecomment-127010352.

--
Andrei Ben-Hur
Webdesigner / Front-End Developer
São Paulo - SP
+55 11 9 7461020

authors: andreibenhur webroo

repo: webroo/dummy-json


text:
[ICE/STUN] replace crc32fast with crc

crc32fast should be replaced with crc crate, due to crc32fast issue found in sctp crate

Hi, can I try tackling this issue? also, is there a reason for using crc 1.8.1 instead of 2.0?

sure. It is better to use the latest version of crc.

@u-03c9 , I assign this task to you. You can also upgrade crc in sctp crate to the latest version.

I am a beginner. So, please let me know if the code needs any modifications.

LGTM, accepted all PRs.

Thank you for the fix

repo: webrtc-rs/webrtc


text:
Migrate to Travis CI

This provides equivalent functionality:

site build runs on every commit push and Pull Request
the build is then copied to the prod website, if the commit push was on gh-pages branch

Additionally, html-proofer can be run for all builds.
It is currently disabled due to #131.
Closes #130.

Ah, it's a good point about travis encrypt-file. I should definitely add a comment in the script. Thanks.
Will do it in few hours, when I get to my laptop (on mobile now).

repo: webrtc/webrtc-org


text:
🛑 Jeff with Susan is down

In dab9caa, Jeff with Susan (https://www.jeffwithsusan.com) was down:

HTTP code: 521
Response time: 107 ms

Resolved: Jeff with Susan is back up in ab0803b after 417 days, 3 hours, 52 minutes.

repo: webworldview/uptime


text:
🛑 Web World View is down

In 4b0b507, Web World View (https://www.webworldview.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Web World View is back up in 887a3f1 after 18 minutes.


text:
"Content" Development

The most "natural" way to use WP Starter is to pull themes and plugins as Composer packages.
However, very often I found myself in the need to have some plugin or mu-plugins only for the website I'm working on. An example could be a MU plugin used to store configurations...
Considering that one hardly wants to create a package for that kind of things, there are, at least, 2 ways to do this.

Create Gists, and set up a Composer repository for them. An example of doing this is even included in current WP Starter documentation. However this is not a very good approach, since it is hard keep in sync local with remote
Include the package in the main repository, the one that contains the main composer.json.

This is valid for plugins, MU plugins and even for themes. When a package is developed just for the website and will never be used in any other place, it makes perfectly sense keep under the same repository of the website stack.
This has been discussed in #23
In my projects I'm currently using an approach where I have a content-dev folder, with plugins, themes and mu-plugins subfolders. On install / update all of these folders are symlinked in the related "wp-content" folder, so WordPress recognize them.
This way I can keep under version control plugin and themes without keep under version control the content folder, that contains 3rd party plugin and themes.
I found this approach works very well, and I think it worth to be more integrated in WP Starter.

This is done on current v3 version. Closing for cleanup.

repo: wecodemore/wpstarter


text:
Tutorial Problem

URL: /tutorials/auth-web/deploy-project/

I'm trying to deploy an app using this tutorial but if fails with the error "Invalid credentials"
OS: Windows 10; CLI: 1.0.17
This is the full output:
we deploy -p 980273254666 -V
Deploying services on project 980273254666 in wedeploy.com...
⠸ Uploading deployment package...
⠂ auth-980273254666.wedeploy.io
⠂ ui-980273254666.wedeploy.io
Deploying services on project 980273254666 in wedeploy.com...
! Deployment failed in 1s.
! Upload failed auth-980273254666.wedeploy.io.
! Upload failed ui-980273254666.wedeploy.io.
! Something went wrong with your "we deploy" operation.
! Invalid credentials.
Deferred verbose messages below
> GET https://api.wedeploy.com/projects/980273254666 HTTP/1.1
User-Agent: WeDeploy/master (+https://wedeploy.com)
Content-Type: application/json
Authorization: 1 hidden value

< HTTP/1.1 200 OK
Vary: Accept-Encoding
Date: Wed, 30 Aug 2017 19:32:14 GMT
X-Dns-Prefetch-Control: off
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Access-Control-Allow-Origin: *
Content-Type: application/json; charset=utf-8
Content-Length: 316
Etag: W/"13c-jggzPC7naeKKwS69HXjEnMBkb2w"
Strict-Transport-Security: max-age=15552000; includeSubDomains
X-Download-Options: noopen
X-Xss-Protection: 1; mode=block
{
"createdAt": 1504120380881,
"github": {},
"invitations": {},
"collaborators": [
"240137170347138544"
],
"health": "empty",
"healthUid": "52d914db-4637-448c-ac23-149029a7e6ab",
"planId": "free",
"id": "242469318719032829",
"masterToken": "1442cb9c-942b-48e6-8a6c-186bc4721a70",
"ownerId": "240137170347138544",
"projectId": "980273254666"
}
Running git init
Microsoft Windows detected: using git system config
Running git config user.name WeDeploy user --local
Running git config user.email user@deployment --local
Running git add C:\wedeploy\tutorial-auth-web\auth
Running git add C:\wedeploy\tutorial-auth-web\ui
Running git commit --allow-empty --message Deployment at Wed Aug 30 16:31:43 -0300 2017
Running git rev-parse HEAD
commit c1e83f335c1a282ed18f0994441404469d75339f
Running git remote add wedeploy https://git.wedeploy.com/980273254666.git
Resetting credential helpers
Running git config --add credential.helper
Running git config --add credential.helper C:\\Users\\PSANTIAGO\\AppData\\Local\\Programs\\we\\bin\\we.exe git-credential-helper
Running git push wedeploy master --force --verbose

@henvic can you check?

@psantiago32,
Sorry for the delay in answering you.
Do you still have the same issue? If you do, do you mind contacting me at henrique.vicente@liferay.com from the same email address you use [allowing me permission to impersonate you for 96h to debug this feature]?
Thanks.
This seems to be an intermittent issue and I would need your help to debug this.
I have been able to reproduce it myself for a while, but then it started working normally.

@henvic I sent you an email

Hey @psantiago32 and @henvic, were you able to resolve this issue? If so, we will close. Thanks!

I think this is already fixed. If not, please reopen.

authors: henvic jonnilundy psantiago32 zenorocha


text:
Replaces all tabs with spaces

Closes #446

Congrats on your first PR! 🎉

authors: jaredgorski jonnilundy


text:
Cannot read property 'Symbol(Symbol.iterator)' of undefined

请问一下，有谁碰到过这个问题么。这个脚手架坑好多啊。

同样有这个问题，先是 ATSDK找不着，把ATSDK-weex改成ATSDK之后，编译是能过了，但是启动的时候又报这个错，简直无语啊，weex坑为啥那么多，照着官方文档连个hello world都跑不起来

repo: weexteam/weex-pack


text:
Aggressiveness

Any way i can make it less aggressive?
Thank you for your work!!!

See BenV's fork improve-vad branch for switching models.


text:
Correct alignment of icons

corrected alignment of icons to filenames
changed vertical spacing of li elements to account for increased height of anchors

Demo of improvement

s.

Sorry but I didn't get the point. Here is what this PR looks like on my machine (macOS Monteray with Firefox)

Hmm. I have a Mac computer, let me investigate it on there.

Thank you for the PR. Unfortunately I have no time working on it. See #108.

authors: mu-arch weihanglo

repo: weihanglo/sfz


text:
xelatex thesis 编译报错

当运行xelatex thesis的时候编译报错，错误信息如下
(/usr/share/texmf-dist/tex/latex/listings/lstmisc.sty) [11]) [12]
(./tex/chapter03.tex
第三章
Error: /typecheck in resourcestatus
Operand stack:
   false   ct_StyleDicts   --dict:0/4(L)--   Adobe-Japan1   --dict:0/4(L)--   Serif   HeiseiMin-W3-83pv-RKSJ-H   Font   HeiseiMin-W3-83pv-RKSJ-H   (HeiseiMin-W3-83pv-RKSJ-H)   true   --nostringval--   --nostringval--   0
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1977   1   3   %oparray_pop   1976   1   3   %oparray_pop   --nostringval--   1960   1   3   %oparray_pop   1852   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   1931   8   8   %oparray_pop
Dictionary stack:
   --dict:1202/1684(ro)(G)--   --dict:0/20(G)--   --dict:88/200(L)--   --dict:57/75(L)--   --dict:2/10(L)--   --dict:39/70(L)--   --dict:0/4(L)--   --dict:0/4(L)--   --dict:17/17(ro)(G)--
Current allocation mode is local
Current file position is 91048
GPL Ghostscript 9.18: Unrecoverable error, exit code 1
[13
xdvipdfmx:fatal: pdf_ref_obj(): passed invalid object.

系统环境：

archlinux
texlive 2015
TeX Gyre Font西文字体和Adobe四款中文字体已安装

怎么会引用到Adobe-Japan1和HeiseiMin-W3这些日文编码区域的东西？你确定你编译的是sjtuthesis附带的示例文档，没有对其内容进行过编辑？

我是clone下来以后直接编译的，没有做过任何修改。我把texlive重新安装以后还是不行。
以下是完整的log.
http://bl.ocks.org/YanlongLi/93efed3928fac9b62390

我在 MacTeX 上不能重现这个问题，在编译日志中也没有看到调用ghostscript。我担心是ghostscript的问题，使用ghostscript /typecheck error在Google搜索能找到不少类似条目。
http://www.cnblogs.com/atison/p/3480092.html
建议再进一步确定是哪一段代码触发该问题：

注释正文第11页用lstlist插入的两段代码；
注释插入PDF和EPS图片(有字型嵌入)；

注释掉包含eps文件的代码后能够正常编译，问题是出在gs转换eps文件的时候，同时我用gs转换esp文件时候报如上的错误。

我这边gs版本是：
$ gs -v
GPL Ghostscript 9.16 (2015-03-30)
Copyright (C) 2015 Artifex Software, Inc.  All rights reserved.

请问用gs转换eps操作是用了哪个命令？

$ gs -v
GPL Ghostscript 9.18 (2015-10-05)
Copyright (C) 2015 Artifex Software, Inc.  All rights reserved.

转换用的ps2pdf命令，用gs命令也无法打开文件sjtulogo.eps。报的错误是一样的。
找了另外一个eps文件转换没有问题。
怀疑是不是我这个版本的ghostscript的bug。

好的，临时解决方案是不插入EPS图，尽可能用PDF或者其他格式替代，待ghostscript更新后看这个问题是否还存在。
这个issue我先关了。

嗯。应该是这个bug，
ghostscript fails on some EPS files
我这里安装完整的texlive-lang包还是不行，反正就是eps文件字体的原因。先暂时用pdf替代吧。

最近升级以后，我在 Mac OS X 下也踩到了这个坑，编译的错误提示是：
GPL Ghostscript 9.16: Can't find initialization file gs_init.ps.
xdvipdfmx:fatal: pdf_ref_obj(): passed invalid object.

临时的解决办法就是不插入EPS文件。考虑到EPS文件受众面越小，后面就干脆不要给插入EPS图片的例子了。

@YanlongLi
TeX 下使用 EPS 插图估计是上古时代的用法了，历史遗留问题。
插图首推 PDF, 其次如 png 等，如果遇到非 PDF/png 等图片，先转换下，Windows 下虚拟打印(Foxit Reader/CUPS-PDF)输出 PDF 即可，Linux/OS X 下可使用 imagemagick, Matlab/matplotlib 等最好设置直接输出 PDF.

authors: YanlongLi billryan weijianwen

repo: weijianwen/SJTUThesis


text:
Evaluate use of concepts pages

What is the problem to solve?
The concepts pages are useful
What stage of research is it? (discovery/general usability testing/post release)
general usability testing
What are the objectives?

The concepts pages are useful
People use the concepts pages
People view more after being inspired by Concepts
People find more stuff they want to view
Arriving users from Google have a better understanding of the site

What are the assumptions?

People use the All images/works and About/By tabs.
Total views of concepts pages: concepts will appear in url so can use GA
Total unique concepts pages viewed
Increased average time in collections
Googlers - do they land on concepts?

What research technique is required?
Python, Kibana

@jennpb Here is the first draft of a discussion document:
https://docs.google.com/document/d/1qdhSZuqg_9iFlyHxCDGG5482Fg3lumNPKqjcXQZ59yo/edit

Work following from this is in #10194


text:
Extend label to be subfields a,b,c,d,t and remove prefix / numeration from person

Does the Person /  Organisation transformation bit for https://github.com/wellcometrust/platform/issues/3591

@alexwlchan made another change post review, fancy another set of 👁s on it?
https://github.com/wellcometrust/catalogue/pull/40/commits/366291a4d23e99e1a24175e0124e1bb8115a825a

repo: wellcometrust/catalogue


text:
Investigate removal of lambda triggers ...

... when lambdas are tainted and recreated.

Having done a bit of digging: this only occurs with the CloudWatch based triggers.
I’d like to use depends_on so that the triggers can’t be created until after the Lambda is done, but it doesn’t seem like Terraform lets you do that.

You can depend on an entire module being created…
But the creation of a module can’t be dependent on anything.
Nor can you inject a dependency into a module.

The triggers are updated when you re-run terraform plan. Next Q: what happens if we taint the trigger at the same time we taint the Lambda? 🤔

if we taint the trigger at the same time we taint the Lambda?

Nope, we still lose the trigger when we re-apply. :(
How would folks feel about having an apply wrapper script that detects if we need to re-plan and apply because the Lambdas got tainted? @alicefuzier @kenoir

It’s still the case that re-running plan if you've changed the Lambda source code doesn't notice and trigger an update. Maybe trashing the auto-generated ZIP bundle…?

Nope, trashing the ZIP bundles in such a way that their contents/checksums change doesn’t do it.

authors: alexwlchan kenoir

repo: wellcometrust/platform-api


text:
update gruntfile to not break on JS compiling while watching

Grunt JS compile errors were breaking the watch loop - this fixes that.

Merging this as it's slowing my workflow.