-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port kernel extension API to web #9585
Comments
Here's the current api:
|
Yup, that's how I've built the powertoys extension. I.e. with the plan we will web-enable that extension as well. |
Would this API enable an extension to provision a remote Jupyter kernel (e.g. within a GitHub Codespace), and then provide the server URL, so that the Jupyter extension could handle the communication between VS Code and Jupyter? |
No, at this stage there's no such plan for this extension to provision Jupyter. I believe something similar is being addressed in the VS Code iteration plan here Explore support for proxy controllers |
@DonJayamanne I believe @lostintangent will be using the proxy controller support, but then as a secondary step, they want to provide us with the URI to connect to. @lostintangent it sounds like you want something like so? export interface IJupyterExtension {
provideServerUri(uri: URI);
} That would be the same as the user picking a remote server in the jupyter extension today? Maybe we could handle that with the current command we already have. In fact a user added that extensibility already: Essentially another extension just executes a command to set a jupyter server URI. So @lostintangent I believe this is already supported. |
Yep, something like what you mentioned should work well! That way, we could register the kernel controllers with VS Code, and when selected, provision the Codespace compute, start up Jupyter on it, and then automate connecting the Jupyter client to it. |
Hasn't been requested by any users, closing this issue for now |
Web extensions will likely need support for the kernel API too
The text was updated successfully, but these errors were encountered: