-
Notifications
You must be signed in to change notification settings - Fork 182
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
Confusing bq_auth() selection choice and output #333
Comments
I have never seen this. The choice you're being asked to make should be clearly labelled, along the lines of this example in the gargle README: #> The gargle package is requesting access to your Google account. Select a
#> pre-authorised account or enter '0' to obtain a new token. Press
#> Esc/Ctrl + C to abort.
#> 1: janedoe_personal@gmail.com
#> 2: janedoe@example.com
#> Selection: 1 But it looks like you've got some pre-existing gcloud config that's part of the story. Are you aware of that and you're trying to use creds stored there? Or were you expecting to do OAuth in the browser? Can you set this option and try again? It should give us much more verbose output.
I'd also appreciate your session info. |
Thanks so much for the quick reply.
Yes, I think that is likely the problem. (Although the missing choice message is still odd.) I have installed the gcloud command line utility, which I use to interact with VMs on Google Compute Engine among other things. Here are the files in my
Separately, I've also previously downloaded an API service key as part of @MarkEdmondson1234's googleComputeEngineR package. However, I don't think that could be causing the problem, since this particular JSON file is not stored in the If it's any help at all, the full details of all of this are contained in my GCE lecture.
Yes, that's what I was expecting although perhaps I should have been more specific given my existing setup? Session info:
|
Sorry, forgot to add the output with
|
Aha! You are supposed to be seeing this question, when confronted with that "yes/ no":
I think I've fixed it. If you're in a position to install gargle from GitHub and check me, that would be awesome. It does not contain any compiled code btw. devtools::install_github("r-lib/gargle") I don't really understand why your indicating |
Super, thanks Jenny. That fixes the missing message problem. I'm still not able to proceed when selecting
Is the idea that gargle will create / look for a regular cache file at Is the solution then simply for gargle to create / search the cache file within the directory? There's already a
|
No, I think those messages are a red herring (and should be silenced). From your output, it looks like we cruise past them and successfully fall through to OAuth. I think the failure to create the cache folder, even though you've said "yes", is a separate problem. I will open two issues for these on gargle. |
I've just upgraded to version 1.2.0. of bigrquery, which uses the new gargle /
bq_auth()
authentication method. However, I struggled to authenticate correctly. Mostly because I kept selecting "Yes" (the normal default with these things) and I would just get an error message. Eventually, I tried selecting "No" on a whim and was taken through the browser authentication process.I can't include standard reprex() output because of the interactive selection. (Apologies if there's a way that I missed.) But here is the output directly from my console.
Selecting "Yes" yields the following error message and some warnings.
Selecting "No" works (I get taken to my browser for authentication), but still presents warning messages.
In summary:
bq_auth()
give the user more detailed instructions than just "Yes" or "No". What exactly are we choosing here?The text was updated successfully, but these errors were encountered: