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

Can't initialise connection on Google Colab #440

Closed
rbeucher opened this issue Nov 2, 2024 · 2 comments
Closed

Can't initialise connection on Google Colab #440

rbeucher opened this issue Nov 2, 2024 · 2 comments

Comments

@rbeucher
Copy link

rbeucher commented Nov 2, 2024

Hi,

I am trying to run your examples using Google Colab but the connection fails to initialise.

import sliderule
sliderule.init(url="slideruleearth.io", verbose=True)

returns:

Setting URL to slideruleearth.io
INFO:sliderule.sliderule:Setting URL to slideruleearth.io
Login status to slideruleearth.io/sliderule: failure
INFO:sliderule.sliderule:Login status to slideruleearth.io/sliderule: failure
True
@jpswinski
Copy link
Member

@rbeucher thank you for reporting this issue - we have some work to do to make these messages more user friendly.

The login failure message is saying that you failed to login to the slideruleearth.io/sliderule cluster, which happened because you didn't have an account on our provisioning system for the slideruleearth.io/sliderule cluster. But that is actually okay because the slideruleearth.io/sliderule cluster is a public cluster and therefore most of the APIs (and all of the ones you'd be interested in) do not need credentials to use. The only APIs that failing to login would preclude are the ones related to changing the size of the cluster.

But for a private cluster (for example if you were logging into the University of Texas cluster at slideruleearth.io/ut), then a login failure prevents you from accessing any of the APIs, and the message is much more meaningful.

So these messages are very misleading for the public cluster and need to be changed. Thank you for bringing this to our attention. I'll make this change in the next release and notify you here.

@rbeucher
Copy link
Author

rbeucher commented Nov 2, 2024

Thank you @jpswinski.
I don't have that issue when I run the command on a local install of Jupyter. Why is that?

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

No branches or pull requests

2 participants