Fatal errors on Rancher and now no way to connect the host using SSH

Rancher Version:
v1.2.2
Docker Version:
1.12
OS and where are the hosts located? (cloud, bare metal, etc):
AWS - ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20161214 (ami-6f587e1c)
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node (AWS EC2), External DB (postgres AWS RDS)
Single host (same ubuntu-image). This host has one service running five containers.
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Not sure if this is reproducible but here's what I did

Created EC2 instance
Installed Rancher
Changed Rancher to use external database (postgres)

I know that PostgreSQL is not officially supported but I was testing how it currently works with Rancher

Added one host
Added service with five containers
Started services and let them run over the weekend

Results:
On Monday after coming back to work I noticed Rancher had logged few fatal errors and SSH connection was down. After trying everything else I finally resorted to stopping and starting the instance where Rancher is. Still cannot connect to the instance using SSH.
Expected:
Rancher to either stay operational or cleanly die without making the host unresponsive to SSH.
I had docker logs -f rancher-server running on the host before connection went down. Here is the output:
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.activate(DeploymentManagerImpl.java:117) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.activate(DeploymentManagerImpl.java:103) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl$5$1.run(DeploymentManagerImpl.java:445) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.activity.ActivityService.run(ActivityService.java:43) ~[cattle-activity-log-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl$5.run(DeploymentManagerImpl.java:442) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.configitem.version.impl.ConfigItemStatusManagerImpl$1.doWithLock(ConfigItemStatusManagerImpl.java:92) ~[cattle-config-item-common-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl$4.doWithLock(AbstractLockManagerImpl.java:50) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.tryLock(AbstractLockManagerImpl.java:25) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.tryLock(AbstractLockManagerImpl.java:47) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.configitem.version.impl.ConfigItemStatusManagerImpl.runUpdateForEvent(ConfigItemStatusManagerImpl.java:85) ~[cattle-config-item-common-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.servicediscovery.deployment.impl.DeploymentManagerImpl.serviceUpdate(DeploymentManagerImpl.java:435) ~[cattle-iaas-service-discovery-server-0.5.0-SNAPSHOT.jar:na]
	at sun.reflect.GeneratedMethodAccessor1496.invoke(Unknown Source) ~[na:na]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_72]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_72]
time="2017-01-01T02:39:35Z" level=info msg="Setting log level" logLevel=info
	at io.cattle.platform.eventing.annotation.MethodInvokingListener$1.doWithLockNoResult(MethodInvokingListener.java:76) ~[cattle-framework-eventing-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:7) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
time="2017-01-01T02:39:37Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
	at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:3) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
time="2017-01-01T02:39:40Z" level=info msg="Waiting for handler registration (1/2)"
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.eventing.annotation.MethodInvokingListener.onEvent(MethodInvokingListener.java:72) ~[cattle-framework-eventing-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.eventing.impl.AbstractThreadPoolingEventService$2.doRun(AbstractThreadPoolingEventService.java:140) ~[cattle-framework-eventing-0.5.0-SNAPSHOT.jar:na]
time="2017-01-01T02:40:00Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: EOF"
	at org.apache.cloudstack.managed.context.NoExceptionRunnable.runInContext(NoExceptionRunnable.java:15) ~[cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
	at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:108) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
	at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) [cattle-framework-managed-context-0.5.0-SNAPSHOT.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_72]
2017/01/01 02:40:10 http: proxy error: net/http: request canceled
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_72]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_72]

time="2017-01-01T02:38:12Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
2017-01-01 02:38:24,601 ERROR [244c2802-a118-4ea8-a054-bfa390c4bd16:252117] [instance:12515] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12515]
time="2017-01-01T02:38:35Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:45974->[::1]:8080: read: connection reset by peer"
2017-01-01 02:38:49,796 ERROR [cae18c21-b042-47ce-9475-5645771cbf5b:252150] [instance:12516] [instance.start->(InstanceStart)] [] [ecutorService-2] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12516]
2017-01-01 02:39:19,794 ERROR [c67d6c97-d823-429a-ba62-336a9d20823a:252161] [instance:12517] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12517]
time="2017-01-01T02:39:27Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:39:47Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: EOF"
2017-01-01 02:39:50,677 ERROR [92740279-4572-471d-ab5c-56ecc224a063:252194] [instance:12518] [instance.start->(InstanceStart)] [] [ecutorService-1] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12518]
2017-01-01 02:40:07,898 ERROR [d262f1cd-2e28-4e09-b145-2fd4fa19f55a:252205] [instance:12519] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12519]
time="2017-01-01T02:40:33Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:40:46Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:40:47Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:40:50Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 02:40:51,162 ERROR [0121cf93-d3a7-4796-87dc-cc4d80e44f8b:252216] [instance:12520] [instance.start->(InstanceStart)] [] [ecutorService-1] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12520]
time="2017-01-01T02:40:53Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: EOF"
time="2017-01-01T02:41:06Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:45990->[::1]:8080: read: connection reset by peer"
2017-01-01 02:41:09,721 ERROR [90d94d5f-f7a6-4404-b610-7dfe6473b937:252250] [instance:12521] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12521]
2017/01/01 02:41:16 http: proxy error: net/http: request canceled
time="2017-01-01T02:41:38Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
2017-01-01 02:41:40,213 ERROR [777d269e-2784-49d9-b3a1-10275cc92773:252259] [instance:12522] [instance.start->(InstanceStart)] [] [ecutorService-5] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12522]
time="2017-01-01T02:41:56Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:45996->[::1]:8080: read: connection reset by peer"
time="2017-01-01T02:41:56Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:41:57Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:41:58Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 02:42:03,923 ERROR [3814304b-f2cb-4c2a-9e47-ab4bb05b79e5:252284] [instance:12523] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12523]
time="2017-01-01T02:42:13Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:45998->[::1]:8080: read: connection reset by peer"
2017/01/01 02:42:23 http: proxy error: net/http: request canceled
2017-01-01 02:42:26,219 ERROR [3a28e637-3974-46d6-b95d-76fd9b5880ed:252298] [instance:12524] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12524]
time="2017-01-01T02:42:50Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
2017-01-01 02:42:59,154 ERROR [cbeb519e-bc93-4c03-b6aa-159f06c82a7f:252325] [instance:12525] [instance.start->(InstanceStart)] [] [cutorService-10] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12525]
time="2017-01-01T02:43:07Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46004->[::1]:8080: read: connection reset by peer"
time="2017-01-01T02:43:02Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:43:04Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:43:06Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:43:17Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: EOF"
2017-01-01 02:43:23,496 ERROR [f9be87ba-9dc8-4c29-b7ab-e38013aee5a3:252336] [instance:12526] [instance.start->(InstanceStart)] [] [ecutorService-1] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12526]
2017/01/01 02:43:29 http: proxy error: net/http: request canceled
time="2017-01-01T02:43:46Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:43:47Z" level=info msg="Setting log level" logLevel=info
2017-01-01 02:43:48,469 ERROR [f92f3cc4-6b1b-4405-8ca1-1703d218edf4:252363] [instance:12527] [instance.start->(InstanceStart)] [] [ecutorService-5] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12527]
time="2017-01-01T02:43:48Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:43:49Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:43:58Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: EOF"
time="2017-01-01T02:44:10Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta/schemas: read tcp [::1]:46022->[::1]:8080: read: connection reset by peer"
2017-01-01 02:44:11,447 ERROR [adff42e6-c6a8-4707-87d2-59e8f9e866bc:252376] [instance:12528] [instance.start->(InstanceStart)] [] [ecutorService-7] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12528]
2017/01/01 02:44:13 http: proxy error: net/http: request canceled
time="2017-01-01T02:44:17Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:44:26Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46026->[::1]:8080: read: connection reset by peer"
2017-01-01 02:44:28,843 ERROR [7b408842-4da4-4e92-8f11-04db54bf03b7:252387] [instance:12529] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12529]
time="2017-01-01T02:44:29Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:44:30Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:44:32Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:44:40Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46028->[::1]:8080: read: connection reset by peer"
2017/01/01 02:44:46 http: proxy error: net/http: request canceled
time="2017-01-01T02:44:53Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:45:04Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46034->[::1]:8080: read: connection reset by peer"
2017-01-01 02:45:06,054 ERROR [09c2ed58-9c10-4873-8779-c37292cefdcc:252417] [instance:12530] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12530]
time="2017-01-01T02:45:05Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:45:06Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:45:06Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:45:29Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta/schemas: read tcp [::1]:46044->[::1]:8080: read: connection reset by peer"
time="2017-01-01T02:45:29Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
2017-01-01 02:45:32,501 ERROR [acbc2fec-e4d0-455c-ba3a-6fe0f636ebe8:252428] [instance:12531] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12531]
2017/01/01 02:45:39 http: proxy error: net/http: request canceled
time="2017-01-01T02:45:55Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:45:56Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
2017-01-01 02:46:01,970 ERROR [446b3fca-763c-4a4e-9b10-3254d8dddb19:252457] [instance:12532] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12532]
time="2017-01-01T02:45:58Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:46:17Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: EOF"
2017-01-01 02:46:41,171 ERROR [366cc994-b41d-4842-8d24-0d83a0961008:252470] [instance:12533] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12533]
time="2017-01-01T02:47:00Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:47:01Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:47:03Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:47:30Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46060->[::1]:8080: read: connection reset by peer"
2017-01-01 02:47:51,639 ERROR [2043ffb4-d842-4645-a49d-203cf2b0b51e:252502] [instance:12534] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12534]
2017/01/01 02:48:00 http: proxy error: net/http: request canceled
time="2017-01-01T02:48:36Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:48:37Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:48:42Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 02:49:04,365 ERROR [8d722a4c-457c-48c3-b250-0737ebac0863:252529] [instance:12535] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12535]
time="2017-01-01T02:49:30Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
2017-01-01 02:49:59,946 ERROR [4aeb95cc-787d-41cc-be3d-d42ebbe4c5b4:252570] [instance:12536] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12536]
time="2017-01-01T02:50:36Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:50:41Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:50:48Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 02:51:14,349 ERROR [ef46500d-31ba-47f0-864b-0aa5ea27d800:252599] [instance:12537] [instance.start->(InstanceStart)] [] [ecutorService-7] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12537]
time="2017-01-01T02:51:48Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
time="2017-01-01T02:52:17Z" level=fatal msg="Unable to start event router" error="Get http://localhost:8080/v2-beta/externalhandlers?name=rancher-compose-executor&state=active: EOF"
2017-01-01 02:52:21,215 ERROR [de3256c1-d2b9-4f0a-b4f9-b82d7c3d66db:252639] [instance:12538] [instance.start->(InstanceStart)] [] [ecutorService-4] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12538]
2017-01-01 02:52:34,240 ERROR [7712addb-c4ca-43a1-9d7b-f8a19f3ed7c5:252661] [instance:12539] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12539]
time="2017-01-01T02:52:36Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:52:37Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:52:39Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:52:59Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46072->[::1]:8080: read: connection reset by peer"
time="2017-01-01T02:53:00Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
2017-01-01 02:53:13,768 ERROR [5974d135-d4a9-43d2-972c-fb29405e4dd7:252674] [instance:12540] [instance.start->(InstanceStart)] [] [ecutorService-5] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12540]
2017/01/01 02:53:16 http: proxy error: net/http: request canceled
time="2017-01-01T02:53:35Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:53:37Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:53:38Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta/schemas: read tcp [::1]:46082->[::1]:8080: read: connection reset by peer"
time="2017-01-01T02:53:39Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 02:53:39,666 ERROR [d8bad0d1-551e-4af6-b353-ec876b542d80:252693] [instance:12541] [instance.start->(InstanceStart)] [] [cutorService-10] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12541]
time="2017-01-01T02:53:47Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: EOF"
2017-01-01 02:53:50,786 ERROR [a8ce4a72-1ff1-4d20-9baf-282d3bd0a584:252706] [instance:12542] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12542]
time="2017-01-01T02:54:04Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:54:07Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:54:07Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:54:09Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 02:54:18,233 ERROR [a2f59f9e-c1a7-4075-b6f3-7924fd5c5c89:252717] [instance:12543] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12543]
time="2017-01-01T02:54:18Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: EOF"
time="2017-01-01T02:54:23Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46090->[::1]:8080: read: connection reset by peer"
2017/01/01 02:54:29 http: proxy error: net/http: request canceled
2017-01-01 02:54:35,832 ERROR [735b8ff3-fd1d-4012-be1c-c8287e36a44f:252736] [instance:12544] [instance.start->(InstanceStart)] [] [ecutorService-4] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12544]
time="2017-01-01T02:54:44Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:54:45Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:54:47Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:54:47Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:55:02Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46096->[::1]:8080: read: connection reset by peer"
2017-01-01 02:55:03,552 ERROR [55f99f98-e2b0-4fb5-8a1e-3983bfdba424:252749] [instance:12545] [instance.start->(InstanceStart)] [] [ecutorService-7] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12545]
2017/01/01 02:55:15 http: proxy error: net/http: request canceled
2017-01-01 02:55:19,737 ERROR [95a400a5-5d1e-4707-ac53-0817cd152cc8:252760] [instance:12546] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12546]
time="2017-01-01T02:55:21Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
time="2017-01-01T02:55:24Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:55:24Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:55:25Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:55:34Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46106->[::1]:8080: read: connection reset by peer"
2017/01/01 02:55:38 http: proxy error: net/http: request canceled
2017-01-01 02:55:43,820 ERROR [3efb96df-7704-41c2-803c-29020a7d37f7:252783] [instance:12547] [instance.start->(InstanceStart)] [] [ecutorService-5] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12547]
time="2017-01-01T02:55:52Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:56:04Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46110->[::1]:8080: read: connection reset by peer"
2017-01-01 02:56:05,046 ERROR [63edd246-614b-4b8f-820d-3d9ff5125150:252794] [instance:12548] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12548]
time="2017-01-01T02:56:06Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:56:06Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:56:07Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:56:17Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46112->[::1]:8080: read: connection reset by peer"
2017-01-01 02:56:19,201 ERROR [8a0bbc2f-579d-4447-a0bb-6966bd1b9186:252805] [instance:12549] [instance.start->(InstanceStart)] [] [ecutorService-5] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12549]
2017/01/01 02:56:26 http: proxy error: net/http: request canceled
time="2017-01-01T02:56:37Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:56:49Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46118->[::1]:8080: read: connection reset by peer"
2017-01-01 02:56:50,327 ERROR [201f5dcd-a20a-41e1-a07e-a0b10282b1db:252835] [instance:12550] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12550]
time="2017-01-01T02:56:51Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:56:52Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:56:54Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:57:03Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46120->[::1]:8080: read: connection reset by peer"
2017-01-01 02:57:14,040 ERROR [69789d03-c427-4363-8fa8-a66406d9ba61:252846] [instance:12551] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12551]
2017/01/01 02:57:15 http: proxy error: net/http: request canceled
time="2017-01-01T02:57:22Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
2017-01-01 02:57:34,564 ERROR [1d7210ae-3bf0-4728-a3e5-47b81c846eb7:252857] [instance:12552] [instance.start->(InstanceStart)] [] [ecutorService-4] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12552]
time="2017-01-01T02:57:35Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46126->[::1]:8080: read: connection reset by peer"
time="2017-01-01T02:57:36Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:57:36Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:57:37Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:57:46Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46128->[::1]:8080: read: connection reset by peer"
2017-01-01 02:57:52,418 ERROR [638dc7a7-0a5d-4ad7-8c0d-078f4d05a5dc:252881] [instance:12553] [instance.start->(InstanceStart)] [] [ecutorService-1] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12553]
2017/01/01 02:57:55 http: proxy error: net/http: request canceled
2017-01-01 02:58:10,042 ERROR [3ccc7675-2bc9-46e5-b40d-b60cf24bc22c:252890] [instance:12554] [instance.start->(InstanceStart)] [] [ecutorService-2] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12554]
time="2017-01-01T02:58:13Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:58:14Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:58:17Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:58:20Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T02:58:31Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: EOF"
2017-01-01 02:58:33,508 ERROR [cc136d2b-daf2-442d-8c02-804c0d84ed20:252903] [instance:12555] [instance.start->(InstanceStart)] [] [ecutorService-1] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12555]
time="2017-01-01T02:58:38Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46136->[::1]:8080: read: connection reset by peer"
2017/01/01 02:58:44 http: proxy error: net/http: request canceled
2017-01-01 02:58:54,302 ERROR [144cbada-8f34-4148-8229-5c4825f63ab9:252933] [instance:12556] [instance.start->(InstanceStart)] [] [cutorService-10] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12556]
time="2017-01-01T02:59:04Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T02:59:14Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T02:59:16Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T02:59:19Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46146->[::1]:8080: read: connection reset by peer"
time="2017-01-01T02:59:19Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 02:59:23,781 ERROR [a840565d-b8da-44c9-a84c-a81731f535e7:252944] [instance:12557] [instance.start->(InstanceStart)] [] [ecutorService-1] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12557]
time="2017-01-01T02:59:33Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46148->[::1]:8080: read: connection reset by peer"
2017/01/01 02:59:43 http: proxy error: net/http: request canceled
2017-01-01 02:59:52,911 ERROR [c277ac6e-e7e5-42de-bb5a-9e4f4eadcb29:252970] [instance:12558] [instance.start->(InstanceStart)] [] [ecutorService-5] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12558]
time="2017-01-01T03:00:00Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:00:12Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46154->[::1]:8080: read: connection reset by peer"
time="2017-01-01T03:00:13Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T03:00:13Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T03:00:14Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 03:00:17,894 ERROR [877c6324-3153-4df7-a9c6-6930b75ba447:252981] [instance:12559] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12559]
time="2017-01-01T03:00:25Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46156->[::1]:8080: read: connection reset by peer"
2017/01/01 03:00:33 http: proxy error: net/http: request canceled
2017-01-01 03:00:36,210 ERROR [876b3850-c33e-49fd-926d-79c9788e2586:252992] [instance:12560] [instance.start->(InstanceStart)] [] [cutorService-10] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12560]
time="2017-01-01T03:00:54Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:01:02Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T03:01:03Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T03:01:06Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:01:09Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46164->[::1]:8080: read: connection reset by peer"
2017-01-01 03:01:13,242 ERROR [1bf51475-f438-4f88-83a3-03e60382d448:253034] [instance:12561] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12561]
time="2017-01-01T03:01:21Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46166->[::1]:8080: read: connection reset by peer"
2017/01/01 03:01:26 http: proxy error: net/http: request canceled
2017-01-01 03:01:26,832 ERROR [5494baaf-f69e-4d3b-9afe-658fd346e00d:253045] [instance:12562] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12562]
time="2017-01-01T03:01:46Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:01:50Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T03:01:52Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T03:01:54Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:02:04Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46182->[::1]:8080: read: connection reset by peer"
2017-01-01 03:02:08,346 ERROR [07c0b3f1-83b0-492a-8908-d5d0d43b5566:253084] [instance:12563] [instance.start->(InstanceStart)] [] [ecutorService-7] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12563]
time="2017-01-01T03:02:12Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46184->[::1]:8080: read: connection reset by peer"
2017/01/01 03:02:18 http: proxy error: net/http: request canceled
2017-01-01 03:02:37,634 ERROR [631702cc-f8bc-40e6-a651-727b10db397c:253095] [instance:12564] [instance.start->(InstanceStart)] [] [ecutorService-4] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12564]
time="2017-01-01T03:02:37Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:02:39Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T03:02:41Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T03:02:43Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:02:56Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: EOF"
time="2017-01-01T03:03:01Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46192->[::1]:8080: read: connection reset by peer"
2017-01-01 03:03:05,971 ERROR [f281fe98-8ec0-44f8-b81d-b3b786b3893f:253127] [instance:12565] [instance.start->(InstanceStart)] [] [ecutorService-5] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12565]
2017/01/01 03:03:09 http: proxy error: net/http: request canceled
time="2017-01-01T03:03:30Z" level=info msg="Setting log level" logLevel=info
2017-01-01 03:03:32,108 ERROR [a3ddc1bb-920e-432c-b398-349cdb0bdd30:253138] [instance:12566] [instance.start->(InstanceStart)] [] [ecutorService-4] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12566]
time="2017-01-01T03:03:32Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T03:03:33Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:03:35Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:03:50Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46198->[::1]:8080: read: connection reset by peer"
2017-01-01 03:03:56,832 ERROR [74286c70-1035-41e6-98cc-73e1e18d7399:253169] [instance:12567] [instance.start->(InstanceStart)] [] [ecutorService-3] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12567]
time="2017-01-01T03:04:13Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta/schemas: read tcp [::1]:46208->[::1]:8080: read: connection reset by peer"
2017/01/01 03:04:16 http: proxy error: net/http: request canceled
time="2017-01-01T03:04:20Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
2017-01-01 03:04:24,602 ERROR [f65cf672-3142-4d71-ae4c-9d421e5d7850:253180] [instance:12568] [instance.start->(InstanceStart)] [] [ecutorService-1] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12568]
time="2017-01-01T03:04:33Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46212->[::1]:8080: read: connection reset by peer"
time="2017-01-01T03:04:39Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T03:04:40Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T03:04:41Z" level=info msg="Waiting for handler registration (1/2)"
2017-01-01 03:04:46,053 ERROR [6aedda4a-151c-4a78-b74e-bb4f508b7b90:253204] [instance:12569] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12569]
time="2017-01-01T03:04:55Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46214->[::1]:8080: read: connection reset by peer"
2017/01/01 03:05:07 http: proxy error: net/http: request canceled
time="2017-01-01T03:05:08Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:05:25Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: read tcp [::1]:46220->[::1]:8080: read: connection reset by peer"
2017-01-01 03:05:26,478 ERROR [5da7597e-a1b4-4c70-ae7a-25ea67cf764c:253217] [instance:12570] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12570]
time="2017-01-01T03:05:30Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T03:05:31Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T03:05:33Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:05:43Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: read tcp [::1]:46222->[::1]:8080: read: connection reset by peer"
2017-01-01 03:05:45,287 ERROR [:] [] [] [] [ecutorService-4] [i.c.p.core.cleanup.TableCleanup     ] Skipped "cattle"."instance" where id in [12, 1, 10, 77, 76, 9, 74]
2017-01-01 03:05:45,307 ERROR [:] [] [] [] [ecutorService-4] [i.c.p.core.cleanup.TableCleanup     ] Skipped "cattle"."service_index" where id in [18, 20]
2017-01-01 03:05:45,332 ERROR [:] [] [] [] [ecutorService-4] [i.c.p.core.cleanup.TableCleanup     ] Skipped "cattle"."image" where id in [1, 9, 10, 12, 74, 76, 77]
2017-01-01 03:05:45,347 ERROR [:] [] [] [] [ecutorService-4] [i.c.p.core.cleanup.TableCleanup     ] Skipped "cattle"."agent" where id in [3, 6, 7, 9]
2017-01-01 03:05:45,366 ERROR [:] [] [] [] [ecutorService-4] [i.c.p.core.cleanup.TableCleanup     ] Skipped "cattle"."service" where id in [21, 23]
2017-01-01 03:05:45,373 ERROR [:] [] [] [] [ecutorService-4] [i.c.p.core.cleanup.TableCleanup     ] Skipped "cattle"."environment" where id in [11]
2017-01-01 03:05:45,457 ERROR [:] [] [] [] [ecutorService-4] [i.c.p.core.cleanup.TableCleanup     ] Skipped "cattle"."account" where id in [10, 12, 13, 15]
2017-01-01 03:05:46,639 ERROR [9f3cbd76-a689-46f8-bfa2-f26b4cb288c7:253249] [instance:12571] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12571]
2017/01/01 03:06:02 http: proxy error: net/http: request canceled
time="2017-01-01T03:06:08Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
2017-01-01 03:06:19,573 ERROR [c21ebeb6-81e2-4e85-bf79-878252f60d93:3672] [service:3] [service.update] [] [cutorService-24] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting with code [STATE_CHANGED] : STATE_CHANGED
2017-01-01 03:06:21,012 ERROR [:] [] [] [] [cutorService-24] [.e.s.i.ProcessInstanceDispatcherImpl] Process [service.update:3672] on [3] failed, exit [STATE_CHANGED] : io.cattle.platform.engine.process.impl.ProcessExecutionExitException: STATE_CHANGED
time="2017-01-01T03:06:30Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: EOF"
2017-01-01 03:06:32,677 ERROR [2fee4fac-c087-46a0-b674-83f8986ec97b:253266] [instance:12572] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12572]
time="2017-01-01T03:06:38Z" level=info msg="Setting log level" logLevel=info
time="2017-01-01T03:06:38Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
time="2017-01-01T03:06:40Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:06:57Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: EOF"
2017-01-01 03:07:15,130 ERROR [b9e124d0-1b83-42f6-88cc-96767cb22d4a:253296] [instance:12573] [instance.start->(InstanceStart)] [] [ecutorService-7] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12573]
time="2017-01-01T03:08:52Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:11:08Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
2017-01-01 03:12:58,551 ERROR [dfb2e2d5-cf61-466a-aa2c-d5e4777c316b:3672] [service:3] [service.update] [] [cutorService-50] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting with code [STATE_CHANGED] : STATE_CHANGED
2017-01-01 03:12:58,779 ERROR [:] [] [] [] [cutorService-50] [.e.s.i.ProcessInstanceDispatcherImpl] Process [service.update:3672] on [3] failed, exit [STATE_CHANGED] : io.cattle.platform.engine.process.impl.ProcessExecutionExitException: STATE_CHANGED
2017-01-01 03:13:03,671 ERROR [d4338e8c-fc46-4cd8-9250-83a245066b10:253375] [instance:12574] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12574]
time="2017-01-01T03:15:23Z" level=info msg="Setting log level" logLevel=info
2017-01-01 03:16:00,200 ERROR [c31f1535-0f5a-4dd4-8602-e7ccb525ba33:253417] [instance:12575] [instance.start->(InstanceStart)] [] [cutorService-10] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12575]
time="2017-01-01T03:15:40Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
2017-01-01 03:21:10,449 ERROR [8e4c0649-e31e-4f32-9849-c9e53a54b1bb:253442] [instance:12576] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12576]
time="2017-01-01T03:17:43Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:20:37Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
time="2017-01-01T03:30:38Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:32:12Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
2017-01-01 03:33:57,265 ERROR [f2c7574e-1c69-4572-b002-75cbab0b9c0e:253469] [instance:12577] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12577]
2017-01-01 03:35:02,366 ERROR [aa83db39-159c-4659-9b04-e75331eec5e0:253487] [instance:12578] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12578]
2017-01-01 03:36:16,545 ERROR [ae83b384-dac4-49dd-b54a-78105e2b5edf:253499] [instance:12579] [instance.start->(InstanceStart)] [] [ecutorService-9] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12579]
2017-01-01 03:37:33,896 ERROR [a095eb66-0bf9-4918-84ba-847530a0d1d8:253516] [instance:12580] [instance.start->(InstanceStart)] [] [ecutorService-1] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12580]
time="2017-01-01T03:38:30Z" level=info msg="Setting log level" logLevel=info
2017-01-01 03:39:16,916 ERROR [30bd39c4-6d6f-4fb1-a626-3577846a1f36:253529] [instance:12581] [instance.start->(InstanceStart)] [] [cutorService-10] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12581]
time="2017-01-01T03:38:39Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
2017-01-01 03:40:28,518 ERROR [418442bc-84a0-4d31-b1ce-5fbf8b2963fe:253542] [instance:12582] [instance.start->(InstanceStart)] [] [ecutorService-7] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12582]
time="2017-01-01T03:39:15Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:47:49Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T03:42:43Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
time="2017-01-01T03:49:23Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
2017-01-01 03:51:13,464 ERROR [e23b0f41-0c1e-4a7a-bc6d-623e640cb6b2:253572] [instance:12583] [instance.start->(InstanceStart)] [] [ecutorService-4] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12583]
2017-01-01 03:54:35,574 ERROR [c599e7e3-5a2a-4385-a0b6-d796a2581a10:253610] [instance:12584] [instance.start->(InstanceStart)] [] [ecutorService-7] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12584]
time="2017-01-01T03:56:38Z" level=info msg="Setting log level" logLevel=info
2017-01-01 03:57:33,674 ERROR [f3a92bed-a1df-4cd0-996d-cb1ab2579b13:253623] [instance:12585] [instance.start->(InstanceStart)] [] [ecutorService-6] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12585]
time="2017-01-01T03:57:22Z" level=info msg="Starting go-machine-service..." gitcommit=v0.34.1
2017-01-01 04:02:25,023 ERROR [cb605d6e-d44e-4c17-b2a5-178b480f62c3:253638] [instance:12586] [instance.start->(InstanceStart)] [] [ecutorService-8] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [12586]
time="2017-01-01T03:58:16Z" level=info msg="Waiting for handler registration (1/2)"
time="2017-01-01T03:59:24Z" level=fatal msg="Exiting go-machine-service: Get http://localhost:8080/v2-beta: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
time="2017-01-01T04:04:32Z" level=info msg="Starting rancher-compose-executor" version=v0.12.1
time="2017-01-01T04:06:38Z" level=fatal msg="Unable to create event router" error="Get http://localhost:8080/v2-beta: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"

This sounds like "t2-itis", where if you try to use any significant sustained CPU on a t2 insurance (particularly the smaller ones) they run out of CPU credits and stop getting scheduler slots for seconds at a time.

AWS EC2 logs show that CPU credits have not run out for this instance while it has been running.

@Shemeikka can you reproduce this on modern versions of rancher? There could have been many things going wrong to induce these types of errors... It'd be good to troubleshoot on the latest.


Run jobs at specific date

Coverage remained the same at 100.0% when pulling 7b4d1efdfb5c010f34a59d93e308ab8a73ec8a7a on feature-run-at-specific-date into 110f8a0e509d7f2d92340c34e82e69555e566d21 on master.


KeyError: 'SSFA is not in the neck registry'

Thank you for sharing the code.
I am trying to train and test.
But i had a problem while training and testing with KITTI.
The issue is like this.

What is wrong with me?
If anyone knows what error it is, please let me know how to solve it.
Thank you.

SSFA module is in SE-SSD/det3d/models/necks/rpn_v1.py. Please ensure the installation with setup.py or citation in SE-SSD/det3d/models/necks/init.py.

Ok. Let me try again.
Thank you for replying.

@Vegeta2020
It was solved when i did setup.py again thanks.
But i got a different error.
Do you or anyone know what problem it is?

... skip ...

... skip ...

... skip ...

What is this problem from?
TypeError: can't pickle _thread.RLock objects
Please let me know if you know what it is.
Thank you.

It was solved.
#14 helped me.

Hello, I also met this problem.
I am wondering which setup.py did you run to solve the KeyError: 'SSFA is not in the neck registry'?
$ cd ./SE-SSD/det3d/core/iou3d
$ python setup.py install
or
$ cd ./SE-SSD
$ python setup.py build develop
Thank you so much for the help.

I did both.
Make sure to do it in order.
I think the order is important to run.

Thank you for the quick reply. It was solved.
And I am also wondering about your PyTorch version?
Best Regards.

I am using 1.7.1.


Unable to use --use-elf option in 'west flash' to correctly flash the .elf file

Describe the bug
When flashing the cc3220sf_launchxl using the --use-elf option in west, I get the following error:
$ west --verbose flash --use-elf
ZEPHYR_BASE=/home/vwan/zephyrproject-work/zephyr (origin: env)
-- west flash: rebuilding
cmake version 3.13.2 is OK; minimum version is 3.13.1
Running CMake: /home/vwan/cmake/cmake-3.13.2-Linux-x86_64/bin/cmake --build /home/vwan/zephyrproject-work/zephyr/samples/hello_world/build
ninja: no work to do.
-- west flash: using runner openocd
runners.openocd: /home/vwan/bin/zephyr-sdk-0.11.2/sysroots/x86_64-pokysdk-linux/usr/bin/openocd -s /home/vwan/zephyrproject-work/zephyr/boards/arm/cc3220sf_launchxl/support -s /home/vwan/bin/zephyr-sdk-0.11.2/sysroots/x86_64-pokysdk-linux/usr/share/openocd/scripts -f /home/vwan/zephyrproject-work/zephyr/boards/arm/cc3220sf_launchxl/support/openocd.cfg -c init -c targets -c 'reset halt' -c 'load_image /home/vwan/zephyrproject-work/zephyr/samples/hello_world/build/zephyr/zephyr.elf' -c 'resume 0x00000000010012e9' -c shutdown
Open On-Chip Debugger 0.10.0+dev-01340-ga0e8edc4e-dirty (2020-02-14-05:38)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : XDS110: connected
Info : XDS110: firmware version = <IP_ADDRESS>
Info : XDS110: hardware version = 0x0027
Info : XDS110: connected to target via SWD
Info : XDS110: SWCLK set to 2500 kHz
Info : clock speed 2500 kHz
Info : SWD DPIDR 0x2ba01477
Info : cc32xx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : Listening on port 3333 for gdb connections
    TargetName         Type       Endian TapName            State
--  ------------------ ---------- ------ ------------------ ------------
 0* cc32xx.cpu         cortex_m   little cc32xx.cpu         running

Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0000eb30 msp: 0x20004000
Info : SWD DPIDR 0x2ba01477
Error: Failed to write memory at 0x01000014

Info : XDS110: disconnected
FATAL ERROR: command exited with status 1: /home/vwan/bin/zephyr-sdk-0.11.2/sysroots/x86_64-pokysdk-linux/usr/bin/openocd -s /home/vwan/zephyrproject-work/zephyr/boards/arm/cc3220sf_launchxl/support -s /home/vwan/bin/zephyr-sdk-0.11.2/sysroots/x86_64-pokysdk-linux/usr/share/openocd/scripts -f /home/vwan/zephyrproject-work/zephyr/boards/arm/cc3220sf_launchxl/support/openocd.cfg -c init -c targets -c 'reset halt' -c 'load_image /home/vwan/zephyrproject-work/zephyr/samples/hello_world/build/zephyr/zephyr.elf' -c 'resume 0x00000000010012e9' -c shutdown

It seems to be using different command line options for OpenOCD when compared with flashing using 'west flash' (ie. using .hex file), which works fine.
To Reproduce
Steps to reproduce the behavior:

cd samples/hello_world
west build -b cc3220sf_launchxl
west --verbose flash --use-elf

Expected behavior
I'd have expected it to correctly flash and run zephyr.elf, using the same OpenOCD command line invocation as for .hex files:
$ west --verbose flash
ZEPHYR_BASE=/home/vwan/zephyrproject-work/zephyr (origin: env)
-- west flash: rebuilding
cmake version 3.13.2 is OK; minimum version is 3.13.1
Running CMake: /home/vwan/cmake/cmake-3.13.2-Linux-x86_64/bin/cmake --build /home/vwan/zephyrproject-work/zephyr/samples/hello_world/build
ninja: no work to do.
-- west flash: using runner openocd
-- runners.openocd: Flashing file: /home/vwan/zephyrproject-work/zephyr/samples/hello_world/build/zephyr/zephyr.hex
runners.openocd: /home/vwan/bin/zephyr-sdk-0.11.2/sysroots/x86_64-pokysdk-linux/usr/bin/openocd -s /home/vwan/zephyrproject-work/zephyr/boards/arm/cc3220sf_launchxl/support -s /home/vwan/bin/zephyr-sdk-0.11.2/sysroots/x86_64-pokysdk-linux/usr/share/openocd/scripts -f /home/vwan/zephyrproject-work/zephyr/boards/arm/cc3220sf_launchxl/support/openocd.cfg -c init -c targets -c 'reset halt' -c 'flash write_image erase /home/vwan/zephyrproject-work/zephyr/samples/hello_world/build/zephyr/zephyr.hex' -c 'reset halt' -c 'verify_image /home/vwan/zephyrproject-work/zephyr/samples/hello_world/build/zephyr/zephyr.hex' -c 'reset run' -c shutdown

Impact
Unable to use west to flash .elf files, which are natively supported by OpenOCD.
Environment (please complete the following information):

OS: Ubuntu 18.04
Toolchain: Zephyr SDK 0.11.2
Commit SHA or Version used: 6ba69f19d4a4faaa75abbc8a75845049e51077db

@abrodkin can you take a look please?

@vanti I guess you see the difference between flashing binary in the flash-memory (via quite special procedure with block erase, write protection management etc) and later execution of that code after board reset and loading contents of the Elf-file in word-writable RAM (be it on-chip SRAM, DDR etc).
From your log I see this: Error: Failed to write memory at 0x01000014 which means you're trying to write non-writable memory (I guess Flash in your case). And that's pretty expected.
First of all why are you trying to use Elf? If you really want to use it and have enough on-board RAM you may link your application so that it is loaded in RAM but not flash.
Let me know if you need more help with that.

@abrodkin We are making some changes to OpenOCD for our platform, and wanted to validate the behavior when loading elf files was when we came across this issue. Afaik, elf format is generic and does not imply that code would reside in RAM vs flash. and when I look at the help text for "--use-elf":
    --use-elf             if given, Elf file will be used for loading instead of
                          HEX image

It simply states that it would use the elf file as opposed to the hex file, so I wouldn't have expected it to make any assumption on code location. OpenOCD itself supports loading to flash when an elf file is used; thus there is no limitation on that front either.
It seems to me that either 1) the option is badly named and should state that it is there to load to RAM or 2) there should be a different command line flag (e.g. --load-to-ram) that when used in conjunction with --use-elf would determine whether RAM or flash is to be used.

@vanti indeed Elf itself has nothing to do with a way its contents end-up in target's memory. But I may guess from OpenOCD stand-point there's a difference between mechanics of pushing data in memory in case of flash write_image erase command and load_image.
And I do understand your confusion which I guess happens due to the fact that west's command name is flash in both cases - I did chose to just extend its functionality in a bit unusual for meaning of "flash" (as a verb) in a more of "load" sense.
@nashif do you think we should implement a separate load command for west to overcome mentioned confusion? But I guess if we go that far we'd need to change some more things as well like sanitycheck script in a way so it determines somehow for which platform we use west run and for which west flash.


Fix: clipboard on linux

This PR introduces a possible fix for clipboard handling on simpler desktop environments. The implementation leverages multithreading to avoid blocking the main thread when interacting with the clipboard, improving responsiveness and compatibility with certain desktop environments.

The EditorClipboard struct wraps the arboard::Clipboard functionality in a thread-safe Arc<Mutex<Clipboard>> to ensure safe concurrent access.
Clipboard contents are set directly within the current thread for non-Linux platforms.
For Linux platforms, clipboard contents are set asynchronously using a new thread to prevent blocking.

Known Limitation
While this solution handles clipboard interaction in simpler DEs, there is a limitation. If the main program exits, the clipboard thread will also terminate (have not tested this but it is expected), meaning the clipboard contents may be lost. To allow clipboard contents to persist beyond the life of the program, a longer-lasting solution would be to spawn a daemon process. An example of how to implement this can be found in the arboard daemonize example.

Tests are failing due to clipboard not being mocked, I'll try fixing this


Basic UI for RasterSymbolizer / ColorMap

FEATUREREQUEST
Description:
A basic UI to take advantage of the RasterSymbolizer would be a good thing IMHO to put things forward.
I suggest to start with a simple UI to let the user create and manipulate a ColorMap. Maybe we can re-use several components of the classification dialog for vector data or am I wrong?
I created a (very quick and dirty) UI sketch as discussion base:

As always: Improving / extending the UI at later points should not be the problem due to the micro-component based architecture.  For example adding a RasterCalculator (see #935).

@jansule did this already.

It's in the demo app.

:heart_eyes: Awesome! Wasn't aware of this.
So what is needed to get advanced styling possibilities based on concrete raster data is a data connection by GeoTiff (#992) or WCS (#1137).


Add notimouts to eksd installer and upgrader

Issue #, if available:
Part of #5565
Description of changes:
Respect --no-timeouts in eksd installer and upgrader.
Testing (if applicable):
Unit tests
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/lgtm

/approve
/cherry-pick release-0.15

/lgtm


Cannot specify the docker version of the vSphere node

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

I want to specify the docker version, so modify Global -> Settings -> engine-install-url to http://ip/18.09.sh.
Change the default docker_version=18.09.3 to docker_version=18.09.0 and upload it to http://ip/18.09.sh
Create a vSphere Node Template
Create a vSphere Cluster

Result:
The cluster can be launched, but the docker version of the node is 18.09.3, not the expected 18.09.0. Now I can't specify the docker version of the vSphere node.
Then I check the vSphere Node Template API and find "engineInstallURL": null, maybe related to this
{
"amazonec2Config": null,
"annotations": { },
"baseType": "nodeTemplate",
"cloudCredentialId": "cattle-global-data:vmware",
"created": "2019-03-25T11:18:29Z",
"createdTS":<PHONE_NUMBER>000,
"creatorId": "user-nwmn8",
"driver": "vmwarevsphere",
"engineEnv": { },
"engineInstallURL": null,
"engineLabel": { },
"engineOpt": { },
"engineRegistryMirror": null,
"id": "user-nwmn8:nt-n6kj7",

Other details that may be helpful:
Environment information

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

root cause is https://github.com/rancher/ui/blob/f777cf1589c3c9ec4d6015ada3e0c5d99a3e3c5d/lib/nodes/addon/components/driver-vmwarevsphere/component.js#L18

It happens in 2.1.x as well. So it's not a regression.

Fixed in rancher/rancher: v2.3.0-alpha3 version, you can modify the Docker Install URL in the template to set the docker version.


Minors changes for JOSS paper

This PR includes following minor changes:

My second affiliation has been removed
/paper has been excluded from codecov, which should largely address #64
The abstracts have been removed from paper.bib
The url link for the documentation in paper.md has been fixed

it is a waste of computational resources to constantly build the PDF of the paper in every single PR. Let's please remove the draft-pdf workflow once you have managed to build the paper once.

Documentation is not built properly because of a change in the interplay between trajectory and obtain_state in DynamicalSystemsBase.jl (used in logisitc example of the docs).

Fixed in https://github.com/JuliaDynamics/DynamicalSystemsBase.jl/pull/201
@JanJereczek , some advice for the future. If you have found an error, paste it. Don't just say "this error happened", copy the error message and paste it. Or alternatively copy the CI log line that has the error if you don't want to paste the entire thing. Let's not duplicate the effort to find the bug, which in some cases like now is trivial, but in general is non zero.

Thanks for fixing it @Datseris. The PR should be ready to merge! You are right, I will include the error messages in future :)


Replication and migrations don't work properly together

What steps will reproduce the problem?
If we have an app with the next conf:
        'db' => [
            'masterConfig' => [
                'username' => 'username',
                'password' => 'password',
                'attributes' => [
                    PDO::ATTR_TIMEOUT => 10,
                ],
            ],
            'masters' => [
                'db1' => [
                    'dsn' => 'pgsql:host=db1.example.ru;dbname=db1',
                ],
                'db2' => [
                    'dsn' => 'pgsql:host=db1.example.ru;dbname=db2',
                ],
            ]
        ],

and try to use yii2 migrations (for example: php yii migrate)
What is the expected result?
We expect that migrations should be applyed to each connection in order to keep databases structures identical.
What do you get instead?
We get the same behaviour with a random connection during migrate perfomance. desync db structures
Additional info
As near as figure out we get only one random  $this->db = Instance::ensure($this->db, Connection::className()); by common app rules and then we use this connection for all BaseMigrateController functions. Probably it will be better if those fuctions follow throuh array of db dsn.

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.1.9

Operating system
Ubuntu 16.04.3 LTS

Yes. Providing an opportunity by config option.
I understand that structure of replicas can be different in theory but in practice it almost never happens. Now we have to init an app step by step in each environment with only one dsn and migrate commands. And only after that switch the app to work-mode with a replica config.

in practice it almost never happens

I disagree. It happens and we should consider that replication itself could be two-way and could be done by a third party tool, not code.

I see. Thanks for the answers.


Monday meeting with Musedev

Tasks to complete before monday meeting:

[ ] sergio: find container to run service and push to dockerhub
[ ] shawn: add sergio to dockerhub org
[ ] shawn: test that our script works in their docker container
[ ] have demo to walk through

Minor points to clarify:

file in the toolnote: what format is it? Link to github file or relative path to the file in the repository?

Update: this task is now to deploy the docker container to musedev.


FEAT: support LoRA

Resolves #271.

[x] LoRA automatic cache
[ ] doc

Close this since implement this functionality in other PR.


[core.regexp] add matchEntirely and matchAsSuffix

There is the method matchAsPrefix already. It seems weird the two other alternatives are not present: matchAsSuffix, matchEntirely.
A replace with template would be nice as well to replace groups.
RegExp('hello').matchAsPrefix('hello you');

// match entirely
// you don't really convey the intent here, especially if the pattern comes from a variable you
// then have to check the string to be sure the pattern doesn't already includes the start and end codes.
// you also cannot use a raw string with the char $ at the end making it even less lisible
RegExp('^hello$').firstMatch('hello');

final pattern = r'(hello)(.*)';
final template = r'bonjour $2';
// this code doesn't exists but would produce "bonjour you", swift has something like that, I believe java does too
RegExp(pattern).match('hello you').replaceWithTemplate(template);

/cc @lrhn to make a call

tl;dr: Can't be efficiently compiled to JavaScript.
The matchAsPrefix functionality isn't really there to only match at the beginning of the string. You could just match with ^(?:$orioginal) instead. It's there because the start parameter allows you to try a match at any position, something ^ cannot do. Having it allows you to implement your own search for the next match, an anchored match at any position, rather than the default behavior which is to search for the next match automatically.
The reason we only have matchAsPrefix and not matchAsSuffix is that RegExps are traditionally matching forward. It's easy to say "Try to match from this position" because the underlying machinery does that all the time, but "try to find a match ending at this position" is not nearly as easy (not even with look-behinds). We need to be able to implement the functionality efficiently, also when compiling to JavaScript using their native RegExp. That means we cannot do anything which isn't supported at least somwwhat efficiently by that.
For matchEntireString, you can also do ^(?:$original)\$. That does work, whether the original regexp contains anchors or not, as long as you avoid multiline: true.
To do something useful, it should work on a substring, something like re.matchSubstring(source, start, end) which would accept only a match starting at start and ending at end.
Again, the underlying RegExp machinery doesn't really allow us to implement this efficiently. (Creating the substring is not considered efficient, and would still might not work correctly if the regexp contains lookaheads).

Given the @lrhn I will just close this.

tl;dr: Can't be efficiently compiled to JavaScript.
The matchAsPrefix functionality isn't really there to only match at the beginning of the string. You could just match with ^(?:$orioginal) instead. It's there because the start parameter allows you to try a match at any position, something ^ cannot do. Having it allows you to implement your own search for the next match, an anchored match at any position, rather than the default behavior which is to search for the next match automatically.
The reason we only have matchAsPrefix and not matchAsSuffix is that RegExps are traditionally matching forward. It's easy to say "Try to match from this position" because the underlying machinery does that all the time, but "try to find a match ending at this position" is not nearly as easy (not even with look-behinds). We need to be able to implement the functionality efficiently, also when compiling to JavaScript using their native RegExp. That means we cannot do anything which isn't supported at least somwwhat efficiently by that.
For matchEntireString, you can also do ^(?:$original)\$. That does work, whether the original regexp contains anchors or not, as long as you avoid multiline: true.
To do something useful, it should work on a substring, something like re.matchSubstring(source, start, end) which would accept only a match starting at start and ending at end.
Again, the underlying RegExp machinery doesn't really allow us to implement this efficiently. (Creating the substring is not considered efficient, and would still might not work correctly if the regexp contains lookaheads).

It sounds like it is implemetable in javascript. If I understand correctly you can use matchAsPrefix and check the underlying lengths. Whether that's efficient or not idk.
for match entirely I have this:
extension MatchEntirely on RegExp {
  Match? matchEntirely(String pattern) {
    if (!pattern.endsWith(r'$')) {
      pattern = pattern + r'$';
    }
    return matchAsPrefix(pattern);
  }
}

A matchEntirely on RegExp (not on Pattern in general) could definitely be created. Something like:
Match? matchEntirely(String input) => RegExp("^(?:${this.pattern})\$").firstMatch(input);

My point is that because it's easy as this, it's not really needed as a feature. You can always write your pattern that way to begin with, and in the vast majority of use-cases, you have the pattern directly in your source code.
If the method cannot take a start/end position, like matchAsPrefix takes a start position, then it won't be worth having an extra method.
If it does have a start and end, then it's not efficiently implementable in JavaScript. Possibly not on the VM either, depending on the restrictions of the underlying regexp engine (it's an implementation of JavaScript regexps, so it doesn't have to support an end position different from the end of the string.

then it won't be worth having an extra method.

Happy to disagree, for readability of code I think it would be worth it. Case closed then, I won't push it.


Advanced Search Syntax: "created:-100 days" not working

Expected behaviour
I put "status:open created:<-100 days" as a search.
I expect to see all tasks that I created more than 100 days ago.
Actual behaviour
No tasks are found.
The syntax "status:open created:<2015-07-01" works though.
Steps to reproduce
see above
Configuration
Copy and paste the configuration section from the Kanboard settings page or fill these fields:

Kanboard version: 1.0.26
Database type and version: sqlite3 3.6.20
PHP version: <IP_ADDRESS>
OS: CentOS 6.7
Browser: Firefox 45.0.1

With the current development version, the syntax status:open created:<"-100 days" is now supported. The double quotes are required.


Node-inspector unable handle console = true

i run my node-inspector then with console=true, it will crash everytime. Node-inspector print an empty object but somehow my terminal is fine. Is this a bug??

I think so, in that the following behavior should either be documented or changed: the console option only supports logging objects / JSON.
I'm surprised this hasn't surfaced before actually. Can you confirm that what you were logging was just a string message or similar? If so, does logging an object work?

Yeah i'm only logging some request info out to LE in JSON string format. I try an object this morning and saw the same issue.
If this is bug, is there a work around for now?

If you're seeing the issue with objects, I don't think it's related to what I first suspected was the issue. Can you show how to reproduce it?

Here is my version >> Node Inspector v0.12.5 & le_node 1.2.0.
node-inspector run and with sample code blow:
var test = new Logger({ token: token, console: true });
    test.info({
        "x": "1",
        "xx": "2",
        "xxx": "3",
        "xxxx": "4"
    });

Sorry, @fchengpc, I should have specified to test it with node. At a glance it looks like node-inspector is a pretty hefty tool that may change how any number of the normal systems it needs to intercept work, and one of the areas they're patching is logging, so I couldn't predict how it might interact with le_node.

i see, just node is fine. all the terminal output is fine. just not with node-inspector. Guess you can close.


release-3.0 etcdmain/config.go format question

LPUrlsCfgFile  string json:"listen-peer-urls"
LCUrlsCfgFile  string json:"listen-client-urls"
ApurlsCfgFile  string json:"initial-advertise-peer-urls"
AcurlsCfgFile   string json:"advertise-client-urls"
The format is differ, and why? (LP* and Ap*)

@shuqilou no particular reason. It's consistent in master. Cf. https://github.com/coreos/etcd/blob/master/embed/config.go#L118-L122

I think the questions is answered. Closing.


Add utfpr/alunos.txt

@GustavoK101 I am sorry, the domain utfpr.edu.br is removed from our trusted domains list because the school allows to register an email address there even if you are not a student of the school. If you are the student of this school, please apply with official document (OFFICIAL DOCUMENT tab at https://www.jetbrains.com/shop/eform/students).


Cannot perform DataView.prototype.setBigUint64 on a detached ArrayBuffer

Forward https://github.com/swiftwasm/JavaScriptKit/issues/217
Could you apply the patch for wasmer-js/wasi https://github.com/swiftwasm/carton/blob/74b8ca6e1d5ebef70ff6ecebf445b5a9674f83a1/entrypoint/common.js#L135-L152, or you can use uwasi instead of it.

@kateinoigakukun thank you very much, I applied the patch! 🚀 (swiftwasm/JavaScriptKit#217)
@tierracero could you please update webber to 1.4.0 via brew upgrade webber to check if issue is solved?

Thanks for forwarding issue to the SwifWeb team, they made a fix that you suggested.
I have been doing various stress tests and everything seems to be working fine now.


Enhance User-Accessibility of CkLocMgr Information

Libraries/users may require more information than the current location manager interface exposes -- including access to (all) location updates and known indices. While (some) location updates can be derived from array listener events, they provide additional details that may be unnecessary. Additionally, array listener events only involve changes to elements on a given PE, whereas location manager updates may be for distant elements (e.g., when a PE receives an informHome update).
Secondly, there is currently no mechanism for sweeping the cache of known indices of an array. This is useful for spanning tree creation, wherein distant members of a section can be discovered through prior communication.
Example usage:
void on_location_update(const CkGroupID& gid, const CmiUInt8& id, const int& pe) {
  auto *loc = CProxy_CkLocMgr(gid).ckLocalBranch();

  CkPrintf("pe%d> got a location update, 0x%lx (with home %d) moved to %d!\n", CkMyPe(), id, loc->homePe(id), pe);

  auto found = false;
  loc->perKnown([&](const CkArrayIndex& idx) -> bool {
    found = id == loc->lookupID(idx);
    return !found; // continue search while elt not found
  });
  CkAssert(found);
}

void subscribe_to(CkArray* arr) {
  auto* locMgr = arr->getLocMgr();
  using namespace std::placeholders;
  locMgr->addListener(std::bind(
    &on_location_update,
    this,
    _1,
    _2,
    _3
  ));
}

No longer relevant.


Update docs for #3129

Update docs for #3129

[#3129  ] Docs added
Please, regenerate docs by running next command:
$ php bin/docgen

Added documentation https://deployer.org/docs/7.x/selector


Wrong FILE_INFORMATION_CLASS on MSDN

The FILE_INFORMATION_CLASS enum on MSDN is 0-based. It should be instead:
typedef enum _FILE_INFORMATION_CLASS {
    FileDirectoryInformation         = 1,
    FileFullDirectoryInformation,   // 2
    FileBothDirectoryInformation,   // 3
    FileBasicInformation,           // 4

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

ID: a8119f8b-9c83-60f2-ac36-0478b88c4ab0
Version Independent ID: 404ee010-b7dc-6a9e-7bbe-7cee72809333
Content: _FILE_INFORMATION_CLASS (wdm.h) - Windows drivers
Content Source: wdk-ddi-src/content/wdm/ne-wdm-_file_information_class.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Sorry for the delay on this.  This is a known issue with our doc reflection system. I just pushed a change that attempts to override the auto-gen syntax block, we'll see if it works.

Fixed on https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/ne-wdm-_file_information_class.  Thanks again for the report @0xeb


make training Error: missing ground truth for training

I've followed the instructions on how to train images but I keep on getting this error
PYTHONIOENCODING=utf-8 python3 generate_line_box.py -i "data/foo-ground-truth/wackenroder_herzensergiessungen_1797_0051_001.tif" -t "data/foo-ground-truth/wackenroder_herzensergiessungen_1797_0051_001.gt.txt" > "data/foo-ground-truth/wackenroder_herzensergiessungen_1797_0051_001.box"
+ tesseract data/foo-ground-truth/wackenroder_herzensergiessungen_1797_0051_001.tif data/foo-ground-truth/wackenroder_herzensergiessungen_1797_0051_001 --psm 6 lstm.train
Tesseract Open Source OCR Engine v5.0.0-alpha-635-g90405 with Leptonica
Page 1
Warning: Invalid resolution 0 dpi. Using 70 instead.
find data/foo-ground-truth -name '*.lstmf' | python3 shuffle.py 0 > "data/foo/all-lstmf"
Error: missing ground truth for training
Makefile:147: recipe for target 'data/foo/list.train' failed
make: *** [data/foo/list.train] Error 1

It keeps on showing this error Error: missing ground truth for training
command i used make training
the image and ground truth text are from the same repo ocrd-testset.zip
what could possibly the solution to fix this?

How are you running the training?
I ran it after a fresh install and it worked fine. See attached log.
git clone https://github.com/tesseract-ocr/tesstrain.git
cd tesstrain
mkdir data
unzip /home/ubuntu/tesstrain/ocrd-testset.zip -d data/foo-ground-truth
nohup make training &

nohup.out.txt

i did the same step you did
git clone https://github.com/tesseract-ocr/tesstrain.git
cd tesstrain
mkdir data

Downloaded the zip file and unzipped it in the data/foo-ground-truth
make training

@royudev I cannot reproduce your error. Could you please run the exact steps which @Shreeshrii proposed and post the file nohup.out.txt here? In addition, please run ls -l on data and on data/foo-ground-truth.

Hi @wrznr I was able to make it work, I've attached the nohup.out.txt
nohup.out.txt
here's the ls -l of data
total 256
drwxrwxrwx 1 vagrant vagrant 262144 Mar 13 18:01 foo-ground-truth

weird thing is when i use only 1 .tif file and it's equivalent .gt.txt in the foo-ground-truth (for example: alexis_ruhe01_1852_0018_022.gt.txt and alexis_ruhe01_1852_0018_022.tif) i always get the Error: missing ground truth for training

You need lines for training as well as evaluation. The default ratio is 9:1 (I think). So, use at least 10 lines of text and image pairs.

Hi @wrznr I was able to make it work, I've attached the nohup.out.txt
nohup.out.txt
here's the ls -l of data
total 256
drwxrwxrwx 1 vagrant vagrant 262144 Mar 13 18:01 foo-ground-truth

weird thing is when i use only 1 .tif file and it's equivalent .gt.txt in the foo-ground-truth (for example: alexis_ruhe01_1852_0018_022.gt.txt and alexis_ruhe01_1852_0018_022.tif) i always get the Error: missing ground truth for training

I have the same error, how did u fix this?

@atuanbk58 Pls. see the answer by @Shreeshrii: It is not fixable. You will need at least two lines GT when setting the ration to 1:1 or ten lines with the default ratio of 9:1 between training and test set. However, both scenarios will not result in usable models. For training OCR, you will need several hundreds of GT lines.


backward() vs backwardThroughTime()

I'm confused about how to use this library in such a way that it is API-compatible with the rest of torch. For other parts of torch, eg for simple MLPs, it seems that the standard pattern for training models is to do something like:
local parameters, gradParameters = model:getParameters()
local inputs, targets = getMiniBatch()
local function fEval(x)
if parameters ~= x then parameters:copy(x) end
model:zeroGradParameters()
local output = model:forward(inputs)
local err = criterion:forward(output, targets)
local df_do = criterion:backward(output, targets)
model:backward(inputs, df_do)
return err, gradParameters
end
optim.optimMethod(fEval, parameters)
I'd like to be able to use this package's RNN code, but train using training code I already have.  However, it seems that backward() doesn't do something and we have to call backwardThroughTime() instead.

Is this true? Why not make the RNN stuff API-compatible so that we can call backward()?
If I'm going to add a backwardThroughTime() call to my training code? Where do I put it? Do I call backward() and then backwardThroughTime(). Suppose there are LookupTable layers below the RNN. After calling backwardThroughTime, would I need to call backward() on them?

Thanks,
David

@davidBelanger 1. yes. However, if you want your rnn to be compatible with the optim API, you wrap it in a nn.Sequencer. The Sequencer takes care of the backwardThroughTime during its backward call.

if you don't want to wrap your rnn in a Sequencer, you will have to call backwardThroughTime after your sequence of inputs,targets has been fed in (forward/backwarded). Please refer to the Recurrent doc examples for additional details.

Thanks! It sounds like Sequencer is exactly what I was looking for. My mistake was just to use the RNN and not wrap it in that.
Cheers,
David


lea.verou.me/prefixfree is out of date

http://lea.verou.me/prefixfree/ is out of sync with the github.io page ('only 4 kb' and the github ribbon 404s).

The size refers to minified & gzipped size, checked via Google Closure Compiler.
Regarding the github ribbon, thanks, PR? :)

Then http://leaverou.github.io/prefixfree/ is out of date (2KB, and a different design).
Since it's linked from both the README and the GitHub description, I though it was current.
I'll happily send a PR once I know what to update :-).

Looks like http://lea.verou.me/prefixfree/ still has the source from before 2012.

Just noticed the URL. The correct one is leaverou.github.io/prefixfree. The other one is wildly out of date and I should probably delete it.


Automated Download Fail

I have followed the steps for the Automated download.
on these step "git clone git@github.com:trailheadapps/ecars.git" my console(command prompt) throws the error.
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists."
so I switched on the git clone https URL.
it successfully clone the repo.
now on the last step it was failed showing these error.
" if (config.fatal) throw e;
^
Error: exec: error: unknown option `show-current' ".
Please anyone, can help on these error.

Hi @mayankagarwal900 - can you check which version of git you have? You can do that by running git --version
I believe you need at least version 2.22 to use the show-current subcommand.
Also, this article might help with the permission denied error you were getting, but it sounds like you got by that. https://docs.github.com/en/github/authenticating-to-github/error-permission-denied-publickey

@crcastle Thanks for your quick reply and it has solved my previous error.
But while proceeding the further from the automated deploy it shows the error.
"spawnSync sfdx ENOENT" .
So I switched into the manual deploy somehow I completed all the steps. And application is running. But in one step its shows the error can you please help on that point also.
step is running these command
"heroku run 'cd packages/ecars-db && npx sequelize db:migrate' --app=[STREAMING APP NAME]"
and error is
" »   Error: Missing required flag:
»     -a, --app APP  parent app used by review apps
»   See more help with --help "
Thanks

Hi @mayankagarwal900- When you run that command, did you replace [STREAMING APP NAME] with the name of your heroku app that manages the streaming data?

@crcastle Yes I have done that.


Unnecessary margin for icon buttons

Hello,
Looks something in the code is adding an unnecessary margin for buttons only based on icons:

Interesting 🤔
CSS is a pain, I will take a look at this today


[Logging] Log exceptions to Slack

:+1:

(But please remove the email env vars when this is merged)


Update misleading statements about TRUNCATE TABLE

The document says that TRUNCATE TABLE is non-logged, but that is incorrect and misleads the reader in a big way. It does not log the removal of individual rows, but the operation (removing pages) is captured in the transaction log. That is an important distinction because readers of this document may also be considering log shipping and will conclude that TRUNCATE TABLE is not compatible with that. Secondly, the document states that TRUNCATE TABLE does not fire triggers. While it does not fire DML triggers, which are used to detect changes for merge replication, it does fire DDL triggers.

@sqlsauce : Thanks for your contribution! The author, @MashaMSFT, has been notified to review your proposed change.

@sqlsauce Thank you for your SQL Content contribution! You are correct, thanks for catching this :) #sign-off

@craigg-msft per our discussion, I am merging this.

Great! That was my first contribution to the sql-docs repo  :-)

@sqlsauce Thanks again for your contribution! As you probably already know,  your change is now live :) If you find anything else that needs to be changed, please let us know!


Update README.md

Added NPM install

Codecov Report

Merging #194 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #194   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines         387    387
=====================================
  Hits          387    387

Continue to review full report at Codecov.

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


Ionic 2: input doesn't get scrolled into view when keyboard opens

Short description of the problem:
Focus an input on a long form (see plunkr below), when the keyboard pops up, the input is now hidden behind the keyboard and not scrolled into view as expected.
What behavior are you expecting?
The selected input scrolls into view.
Which Ionic Version? 1.x or 2.x
2.x
Plunker that shows an example of your issue
yep, here you go: http://plnkr.co/edit/CVsJCpQMVRJoMuF8Sd9M?p=preview
but you'd need to run this on an Android device obviously.
I was testing on a Nexus 5 and Samsung Galaxy Note 4 FYI.
Run ionic info from terminal/cmd prompt: (paste output below)
Davids-MacBook-Air:AppHazard daveshirman$ ionic info
Your system information:
Cordova CLI: 6.2.0
Ionic Framework Version: 2.0.0-beta.10
Ionic CLI Version: 2.0.0-beta.32
Ionic App Lib Version: 2.0.0-beta.18
ios-deploy version: 1.8.6
ios-sim version: 5.0.8
OS: Mac OS X El Capitan
Node Version: v4.3.0
Xcode version: Xcode 7.2.1 Build version 7C1002

Hey @jgw96, is there any update on this please?
Thanks.

Same issue on Android 4.4.2 Acer Z500
Additional info:
Input moves into viewable area of screen once any key on keyboard is pressed

Hello all! Thanks for opening an issue with us and sorry for the delay on this. We actually plan on handling this issue as part of https://github.com/driftyco/ionic/issues/6228 so I am going to close this issue for now as a duplicate. Thanks for using Ionic!

any alternative solution for this issue.


Documentation

Hi,
I recently came to see your repo and I was amazed to find the devtools unlocked ig.
Can you guide me through the process of creating/reverse engineering the apps along with the tools you use. Also post in the Readme.md, and that will increase the authenticity of your repo.

Hi,
I recently came to see your repo and I was amazed to find the devtools unlocked ig.
Can you guide me through the process of creating/reverse engineering the apps along with the tools you use. Also post in the Readme.md, and that will increase the authenticity of your repo.

Hello 🤗. Good to Know welcome to repo .
Opening Devloper settings is not easy work for very first time . I do manage all things alone . For Readme.md I am currently thinking what to put. I am looking for it .
Thanks. if you like repo i hope for a star

Thanks for the response.
I am very much interested in this kind of stuffs but I am not sure how and where to start. If you can guide and help me on it, I am happy to contribute towards your repo.
Currently the repo is seems empty, once you update the readme and other details, surely you will receive stars.

Thanks for the response.
I am very much interested in this kind of stuffs but I am not sure how and where to start. If you can guide and help me on it, I am happy to contribute towards your repo.
Currently the repo is seems empty, once you update the readme and other details, surely you will receive stars.

Can We Talk on Telegram
t.me/salman_memon

Thanks for the response.
I am very much interested in this kind of stuffs but I am not sure how and where to start. If you can guide and help me on it, I am happy to contribute towards your repo.
Currently the repo is seems empty, once you update the readme and other details, surely you will receive stars.

Can We Talk on Telegram t.me/salman_memon
I have updated many things see
And
Add new update just now