Routing mesh not working as expected in docker swarm mode

BUG REPORT INFORMATION
Description
Same as this thread:
https://github.com/docker/docker/issues/25395
Steps to reproduce the issue:
manager-node1# docker swarm init
manager-node2# docker swarm join --token MANAGER-TOKEN <IP_ADDRESS>:2377
worker-node1# docker swarm join --token WORKER-TOKEN <IP_ADDRESS>:2377

manager-node1# docker node ls
ID                           HOSTNAME       STATUS  AVAILABILITY  MANAGER STATUS
3qlnufc9dvk1rg6a45ri5i8zr *  ip-10-0-1-100  Ready   Active        Leader
834zcbi5ks6qu5goxx4mtvt9m    ip-10-0-2-100  Ready   Active        Reachable
d5pdp8uv85lf55ta8tazerx30    ip-10-0-22-47  Ready   Active

manager-node1# docker service create --name=nginx --publish=80:80/tcp nginx
2o2y4i6h6cf1svikxwi3zil3o

manager-node1# docker service ls
ID            NAME   REPLICAS  IMAGE  COMMAND
2o2y4i6h6cf1  nginx  1/1       nginx

manager-node1# docker service ps nginx
ID                         NAME     IMAGE  NODE           DESIRED STATE  CURRENT STATE           ERROR
399vteqgdg9d7euxxc8vumegv  nginx.1  nginx  ip-10-0-1-100  Running        Running 15 minutes ago

manager-node1# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
69ed9d5ed624        bridge              bridge              local
6d71fb491526        docker_gwbridge     bridge              local
9f67db38bffa        host                host                local
3aoco5o66v6e        ingress             overlay             swarm
3ca82b5cdb8e        none                null                local

manager-node1# docker service inspect nginx
[
    {
        "ID": "2o2y4i6h6cf1svikxwi3zil3o",
        "Version": {
            "Index": 45
        },
        "CreatedAt": "2016-12-14T17:17:28.195816051Z",
        "UpdatedAt": "2016-12-14T17:17:28.202463462Z",
        "Spec": {
            "Name": "nginx",
            "TaskTemplate": {
                "ContainerSpec": {
                    "Image": "nginx"
                },
                "Resources": {
                    "Limits": {},
                    "Reservations": {}
                },
                "RestartPolicy": {
                    "Condition": "any",
                    "MaxAttempts": 0
                },
                "Placement": {}
            },
            "Mode": {
                "Replicated": {
                    "Replicas": 1
                }
            },
            "UpdateConfig": {
                "Parallelism": 1,
                "FailureAction": "pause"
            },
            "EndpointSpec": {
                "Mode": "vip",
                "Ports": [
                    {
                        "Protocol": "tcp",
                        "TargetPort": 80,
                        "PublishedPort": 80
                    }
                ]
            }
        },
        "Endpoint": {
            "Spec": {
                "Mode": "vip",
                "Ports": [
                    {
                        "Protocol": "tcp",
                        "TargetPort": 80,
                        "PublishedPort": 80
                    }
                ]
            },
            "Ports": [
                {
                    "Protocol": "tcp",
                    "TargetPort": 80,
                    "PublishedPort": 80
                }
            ],
            "VirtualIPs": [
                {
                    "NetworkID": "3aoco5o66v6e8hro8u26gm5nf",
                    "Addr": "<IP_ADDRESS>/16"
                }
            ]
        },
        "UpdateStatus": {
            "StartedAt": "0001-01-01T00:00:00Z",
            "CompletedAt": "0001-01-01T00:00:00Z"
        }
    }
]

manager-node2# docker network inspect ingress
[
    {
        "Name": "ingress",
        "Id": "3aoco5o66v6e8hro8u26gm5nf",
        "Scope": "swarm",
        "Driver": "overlay",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/16",
                    "Gateway": "<IP_ADDRESS>"
                }
            ]
        },
        "Internal": false,
        "Containers": {
            "2398151d877a813cbd10e09803ef6c13427fea0e62452b097b777b965ee18516": {
                "Name": "nginx.1.399vteqgdg9d7euxxc8vumegv",
                "EndpointID": "786ffbb8aa2c0b189a239fee8221bb412b33f1a5ef96a057d1d6358c757e88fa",
                "MacAddress": "02:42:0a:ff:00:07",
                "IPv4Address": "<IP_ADDRESS>/16",
                "IPv6Address": ""
            },
            "ingress-sbox": {
                "Name": "ingress-endpoint",
                "EndpointID": "83a34f5d1bb76d8d0de3fd09ed8e381b22a2b9bfd82723bf3565f0845903156d",
                "MacAddress": "02:42:0a:ff:00:03",
                "IPv4Address": "<IP_ADDRESS>/16",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.driver.overlay.vxlanid_list": "256"
        },
        "Labels": {}
    }
]

manager-node1# ss -tlnp
State      Recv-Q Send-Q                                                  Local Address:Port                                                                 Peer Address:Port
LISTEN     0      128                                                                 *:22                                                                              *:*                   users:(("sshd",pid=1185,fd=3))
LISTEN     0      128                                                                :::2377                                                                           :::*                   users:(("dockerd",pid=1154,fd=15))
LISTEN     0      128                                                                :::7946                                                                           :::*                   users:(("dockerd",pid=1154,fd=22))
LISTEN     0      128                                                                :::80                                                                             :::*                   users:(("dockerd",pid=1154,fd=32))
LISTEN     0      128                                                                :::22                                                                             :::*                   users:(("sshd",pid=1185,fd=4))

manager-node2# docker service inspect nginx
[
    {
        "ID": "2o2y4i6h6cf1svikxwi3zil3o",
        "Version": {
            "Index": 45
        },
        "CreatedAt": "2016-12-14T17:17:28.195816051Z",
        "UpdatedAt": "2016-12-14T17:17:28.202463462Z",
        "Spec": {
            "Name": "nginx",
            "TaskTemplate": {
                "ContainerSpec": {
                    "Image": "nginx"
                },
                "Resources": {
                    "Limits": {},
                    "Reservations": {}
                },
                "RestartPolicy": {
                    "Condition": "any",
                    "MaxAttempts": 0
                },
                "Placement": {}
            },
            "Mode": {
                "Replicated": {
                    "Replicas": 1
                }
            },
            "UpdateConfig": {
                "Parallelism": 1,
                "FailureAction": "pause"
            },
            "EndpointSpec": {
                "Mode": "vip",
                "Ports": [
                    {
                        "Protocol": "tcp",
                        "TargetPort": 80,
                        "PublishedPort": 80
                    }
                ]
            }
        },
        "Endpoint": {
            "Spec": {
                "Mode": "vip",
                "Ports": [
                    {
                        "Protocol": "tcp",
                        "TargetPort": 80,
                        "PublishedPort": 80
                    }
                ]
            },
            "Ports": [
                {
                    "Protocol": "tcp",
                    "TargetPort": 80,
                    "PublishedPort": 80
                }
            ],
            "VirtualIPs": [
                {
                    "NetworkID": "3aoco5o66v6e8hro8u26gm5nf",
                    "Addr": "<IP_ADDRESS>/16"
                }
            ]
        },
        "UpdateStatus": {
            "StartedAt": "0001-01-01T00:00:00Z",
            "CompletedAt": "0001-01-01T00:00:00Z"
        }
    }
]

manager-node2# docker network inspect ingress
[
    {
        "Name": "ingress",
        "Id": "3aoco5o66v6e8hro8u26gm5nf",
        "Scope": "swarm",
        "Driver": "overlay",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/16",
                    "Gateway": "<IP_ADDRESS>"
                }
            ]
        },
        "Internal": false,
        "Containers": {
            "ingress-sbox": {
                "Name": "ingress-endpoint",
                "EndpointID": "9741db0beaf259829293316a96415168657efc93c2ac35d2dc53d8fcea68cba3",
                "MacAddress": "02:42:0a:ff:00:05",
                "IPv4Address": "<IP_ADDRESS>/16",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.driver.overlay.vxlanid_list": "256"
        },
        "Labels": {}
    }
]

manager-node2# ss -tlnp
State      Recv-Q Send-Q                                                  Local Address:Port                                                                 Peer Address:Port
LISTEN     0      128                                                                 *:22                                                                              *:*                   users:(("sshd",pid=1197,fd=3))
LISTEN     0      128                                                                :::2377                                                                           :::*                   users:(("dockerd",pid=1191,fd=14))
LISTEN     0      128                                                                :::7946                                                                           :::*                   users:(("dockerd",pid=1191,fd=21))
LISTEN     0      128                                                                :::80                                                                             :::*                   users:(("dockerd",pid=1191,fd=26))
LISTEN     0      128                                                                :::22                                                                             :::*                   users:(("sshd",pid=1197,fd=4))

worker-node1# docker service inspect nginx
[]
Error response from daemon: This node is not a swarm manager. Worker nodes can't be used to view or modify cluster state. Please run this command on a manager node or promote the current node to a manager.

worker-node1# docker network inspect ingress
[]
Error: No such network: ingress

worker-node1# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
90edd96c41f6        bridge              bridge              local
d7e7a7e629fa        host                host                local
eeaad60df004        none                null                local

worker-node1# ss -tlnp
State      Recv-Q Send-Q                                                  Local Address:Port                                                                 Peer Address:Port
LISTEN     0      128                                                                 *:22                                                                              *:*                   users:(("sshd",pid=1144,fd=3))
LISTEN     0      128                                                                :::22                                                                             :::*                   users:(("sshd",pid=1144,fd=4))

docker logs:
#MANAGER1
Dec 14 14:54:27 ip-10-0-1-100 systemd[1]: Found device /dev/mapper/vg_docker-lv_docker.
Dec 14 14:54:27 ip-10-0-1-100 systemd[1]: Starting File System Check on /dev/mapper/vg_docker-lv_docker...
Dec 14 14:54:27 ip-10-0-1-100 systemd[1]: Started File System Check on /dev/mapper/vg_docker-lv_docker.
Dec 14 14:54:27 ip-10-0-1-100 systemd[1]: Mounting /var/lib/docker...
Dec 14 14:54:27 ip-10-0-1-100 systemd[1]: Mounted /var/lib/docker.
Dec 14 14:54:27 ip-10-0-1-100 kernel: [    4.935626] audit: type=1400 audit(1481727261.736:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=885 comm="apparmor_parser"
Dec 14 14:54:43 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:43.043042236Z" level=info msg="libcontainerd: new containerd process, pid: 1383"
Dec 14 14:54:48 ip-10-0-1-100 kernel: [   31.209184] audit: type=1400 audit(1481727288.012:16): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="docker-default" pid=1623 comm="apparmor_parser"
Dec 14 14:54:48 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:48.144414922Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Dec 14 14:54:48 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:48.145112507Z" level=warning msg="Your kernel does not support swap memory limit."
Dec 14 14:54:48 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:48.145935090Z" level=info msg="Loading containers: start."
Dec 14 14:54:48 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:48.392406506Z" level=info msg="Firewalld running: false"
Dec 14 14:54:48 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:48.796593320Z" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
Dec 14 14:54:49 ip-10-0-1-100 kernel: [   32.538664] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Dec 14 14:54:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:49.371255046Z" level=info msg="Loading containers: done."
Dec 14 14:54:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:49.371372791Z" level=info msg="Daemon has completed initialization"
Dec 14 14:54:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:49.371395293Z" level=info msg="Docker daemon" commit=6b644ec graphdriver=aufs version=1.12.3
Dec 14 14:54:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:54:49.387548799Z" level=info msg="API listen on /var/run/docker.sock"
Dec 14 14:57:21 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:21.208343328Z" level=error msg="Error getting nodes: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
Dec 14 14:57:21 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:21.208383211Z" level=error msg="Handler for GET /v1.24/nodes returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
Dec 14 14:57:48 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:48.997624153Z" level=info msg="Listening for local connections" addr="/var/lib/docker/swarm/control.sock" proto=unix
Dec 14 14:57:48 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:48.998421064Z" level=info msg="Listening for connections" addr="[::]:2377" proto=tcp
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.011433056Z" level=info msg="65af61b7b0ebc9f became follower at term 0"
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.011948885Z" level=info msg="newRaft 65af61b7b0ebc9f [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]"
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.011981102Z" level=info msg="65af61b7b0ebc9f became follower at term 1"
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.012825042Z" level=info msg="65af61b7b0ebc9f is starting a new election at term 1"
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.013138362Z" level=info msg="65af61b7b0ebc9f became candidate at term 2"
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.013356951Z" level=info msg="65af61b7b0ebc9f received vote from 65af61b7b0ebc9f at term 2"
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.013589176Z" level=info msg="65af61b7b0ebc9f became leader at term 2"
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.013623786Z" level=info msg="raft.node: 65af61b7b0ebc9f elected leader 65af61b7b0ebc9f at term 2"
Dec 14 14:57:49 ip-10-0-1-100 kernel: [  211.316041] aufs au_opts_verify:1597:dockerd[1293]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.060544330Z" level=info msg="Initializing Libnetwork Agent Listen-Addr=<IP_ADDRESS> Local-addr=<IP_ADDRESS> Adv-addr=<IP_ADDRESS> Remote-addr ="
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.061964479Z" level=info msg="Initializing Libnetwork Agent Listen-Addr=<IP_ADDRESS> Local-addr=<IP_ADDRESS> Adv-addr=<IP_ADDRESS> Remote-addr ="
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.062073063Z" level=info msg="Gossip cluster hostname ip-10-0-1-100-70450107a110"
Dec 14 14:57:50 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:50Z" level=info msg="Firewalld running: false"
Dec 14 14:57:50 ip-10-0-1-100 kernel: [  212.477736] IPv6: ADDRCONF(NETDEV_UP): docker_gwbridge: link is not ready
Dec 14 14:57:50 ip-10-0-1-100 kernel: [  212.485111] docker_gwbridge: port 1(vethe196635) entered forwarding state
Dec 14 14:57:50 ip-10-0-1-100 kernel: [  212.485118] docker_gwbridge: port 1(vethe196635) entered forwarding state
Dec 14 14:57:50 ip-10-0-1-100 kernel: [  212.485137] IPv6: ADDRCONF(NETDEV_CHANGE): docker_gwbridge: link becomes ready
Dec 14 14:57:50 ip-10-0-1-100 kernel: [  212.485196] docker_gwbridge: port 1(vethe196635) entered disabled state
Dec 14 14:57:50 ip-10-0-1-100 kernel: [  212.532425] docker_gwbridge: port 1(vethe196635) entered forwarding state
Dec 14 14:57:50 ip-10-0-1-100 kernel: [  212.532432] docker_gwbridge: port 1(vethe196635) entered forwarding state
Dec 14 14:58:05 ip-10-0-1-100 kernel: [  227.552079] docker_gwbridge: port 1(vethe196635) entered forwarding state
Dec 14 15:06:59 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T15:06:59.157414104Z" level=error msg="Error getting service nginx: service nginx not found"
Dec 14 15:06:59 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T15:06:59.157463780Z" level=error msg="Handler for GET /v1.24/services/nginx returned error: service nginx not found"
Dec 14 15:07:01 ip-10-0-1-100 kernel: [  764.201359] aufs au_opts_verify:1597:dockerd[1619]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 15:07:01 ip-10-0-1-100 kernel: [  764.228869] aufs au_opts_verify:1597:dockerd[1619]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 15:07:01 ip-10-0-1-100 kernel: [  764.255281] aufs au_opts_verify:1597:dockerd[1619]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 15:07:02 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T15:07:02Z" level=info msg="Firewalld running: false"
Dec 14 15:07:02 ip-10-0-1-100 kernel: [  764.398212] docker_gwbridge: port 2(vethba213ae) entered forwarding state
Dec 14 15:07:02 ip-10-0-1-100 kernel: [  764.398218] docker_gwbridge: port 2(vethba213ae) entered forwarding state
Dec 14 15:07:02 ip-10-0-1-100 kernel: [  765.260094] docker_gwbridge: port 2(vethba213ae) entered disabled state
Dec 14 15:07:05 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T15:07:05Z" level=info msg="Firewalld running: false"
Dec 14 15:07:05 ip-10-0-1-100 kernel: [  767.668418] docker_gwbridge: port 2(vethba213ae) entered forwarding state
Dec 14 15:07:05 ip-10-0-1-100 kernel: [  767.668425] docker_gwbridge: port 2(vethba213ae) entered forwarding state
Dec 14 15:07:20 ip-10-0-1-100 kernel: [  782.688069] docker_gwbridge: port 2(vethba213ae) entered forwarding state
Dec 14 15:07:05 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T15:07:05Z" level=info msg="Firewalld running: false"
Dec 14 17:15:35 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:15:35.482669623Z" level=error msg="container status unavailable" error="context canceled" module=taskmanager task.id=1wpy8fu182s1a4pbu3ua66abe
Dec 14 17:15:35 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:15:35.485228822Z" level=warning msg="cannot find target task in store" method="(*Dispatcher).UpdateTaskStatus" node.id=3qlnufc9dvk1rg6a45ri5i8zr node.session=1yvnmw79cvmxj4se58a5uok36 task.id=1wpy8fu182s1a4pbu3ua66abe
Dec 14 17:15:35 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:15:35.487646126Z" level=warning msg="cannot find target task in store" method="(*Dispatcher).UpdateTaskStatus" node.id=834zcbi5ks6qu5goxx4mtvt9m node.session=eu8bhel5u8t0yx68verm07zh4 task.id=7a467o2cmm1ej9pcp04ockw7a
Dec 14 17:15:35 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:15:35.497420289Z" level=error msg="task unavailable" method="(*Dispatcher).processTaskUpdates" module=dispatcher task.id=1wpy8fu182s1a4pbu3ua66abe
Dec 14 17:15:35 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:15:35.497452345Z" level=error msg="task unavailable" method="(*Dispatcher).processTaskUpdates" module=dispatcher task.id=7a467o2cmm1ej9pcp04ockw7a
Dec 14 17:15:35 ip-10-0-1-100 kernel: [ 8477.892273] docker_gwbridge: port 2(vethba213ae) entered disabled state
Dec 14 17:15:35 ip-10-0-1-100 kernel: [ 8477.919487] docker_gwbridge: port 2(vethba213ae) entered disabled state
Dec 14 17:15:35 ip-10-0-1-100 kernel: [ 8477.922597] docker_gwbridge: port 2(vethba213ae) entered disabled state
Dec 14 17:15:35 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:15:35Z" level=info msg="Firewalld running: false"
Dec 14 17:16:54 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:16:54.484773663Z" level=warning msg="cannot find target task in store" method="(*Dispatcher).UpdateTaskStatus" node.id=d5pdp8uv85lf55ta8tazerx30 node.session=exd6krsjvx9y8q6qposllxyyr task.id=cw93xplemo2kle6lbg3wmibko
Dec 14 17:16:54 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:16:54.544151098Z" level=error msg="task unavailable" method="(*Dispatcher).processTaskUpdates" module=dispatcher task.id=cw93xplemo2kle6lbg3wmibko
Dec 14 17:17:30 ip-10-0-1-100 kernel: [ 8592.872478] aufs au_opts_verify:1597:dockerd[1620]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 17:17:30 ip-10-0-1-100 kernel: [ 8592.899972] aufs au_opts_verify:1597:dockerd[1620]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 17:17:30 ip-10-0-1-100 kernel: [ 8592.933147] aufs au_opts_verify:1597:dockerd[1620]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 17:17:30 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:17:30Z" level=info msg="Firewalld running: false"
Dec 14 17:17:30 ip-10-0-1-100 kernel: [ 8593.051593] docker_gwbridge: port 2(veth774fe58) entered forwarding state
Dec 14 17:17:30 ip-10-0-1-100 kernel: [ 8593.051603] docker_gwbridge: port 2(veth774fe58) entered forwarding state
Dec 14 17:17:30 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T17:17:30Z" level=info msg="Firewalld running: false"
Dec 14 17:17:30 ip-10-0-1-100 kernel: [ 8593.196328] docker_gwbridge: port 2(veth774fe58) entered disabled state
Dec 14 17:17:30 ip-10-0-1-100 kernel: [ 8593.244307] docker_gwbridge: port 2(veth774fe58) entered forwarding state
Dec 14 17:17:30 ip-10-0-1-100 kernel: [ 8593.244313] docker_gwbridge: port 2(veth774fe58) entered forwarding state
Dec 14 17:17:45 ip-10-0-1-100 kernel: [ 8608.288062] docker_gwbridge: port 2(veth774fe58) entered forwarding state

#MANAGER2
Dec 14 14:55:30 ip-10-0-2-100 systemd[1]: Found device /dev/mapper/vg_docker-lv_docker.
Dec 14 14:55:30 ip-10-0-2-100 systemd[1]: Starting File System Check on /dev/mapper/vg_docker-lv_docker...
Dec 14 14:55:30 ip-10-0-2-100 systemd[1]: Started File System Check on /dev/mapper/vg_docker-lv_docker.
Dec 14 14:55:30 ip-10-0-2-100 systemd[1]: Mounting /var/lib/docker...
Dec 14 14:55:30 ip-10-0-2-100 systemd[1]: Mounted /var/lib/docker.
Dec 14 14:55:30 ip-10-0-2-100 kernel: [    5.722039] audit: type=1400 audit(1481727326.640:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=901 comm="apparmor_parser"
Dec 14 14:55:35 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:35.789670422Z" level=info msg="libcontainerd: new containerd process, pid: 1385"
Dec 14 14:55:38 ip-10-0-2-100 kernel: [   17.218931] audit: type=1400 audit(1481727338.136:16): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="docker-default" pid=1425 comm="apparmor_parser"
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.167575539Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.167909294Z" level=warning msg="Your kernel does not support swap memory limit."
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.168414527Z" level=info msg="Loading containers: start."
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.354960651Z" level=info msg="Firewalld running: false"
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.540260919Z" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
Dec 14 14:55:38 ip-10-0-2-100 kernel: [   17.663482] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.590628675Z" level=info msg="Loading containers: done."
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.590751507Z" level=info msg="Daemon has completed initialization"
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.590786016Z" level=info msg="Docker daemon" commit=6b644ec graphdriver=aufs version=1.12.3
Dec 14 14:55:38 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:55:38.606956918Z" level=info msg="API listen on /var/run/docker.sock"
Dec 14 14:57:20 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:57:20.904025291Z" level=error msg="Error getting nodes: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
Dec 14 14:57:20 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:57:20.904090624Z" level=error msg="Handler for GET /v1.24/nodes returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.366018682Z" level=info msg="Waiting for TLS certificate to be issued..."
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.370886546Z" level=info msg="Downloaded new TLS credentials with role: swarm-manager."
Dec 14 14:58:14 ip-10-0-2-100 kernel: [  173.456953] aufs au_opts_verify:1597:dockerd[1290]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.632692308Z" level=info msg="Listening for connections" addr="[::]:2377" proto=tcp
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.632852738Z" level=info msg="Listening for local connections" addr="/var/lib/docker/swarm/control.sock" proto=unix
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.634823371Z" level=info msg="Initializing Libnetwork Agent Listen-Addr=<IP_ADDRESS> Local-addr=<IP_ADDRESS> Adv-addr=<IP_ADDRESS> Remote-addr =<IP_ADDRESS>"
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.635137106Z" level=info msg="Initializing Libnetwork Agent Listen-Addr=<IP_ADDRESS> Local-addr=<IP_ADDRESS> Adv-addr=<IP_ADDRESS> Remote-addr =<IP_ADDRESS>"
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.635203435Z" level=info msg="Gossip cluster hostname ip-10-0-2-100-bd423bbc1bd6"
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.670820289Z" level=info msg="3c6b7e780574717 became follower at term 0"
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.670866886Z" level=info msg="newRaft 3c6b7e780574717 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]"
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.670902932Z" level=info msg="3c6b7e780574717 became follower at term 1"
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.905877021Z" level=info msg="3c6b7e780574717 [term: 1] received a MsgHeartbeat message with higher term from 65af61b7b0ebc9f [term: 2]"
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.905942565Z" level=info msg="3c6b7e780574717 became follower at term 2"
Dec 14 14:58:14 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:14.905965256Z" level=info msg="raft.node: 3c6b7e780574717 elected leader 65af61b7b0ebc9f at term 2"
Dec 14 14:58:15 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T14:58:15Z" level=info msg="Firewalld running: false"
Dec 14 14:58:15 ip-10-0-2-100 kernel: [  174.888432] IPv6: ADDRCONF(NETDEV_UP): docker_gwbridge: link is not ready
Dec 14 14:58:15 ip-10-0-2-100 kernel: [  174.897195] docker_gwbridge: port 1(veth240cea2) entered forwarding state
Dec 14 14:58:15 ip-10-0-2-100 kernel: [  174.897203] docker_gwbridge: port 1(veth240cea2) entered forwarding state
Dec 14 14:58:15 ip-10-0-2-100 kernel: [  174.897221] IPv6: ADDRCONF(NETDEV_CHANGE): docker_gwbridge: link becomes ready
Dec 14 14:58:15 ip-10-0-2-100 kernel: [  174.897294] docker_gwbridge: port 1(veth240cea2) entered disabled state
Dec 14 14:58:15 ip-10-0-2-100 kernel: [  174.960340] docker_gwbridge: port 1(veth240cea2) entered forwarding state
Dec 14 14:58:15 ip-10-0-2-100 kernel: [  174.960349] docker_gwbridge: port 1(veth240cea2) entered forwarding state
Dec 14 14:58:30 ip-10-0-2-100 kernel: [  189.980086] docker_gwbridge: port 1(veth240cea2) entered forwarding state
Dec 14 15:07:02 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T15:07:02Z" level=info msg="Firewalld running: false"
Dec 14 15:07:02 ip-10-0-2-100 kernel: [  701.463533] aufs au_opts_verify:1597:dockerd[1422]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 15:07:02 ip-10-0-2-100 kernel: [  701.484982] aufs au_opts_verify:1597:dockerd[1422]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 15:07:02 ip-10-0-2-100 kernel: [  701.511546] aufs au_opts_verify:1597:dockerd[1422]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 15:07:02 ip-10-0-2-100 kernel: [  701.554847] docker_gwbridge: port 2(vethbb59a19) entered forwarding state
Dec 14 15:07:02 ip-10-0-2-100 kernel: [  701.554855] docker_gwbridge: port 2(vethbb59a19) entered forwarding state
Dec 14 15:07:02 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T15:07:02Z" level=info msg="Firewalld running: false"
Dec 14 15:07:02 ip-10-0-2-100 kernel: [  701.812394] docker_gwbridge: port 2(vethbb59a19) entered disabled state
Dec 14 15:07:02 ip-10-0-2-100 kernel: [  701.876462] docker_gwbridge: port 2(vethbb59a19) entered forwarding state
Dec 14 15:07:02 ip-10-0-2-100 kernel: [  701.876470] docker_gwbridge: port 2(vethbb59a19) entered forwarding state
Dec 14 15:07:17 ip-10-0-2-100 kernel: [  716.892064] docker_gwbridge: port 2(vethbb59a19) entered forwarding state
Dec 14 15:07:02 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T15:07:02Z" level=info msg="Firewalld running: false"
Dec 14 17:15:35 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T17:15:35.483997351Z" level=error msg="container status unavailable" error="context canceled" module=taskmanager task.id=7a467o2cmm1ej9pcp04ockw7a
Dec 14 17:15:35 ip-10-0-2-100 kernel: [ 8414.650287] docker_gwbridge: port 2(vethbb59a19) entered disabled state
Dec 14 17:15:35 ip-10-0-2-100 kernel: [ 8414.684458] docker_gwbridge: port 2(vethbb59a19) entered disabled state
Dec 14 17:15:35 ip-10-0-2-100 kernel: [ 8414.687036] docker_gwbridge: port 2(vethbb59a19) entered disabled state
Dec 14 17:15:35 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T17:15:35Z" level=info msg="Firewalld running: false"
Dec 14 17:17:30 ip-10-0-2-100 dockerd[1191]: time="2016-12-14T17:17:30Z" level=info msg="Firewalld running: false"

#WORKER
Dec 14 14:54:47 ip-10-0-22-47 kernel: [   13.774206] audit: type=1400 audit(1481727274.664:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=692 comm="apparmor_parser"
Dec 14 14:54:52 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:52.831044611Z" level=info msg="libcontainerd: new containerd process, pid: 1361"
Dec 14 14:54:53 ip-10-0-22-47 kernel: [   32.976039] audit: type=1400 audit(1481727293.864:16): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="docker-default" pid=1379 comm="apparmor_parser"
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.052865507Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.053147096Z" level=warning msg="Your kernel does not support swap memory limit."
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.053613962Z" level=info msg="Loading containers: start."
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.234652055Z" level=info msg="Firewalld running: false"
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.312633640Z" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
Dec 14 14:54:54 ip-10-0-22-47 kernel: [   33.595379] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.496479455Z" level=info msg="Loading containers: done."
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.496696301Z" level=info msg="Daemon has completed initialization"
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.496723298Z" level=info msg="Docker daemon" commit=6b644ec graphdriver=aufs version=1.12.3
Dec 14 14:54:54 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:54:54.513821381Z" level=info msg="API listen on /var/run/docker.sock"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.372775402Z" level=error msg="Handler for POST /v1.24/swarm/join returned error: Timeout was reached before node was joined. The attempt to join the swarm will continue in the background. Use the \"docker info\" command to see the current swarm status of your node."
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.383116901Z" level=error msg="Handler for POST /v1.24/swarm/join returned error: This node is already part of a swarm. Use \"docker swarm leave\" to leave this swarm and join another one."
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.392826026Z" level=error msg="Handler for POST /v1.24/swarm/join returned error: This node is already part of a swarm. Use \"docker swarm leave\" to leave this swarm and join another one."
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396481655Z" level=info msg="Processing signal 'terminated'"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396630962Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396729050Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396778272Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396824550Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396895252Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.397000024Z" level=error msg="cluster exited with error: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.411200913Z" level=info msg="stopping containerd after receiving terminated"
Dec 14 14:55:19 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:19.443073202Z" level=info msg="libcontainerd: new containerd process, pid: 1755"
Dec 14 14:55:20 ip-10-0-22-47 kernel: [   58.805887] audit: type=1400 audit(1481727320.471:17): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="docker-default" pid=1767 comm="apparmor_parser"
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.479904671Z" level=info msg="[graphdriver] using prior storage driver \"aufs\""
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.482533935Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.482778312Z" level=warning msg="Your kernel does not support swap memory limit."
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.483230911Z" level=info msg="Loading containers: start."
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.487842733Z" level=info msg="Firewalld running: false"
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.564656560Z" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.594703726Z" level=info msg="Loading containers: done."
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.595006919Z" level=info msg="Daemon has completed initialization"
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.595034646Z" level=info msg="Docker daemon" commit=6b644ec graphdriver=aufs version=1.12.3
Dec 14 14:55:20 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:55:20.610116645Z" level=info msg="API listen on /var/run/docker.sock"
Dec 14 14:57:17 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:57:17.595117529Z" level=error msg="Error getting nodes: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
Dec 14 14:57:17 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:57:17.595154512Z" level=error msg="Handler for GET /v1.24/nodes returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
Dec 14 14:58:00 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:58:00.388177916Z" level=warning msg="Could not find ingress network while leaving: network ingress not found"
Dec 14 14:58:00 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:58:00.441616322Z" level=info msg="Waiting for TLS certificate to be issued..."
Dec 14 14:58:00 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:58:00.447945642Z" level=info msg="Downloaded new TLS credentials with role: swarm-worker."
Dec 14 14:58:00 ip-10-0-22-47 kernel: [  218.783844] aufs au_opts_verify:1597:dockerd[1754]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 14:58:00 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:58:00.484891877Z" level=error msg="Error getting node d5pdp8uv85lf55ta8tazerx30: This node is not a swarm manager. Worker nodes can't be used to view or modify cluster state. Please run this command on a manager node or promote the current node to a manager."
Dec 14 14:58:00 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:58:00.484938923Z" level=error msg="Handler for GET /v1.24/nodes/d5pdp8uv85lf55ta8tazerx30 returned error: This node is not a swarm manager. Worker nodes can't be used to view or modify cluster state. Please run this command on a manager node or promote the current node to a manager."
Dec 14 14:59:02 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:59:02.950022372Z" level=error msg="Error getting services: This node is not a swarm manager. Worker nodes can't be used to view or modify cluster state. Please run this command on a manager node or promote the current node to a manager."
Dec 14 14:59:02 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:59:02.950061365Z" level=error msg="Handler for GET /v1.24/services returned error: This node is not a swarm manager. Worker nodes can't be used to view or modify cluster state. Please run this command on a manager node or promote the current node to a manager."
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.601229] aufs au_opts_verify:1597:dockerd[1764]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.627507] aufs au_opts_verify:1597:dockerd[1764]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.657097] aufs au_opts_verify:1597:dockerd[1764]: dirperm1 breaks the protection by the permission bits on the lower branch
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.663716] docker0: port 1(vetha146b71) entered forwarding state
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.663723] docker0: port 1(vetha146b71) entered forwarding state
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.664190] docker0: port 1(vetha146b71) entered disabled state
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.900454] docker0: port 1(vetha146b71) entered forwarding state
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.900461] docker0: port 1(vetha146b71) entered forwarding state
Dec 14 17:16:23 ip-10-0-22-47 kernel: [ 8521.900478] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Dec 14 17:16:38 ip-10-0-22-47 kernel: [ 8536.924087] docker0: port 1(vetha146b71) entered forwarding state
Dec 14 17:16:54 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T17:16:54.476680537Z" level=error msg="container status unavailable" error="context canceled" module=taskmanager task.id=cw93xplemo2kle6lbg3wmibko
Dec 14 17:16:54 ip-10-0-22-47 kernel: [ 8552.874571] docker0: port 1(vetha146b71) entered disabled state
Dec 14 17:16:54 ip-10-0-22-47 kernel: [ 8552.896175] docker0: port 1(vetha146b71) entered disabled state
Dec 14 17:16:54 ip-10-0-22-47 kernel: [ 8552.898589] docker0: port 1(vetha146b71) entered disabled state

Describe the results you received:
Can't access published service from one of the nodes.
curl --connect-timeout 3 http://<IP_ADDRESS>:80

Welcome to nginx!

Welcome to nginx!
If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.
For online documentation and support please refer to
nginx.org.
Commercial support is available at
nginx.com.
Thank you for using nginx.

curl --connect-timeout 3 http://<IP_ADDRESS>:80

Welcome to nginx!

Welcome to nginx!
If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.
For online documentation and support please refer to
nginx.org.
Commercial support is available at
nginx.com.
Thank you for using nginx.

curl --connect-timeout 3 http://<IP_ADDRESS>:80
curl: (28) Connection timed out after 3001 milliseconds
Describe the results you expected:
I expect that the worker node routes the traffic to where the service tasks are running
Additional information you deem important (e.g. issue happens only occasionally):
I've noticed that this occurs with workers and with managers and with versions 1.12.3 and 1.12.4
Output of docker version:
# docker version
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64

Output of docker info:
manager-node1# docker info
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: xfs
 Dirs: 5
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge overlay
Swarm: active
 NodeID: 3qlnufc9dvk1rg6a45ri5i8zr
 Is Manager: true
 ClusterID: amf6avdqssky4w8wr1ineod69
 Managers: 2
 Nodes: 3
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-53-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.795 GiB
Name: ip-10-0-1-100
ID: PT4G:CMUG:DDRH:M45E:OTTE:ESJD:TGPA:SJHA:6GN4:TZ66:HSDM:LCCR
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

manager-node2#docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: xfs
 Dirs: 3
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge overlay
Swarm: active
 NodeID: 834zcbi5ks6qu5goxx4mtvt9m
 Is Manager: true
 ClusterID: amf6avdqssky4w8wr1ineod69
 Managers: 2
 Nodes: 3
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-53-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.303 GiB
Name: ip-10-0-2-100
ID: PT4G:CMUG:DDRH:M45E:OTTE:ESJD:TGPA:SJHA:6GN4:TZ66:HSDM:LCCR
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

worker-node1# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 3
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host null bridge overlay
Swarm: active
 NodeID: d5pdp8uv85lf55ta8tazerx30
 Is Manager: false
 Node Address: <IP_ADDRESS>
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-53-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.795 GiB
Name: ip-10-0-22-47
ID: PT4G:CMUG:DDRH:M45E:OTTE:ESJD:TGPA:SJHA:6GN4:TZ66:HSDM:LCCR
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Labels:
 services=true
 redis=true
 rabbitmq=true
 mongo=true
 es=true
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
I'm running it on AWS/EC2 with Ubuntu 16.04.1 LTS

@galindro Can you make sure the worker node is part of the cluster ?
Or something else must have happened. The fact that the ingress network is missing on your worker is the culprit: Routing mesh is not extended to that node.
I see these logs on the worker:
12-14T14:55:18.396630962Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396729050Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396778272Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396824550Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.396895252Z" level=warning msg="failed to retrieve remote root CA certificate: rpc error: code = 1 desc = context canceled"
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.397000024Z" level=error msg="cluster exited with error: rpc error: code = 1 desc = context canceled"

Also this log:
Dec 14 14:58:00 ip-10-0-22-47 dockerd[1747]: time="2016-12-14T14:58:00.388177916Z" level=warning msg="Could not find ingress network while leaving: network ingress not found"

tells us the swarm agent is down on this node

No @aboch . Swarm isn't down on that node. I've checked twice before open this thread.
All of those virtual instances was created inside a VPC that has this address range: <IP_ADDRESS>/16.
Each VM is located in a different subnet (<IP_ADDRESS>/24, <IP_ADDRESS>/24 and <IP_ADDRESS>/24). I'm sure that all instances have the same security group configured and it permits ALL TRAFFIC (tcp/udp/icmp/...) between each instance.

Unfortunately I've excluded all this test environment. Did you try to create the same scenario on AWS?

ping @aboch: Any other ideas about what could be happening here?

@galindro
I do not think this is a routing mesh issue, because the swarm network agent is not even running in your worker-node1. So it is expected the routing mesh is not extended to the node.
If you look at the worker-node1 daemon logs,
This is the error message in response to when you issued the join command:
Dec 14 14:55:18 ip-10-0-22-47 dockerd[1182]: time="2016-12-14T14:55:18.372775402Z" level=error msg="Handler for POST /v1.24/swarm/join returned error: Timeout was reached before node was joined. The attempt to join the swarm will continue in the background. Use the \"docker info\" command to see the current swarm status of your node."

Later the daemon was reloaded.  At next boot we do not see anywhere a message like:
Dec 14 14:57:49 ip-10-0-1-100 dockerd[1154]: time="2016-12-14T14:57:49.060544330Z" level=info msg="Initializing Libnetwork Agent Listen-Addr=<IP_ADDRESS> Local-addr=<IP_ADDRESS> Adv-addr=<IP_ADDRESS> Remote-addr ="

which would say that the counterpart network agent was initialized.
Which is why no ingress network is created on that node and the service published port is not open.
To avoid confusion, I am going ahead and will remove the networking label from this issue.
So my guess is that the node did not join the cluster. Or did not join it properly, because as you reported, docker node ls lists the node and docker info on the worker-node1 shows that the swarm is active.
@aaronlehmann Do you have an idea of what could be causing this ?

All of those virtual instances was created inside a VPC that has this address range: <IP_ADDRESS>/16.
Each VM is located in a different subnet (<IP_ADDRESS>/24, <IP_ADDRESS>/24 and <IP_ADDRESS>/24).
Did you try to create the same scenario on AWS?

What you are testing and the AWS deployment is very common. Yes I tested this before.

Do you have an idea of what could be causing this ?

Not sure. It does look like the node joined the cluster successfully. node ls shows a status of "Ready", which means that node is responding to heartbeats. Could there be some kind of firewall issue that's preventing the routing mesh from working even though the gRPC communication between nodes apparently works?

Could there be some kind of firewall issue that's preventing the routing mesh from working even though the gRPC communication between nodes apparently works?

No, this issue is not related to routing mesh working or not working: Routing mesh was not even extended to the worker-node1, in other words, the ingress network was never created on that node.
And this is consistent with the log messages stating the swarm join failed.
Only on successful join the ingress network is created, and the network control plane started (Note netstat output does not have the tcp/7946 port opened by dockerd).
One way to recreate a similar issue (worker failed the join but shows in docker node ls) is to have firewalld (default options) running on the manager, worker join will fail, but will show in docker node ls.
But with the difference that the worker node STATUS will show as Down.
So the fact the worker node shows as Active remains unexplained.
@galindro Regardless, I'd suggest to move to the latest 1.12.6 image.
Are you able to reproduce this ? Do you have any firewall (ufw, firewalld) running on the hosts ?

@aboc, After this issue, I've moved to Docker 1.13-rc. Now I'm using rc7. ASAP I'll test this scenario with 1.13 and, If this problem persists, I'll open a new ticket. So I think that we can close this ticket for now.
P.S.: I don't have any firewall running on hosts.

I've moved to Docker 1.13-rc

Actually you can now move away from rc. 1.13.0 was just released: https://github.com/docker/docker/releases/tag/v1.13.0


TMAX - logo cannot be seen clearly because it is white and the background is light

ENVIROMENT: production
URL: https://firme.peviitor.ro/
Browser: Chrome
Device: laptop
OS: Windows 10
STEPS TO REPRODUCE:
Open URL in browser
Type the name of the company in the search bar and click Enter
Verify  if the logo is displayed well.
EXPECTED RESULTS:
The logo should be displayed properly.
ACTUAL RESULTS:
The logo is difficult to see because it is white on a light background

@DeedeeDL please retest after update

@davidmondoc  still on the light background on firme.peviitor.to

retested.passs


Use view for finding players

Use views when finding players.
Update script to ensure views exist when running locally.
Signed-off-by: Erin Schnabel<EMAIL_ADDRESS>

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


added vantage.js

New entries should be added to the bottom of the section.

Thanks and tracking. Wasn't sure where to put it. All fixed now.

@sboudrias Fyi, this uses Inquirer ;)

Inquirer and Commander are the only reason this app qualifies as awesome :)

You might want to reconsider your use of colors though. See: https://github.com/chalk/chalk

Thanks for the advice. Was looking at that a few weeks ago - I wasn't sure if native string extensions was a big argument in the real world, or just theoretically. If it actually turns off people, I can totally change it.

It is. Especially in Node, since eg. a sub-sub-sub dependency extending a native prototype will affect all running dependencies.

Good point. I'll definitely be doing that then.
Anyway, thanks for accepting this PR! Hope you like it otherwise.
David

Yup, super cool idea :)

Thanks :)

@sindresorhus thought I'd let you know that I finished ditching colors and implemented chalk into Vantage.js. I also noticed I happened to use your strip-ansi module as well lol.  :)


react/function-component-definition: add possibility to use "const" instead of "var" for arrow function definition

This one is a feature request. The original implementation uses "var" for an arrow component definition. Thus, when you use this rule to fix existing code, this one will generate replacements with "var" definition https://github.com/yannickcr/eslint-plugin-react/blob/master/lib/rules/function-component-definition.js#L22-L23.
Partially it can be address by adding "no-var" and "prefer-const" rules. But when you apply the transformation manually (like with VSCode), you have to do it multiple times.
Would be nice to add a param to customise this behaviour.

It's not possible for this rule to know what folks have configured - whether they prefer var, const, let, etc - and it's both a best and a common practice to defer things to other rules, especially autofixable ones.
That editors like VSCode often require multiple passes (something the CLI does by default) to autofix everything is a flaw in their implementation, and not something that individual rules can or should address.

Disagree. This is a case of a rule being opinionated. And multiple passes don't fix it because of course the second pass tries to change it back to var. IMO almost all eslint rules have some configuration available, the ability to define what your preference is, etc. This is exactly such a case.

@ianpaschal any choice is the rule being opinionated. This rule will change it to var - the safest, most backwards compatible choice - and then prefer-const or no-var will tell you to change it again, and you’ll do so, and everything will be fine.


feat(html-to-slate-ast): add htmlToSlateASTSync function

It adds htmlToSlateASTSync, which doesn't depend on jsdom and will work exclusively on the browser environment.

How about adding a browser file that exports this instead – Like react-dom/server is only for server – to make it more explicit? cuz reading htmlToSlateASTSync doesn't convey that it's browser exclusive.

How about adding a browser file that exports this instead – like react-dom/server is only for server – to make it more explicit? cuz reading htmlToSlateASTSync doesn't convey that it's browser exclusive.

I tried to make it work like this, but no luck. When using exports it works, but then breaks TypeScript in the application unless I change the tsconfig moduleResolution to nodenext, which then breaks a bunch of other things 🫠

Sounds great. I'll document this internally and create a ticket so we can move away from tsdx completely. @anmolarora1


Godot navigation agent tanks FPS when using huge tile map (also velocity computed no longer works)

Godot version
v3.5.1.stable.official [6fed1ffa3]
System information
Windows 10, Nvidia GTX 750 TI, Nvidia GTX 1050 TI
Issue description
This originally meant to be about one issue but I think I ended up finding another issue as well, it just happens that both issues can be reproduced in this project.
It seems like with huge tile maps, the navigation agent will tank your FPS when your in an area where the agent can't reach you.
I don't think lag issues like this will happen when you are using 3D nodes instead. I expect the FPS to stay the same even when using large tile maps like this.
Second issue, velocity_computed used to work but when updating my Godot project, it has been broken as far as I know of and never sends any velocity_computed signals at all.
I should probably test when this was broken. I expect this to completely work and send a velocity through the velocity_computed signal.
Steps to reproduce
Download the minimal reproduction project below, extract the project, open up the project and press F5.
First issue, when you run the minimal reproduction project, the game will lag completely.
By moving with the arrow keys, from the small area, into the huge area, the game will stop lagging.
Second issue, I remember when updating my Godot project that velocity_computed used to work before with this code, but it no longer does now. I need to do some more testing to see when this was broken.
Minimal reproduction project
GodotNavigationAgentLagIssue.zip

For the second issue, avoidance_enabled on the NavigationAgent2D should be true in order to get the signal.

Please create separate issues. You can refer to an another issue if they are linked.

Second issue as others mentioned you need to enabled avoidance on the node, connect the signal and use set_velocity().
For the first performance issue that is not a NavigationAgent issue or bug but a project specific navigation layout issue that tanks your performance. When a path is possible AStar will do an early exit as soon as a path is found. Since your path is impossible while in the box AStar searches all available and connected navpolygons everytime which results in the noticeable lag difference between when a path is possible or impossible.
So why the lag inside the box? Each baked navigationpolygon has at least 3-4 polygon edges and creates a navigationregion on the navigationmap. Your TileMap has 15264 cells and 14264 of them use the baked navigationpolygon. The lag at the startup is because the NavigationServer needs to dig through all those regions to connect the edges. Also that is around 50000+ polygon edges that the navigation path query has to dig through everytime the navigationagent requests a path while inside that impossible box which is an unreasonable amount for navigation performance.
At that project scale with such small TileMap cell sizes you really should no longer use the tile baked navigationpolygons and work with a NavigationPolygonInstance. 3D will have the same performance issues with so many, small cells when every cells uses its own NavigationMeshInstance.

First yea avoidance was the reason why it wasn't sending safe_velocity.
Second, I was using a TileMap in my game as a way for players to use tiles to build obstacles against enemies. I didn't know that TileMaps didn't optimize the points at all, though I guess it makes more sense now why it would be lagging. Thanks for the confirmation that this wasn't a bug.

@smix8 Is there anywhere this could be documented (specifically in the class reference)?


new terms for pathogen sampling sites

We have a number of terms it seems AGRO is the best home for?!  For a number of entries that have basic definitions I marked myself as source, but I don't need to be mentioned unless you need that.
parent: ENVO_0010003	agricultural environmental material
term: crop
definition: A crop is any cultivated plant, fungus, or alga that is harvested for food, clothing, livestock, fodder, biofuel, medicine, or other uses.
source: https://en.wikipedia.org/wiki/Crop
parent: ENVO_0010003	agricultural environmental material
term: forage
definition: The vegetation of tended pasture, consists mainly of grasses, with an interspersion of legumes and other forbs (non-grass herbaceous plants)
source: https://en.wikipedia.org/wiki/Pasture
parent: ENVO_00000077	agricultural feature
term: pasture
definition: Pasture is land used for grazing.
source: https://en.wikipedia.org/wiki/Pasture
parent: ENVO_00000077	agricultural feature
term: feed storage
definition: Feed storage is any physical space or structure used to store agricultural animal feed
source: (Damion Dooley)
parent: ENVO_00000077	agricultural feature
term: manure storage
definition: Manure storage is any physical space or structure used to store manure
source: (Damion Dooley)
parent: ENVO_00003031	animal manure
term: bovine dairy liquid manure
definition: bovine (dairy liquid) manure is manure collected directly or indirectly from dairy cattle, as from flushing of manure from concrete feed lanes, free stalls, and milking facilities
source: http://manuremanagement.ucdavis.edu/files/134369.pdf
parent: ENVO_00003031	animal manure
term: poultry manure
definition: Poultry manure is manure originating from poultry
source: (Damion Dooley)
parent: ENVO_00003031	animal manure
term: heat treated animal manure
definition: Heat treated animal manure is animal manure subject to heat treatment for solidification or sterilization purposes.
source: (Damion Dooley)
parent: ENVO_00003031	animal manure
term: composted animal manure
definition: Composted animal manure is animal manure subjected to a composting process.
source: (Damion Dooley)
parent: ENVO_00003031	animal manure
term: animal manure product
definition: An animal manure product is heat treated animal manure processed into a product for commercial or consumer use.
source: (Damion Dooley)

Ah, @celineaubert I forgot "crop" has already been defined in AgrO as you mention in Envo #460. You can scratch that one.
But what about the animal feed items -
fish meal: http://purl.obolibrary.org/obo/AGRO_00000083
blood meal: http://purl.obolibrary.org/obo/AGRO_00000086

Should these be moved over to FoodOn?  Any other animal food categories like that too?

Compelled to be brief right now, but let's recall that we need a very
careful and principled approach to the ENVO-FOODON-AGRO balance. We arrived
at a general policy some time back, IIRC...
On 27 Jun 2017 06:08, "Damion Dooley"<EMAIL_ADDRESS>wrote:

Ah, @celineaubert https://github.com/celineaubert I forgot "crop" has
already been defined in AgrO as you mention in Envo #460. You can scratch
that one.
But what about the animal feed items -
fish meal: http://purl.obolibrary.org/obo/AGRO_00000083
blood meal: http://purl.obolibrary.org/obo/AGRO_00000086
Should these be moved over to FoodOn? Any other animal food categories
like that too?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AgriculturalSemantics/agro/issues/31#issuecomment-311247553,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACK7MqCsRrJElZXX5kCp3v4R8QWnzdznks5sIIAqgaJpZM4OEKvb
.

Ok, could the AgrO mission statement be restated again here, esp. in relation to ENVO?  I just have from ENVO #460 that "I'm placing all animal-related terms in ENVO to prevent mission creep for AgrO", and that FoodOn should take food related terms for both humans and animals.

@cmungall @marieALaporte please chime in if this is off:
From the README.Md AGRO concerns itself with the domain of "agronomic practices, agronomic techniques, and agronomic variables". For development convenience and due to pressing deployment schedules, AGRO also has classes for the equipment used in the techniques and practices, which may be moved at a later stage.
The practices and techniques will be under some  planned process and agronomic variables will be partly represented using qualities (e.g. "temperature of soil").  Most of the latter are of general interest and are ENVO classes. @marieALaporte is working to extend ENVO's patterns to produce these terms quickly https://github.com/EnvironmentOntology/envo/issues/492 . However, some of these qualities are so closely tied to the content of AGRO (i.e. they are defined by an AGRO-specific understanding of a technique), that they live therein (e.g. #14 #15).
A lot of the material entities relevant to AGRO are also of general interest outside agronomy (e.g. manure, vehicles, etc) and thus should either be minted in or eventually moved to ENVO (unless a more specific domain ontology emerges, like a manure or vehicle ontology) and be imported to AGRO. This is both a domain issue and also practical one as we can axiomatise more in ENVO for the moment. If there are derived terms that are strongly flavoured by AGRO semantics (e.g. are the output of a process that is the realisation of an AGRO technique), those can certainly live in AGRO itself.
This somewhat modifies the position in https://github.com/EnvironmentOntology/envo/issues/460 , in that classes like...

subclass of http://purl.obolibrary.org/obo/ENVO_00000042 #    agricultural - drainage canal
subclass of http://purl.obolibrary.org/obo/ENVO_00000140 #    agricultural - drainage ditch
# http://purl.obolibrary.org/obo/ # edit    agricultural - storage - feed
# http://purl.obolibrary.org/obo/ # edit    agricultural - storage - manure

...would be better hosted in ENVO as we can weave them in with our building and topology semantics; however, classes like...
# http://purl.obolibrary.org/obo/ #    agricultural - crop

...should go in AGRO as it's clearly contained in the agronomy domain and AGRO would likely have a technique/process like crop cultivation for axiomatisation. ENVO would then import it if needed.

Ok, I'm fine with closing the above item and moving most of the defn. requests over to ENVO.


ERROR: srt >= 1.3.0 not found using pkg-config

Hi,
I get the error written above while executing your install script with gpl and non free codecs bash <(curl -s "https://raw.githubusercontent.com/markus-perl/ffmpeg-build-script/master/web-install-gpl-and-non-free.sh?v1")
My OS is a clean installation of debian 11.
If I execute pkg-config --modversion srt im getting the output 1.4.2.
Am I missing something?
Full output:
ffmpeg-build-script-downloader v0.1
=========================================

First we create the ffmpeg build directory ffmpeg-build
Now we download and execute the build script

ffmpeg-build-script v1.33
=========================

Using 8 make jobs simultaneously.
With GPL and non-free codecs
cargo not installed. rav1e encoder will not be available.

building giflib - version 5.2.1
=======================
giflib version 5.2.1 already built. Remove /root/ffmpeg-build/packages/giflib.done lockfile to rebuild it.

building pkg-config - version 0.29.2
=======================
pkg-config version 0.29.2 already built. Remove /root/ffmpeg-build/packages/pkg-config.done lockfile to rebuild it.

building yasm - version 1.3.0
=======================
yasm version 1.3.0 already built. Remove /root/ffmpeg-build/packages/yasm.done lockfile to rebuild it.

building nasm - version 2.15.05
=======================
nasm version 2.15.05 already built. Remove /root/ffmpeg-build/packages/nasm.done lockfile to rebuild it.

building zlib - version 1.2.11
=======================
zlib version 1.2.11 already built. Remove /root/ffmpeg-build/packages/zlib.done lockfile to rebuild it.

building m4 - version 1.4.19
=======================
m4 version 1.4.19 already built. Remove /root/ffmpeg-build/packages/m4.done lockfile to rebuild it.

building autoconf - version 2.71
=======================
autoconf version 2.71 already built. Remove /root/ffmpeg-build/packages/autoconf.done lockfile to rebuild it.

building automake - version 1.16.4
=======================
automake version 1.16.4 already built. Remove /root/ffmpeg-build/packages/automake.done lockfile to rebuild it.

building libtool - version 2.4.6
=======================
libtool version 2.4.6 already built. Remove /root/ffmpeg-build/packages/libtool.done lockfile to rebuild it.

building openssl - version 1.1.1l
=======================
openssl version 1.1.1l already built. Remove /root/ffmpeg-build/packages/openssl.done lockfile to rebuild it.

building cmake - version 3.22.0
=======================
cmake version 3.22.0 already built. Remove /root/ffmpeg-build/packages/cmake.done lockfile to rebuild it.

building svtav1 - version 1a3e32b
=======================
svtav1 version 1a3e32b already built. Remove /root/ffmpeg-build/packages/svtav1.done lockfile to rebuild it.

building x264 - version 5db6aa6
=======================
x264 version 5db6aa6 already built. Remove /root/ffmpeg-build/packages/x264.done lockfile to rebuild it.

building x265 - version 3.5
=======================
x265 version 3.5 already built. Remove /root/ffmpeg-build/packages/x265.done lockfile to rebuild it.

building libvpx - version 1.10.0
=======================
libvpx version 1.10.0 already built. Remove /root/ffmpeg-build/packages/libvpx.done lockfile to rebuild it.

building xvidcore - version 1.3.7
=======================
xvidcore version 1.3.7 already built. Remove /root/ffmpeg-build/packages/xvidcore.done lockfile to rebuild it.

building vid_stab - version 1.1.0
=======================
vid_stab version 1.1.0 already built. Remove /root/ffmpeg-build/packages/vid_stab.done lockfile to rebuild it.

building av1 - version ae2be80
=======================
av1 version ae2be80 already built. Remove /root/ffmpeg-build/packages/av1.done lockfile to rebuild it.

building zimg - version 3.0.3
=======================
zimg version 3.0.3 already built. Remove /root/ffmpeg-build/packages/zimg.done lockfile to rebuild it.

building lv2 - version 1.18.2
=======================
lv2 version 1.18.2 already built. Remove /root/ffmpeg-build/packages/lv2.done lockfile to rebuild it.

building waflib - version b600c92
=======================
waflib version b600c92 already built. Remove /root/ffmpeg-build/packages/waflib.done lockfile to rebuild it.

building serd - version 0.30.10
=======================
serd version 0.30.10 already built. Remove /root/ffmpeg-build/packages/serd.done lockfile to rebuild it.

building pcre - version 8.45
=======================
pcre version 8.45 already built. Remove /root/ffmpeg-build/packages/pcre.done lockfile to rebuild it.

building sord - version 0.16.8
=======================
sord version 0.16.8 already built. Remove /root/ffmpeg-build/packages/sord.done lockfile to rebuild it.

building sratom - version 0.6.8
=======================
sratom version 0.6.8 already built. Remove /root/ffmpeg-build/packages/sratom.done lockfile to rebuild it.

building lilv - version 0.24.12
=======================
lilv version 0.24.12 already built. Remove /root/ffmpeg-build/packages/lilv.done lockfile to rebuild it.

building opencore - version 0.1.5
=======================
opencore version 0.1.5 already built. Remove /root/ffmpeg-build/packages/opencore.done lockfile to rebuild it.

building lame - version 3.100
=======================
lame version 3.100 already built. Remove /root/ffmpeg-build/packages/lame.done lockfile to rebuild it.

building opus - version 1.3.1
=======================
opus version 1.3.1 already built. Remove /root/ffmpeg-build/packages/opus.done lockfile to rebuild it.

building libogg - version 1.3.3
=======================
libogg version 1.3.3 already built. Remove /root/ffmpeg-build/packages/libogg.done lockfile to rebuild it.

building libvorbis - version 1.3.6
=======================
libvorbis version 1.3.6 already built. Remove /root/ffmpeg-build/packages/libvorbis.done lockfile to rebuild it.

building libtheora - version 1.1.1
=======================
libtheora version 1.1.1 already built. Remove /root/ffmpeg-build/packages/libtheora.done lockfile to rebuild it.

building fdk_aac - version 2.0.2
=======================
fdk_aac version 2.0.2 already built. Remove /root/ffmpeg-build/packages/fdk_aac.done lockfile to rebuild it.

building libtiff - version 4.2.0
=======================
libtiff version 4.2.0 already built. Remove /root/ffmpeg-build/packages/libtiff.done lockfile to rebuild it.

building libpng - version 1.6.37
=======================
libpng version 1.6.37 already built. Remove /root/ffmpeg-build/packages/libpng.done lockfile to rebuild it.

building libwebp - version 1.2.1
=======================
libwebp version 1.2.1 already built. Remove /root/ffmpeg-build/packages/libwebp.done lockfile to rebuild it.

building libsdl - version 2.0.14
=======================
libsdl version 2.0.14 already built. Remove /root/ffmpeg-build/packages/libsdl.done lockfile to rebuild it.

building srt - version 1.4.3
=======================
srt version 1.4.3 already built. Remove /root/ffmpeg-build/packages/srt.done lockfile to rebuild it.

building amf - version <IP_ADDRESS>
=======================
amf version <IP_ADDRESS> already built. Remove /root/ffmpeg-build/packages/amf.done lockfile to rebuild it.

building ffmpeg - version 4.4
=======================
FFmpeg-release-4.4.tar.gz has already downloaded.
Extracted FFmpeg-release-4.4.tar.gz
ERROR: srt >= 1.3.0 not found using pkg-config

If you think configure made a mistake, make sure you are using the latest
version from Git.  If the latest version fails, report the problem to the
<EMAIL_ADDRESS>mailing list or IRC #ffmpeg on irc.libera.chat.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.
$ make -j 8
Makefile:177: /tests/Makefile: Datei oder Verzeichnis nicht gefunden
make: *** Keine Regel, um „/tests/Makefile“ zu erstellen.  Schluss.

Failed to Execute make -j 8

Same for me. Ubuntu 18.04.6 LTS. Three days ago, the build was fine.
Now
ERROR: srt >= 1.3.0 not found using pkg-config
pkg-config --modversion srt
1.4.4

Also with the same issue on Ubuntu 18.04.2 LTS.
pkg-config --modversion srt
1.4.3
srt is compiled without errors and pkg-config exists in  workspace/lib/pkgconfig/srt.pc and its ok.

I just copy libsrt.a , srt.h and src.pc to /usr/local/lib , /usr/local/inculde and /usr/local/lib/pkgconfig/ can compiler sucess, it's not this repo isuuse , i think most like ubuntu version and ffmppeg 4.4 not match well

Ubuntu 18.04.2 LTS 上也存在同样的问题。
pkg-config --modversion srt 1.4.3
srt 编译没有错误，pkg-config 存在于workspace/lib/pkgconfig/srt.pc 中并且没问题。

我的也是，你最后是怎么解决的？


User names might be longer than 8 chars + non alpha chars

And it breaks both syntax hl and a view

Fixed highlighting, length adjustments should be covered by #14


Timeless data logged through archetype interfaces shows up only on default timelines

timeless data is supposed to be independent of active timelines

That's just the Rust objectron example not logging the data as timeless.


Production deploy of app

Deploy the app on the new server rajdhani.pipal.in and document the deployment process.

I guess this issue should ideally belong to boring-serverless.

I guess this issue should ideally belong to boring-serverless.

Well, not really. We are deploying rajdhani app using boring-serverless. It is fine to be in this repo.

done!
These were the deployment steps i had to follow for this.
Most of it is documented already in boring-serverless README.
Few steps I did extra were disabling nginx.service, installing dependencies of the app to be deployed manually (we may be able to improve this flow), and editing the github workflow for server_url
   git clone https://github.com/pipalacademy/boring-serverless
   cd boring-serverless

   sudo apt-get install python3.10-venv # python3.10 was installed on the system
   python3.10 -m venv venv
   venv/bin/python -m pip install -r requirements.txt

   cp config.yml.sample config.yml

   sudo apt-get install apache2
   vim deployment/etc/sites-available/apache2/boring.conf:
     - change <Directory >
     - change domain name in ServerName
     - change installation directory in RewriteRule
   sudo systemctl disable nginx.service # clear up port 80/443
   sudo a2enmod cgid rewrite
   sudo a2ensite boring
   sudo systemctl restart apache2.service

   sudo chmod +x /home/pipal # enable access to user home directory

   # install dependencies of rajdhani
   mkdir apps
   git clone https://github.com/pipalacademy/train-ride apps/pipalacademy
   venv/bin/python -m pip install -r apps/pipalacademy/requirements.txt
   rm -rf apps/pipalacademy

   # now edit the workflow in train-ride repo to point to the new server_url for boring:
   # boring.rajdhani.pipal.in

Added SSL.
https://boring.rajdhani.pipal.in

This is done

Can you make the deploy work at https://rajdhani.pipal.in/deploy ?
Also, we need to set up wildcard DNS for rajdhani.pipal.in. That required
using digitalocean DNS token.
On Sat, Sep 10, 2022 at 11:00 AM Kaustubh Maske Patil <
@.***> wrote:

Added SSL.
https://boring.rajdhani.pipal.in
—
Reply to this email directly, view it on GitHub
https://github.com/pipalacademy/train-ride/issues/9#issuecomment-1242636359,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAB3EJAF5L5535YQMWZQPTV5QMGRANCNFSM6AAAAAAQJEXYQA
.
You are receiving this because you authored the thread.Message ID:
@.***>

These steps are outdated now and the up-to-date deployment docs are in Hamr's README.

Can you make the deploy work at https://rajdhani.pipal.in/deploy ?

Deploy URL is https://rajdhani.pipal.in/<app_name>/deploy, for an existing app.

Also, we need to set up wildcard DNS for rajdhani.pipal.in. That required
using digitalocean DNS token.

That step is documented in Hamr: https://github.com/pipalacademy/hamr#recommended


Change .github  to .github

Motivation

Solution

Tickets

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


NullReferenceException int the 3.3.1 and 3.3.2

Hi,
Since I updated to the 3.3.1 and 3.3.2 of the Nuget package, there is a Null Reference Exception.
Here is the stack trace :
   at Gremlin.Net.Driver.Connection.<ReceiveAsync>d__14`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Gremlin.Net.Driver.Connection.<SubmitAsync>d__8`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Gremlin.Net.Driver.ProxyConnection.<SubmitAsync>d__3`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Gremlin.Net.Driver.GremlinClient.<SubmitAsync>d__6`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Gremlin.Net.Driver.GremlinClientExtensions.<SubmitAsync>d__4`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at PartitionedGraph.Program.<ExecuteGremlinServerQueryAsync>d__3.MoveNext()

And the code sample:
string query = "g.V().drop()";

GremlinServer server = new GremlinServer(gremlinServerEndPoint, serverPort, true, $"/dbs/{databaseId}/colls/{collectionId}", primaryKey);

using (GremlinClient client = new GremlinClient(server))
{
    IEnumerable<dynamic> results = await GremlinClientExtensions.SubmitAsync<dynamic>(client, requestScript: query);

    foreach (dynamic result in results)
    {
        Console.WriteLine(result.ToString());
    }
}

I know this is not the right version project, but I can not find the original repository for the Nuget package.
This is not blocking, since I can use the 3.2.8 version of the NuGet pacakge.
Thanks in advance.

Hi @EhRom, the right repo is the one from Apache TinkerPop: https://github.com/apache/tinkerpop. It contains the source code for Gremlin.Net in the directory gremlin-dotnet.
The issue tracker for TinkerPop is here: https://issues.apache.org/jira/projects/TINKERPOP/issues
It looks like you're using Cosmos DB which doesn't support GraphSON 3 yet as far as I know. That's probably the reason why it works with version 3.2.8, but now with 3.3.2 as GraphSON 3 is used by default in TinkerPop 3.3.z, whereas GraphSON 2 was used in versions 3.2.z.
You can check if that's actually the case by creating the GremlinClient with Gremlin.Net 3.3.2 like this:
var client = new GremlinClient(server, new GraphSON2Reader(),
        new GraphSON2Writer(), GremlinClient.GraphSON2MimeType));

@FlorianHockmann, I have the same problem. I'm already using GraphSON 2
using (var gremlinClient = new GremlinClient(gremlinServer, new GraphSON2Reader(), new GraphSON2Writer(), GremlinClient.GraphSON2MimeType))

Hi Florian,
Very clear answer. Thank you very much. Specifying the reader and writer works fine.


Update Db2LinkedServiceTypeProperties

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@anthony-c-martin
Hello, if you are OK with Jianshu's explanation would you change the reivew status to approve, so I could merge the PR? Thanks.


Use es6+ syntax

Use es6+ syntax
So that new devs can tweek into the development with newer syntax and get used to it

Issues solved :D


Add post descriptions

There is too much text on the homepage IMO.
I had a go at adding a description field to the Frontmatter.
I actually have no idea what I am doing so this is new and fun (what do you call this type of website?), not confident I have added this field correctly.
I also shortened the default excerpt length to 150 chars.

Nice one.


ps output is not trimmed before checking for running process

Describe the bug
Goss doesn't trim the output of ps command which can cause false alarm.
How To Reproduce
root@sp1:~# ps auxww | grep ngcp-fax
faxserv+ 1539901  0.1  2.9<PHONE_NUMBER>8 ?        Ss   09:54   0:02 ngcp-faxserver --cfg-file /etc/ngcp-faxserver/faxserver.conf
faxserv+ 1539959  0.0  2.2  82880 69800 ?        S    09:54   0:00 ngcp-faxserver --cfg-file /etc/ngcp-faxserver/faxserver.conf
root@sp1:~#

root@sp1:~# ps -p 1539901 -o comm
COMMAND
ngcp-faxserver
root@sp1:~#

root@sp1:~# ps -p 1539901 -o comm | tail -1| hexdump -C
00000000  6e 67 63 70 2d 66 61 78  73 65 72 76 65 72 20 0a  |ngcp-faxserver .|
00000010
root@sp1:~#

#### Steps to reproduce:

root@sp1:~# cat /tmp/failure.yaml

process:
  ngcp-faxserver:
    running: true

root@sp1:~# goss -g /tmp/failure.yaml validate
F

Failures/Skipped:

Process: ngcp-faxserver: running:
Expected
    <bool>: false
to equal
    <bool>: true

Total Duration: 0.004s
Count: 1, Failed: 1, Skipped: 0
root@sp1:~#

root@sp1:~# cat /tmp/workaround.yaml

process:
  "ngcp-faxserver ":
    running: true

root@sp1:~# goss -g /tmp/workaround.yaml validate
.

Total Duration: 0.004s
Count: 1, Failed: 0, Skipped: 0
root@sp1:~#

Expected Behavior
Goss should trim ps output befome matching it to the value from YAML file.
Actual Behavior
Goss is not removing trailing space from ps output:

00000000  6e 67 63 70 2d 66 61 78  73 65 72 76 65 72 20 0a  |ngcp-faxserver .|
........................................................................................................................ ^

Environment:

Version of goss: v0.3.14
OS/Distribution version (if applicable): Debian 11 (bullseye)

This specific daemon sets the process-name via perl's $0 assignment, which includes arguments in there. As on Linux the comm limit is 15 characters, the space is shown but not the subsequent arguments.
I'm not convinced this is a problem in goss, as trimming on space could make it stop matching on other things, which looks like a breaking change.

Updated doc to avoid this issue in the future cat -E /proc/<PID>/comm will show whitespace.


Update Jest

UI Version: 0.9.3
Description:

Updated my dependencies on package.json and by upgrading jest from 21.2.1 to 23.4.2 all my test broke and threw the same error:
  ● Test suite failed to run

    TypeError: jest.genMockFunction is not a function

       7 | global._Date = Date
       8 | global.Date = jest.fn(() => new global._Date(DATE_TO_USE.toISOString()))
    >  9 | Date.now = jest.genMockFunction().mockReturnValue(DATE_TO_USE.getTime())

Had to downgrade to de prev version to solve the issue, but in the long run we might have to change how we mock dates using jest.
See the following issue:

https://github.com/facebook/jest/pull/6173

A better choice is to stop using mocks in accordance with my talk.

Spiked this:

not straight forward
will need some investigation to solve strange bugs

Don't underestimate this.


hasPlayerOwner not set correctly on items

I noticed this in the expansion of an item I'd previously created using the system normal Create Item interface. This looks like it might be indicating a bug or possibly a missing bit of something. The hasPlayerOwner field for the item I was inspecting reads "Exception: TypeError: Cannot read property 'default' of undefined at ageSystemItem.get hasPlayerOwner [as hasPlayerOwner] (https://localhost/scripts/foundry.js:29367:30) at ageSystemItem.invokeGetter (:1:142)]". Granted this example is on an NPC sheet, but I get the same thing on items that are on a sheet for an actor owned by a player.
Also, I've noticed that the actor structure is populating the isPC attribute which is triggering a warning in the console stating that "The Actor#isPC attribute has been deprecated in favor of the more general Entity#hasPlayerOwner attribute". perhaps this is related?

#hasPlayerOwner is the the method in use, as #isPC will be discontinued in future FoundryVTT releases. This method is expected to be used with Actors only. Looking at Item class documentation, #hasPlayerOwner is not even listed. I believe it could be a bug on FoundryVTT version 0.7.9.


Suggestion: Rename tokens feature or edit Gollum's name

This is INCREDIBLY minor, but I've been getting bothered by how Gollum's name on his tag goes past the boundaries of the tag. I'm suggesting either a feature to let you rename tags how you please, or changing his name so that it's on two layers rather than one, or just call him Gollum since that's what the game refers to him as. If this isn't a big enough issue to mess with, don't worry. I just wanted to post it and see what happens

I have already fixed this in my commit from April 22: https://github.com/Berny23/LD-ToyPad-Emulator/commit/1cd636ab4b498a4a5a5ff679d5a79d17b77dd57d
Please try to update to the latest version, then delete the Gollum tag from your toy box completely and add it again via the character selection.

I have already fixed this in my commit from April 22: 1cd636a
Please try to update to the latest version, then delete the Gollum tag from your toy box completely and add it again via the character selection.

My bad, I didn't notice this in a commit and I haven't deleted anyone from my toybox in a while! Thanks for letting me know!


Android support

Anybody working for android support?

+1

Not yet... I have been focusing on react-native-firestack for the time being. If you want to contribute, I'd be glad to accept PRs.
It's on the TODO list, but not the most immediate focus :/.

Will do soon.

@auser are you currently working on Android support? If not, I may take a stab at it, since I'm in need of a good outh library for RN Android.

That would be awesome. If you can match the JS API, that would be the best. I had started it, but between traveling and the flu, I haven't been back at it.
Important needs to match the iOS side:
Oauth v1/2 support, with the key being the provider. Check out how the iOS side is implemented for more details on what I mean.
I can also hop in the gitter room a bit later if you'd like to discuss in realtime.

Cool, I'll hop in the gitter room.

I actually don't see a gitter room for react-native-oauth -- were you going to make one?

Oh join the firestack one. I'll update the readme with a link

So I started a bit of preliminary work on implementing a bridge to an existing Android OAuth library (https://github.com/wuman/android-oauth-client) but ran into some issues. I ended up going with an ad-hoc approach of sorts for my app instead, as I didn't really need a full OAuth solution yet (just an Oauth 2 authorization flow for one of my own applications).
Because of that I'm not sure when I'll be able to get back to helping out with Android support in this library. If someone else wants to pick up on it instead, that would be cool. If not, I may return to it later on.

gday Ari - first a HUGE thanks for all your work with Firestack, and now this OAuth lib. We're implementing an Aust. govt funded app right now and using both. Your a genuine legend.
Do you think Android support is something that could be done in say next few weeks ? I know I'm 'asking' and not 'giving back' which i want to do one day for you (Android isn't my forte). Appreciate if u can let me know ? cheers.

@ajonno I've started the Android implementation today and I've only started working on it for twitter. I'll push this work up to the feature/android branch, if you want to continue the implementation.

configureProvider is implemented
authorize is implemented
savedAccount/savedAccounts method implemented
deauthorize is implemented
makeRequest is not implemented

The rest of the work is really just getting the makeRequest and 2.0 providers working.

Alright, I simplified a LOT of the code and am using a different backing library with a more permissible license (and it's way nicer). In any case, I have pretty much everything implemented for Android (except not Google auth yet). Other than google Auth (which shouldn't be too hard), feel free to test it from the feature/android branch.

thats great thanks Ari. ill definitely look at testing and if i can get time help with adding Google for android. i'm still struggling to get Google iOS auth working with Firebase (Firestack signInWithProvider() call fails when I use the access_token) so that has to be my current priority.

@ajonno Added Google auth support to the branch.

cool ill take a look

Alright, both Android and iOS are supported. My task list before I can close this issue:
[x] Google auth
[x] Github
[x] Facebook
[x] Twitter
[ ] Documentation


program got stuck in the hipMemcpy() function

hello,
I installed ROCm-4.5 on my machine following this guide,
my GPU is  gfx906 and my system is ubuntu20.04, but things do not go well
when I use hipcc compiled this code(which I got in the rocblas's doc), but when I run this program, it got stuck in the first hipMemcpy() function, and with no response feedback, no error and no warning, I think I may have missed something during the installation of rocm. but I have no idea how to find out where it goes wrong.
please help me.
this is the test code:
#include <iostream>
#include <vector>
#include "hip/hip_runtime_api.h"
#include "rocblas.h"
using namespace std;

int main()
{
    rocblas_int n = 10240;
    float alpha = 10.0;
    vector<float> hx(n);
    vector<float> hz(n);
    float* dx;
    rocblas_handle handle;
    rocblas_create_handle(&handle);

    hipMalloc(&dx, n * sizeof(float));

    srand(1);
    for( int i = 0; i < n; ++i )
    {
        hx[i] = rand() % 10 + 1;
    }

    cout << "hello?" << endl;
    hipMemcpy(dx, hx.data(), sizeof(float) * n, hipMemcpyHostToDevice);
    cout << "hello? again" << endl;

    rocblas_status status = rocblas_sscal(handle, n, &alpha, dx, 1);
    if(status == rocblas_status_success)
    {
        cout << "status == rocblas_status_success" << endl;
    }
    else
    {
        cout << "rocblas failure: status = " << status << endl;
    }
    hipMemcpy(hx.data(), dx, sizeof(float) * n, hipMemcpyDeviceToHost);

    hipFree(dx);
    rocblas_destroy_handle(handle);
    return 0;
}
// the compile command
// hipcc test03.cpp -o t3 -lrocblas -lamdhip64 -I/opt/rocm/include -L/opt/rocm/lib

Hi @MOLOjl, Thanks for reaching out.
As you informed, installation might not go well. Can you please help us with below information.
/opt/rocm/bin/rocminfo
/opt/rocm/opencl/bin/clinfo
dmesg

thanks anyway @ROCmSupport,
I figured out this error today. it is because I missed some system rebooting during the installation of ROCm, I don't know which one's missing caused it since there are three (or four?) of them.
I think some indexes need to be updated by system rebooting, if not, some old version dependencies' will be mixed into the new version of ROCm and cause unexpected errors. Of course, I'm just a beginner at this, so it's only a hypothesis.
I followed this guide, and finally got ROCm installed correctly.

Thanks @MOLOjl for the update.
Feel free to file, new issues, if any, for quick resolutions. Thank you.


Update build root image for OpenShift ci-operator

These changes aim to address the Cypress dependency issues as well as improving the build root Dockerfile.

/retest

/lgtm


[tests] added PCL project

Added a general test project for testing PCLs
Only had to create a couple #if to support PCL
Made pcl-compile and pcl-run make targets

This doesn't fix anything, but adds a test project for #407
I investigated if #407 could be fixed without Xamarin.Android, but facade assemblies would need to be extracted along with mscorlib.dll. I will continue work on Xamarin.Android integration to fix this issue.

Build failed


A problem with floating labels

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
When filling in the field for several lines, there is an overlap of the label
https://getbootstrap.com/docs/5.2/forms/floating-labels/#textareas

Reduced test cases
https://getbootstrap.com/docs/5.2/forms/floating-labels/#textareas
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Firefox
What version of Bootstrap are you using?
v5.2

Duplicate of #32800.

Indeed this is a duplicate. Thanks @alecpl. @ale-lit, thanks for reporting this issue, you can subscribe to #32800 to follow the topic. I'm closing this one.