Hang When Client Connects but LabVIEW Shows Exited about g-cli HOT 6 CLOSED

To be fair - this could be the step itself causing LabVIEW to hang - perhaps nothing to worry about

from g-cli.

Even with a longer handover timeout we still see this - it isn't clear what the causality is but it should probably be treated as a separate issue.

from g-cli.

So I think this will all be improved if we can improve the robustness of the socket connection. One being polling with a timeout so we can handle this condition seperate to a disconnect. A timeout on the blocking call causes an exception but not an async call. This will also reduce the message errors on a timeout. See example below:

byte[] data = new byte[4096];
IASyncResult result = stream.BeginRead(data, 0, data.Length, null, null);
result.AsyncWaitHandle.WaitOne();
int bytes = stream.EndRead(result);

if (!result.IsCompleted)

else

...

from g-cli.

If we can still use exceptions (trying to confirm) there is an inner exception which should give more detail for better handling.

from g-cli.

Moving to async doesn't help.

I have confirmed the hang is due to what is being called in LabVIEW - it isn't clear why the process shows as exited though

from g-cli.

Fixed the race condition by setting stop on exit and using while instead. Not clear why. Will address in #55 to see if there is a more reliable method.

from g-cli.