Fix bug with camera control (losing control)

[vnabatov]

currently robot could stuck with camera control command and pilot lose control steps:

1. Send moving command
2. Send Camera command
3. Send stop command ER: robot stops AR: robot continue moving and doesn't react on any commands

[vnabatov]

repeated only with the joystick

probably fixed here https://github.com/spaceshipyard/mars-rover-dispatcher/commit/75949a1aad1f6b666cee3dc16c58bdb719e58c49 need to check on the real robot

[vnabatov]

the issue is still actual, probably related with poor internet connection

[vnabatov]

we need to force socket.io to use the WebSocket, current problem caused by using of longPolling

[chaos-adept]

for information, we have a sandbox for experiments which has certificates - https://github.com/Code-Rush-Experement/electronic-queue

[chaos-adept]

for information, i have tried the electronic-queue, and it works:

I will try to test the same https approach in the dispatcher

[chaos-adept]

I have tried to run the dispatcher on the my laptop, and it works over websocket: engine.io-client:socket socket receive: type "open", data "{"sid":"draL28yzhRwSg-tnAAAB","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":60000}" +1ms

so far it looks that the bug is a problem of the environment rather than the code base.

[vnabatov]

on laptop with mock server runs with the web socket too, very confusing

[chaos-adept]

for your information, the status of messages was implemented in the https://github.com/spaceshipyard/mars-rover-dispatcher/issues/26

[chaos-adept]

on laptop with mock server runs with the web socket too, very confusing

i think that options are following:

• rework control to support big delays (work with long pulling)
• switch connection to the websocket only (it might face an issue within office network)

[chaos-adept]

the workaround for proxy blocking is under progress in #31

[vnabatov]

fixed, tested