-
Notifications
You must be signed in to change notification settings - Fork 18
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
use colab-specific auth if detected on colab #64
Comments
See: https://colab.research.google.com/notebooks/bigquery.ipynb
|
Edit: This is only an FYI for internal Googlers, so that they are aware that this feature needs to be tested on colab.research.google.com, not the internal hosted version. I think internal colab is slightly different?
|
@tswast I tested the above steps (#64 (comment)) on colab.corp.google.com. The authentication is successful but the client creation fails. Am I missing something? |
Internal colab is not a priority. Please ignore. |
This issue can be closed after #68 |
Similar to #63, if we detect that we are on a colab environment, we can use the colab auth by default. Note: I think this should ignore the "local webserver" parameter, as colab uses a slightly different kind of flow.
The text was updated successfully, but these errors were encountered: