-
Notifications
You must be signed in to change notification settings - Fork 291
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
Google Colab Support #489
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm encountering issues with Binder not being able to pull the successfully built images to the execution hosts. I guess this is related to the images being quite big (~4-5GB due to all the dependencies in conda) and the recent reduction in capacity at Binder (https://blog.jupyter.org/mybinder-org-reducing-capacity-c93ccfc6413f). I hope they find a way to get more capacity in the future because it is a truly great service. Meanwhile, I'm looking for alternatives and Google Colab seems to be the only one. Since they recently added the possibility to switch kernels to their UI (https://twitter.com/GoogleColab/status/1671265645756039168), I thought it might be worth thinking about establishing compatibility of xeus-cling with Google colab.
Installing conda is fairly easy and also getting the xeus-cling kernels to show up works. But when running them the jupyter server seems to be unable to connect (the logs appear to be in reverse order):
This can be reproduced in the following notebook:
https://colab.research.google.com/drive/1aLZVb1WbpZshQ-3-XLL1fxN6I5C6h08w?usp=sharing
I'm not sure how to tackle this at the moment but I think it would be great to establish colab support
The text was updated successfully, but these errors were encountered: