create epic for launching a jupyter ws kernel

[rgbkrk]

This sets up a kernel launching epic that launches kernels on jupyter hosts.

🎉 Connections to remote kernels, ready for desktop, play, and the nteract web app. Connecting this up to Desktop is not a focus for this PR, nor is the UI/config for doing so. The first target is the jupyter extension.

TODO:

• Match semantics of the zeromq kernel launch
• Adapt either the jupyter extension or rx-jupyter to adapt the URL based on location.origin as necessary
• Integrate into the jupyter extension app
• Tests

[rgbkrk]

One thing that rx-jupyter doesn't do that it probably should -- if it's not passed the full URL for the endpoint it should construct the full URL (especially for the websockets) using location.origin and the baseURI. Another slight annoyance is the different names we have for some of the same bits:

• baseUrl - our current jupyter extension base URI (e.g. /user/fvzhyd)
• serverUrl - what we've set up for host records
• serverConfig.endpoint || serverConfig.url same thing in rx-jupyter, which is used as the full base URL https://hub.example.org/user/fvzhyd yet can also function as the pure base path on a localhost server /user/fvzhyd but not in all cases (notably websockets)

Thoughts @theengineear? We mostly just need consistency among these while being able to straddle localhost (HTTP) and remote authenticated servers on HTTPS.

[rgbkrk]

Notes from the jupyter notebook server as to why the jupyter extension used baseURL -- the server itself uses baseURL for that base URI.

[theengineear]

@rgbkrk

if it's not passed the full URL for the endpoint it should construct the full URL

Is there any reason for us not to required that users of the lib just pass in the full URL, else we just bail in rx-jupyter?

[rgbkrk]

Is there any reason for us not to required that users of the lib just pass in the full URL, else we just bail in rx-jupyter?

I think that's a good standard.

[rgbkrk]

Rebased this one to stay up to date, going to town on finishing it off now.

[rgbkrk]

The way I'm running this right now (since we don't have the contents API and SET_NOTEBOOK integrations setup) is firing off this action with the redux devtools:

{
  type: 'LAUNCH_KERNEL_BY_NAME',
  kernelSpecName: 'python3',
  cwd: '/'
}

[rgbkrk]

💥

[rgbkrk]

This now also sets the kernel into the app record. Execution works as does autocomplete. 😄

[rgbkrk]

[theengineear]

🎉

[lock]

Howdy! I'm 🔓🤖!

In order to keep information timely (based on the most recent release), we want all activity to be added to either new issues or open issues and PRs. In service to that goal, I, the lock bot close inactive closed issues when they haven't had activity in 120 days.

Feel free to open a new issue for related bugs and link to relevant comments from this thread.