Closed fmauch closed 1 year ago
Base: 51.21% // Head: 51.23% // Increases project coverage by +0.01%
:tada:
Coverage data is based on head (
03a4c68
) compared to base (1d9b975
). Patch coverage: 0.00% of modified lines in pull request are covered.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Apparently, if we connect to the socket right after it became available, it can happen, that we don't get a "connected" message from the dashboard server in a second.
I tested this with a retry timeout of 1ms here. Then, when launching the dashboard_client before starting URSim made the client trying to connect each millisecond. I read the
Connected: Universal Robots Dashboard Server
message roughly 1.5 seconds after the lastFailed to connect to robot on IP...
output. This seems to be the minimum time we need to wait for the bootup message after the socket has been opened (at least on my machine with URSim).Therefore, I set the timeout for the initial
read
call to 10 seconds and added a retry mechanism to that. I don't think this should happen which is why I added a warning output.