Skip to content
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

[Feature Request] Remote JupyterLab support #215

Open
shurensha opened this issue Jul 24, 2024 · 6 comments
Open

[Feature Request] Remote JupyterLab support #215

shurensha opened this issue Jul 24, 2024 · 6 comments
Labels
enhancement New feature or request

Comments

@shurensha
Copy link

Can you please add support for remote jupyter lab server? so the only inputs are the url and port? Thank you very much

@shurensha shurensha added the enhancement New feature or request label Jul 24, 2024
@benlubas
Copy link
Owner

Checkout remote-hosts.

You can create a lua function that takes the url and port, writes a connection file to /tmp/whatever and then runs :MoltenInit /tmp/whatever

Or I'd be open to a PR that adds something similar. I just don't currently have a good way to test this

@shurensha
Copy link
Author

i hope we can hide the kernels and instead rely on jupyter lab to manage the kernels

@benlubas
Copy link
Owner

If you want jupyter lab to manage the kernel then you have to start the kernel from jupyter lab (afaik). And still read remote-hosts so that you can connect.

@opqrstuvcut
Copy link

@shurensha
This fork might be helpful (although it sometimes behaves buggy):
https://github.com/opqrstuvcut/molten-nvim/tree/feature/add_jupyterapi_runtime

You can connect to a kernel started with the jupyter lab command as follows:
:MoltenInit http://localhost:8888

@benlubas
Copy link
Owner

benlubas commented Aug 8, 2024

@opqrstuvcut definitely open a PR, would be happy to add this functionality.

What's the buggy behavior currently?

@opqrstuvcut
Copy link

@benlubas
Thank you for your interest.

The bugs are as follows:

  • Sometimes, the "Kernel xxx is ready" message does not appear unless some code is executed after running MoltenInit.
  • If you execute MoltenEvaluateCell immediately after running MoltenInit, the standard output may not display correctly (however, if you wait some time and then run MoltenEvaluateCell, it works as expected).

I plan to submit a PR once these issues are fixed, but since they don't cause significant problems for personal use, addressing these bugs has been postponed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants