need help, STS can't not connect with AVD got error log

STS log:
21:14:49.654 [Forwarding newSession on session null to remote] DEBUG o.a.h.c.protocol.RequestAddCookies - CookieSpec selected: best-match
-21:14:49.680 [Forwarding newSession on session null to remote] DEBUG o.a.h.c.protocol.RequestAuthCache - Auth cache not set in the context
-21:14:49.682 [Forwarding newSession on session null to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection request: [route: {}->http://<IP_ADDRESS>:4723][total kept alive: 0; route allocated: 0 of 2000; total allocated: 0 of 2000]
-21:14:49.705 [Forwarding newSession on session null to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection leased: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:14:49.708 [Forwarding newSession on session null to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Opening connection {}->http://<IP_ADDRESS>:4723
-21:14:49.709 [Forwarding newSession on session null to remote] DEBUG o.a.h.i.c.HttpClientConnectionOperator - Connecting to /<IP_ADDRESS>:4723
-21:14:49.711 [Forwarding newSession on session null to remote] DEBUG o.a.h.i.c.HttpClientConnectionOperator - Connection established <IP_ADDRESS>:59495<-><IP_ADDRESS>:4723
-21:14:49.711 [Forwarding newSession on session null to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Executing request POST /wd/hub/session HTTP/1.1
-21:14:49.711 [Forwarding newSession on session null to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Target auth state: UNCHALLENGED
-21:14:49.712 [Forwarding newSession on session null to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Proxy auth state: UNCHALLENGED
-21:14:49.713 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> POST /wd/hub/session HTTP/1.1
-21:14:49.713 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Content-Type: application/json; charset=utf-8
-21:14:49.713 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Content-Length: 659
-21:14:49.713 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Host: <IP_ADDRESS>:4723
-21:14:49.713 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Connection: Keep-Alive
-21:14:49.713 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> User-Agent: Apache-HttpClient/4.3.5 (java 1.5)
-21:14:49.714 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Accept-Encoding: gzip,deflate
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "POST /wd/hub/session HTTP/1.1[\r][\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Content-Type: application/json; charset=utf-8[\r][\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Content-Length: 659[\r][\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Host: <IP_ADDRESS>:4723[\r][\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Connection: Keep-Alive[\r][\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "User-Agent: Apache-HttpClient/4.3.5 (java 1.5)[\r][\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Accept-Encoding: gzip,deflate[\r][\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "[\r][\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "{[\n]"
-21:14:49.715 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "  "desiredCapabilities": {[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "appPackage": "com.android.calculator2",[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "appActivity": ".Calculator",[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "platformVersion": "6.0",[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "browserName": "",[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "platformName": "Android",[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "deviceName": "Android6"[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "  },[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "  "requiredCapabilities": {},[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "  "capabilities": {[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "desiredCapabilities": {[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "      "appPackage": "com.android.calculator2",[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "      "appActivity": ".Calculator",[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "      "platformVersion": "6.0",[\n]"
-21:14:49.716 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "      "browserName": "",[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "      "platformName": "Android",[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "      "deviceName": "Android6"[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    },[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "requiredCapabilities": {},[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "alwaysMatch": {[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "      "browserName": "",[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "      "platformName": "Android"[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    },[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "    "firstMatch": [][\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "  }[\n]"
-21:14:49.717 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "}"
-21:15:11.693 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "HTTP/1.1 200 OK[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "X-Powered-By: Express[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Origin: *[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Headers: origin, content-type, accept[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Vary: X-HTTP-Method-Override[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Type: application/json; charset=utf-8[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Length: 731[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "ETag: W/"2db-Y21msYuHoebMx38vzFoDmw20F0U"[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Date: Fri, 15 Sep 2017 01:15:11 GMT[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Connection: keep-alive[\r][\n]"
-21:15:11.694 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[\r][\n]"
-21:15:11.695 [Forwarding newSession on session null to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "{"status":0,"value":{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"emulator-5554","deviceUDID":"emulator-5554","deviceScreenSize":"1440x2560","deviceModel":"Android SDK built for x86","deviceManufacturer":"unknown"},"sessionId":"f16844dd-c40b-4307-a6dd-41198d328088"}"
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << HTTP/1.1 200 OK
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << X-Powered-By: Express
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Origin: *
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Headers: origin, content-type, accept
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Vary: X-HTTP-Method-Override
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: application/json; charset=utf-8
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 731
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << ETag: W/"2db-Y21msYuHoebMx38vzFoDmw20F0U"
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Date: Fri, 15 Sep 2017 01:15:11 GMT
-21:15:11.699 [Forwarding newSession on session null to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Connection: keep-alive
-21:15:11.707 [Forwarding newSession on session null to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Connection can be kept alive indefinitely
-21:15:11.711 [Forwarding newSession on session null to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection [id: 0][route: {}->http://<IP_ADDRESS>:4723] can be kept alive indefinitely
-21:15:11.711 [Forwarding newSession on session null to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection released: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-Sep 14, 2017 9:15:11 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: OSS
21:15:11.755 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.c.protocol.RequestAddCookies - CookieSpec selected: best-match
-21:15:11.755 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.c.protocol.RequestAuthCache - Auth cache not set in the context
-21:15:11.755 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection request: [route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.756 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection leased: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.756 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Stale connection check
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[read] I/O error: Read timed out"
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Executing request GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Target auth state: UNCHALLENGED
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Proxy auth state: UNCHALLENGED
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Cache-Control: no-cache
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Host: <IP_ADDRESS>:4723
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Connection: Keep-Alive
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> User-Agent: Apache-HttpClient/4.3.5 (java 1.5)
-21:15:11.757 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Accept-Encoding: gzip,deflate
-21:15:11.758 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1[\r][\n]"
-21:15:11.758 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Cache-Control: no-cache[\r][\n]"
-21:15:11.758 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Host: <IP_ADDRESS>:4723[\r][\n]"
-21:15:11.758 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Connection: Keep-Alive[\r][\n]"
-21:15:11.758 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "User-Agent: Apache-HttpClient/4.3.5 (java 1.5)[\r][\n]"
-21:15:11.758 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Accept-Encoding: gzip,deflate[\r][\n]"
-21:15:11.758 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "[\r][\n]"
-21:15:11.766 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "HTTP/1.1 200 OK[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "X-Powered-By: Express[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Origin: *[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Headers: origin, content-type, accept[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Type: application/json; charset=utf-8[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Length: 731[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "ETag: W/"2db-Y21msYuHoebMx38vzFoDmw20F0U"[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Date: Fri, 15 Sep 2017 01:15:11 GMT[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Connection: keep-alive[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[\r][\n]"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "{"status":0,"value":{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"emulator-5554","deviceUDID":"emulator-5554","deviceScreenSize":"1440x2560","deviceModel":"Android SDK built for x86","deviceManufacturer":"unknown"},"sessionId":"f16844dd-c40b-4307-a6dd-41198d328088"}"
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << HTTP/1.1 200 OK
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << X-Powered-By: Express
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Origin: *
-21:15:11.767 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Headers: origin, content-type, accept
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: application/json; charset=utf-8
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 731
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << ETag: W/"2db-Y21msYuHoebMx38vzFoDmw20F0U"
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Date: Fri, 15 Sep 2017 01:15:11 GMT
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Connection: keep-alive
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Connection can be kept alive indefinitely
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection [id: 0][route: {}->http://<IP_ADDRESS>:4723] can be kept alive indefinitely
-21:15:11.768 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection released: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.771 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.c.protocol.RequestAddCookies - CookieSpec selected: best-match
-21:15:11.771 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.c.protocol.RequestAuthCache - Auth cache not set in the context
-21:15:11.771 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection request: [route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.771 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection leased: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.771 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Stale connection check
-21:15:11.772 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[read] I/O error: Read timed out"
-21:15:11.772 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Executing request GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1
-21:15:11.772 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Target auth state: UNCHALLENGED
-21:15:11.772 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Proxy auth state: UNCHALLENGED
-21:15:11.772 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1
-21:15:11.772 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Cache-Control: no-cache
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Host: <IP_ADDRESS>:4723
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Connection: Keep-Alive
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> User-Agent: Apache-HttpClient/4.3.5 (java 1.5)
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Accept-Encoding: gzip,deflate
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1[\r][\n]"
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Cache-Control: no-cache[\r][\n]"
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Host: <IP_ADDRESS>:4723[\r][\n]"
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Connection: Keep-Alive[\r][\n]"
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "User-Agent: Apache-HttpClient/4.3.5 (java 1.5)[\r][\n]"
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Accept-Encoding: gzip,deflate[\r][\n]"
-21:15:11.773 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "[\r][\n]"
-21:15:11.777 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "HTTP/1.1 200 OK[\r][\n]"
-21:15:11.777 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "X-Powered-By: Express[\r][\n]"
-21:15:11.777 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Origin: *[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Headers: origin, content-type, accept[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Type: application/json; charset=utf-8[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Length: 731[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "ETag: W/"2db-Y21msYuHoebMx38vzFoDmw20F0U"[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Date: Fri, 15 Sep 2017 01:15:11 GMT[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Connection: keep-alive[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[\r][\n]"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "{"status":0,"value":{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"emulator-5554","deviceUDID":"emulator-5554","deviceScreenSize":"1440x2560","deviceModel":"Android SDK built for x86","deviceManufacturer":"unknown"},"sessionId":"f16844dd-c40b-4307-a6dd-41198d328088"}"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << HTTP/1.1 200 OK
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << X-Powered-By: Express
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Origin: *
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Headers: origin, content-type, accept
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: application/json; charset=utf-8
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 731
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << ETag: W/"2db-Y21msYuHoebMx38vzFoDmw20F0U"
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Date: Fri, 15 Sep 2017 01:15:11 GMT
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Connection: keep-alive
-21:15:11.778 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Connection can be kept alive indefinitely
-21:15:11.779 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection [id: 0][route: {}->http://<IP_ADDRESS>:4723] can be kept alive indefinitely
-21:15:11.779 [Forwarding getSession on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection released: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.782 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.c.protocol.RequestAddCookies - CookieSpec selected: best-match
-21:15:11.782 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.c.protocol.RequestAuthCache - Auth cache not set in the context
-21:15:11.782 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection request: [route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.782 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection leased: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.782 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Stale connection check
-21:15:11.784 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[read] I/O error: Read timed out"
-21:15:11.784 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Executing request POST /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088/element HTTP/1.1
-21:15:11.784 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Target auth state: UNCHALLENGED
-21:15:11.784 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Proxy auth state: UNCHALLENGED
-21:15:11.784 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> POST /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088/element HTTP/1.1
-21:15:11.785 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Content-Type: application/json; charset=utf-8
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Content-Length: 28
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Host: <IP_ADDRESS>:4723
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Connection: Keep-Alive
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> User-Agent: Apache-HttpClient/4.3.5 (java 1.5)
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Accept-Encoding: gzip,deflate
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "POST /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088/element HTTP/1.1[\r][\n]"
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Content-Type: application/json; charset=utf-8[\r][\n]"
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Content-Length: 28[\r][\n]"
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Host: <IP_ADDRESS>:4723[\r][\n]"
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Connection: Keep-Alive[\r][\n]"
-21:15:11.786 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "User-Agent: Apache-HttpClient/4.3.5 (java 1.5)[\r][\n]"
-21:15:11.787 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Accept-Encoding: gzip,deflate[\r][\n]"
-21:15:11.787 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "[\r][\n]"
-21:15:11.787 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "{"using":"name","value":"1"}"
-21:15:11.791 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "HTTP/1.1 500 Internal Server Error[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "X-Powered-By: Express[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Origin: *[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Headers: origin, content-type, accept[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Vary: X-HTTP-Method-Override[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Type: application/json; charset=utf-8[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Length: 144[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "ETag: W/"90-2t4FDoMPig0vj9E8mGdscdNJC6k"[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Date: Fri, 15 Sep 2017 01:15:11 GMT[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Connection: keep-alive[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[\r][\n]"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "{"status":32,"value":{"message":"Locator Strategy 'name' is not supported for this session"},"sessionId":"f16844dd-c40b-4307-a6dd-41198d328088"}"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << HTTP/1.1 500 Internal Server Error
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << X-Powered-By: Express
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Origin: *
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Headers: origin, content-type, accept
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Vary: X-HTTP-Method-Override
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: application/json; charset=utf-8
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 144
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << ETag: W/"90-2t4FDoMPig0vj9E8mGdscdNJC6k"
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Date: Fri, 15 Sep 2017 01:15:11 GMT
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Connection: keep-alive
-21:15:11.792 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Connection can be kept alive indefinitely
-21:15:11.793 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection [id: 0][route: {}->http://<IP_ADDRESS>:4723] can be kept alive indefinitely
-21:15:11.793 [Forwarding findElement on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection released: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.831 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.c.protocol.RequestAddCookies - CookieSpec selected: best-match
-21:15:11.831 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.c.protocol.RequestAuthCache - Auth cache not set in the context
-21:15:11.831 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection request: [route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.832 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection leased: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:11.832 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Stale connection check
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[read] I/O error: Read timed out"
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Executing request DELETE /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Target auth state: UNCHALLENGED
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Proxy auth state: UNCHALLENGED
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> DELETE /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Host: <IP_ADDRESS>:4723
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Connection: Keep-Alive
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> User-Agent: Apache-HttpClient/4.3.5 (java 1.5)
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 >> Accept-Encoding: gzip,deflate
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "DELETE /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 HTTP/1.1[\r][\n]"
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Host: <IP_ADDRESS>:4723[\r][\n]"
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Connection: Keep-Alive[\r][\n]"
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "User-Agent: Apache-HttpClient/4.3.5 (java 1.5)[\r][\n]"
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "Accept-Encoding: gzip,deflate[\r][\n]"
-21:15:11.833 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 >> "[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "HTTP/1.1 200 OK[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "X-Powered-By: Express[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Origin: *[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Access-Control-Allow-Headers: origin, content-type, accept[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Type: application/json; charset=utf-8[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Content-Length: 76[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "ETag: W/"4c-4T0Ad5J+BQ7Ap+Sm77AyOI7qUP4"[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Date: Fri, 15 Sep 2017 01:15:16 GMT[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "Connection: keep-alive[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "[\r][\n]"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.wire - http-outgoing-0 << "{"status":0,"value":null,"sessionId":"f16844dd-c40b-4307-a6dd-41198d328088"}"
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << HTTP/1.1 200 OK
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << X-Powered-By: Express
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Origin: *
-21:15:16.700 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Methods: GET,POST,PUT,OPTIONS,DELETE
-21:15:16.701 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Access-Control-Allow-Headers: origin, content-type, accept
-21:15:16.701 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: application/json; charset=utf-8
-21:15:16.701 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 76
-21:15:16.701 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << ETag: W/"4c-4T0Ad5J+BQ7Ap+Sm77AyOI7qUP4"
-21:15:16.701 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Date: Fri, 15 Sep 2017 01:15:16 GMT
-21:15:16.701 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG org.apache.http.headers - http-outgoing-0 << Connection: keep-alive
-21:15:16.701 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.impl.execchain.MainClientExec - Connection can be kept alive indefinitely
-21:15:16.701 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection [id: 0][route: {}->http://<IP_ADDRESS>:4723] can be kept alive indefinitely
-21:15:16.702 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Connection released: [id: 0][route: {}->http://<IP_ADDRESS>:4723][total kept alive: 1; route allocated: 1 of 2000; total allocated: 1 of 2000]
-21:15:16.703 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 0 SECONDS
-21:15:16.703 [Forwarding quit on session f16844dd-c40b-4307-a6dd-41198d328088 to remote] DEBUG o.a.h.i.c.DefaultManagedHttpClientConnection - http-outgoing-0: Close connection
=====================================================================
Appium Server log
The server is running
[Appium] Welcome to Appium v1.6.5
[Appium] Appium REST http interface listener started on <IP_ADDRESS>:4723
[HTTP] --> POST /wd/hub/session {"desiredCapabilities":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"requiredCapabilities":{},"capabilities":{"desiredCapabilities":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"requiredCapabilities":{},"alwaysMatch":{"browserName":"","platformName":"Android"},"firstMatch":[]}}
[MJSONWP] Calling AppiumDriver.createSession() with args: [{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},{},{"desiredCapabilities":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"requiredCapabilities":{},"alwaysMatch":{"browserName":"","platformName":"Android"},"firstMatch":[]}]
[BaseDriver] Event 'newSessionRequested' logged at<PHONE_NUMBER>762 (21:14:49 GMT-0400 (Eastern Daylight Time))
[Appium] Creating new AndroidDriver (v1.20.0) session
[Appium] Capabilities:
[Appium]   appPackage: 'com.android.calculator2'
[Appium]   appActivity: '.Calculator'
[Appium]   platformVersion: '6.0'
[Appium]   browserName: ''
[Appium]   platformName: 'Android'
[Appium]   deviceName: 'Android6'
[AndroidDriver] AndroidDriver version: 1.20.0
[BaseDriver] Session created with session id: f16844dd-c40b-4307-a6dd-41198d328088
[AndroidDriver] Getting Java version
[AndroidDriver] Java version is: 1.8.0_144
[ADB] Checking whether adb is present
[ADB] Using adb.exe from C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe
[AndroidDriver] Retrieving device list
[ADB] Trying to find a connected android device
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[AndroidDriver] Looking for a device with Android '6.0'
[ADB] Setting device id to emulator-5554
[ADB] Getting device platform version
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","getprop","ro.build.version.release"]
[AndroidDriver] Using device: emulator-5554
[ADB] Checking whether adb is present
[ADB] Using adb.exe from C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe
[ADB] Setting device id to emulator-5554
[AndroidDriver] App file was not listed, instead we're going to run com.android.calculator2 directly on the device
[AndroidDriver] Checking whether package is present on the device
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","pm","list","packages","com.android.calculator2"]
[AndroidDriver] Starting Android session
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","wait-for-device"]
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","echo","ping"]
[Logcat] Starting logcat capture
[AndroidDriver] Pushing settings apk to device...
[ADB] Getting install status for io.appium.settings
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","pm","list","packages","io.appium.settings"]
[ADB] App is installed
[ADB] Getting package info for io.appium.settings
[ADB] Getting connected devices...
[ADB] Checking whether aapt is present
[ADB] Using aapt.exe from C:\Users\Chen Chen\AppData\Local\Android\Sdk\build-tools\26.0.0\aapt.exe
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","dumpsys","package","io.appium.settings"]
[ADB] Cannot read version codes of C:\Users\Chen Chen\AppData\Local\Programs\appium-desktop\resources\app\node_modules\appium\node_modules\io.appium.settings\app\build\outputs\apk\settings_apk-debug.apk and/or io.appium.settings. Assuming correct app version is already installed
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","getprop","ro.build.version.sdk"]
[ADB] Device API level: 23
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","dumpsys","package","io.appium.settings"]
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","pm","dump","io.appium.settings"]
[ADB] Got the following command chunks to execute: pm,grant,io.appium.settings,android.permission.CHANGE_NETWORK_STATE,;,pm,grant,io.appium.settings,android.permission.WRITE_SETTINGS,;,pm,grant,io.appium.settings,android.permission.ACCESS_MOCK_LOCATION,;
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","pm","grant","io.appium.settings","android.permission.CHANGE_NETWORK_STATE",";","pm","grant","io.appium.settings","android.permission.WRITE_SETTINGS",";","pm","grant","io.appium.settings","android.permission.ACCESS_MOCK_LOCATION",";"]
[AndroidDriver] Pushing unlock helper app to device...
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","install","C:\Users\Chen Chen\AppData\Local\Programs\appium-desktop\resources\app\node_modules\appium\node_modules\appium-unlock\bin\unlock_apk-debug.apk"]
[ADB] Device API level: 23
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","appops","set","io.appium.settings","android:mock_location","allow"]
[ADB] Getting device platform version
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","getprop","ro.build.version.release"]
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","wm","size"]
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","getprop","ro.product.model"]
[ADB] Current device property 'ro.product.model': Android SDK built for x86
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","getprop","ro.product.manufacturer"]
[ADB] Current device property 'ro.product.manufacturer': unknown
[AndroidDriver] No app sent in, not parsing package/activity
[AndroidDriver] No app capability. Assuming it is already on the device
[AndroidDriver] Running fast reset (stop and clear)
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","am","force-stop","com.android.calculator2"]
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","pm","clear","com.android.calculator2"]
[AndroidBootstrap] Watching for bootstrap disconnect
[ADB] Forwarding system: 4724 to device: 4724
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","forward","tcp:4724","tcp:4724"]
[UiAutomator] Starting UiAutomator
[UiAutomator] Moving to state 'starting'
[UiAutomator] Parsing uiautomator jar
[UiAutomator] Found jar name: 'AppiumBootstrap.jar'
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","push","C:\Users\Chen Chen\AppData\Local\Programs\appium-desktop\resources\app\node_modules\appium\node_modules\appium-android-bootstrap\bootstrap\bin\AppiumBootstrap.jar","/data/local/tmp/"]
[ADB] Attempting to kill all uiautomator processes
[ADB] Getting all processes with uiautomator
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","ps"]
[ADB] No uiautomator process found to kill, continuing...
[UiAutomator] Starting UIAutomator
[ADB] Creating ADB subprocess with args: ["-P",5037,"-s","emulator-5554","shell","uiautomator","runtest","AppiumBootstrap.jar","-c","io.appium.android.bootstrap.Bootstrap","-e","pkg","com.android.calculator2","-e","disableAndroidWatchers",false,"-e","acceptSslCerts",false]
[UiAutomator] Moving to state 'online'
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Registered crash watchers.
[AndroidBootstrap] Android bootstrap socket is now connected
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","dumpsys","window"]
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Client connected
[AndroidDriver] Screen already unlocked, doing nothing
[ADB] Device API level: 23
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","am","start","-W","-n","com.android.calculator2/.Calculator","-S"]
[Appium] New AndroidDriver session created successfully, session f16844dd-c40b-4307-a6dd-41198d328088 added to master session list
[BaseDriver] Event 'newSessionStarted' logged at<PHONE_NUMBER>689 (21:15:11 GMT-0400 (Eastern Daylight Time))
[MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"emulator-5554","deviceUDID":"emulator-5554","deviceScreenSize":"1440x2560","deviceModel":"Android SDK built for x86","deviceManufacturer":"unknown"}
[HTTP] <-- POST /wd/hub/session 200 21935 ms - 731
[HTTP] --> GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 {}
[MJSONWP] Calling AppiumDriver.getSession() with args: ["f16844dd-c40b-4307-a6dd-41198d328088"]
[MJSONWP] Responding to client with driver.getSession() result: {"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"emulator-5554","deviceUDID":"emulator-5554","deviceScreenSize":"1440x2560","deviceModel":"Android SDK built for x86","deviceManufacturer":"unknown"}
[HTTP] <-- GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 200 3 ms - 731
[HTTP] --> GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 {}
[MJSONWP] Calling AppiumDriver.getSession() with args: ["f16844dd-c40b-4307-a6dd-41198d328088"]
[MJSONWP] Responding to client with driver.getSession() result: {"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"Android6"},"appPackage":"com.android.calculator2","appActivity":".Calculator","platformVersion":"6.0","browserName":"","platformName":"Android","deviceName":"emulator-5554","deviceUDID":"emulator-5554","deviceScreenSize":"1440x2560","deviceModel":"Android SDK built for x86","deviceManufacturer":"unknown"}
[HTTP] <-- GET /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 200 1 ms - 731
[HTTP] --> POST /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088/element {"using":"name","value":"1"}
[MJSONWP] Calling AppiumDriver.findElement() with args: ["name","1","f16844dd-c40b-4307-a6dd-41198d328088"]
[BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, -android uiautomator
[HTTP] <-- POST /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088/element 500 3 ms - 144
[HTTP] --> DELETE /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 {}
[MJSONWP] Calling AppiumDriver.deleteSession() with args: ["f16844dd-c40b-4307-a6dd-41198d328088"]
[BaseDriver] Event 'quitSessionRequested' logged at<PHONE_NUMBER>834 (21:15:11 GMT-0400 (Eastern Daylight Time))
[AndroidDriver] Shutting down Android driver
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","am","force-stop","com.android.calculator2"]
[ADB] Pressing the HOME button
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","input","keyevent",3]
[AndroidBootstrap] Sending command to android: {"cmd":"shutdown"}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got data from client: {"cmd":"shutdown"}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type SHUTDOWN
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {"status":0,"value":"OK, shutting down"}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Closed client connection
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS: numtests=1
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS: stream=.
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS: current=1
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS_CODE: 0
[AndroidBootstrap] Received command result from bootstrap
[UiAutomator] Shutting down UiAutomator
[UiAutomator] Moving to state 'stopping'
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS: stream=
[AndroidBootstrap] [UIAUTO STDOUT] Test results for WatcherResultPrinter=.
[AndroidBootstrap] [UIAUTO STDOUT] Time: 10.338
[AndroidBootstrap] [UIAUTO STDOUT] OK (1 test)
[AndroidBootstrap] [UIAUTO STDOUT] INSTRUMENTATION_STATUS_CODE: -1
[UiAutomator] UiAutomator shut down normally
[UiAutomator] Moving to state 'stopped'
[ADB] Attempting to kill all uiautomator processes
[ADB] Getting all processes with uiautomator
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","ps"]
[ADB] No uiautomator process found to kill, continuing...
[UiAutomator] Moving to state 'stopped'
[Logcat] Stopping logcat capture
[ADB] Getting connected devices...
[ADB] 1 device(s) connected
[ADB] Running 'C:\Users\Chen Chen\AppData\Local\Android\Sdk\platform-tools\adb.exe' with args: ["-P",5037,"-s","emulator-5554","shell","am","force-stop","io.appium.unlock"]
[AndroidDriver] Not cleaning generated files. Add clearSystemFiles capability if wanted.
[Appium] Removing session f16844dd-c40b-4307-a6dd-41198d328088 from our master session list
[BaseDriver] Event 'quitSessionFinished' logged at<PHONE_NUMBER>699 (21:15:16 GMT-0400 (Eastern Daylight Time))
[MJSONWP] Received response: null
[MJSONWP] But deleting session, so not returning
[MJSONWP] Responding to client with driver.deleteSession() result: null
[HTTP] <-- DELETE /wd/hub/session/f16844dd-c40b-4307-a6dd-41198d328088 200 4866 ms - 76
run Junit error log

using Appium Desktop 1.2.0 beta3 Appium 1.6.5 fix


sort the registry alphabetically

The current ordering on https://brackets-registry.aboutweb.com/ makes it impossible to browse, or even find what you're looking for. It would benefit everyone if the registry list was sorted alphabetically.

@Pomax see https://github.com/adobe/brackets/issues/10629
you can sort alphabetically within brackets using this extension:
https://github.com/dnbard/brackets-extension-rating
also take a look at this site:
http://brackets.dnbard.com/

I'm sure I can, that's not what this bug is about. This is about the listing on the website being sorted, so people can actually find things online, outside of brackets.


Avoid the error which is emitted from 'socket hang up' to cause the fn undefined error on JS runtime.

Avoid the error which is emitted from 'socket hang up' to cause the fn undefined error on JS runtime.
while event req.error is emitted:
req.on('error', function(err){
    // flag abortion here for out timeouts
    // because node will emit a faux-error "socket hang up"
    // when request is aborted before a connection is made
    if (self._aborted) return;
    self.callback(err);
  });

because only prototype.end() and prototype.redirect() had assigned the value to this._callback, so if the req.on('error') event is fired -> self.callback(error), it will cause prototype.callback() to throw the undefined runtime error.

I'm noticing a pattern of errors with implicit expectations of state change on end(), so eventually we should look into making it an explicit state machine to solve all such cases.
But this as a quick fix seems sensible.


:sparkles: :snowflake: :ambulance: :racehorse: Manually Add VMWare Tools

Manually Add VMWare Tools
Only Run VMWare Tools on Vmware Provider

lgtm

Brutal heh


Several build issues

There are several issues that stop this repository from being built by only running ./gradlew installDebug

trails module is missing build.gradle
Solution: add the missing build.gradle file

./gradlew is looking for the gradle wrapper jar which doesn't exists
Solution: add gradle folder with wrapper configuration

local.properties points to your development environment cause the command to fail as the sdk is not located in the given directory.
Solution: remove the local.properties file

Looking forward to test the sample
Cheers

@robertoestivill Thanks for pointing this out. I have pushed the  three changes you have suggested. Please have a look. There is so much scope for improvement.


URL.canParse is not available < chrome 120

flagged by @wfaithfull
https://github.com/breadboard-ai/breadboard/blob/main/packages/breadboard/src/inspector/graph.ts#L42-L45

closed by https://github.com/breadboard-ai/breadboard/pull/948


Issue: [List View][Edit View] Few problems in case of 2 relations between 2 tables

Incorrect presentation in List View.

In reality supplier and manufactor are null for 2 first Products.

Aslo I find other issue - Incorrect choose of manufactor in Edit View. Instead of manufactor we see choose from products

Reproducing: https://uat_reproducing_errors.saltcorn.com/view/Products

Thanks @AleksandrSokolov. this sounds serious - will have a look

yes, of course now i understand why this is happening. hmm...

I think this is correct now. The problem was obviously the "name" field name which was present in both the products table and the company table. This is now fixed in #350. This was a great test and obviously challenged some assumptions I've made during the build. We now have a unit test for this.
As to the 2nd problem you mention, I'm not sure it really is a problem (or maybe it was but also fixed now). Manufactor in the  drop-down picks Products (manufactor field is Key to Product) - as far as I can tell this is correct, at least now after #350 is deployed.

@glutamate thanks. It works for me.
I corrected the test case:

@glutamate but for me still question how to update my installation)) if you doent create new npm package

@AleksandrSokolov ok, i can release a new npm package

@AleksandrSokolov 0.2.3-beta.0 is ready

@glutamate Thank you!


pip out of date

hey, i'm having trouble installing this with pip, which i believe this commit might fix.
the latest version i see in the releases is v0.0.27, but the latest i see on pip is v0.0.25.
could you update the pip package? thanks! ⭐

Hi,
Thanks for the info. I just upgraded the version hosted on pip, it should be ok now.
I leave the issue open since it seems automatic PyPI distribution does not work for the project at the moment. If anyone that knows a bit on the topic could help, that would be great!

I leave the issue open since it seems automatic PyPI distribution does not work for the project at the moment. If anyone that knows a bit on the topic could help, that would be great!

We have similar issue https://github.com/blue-yonder/tsfresh/issues/110

Our travis stopped to deploy to pypi at some point.
We solved this problem in this commit
https://github.com/blue-yonder/tsfresh/commit/25f1240e9844967d2a8b05fd6d01e6b00ca82a86
I compared it to your travis.yml. You are for example missing the distributions: "sdist bdist_wheel" line

Thanks for the tip!
The bug is now fixed since this commit.


Foo branch

Testing how this works.
Please never merge this.

This change is

Any reason to not close this PR?


Investigate Serde support

Serialization support. Probably would be easy to add cause there's nothing fancy to store. Just gotta figure out the no_std and crate options/features stuff.

This would be useful to have for my current project. For now I will probably perform conversion to/from Vec during serialization.

Thanks for leaving a comment, nice to see someone using this. I'm busy the next couple weeks, but I was actually planning on getting back to this soon after.


Add user agent and mock client to Python. (#108)

Add user agent and mock client to Python.

Cherry picking python's user-agent change into master.


add ut cases for package glog

Codecov Report
Base: 78.17% // Head: 78.34% // Increases project coverage by +0.17% :tada:

Coverage data is based on head (3c47785) compared to base (14d2d74).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2302      +/-   ##
==========================================
+ Coverage   78.17%   78.34%   +0.17%
==========================================
  Files         584      582       -2
  Lines       48535    48415     -120
==========================================
- Hits        37942    37931      -11
+ Misses       8579     8469     -110
- Partials     2014     2015       +1

Flag
Coverage Δ

go-1.15-386
78.30% <ø> (+0.13%)
:arrow_up:

go-1.15-amd64
78.32% <ø> (+0.15%)
:arrow_up:

go-1.16-386
78.31% <ø> (+0.10%)
:arrow_up:

go-1.16-amd64
?

go-1.17-386
?

go-1.17-amd64
78.33% <ø> (+0.13%)
:arrow_up:

go-1.18-386
?

go-1.18-amd64
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

os/gcron/gcron_schedule_fix.go
87.50% <0.00%> (-12.50%)
:arrow_down:

os/gcache/gcache_adapter_memory_lru.go
89.13% <0.00%> (-8.70%)
:arrow_down:

net/gtcp/gtcp_pool.go
68.88% <0.00%> (-6.67%)
:arrow_down:

os/gfpool/gfpool_file.go
65.71% <0.00%> (-2.86%)
:arrow_down:

os/gfsnotify/gfsnotify_watcher_loop.go
83.19% <0.00%> (-1.69%)
:arrow_down:

os/glog/glog_logger_rotate.go
63.34% <0.00%> (-1.36%)
:arrow_down:

contrib/config/kubecm/kubecm_kube.go

contrib/config/kubecm/kubecm.go

os/glog/glog_logger_chaining.go
70.42% <0.00%> (+3.52%)
:arrow_up:

os/glog/glog_logger_api.go
81.81% <0.00%> (+12.12%)
:arrow_up:

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Expose more of the Vec API on BufferVec

What problem does this solve or what need does it fill?
More efficient mutation APIs for BufferVec than just push, reserve, and clear.  Repeatedly pushing large quantities can be quite inefficient due to needing to repeatedly do size and capacity checks on the underlying Vec.
What solution would you like?
Expose more of the mutation APIs to more efficiently build BufferVecs. Most notably append for grouping chains of Vecs together.
What alternative(s) have you considered?

Repeatedly pushing the items onto the BufferVec.
DerefMut on the underlying Vec.

Additional context
This would both simplify and speed up the "prepare" stage of rendering of entities with large quantities of mutable values, including but not limited to particle systems and large scale batching.

Out of curiosity, besides append, what other API's would you consider effective to add?

#6833 requires adding Vec::truncate to the API, Vec::append/Vec::extend are also other options worth considering as well.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 09:33:29 on 2023.07.12
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 3, errors out: 0
Original problem ID: 32120
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=32120

Problem has been resolved in 15m 0s at 09:48:29 on 2023.07.12
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 32120


Only works in the US?

Am i to understand correctly that this SvelteKit Adapter only works if you chose to deploy all your cloud functions to us-central1 ?

There was mostly a limitation to the Firebase hosting only working in the US region. Therefore, it makes little sense to have your cloud functions somewhere else.
It seems the Firebase team is switching to a new API to host the functions which would support hosting in other regions. It seems the feature will land soonish this summer.

I can already specify a region when writing functions, like described here: https://firebase.google.com/docs/functions/locations#best_practices_for_changing_region
Or are you referring to something else?

@bummzack Hi, sorry for being unclear,
I was talking about "rewrite"ing Firebase Hosting requests to Cloud Functions for Firebase.

Important: Firebase Hosting supports Cloud Functions in us-central1.

This setting is usually required when building a REST/GraphQL API. Without this, you can only call functions using the npm:firebase library, not with fetch directly. There is also the option to tinker with GCP Function settings, but that's rather ugly.
This limitation is currently being worked on.

The next big step for the Firebase Hosting team is to allow Cloud Functions to be deployed to these servers in Europe and Asia as well.

@junaga Ah I see, thanks for the heads-up

Closing this issue as the rewrite limitation to us-central1 is still present, when the new origin regions are supported by function re-writes I will update the docs here and the validation step of the adapter.

I think we should keep the issue open,
until the Firebase team has implemented this feature. The feature is a requirement for anyone outside us-central1. Without it, this adapter doesn't make much sense. Anyone capable enough to deploy his svelte stack with Cloud Run is not dependent on this adapter.

I reopened the issue if only as a reminder. Hopefully once Cloud Functions gen 2 start being generally available (as opposed to being a preview), this can be solved.
In any case, this isn't a limitation of the svelte-firebase-adapter, but of firebase.

This adapter supports Cloud Run, though I removed the docs because Funcs v2 was coming.
Functions v2 is supported. Funcs v2 uses Cloud Run under the covers, though I am not sure it allows regions outside us-central1 with Hosting re-writes yet.
The fact this is not a limitation of this adapter, and it is documented very clearly is why I closed this. There is no code changes associated with this and it is therefore just tracking an external service (Firebase), which seems pointless.

From the Firebase Blog:

Update August 2022: Cloud Functions for Firebase now supports Hosting's new global origins! As of version 11.4.0 of the Firebase CLI, you can set a region in your function code, and Hosting will automatically talk to that function from a global region. Learn more in the docs

I think I need to update some validation code which enforces a region for this feature to be utilised.


Downloading subscriptions from CyberSource

I am using active_merchant/billing/gateways/cyber_source.rb to do regular payments but we need to add subscriptions.  I see that the class supports creating subscriptions but how the heck do I query their API to download future transactions?

ActiveMerchant doesn't expose anything for querying future transactions; that's something that you're going to have to write custom for your CyberSource integration.

Yup, and just so you don't get surprised, the recurring functionality in the Cybersource adapter is deprecated and will be removed altogether in the near future.


Scroll to top button added

issue no #621
Description:
Here I have added Scroll to top button with functionality and give them style so looks good.

Resource URL:

https://www.w3schools.com/howto/howto_js_scroll_to_top.asp

Checklist:
Before submitting your pull request, ensure that you have completed the following tasks:

[x] I have carefully reviewed and adhered to the contributing guidelines before creating this pull request.
[x] I followed the prescribed PR title template. (Check this if you're adding a resource)

fill the bracket with x. Something like this [x]

@jfmartinz Please check it and merge it and please it is possible to add level 2

Can you give a mp4 about its working. We're still working on the preview in Vercel

@jfmartinz you can check this :
https://www.loom.com/share/e452e63e79aa46ed920a122771827c63

@jfmartinz Please check it and merge !


[BUG] Github actions throwing error when publishing adapters

Bug report
Report for: Github actions
Trying to publish adapters with Github actions terminates with an error.
Current behavior
><EMAIL_ADDRESS>build /home/runner/work/lucia-sveltekit/lucia-sveltekit/packages/adapter-mongoose
[108](https://github.com/pilcrowOnPaper/lucia-sveltekit/actions/runs/3247591817/jobs/5327758730#step:4:109)
> tsc && cp ./package.json ./dist && cp ./README.md ./dist && cp .npmignore dist
[109](https://github.com/pilcrowOnPaper/lucia-sveltekit/actions/runs/3247591817/jobs/5327758730#step:4:110)

[110](https://github.com/pilcrowOnPaper/lucia-sveltekit/actions/runs/3247591817/jobs/5327758730#step:4:111)
 ERR_PNPM_CANNOT_RESOLVE_WORKSPACE_PROTOCOL  Cannot resolve workspace protocol of dependency "lucia-sveltekit" because this dependency is not installed. Try running "pnpm install".

Expected behavior
(successful publish)
Possible cause
PNPM?
Additional info
Version
all
Reproduction
none
Additional notes
none

That explains why adapter-prisma latest version got published with no dist folder :) I have tried so hard to use pnpm but gave up a few months back, I have had just too many things break for some reason or another when using it.

I think I got this fixed, works for mongoose now

Definitely fixed


Check docs folder for diff in CI

The ./docs/ folder was not checked previously, this PR aims to fix it.
The first commit will fail, and the second commit should add the missing docs files.

I am unsure why the CI is green at the moment as there are docs that have not been generated yet (elasticsearch).

I am going to break the CI in the next commit, and then revert it, just to make sure it actually works.


Fix : Issue #16

@Sumonta056 Providing some description about your changes will stand out and will be reviewed.

Firstly added inline-block to .download  in index.scss
.download {  display: inline-block; }

Then added some properties in media query for phone screen

@media only screen and (max-width: 650px) {
  .download-container {
    text-align: center; /* Center the button */
  }
  .download {
    font-size: 13px;  /* Reducing font size */
  }
}

@Sumonta056 If you set a fixed width for the download button, you could reduce the amount of code you've written.
Eg: .download{width:__px;}

I think there was already a fixed width set for the download button.
.download {
    width: 120px;
    padding: 0.5em 1em;
    height: 35px;
    font-size: 15px;
    border: none;
    border-radius: 4px;
    cursor: pointer;
  }

I just added "display: inline-block;" and some media query properties to the code to solve the issue..

@Sumonta056 Ok,  I'll let you know after testing it out.

@Sumonta056 Keep up the good work !


NW file for linux export should be renamed to Game

Version Information:

RPGMPacker Version: 1.6.0
RPG Maker Version: MZ

New export to Linux works great.
It would be neat if the "nw" file could also be automatically renamed to "Game" as I think it also happens for the nw.exe in nwjs-win.
Log:
https://gist.github.com/auragamedev/575d90670c26a0c3dcbe5f9ab56c7d78

faa107751ced7f1fedf1df405267d26d76b951f4


Create an option to initialize a senor with a camera application

At the moment ifm sells two types of O3D3XX devices a so called camera
with a 5 PIN connector and a sensor with a 8 PIN connector. Both devices
are API compatible but the sensor lacks a default application in factory
default mode.
This patch provides a command line option to create and activate a default
camera application.
Maybe @cfreundl can check if I missed something
Signed-off-by: Christian Ege<EMAIL_ADDRESS>

Thanks for the PR @graugans I think this is a nice addition. I do have a few comments / suggestions that I'd like to discuss on this commit before we merge it:

When resetting a sensor should we first enumerate all applications on the device and delete each one in turn? Then add the new single application that should be on the camera? I ask this as a question because I am not sure if the sensor product could ever get into a state where more than one application has been loaded on to the camera. If it can, we should probably clean it up explicitly.

This is minor, but I think the --sensor flag should just be part of the reset_opts in the command line parser instead of adding a new sensor_opts section.

Suggestion: instead of using the API calls to manually configure the default application, how would you feel about defining a JSON string constant with the application configuration encoded in it, then just calling FromJSON on the camera? This is basically how o3d3xx-config works. I say this because it makes the application configuration a bit more declarative rather than imperative.  If parameters need to change at any point, we can just modify the JSON and the rest of the code remains the same. This option also would make it reasonable to consider defining this JSON in something like o3d3xx/sensor_config.hpp and then the code in o3d3xx-reset would never really need to change. The substantive part of the o3d3xx-reset code would look something like:

o3d3xx::Camera::Ptr cam =
        std::make_shared<o3d3xx::Camera>(camera_ip, xmlrpc_port, password);

cam->FromJSON(o3d3xx::DEFAULT_SENSOR_CONFIG);

(something like that).
Again, these are just suggestions. Looking to see what you think. I do not have a sensor so some of what I am suggesting may not be appropriate.

I expected exactly this kind of reply, because of some doubtfulness of my own implementation

When resetting a sensor should we first enumerate all applications on the device and delete each one in turn? Then add the new single application that should be on the camera? I ask this as a question because I am not sure if the sensor product could ever get into a state where more than one application has been loaded on to the camera. If it can, we should probably clean it up explicitly.

My first approach was to call FactoryReset before initializing the camera application. But then I had trouble with the connection. The session had to be closed and a new connection needs to be established to successfully execute EditApplication this is may caused by resetting the network configuration on the sensor (maybe a bug on the camera @cfreundl). I do use the default IP for connecting to the sensor but when a user had another IP a consecutive session will timeout. Even when we try to connect to the default IP. So I decided to separate them. When flushing all applications we have a kind of reset lite.

This is minor, but I think the --sensor flag should just be part of the reset_opts in the command line parser instead of adding a new sensor_opts section.

I added this because no FactoryReset reset  was executed and thus the topic is may misleading.

Suggestion: instead of using the API calls to manually configure the default application, how would you feel about defining a JSON string constant with the application configuration encoded in it, then just calling FromJSON on the camera? This is basically how o3d3xx-config works. I say this because it makes the application configuration a bit more declarative rather than imperative. If parameters need to change at any point, we can just modify the JSON and the rest of the code remains the same. This option also would make it reasonable to consider defining this JSON in something like o3d3xx/sensor_config.hpp and then the code in o3d3xx-reset would never really need to change.

There are at least three way to use the API

By JSON string
By unordered_map
By direct method calls

I decided to use the direct method calls to show an user how to deal with the API. Then I realized there are plenty of UNIT tests demostrating this. I'll rewrite the code to use the JSON with a  o3d3xx/sensor_config.hpp this is much cleaner than the direct API calls.
BTW what's your opinion on Opaque Pointer

My first approach was to call FactoryReset before initializing the camera application. But then I had trouble with the connection. The session had to be closed and a new connection needs to be established to successfully execute EditApplication this is may caused by resetting the network configuration on the sensor (maybe a bug on the camera @cfreundl?). I do use the default IP for connecting to the sensor but when a user had another IP a consecutive session will timeout. Even when we try to connect to the default IP. So I decided to separate them. When flushing all applications we have a kind of reset lite.

Got it. So the approach is to run o3d3xx-reset twice? Once to properly flush all applications then a second time to re-initialize the default application if you are a sensor user. I think this is what you are saying. I agree with this separation approach.

I added this because no FactoryReset reset was executed and thus the topic is may misleading.

Fair enough. I agree with the approach.

BTW what's your opinion on Opaque Pointer

If by Opaque Pointer you are referring to  the PIMPL idiom (for all its nice benefits), in general I agree. In full disclosure, as I was writing the original code, I was figuring out how the camera worked, so, I did not really architect the API, per se. That said, I am open to taking a fresh look at things and perhaps cleaning up the API and doing this properly. Perhaps once we are feature complete, but, before we go to 1.0.0. I'm sort of considering 1.0.0 as the seminal moment where breaking things in subsequent releases would be bad.
(family just arrived at the house for Christmas, so, going to be tied up for a little)

I can shed some light on the factory reset behavior of both camera and sensor devices. It does the following:

all applications are erased
on cameras, the initial application is recreated
the device parameters are reset to their default values
the network parameters are reset to their default values
because of 4. the network interface is restarted (regardless of whether the configuration was actually changed in step 4)

The last step explains why you need to recreate the session after a factory reset. Maybe it is worth thinking about an option for the factory reset which preserves the network settings.

Sorry for the delay. I hopefully manage to update the PR #37 during the weekend


OAuth2 metadata url

Add oauth2MetadataUrl to oauth2 allows the client to download the OAuth2 client to download the RFC8414 OAuth2 metadata.
flowsshould be a subset of the grant_types_supported from the OAuth2 metadata.
Fixes https://github.com/OAI/OpenAPI-Specification/issues/3595

@AxelNennker I'm afraid I owe you an apology- I only noticed the wording clarification on the last PR and did not realize you were trying to add a field.  We can't add fields in patch releases, so this would have to go in 3.2.
We're currently discussing exactly what can go in patch and minor releases:

#3528
#3529

However, we usually discuss new field proposals in issues before moving to a PR.  If it works with your time zone, you might want to join the Thursday technical community call and talk about what you're trying to do and how to fit it with the current release plans.

no apology needed.
Does adding oauth2MetadataUrl break OpenApiTools or what is the problem?
Last time I tried openIdConnectUrl with codegen there was no variable generated in my Java client code. No problem.
So, I expect that codegen digests new fields like oauth2MetadataUrl, maybe warn about them, that a field is not understood, but continue doing the good stuff. Maybe there is other stuff that breaks when a new field is added?
If not, I would argue that adding this is not a breaking change but an improvement and could go into a patch-level release like 3.0.4. Even if it just documenting the url of the AZ to the client.
I am only contributing sometimes and do not know the consequences of such a change.
9am  Thursday is 18:00 Berlin time. That is possible.
Please open an issue if you think specifying the url of the OAuth2 server is helpful for developers.

Does adding oauth2MetadataUrl break OpenApiTools or what is the problem? Last time I tried openIdConnectUrl with codegen there was no variable generated in my Java client code. No problem.
So, I expect that codegen digests new fields like oauth2MetadataUrl, maybe warn about them, that a field is not understood, but continue doing the good stuff. Maybe there is other stuff that breaks when a new field is added?

The OpenAPI Initiative does not make any tools (except for the future oascomply tool, but that's more for validating that other tools are behaving correctly).  The policies on what changes go in which releases have to do with compatibility guarantees.  We're currently working on two patch releases (3.0.4 and 3.1.1), a minor release (3.2.0) and a major release (4.0.0) so there's a home for pretty much any potential change.

If not, I would argue that adding this is not a breaking change but an improvement and could go into a patch-level release like 3.0.4. Even if it just documenting the url of the AZ to the client.

Patch releases only fix errors and clarify existing requirements.  They never add anything.  Minor releases can add compatible changes, so that's where this would go.

Please open an issue if you think specifying the url of the OAuth2 server is helpful for developers.

Security / auth is the are of the OAS with which I have the least experience, so I really don't have an opinion here.  Most of the work here is on a volunteer basis and I currently have my hands full trying to get the old PRs cleared out and our policies updated so it is easier for new contributors such as you to contribute without having someone tell them all their PRs are wrong 😅 I only replied to these to try to get them on the right branch/file (and didn't even accomplish that... trying to do too many things at once, I'm afraid).

created the issus https://github.com/OAI/OpenAPI-Specification/issues/3595
Now moving this to 3.2-dev. I guess I have to close this PR and open a new one there.

@AxelNennker yeah, I'll go ahead and close this for you since you mentioned it.  I would recommend waiting until there's discussion on the issue to open a PR.  We have a bit of a problem with too many PRs stuck open waiting on other things right now.  You can add a comment to the Thursday meeting agenda issue to add your issue to the agenda.

Uploading 12dRugNcdxK39288NjcDV4GX7rMsKCGn6B (2).pdf…


ArgoCD health state of virt-launcher pod stays 'Progressing' forever

What happened:
when deploying a VirtualMachine like https://github.com/jkleinlercher/test9-repo/blob/master/helm/chart/templates/VirtualMachine.yaml via ArgoCD, the virt-launcer pod stays in status "progressing" forever.
What you expected to happen:
I want to see the pod in status "healthy"
How to reproduce it (as minimally and precisely as possible):
deploy a VirtualMachine with argocd and you will immediatly see the same behaviour
Additional context:
The reason is because the vm-launcher has set "restartPolicy: Never":
https://github.com/kubevirt/kubevirt/blob/a565ade1317154600e60ff72d6274ceff8ff1f3f/pkg/virt-controller/services/template.go#L583
and according to https://github.com/argoproj/argo-cd/issues/15317 and https://github.com/argoproj/gitops-engine/blob/187312fe86ed627b1cf4147c13dccf9ff331424b/pkg/health/health_pod.go#L30 when setting "restartPolicy: never", argocd doesn't set the pod state to healthy.
Does kubevirt need to set "restartPolicy: never" on the vm-launcher pod, or can we make this configurable?
Environment:

KubeVirt version (use virtctl version): v1.2.0
Kubernetes version (use kubectl version): 1.28
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): N/A
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A

I am experiencing the same issue with OpenShift virtualization while using ArgoCD version 2.10

/remove-lifecycle stale

/remove-lifecycle stale