Elyra needs to recognize loopback scenario in socket mode

[kevin-bates]

On configurations where the elyra server is also a worker node, socket mode requests will timeout if the kernel lands on the elyra node because it never receives the connection information. This is because the kernel launcher received a reference to an existing file and assumes 'push' mode.

What is really happening is that, in this case, because the assignment landed on the elyra server, the connection information created by default is valid. So because the file is not empty, the launcher will behave as if the connection file mode is 'push' and just use the file its given. In this case, Elyra should break out of its loop waiting for a socket response (assuming its in the RUNNING state) and just continue - since the original file is valid.

[ckadner]

good catch @kevin-bates !

[kevin-bates]

Opened PR #63.

[kevin-bates]

PR #63 has been merged - closing this issue.