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

Could not read token file: <path> #55

Closed
Fuco1 opened this issue Aug 30, 2020 · 4 comments
Closed

Could not read token file: <path> #55

Fuco1 opened this issue Aug 30, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@Fuco1
Copy link

Fuco1 commented Aug 30, 2020

I have multiple checkouts of the repository on different paths. It seems this client stores the token path in the repo itself which then creates conflicts between different checkouts.

When I run enableremote on a new computer it will give me

[2020-08-30 20:42:29.579164] git-annex-remote-googledrive[1] --> GETCONFIG token
[2020-08-30 20:42:29.579418] git-annex-remote-googledrive[1] <-- VALUE /media/data-750/data/token.json

but this path does not exist here, the repo is under /home/<user>/data instead and the setup command gave me

Setup complete. An auth token was stored in /home/<user>/data/.git/annex/othertmp/git-annex-remote-googledrive.token. Now run 'git annex initremote' with your desired parameters.

Note that I'm trying to migrate from gcloud using instructions from readme.

How can I configure this to be per-checkout and not a globally shared value.

@Lykos153 Lykos153 added the bug Something isn't working label Aug 31, 2020
@Lykos153
Copy link
Owner

Lykos153 commented Aug 31, 2020

The option token is not intended to be stored permanently at all. However, due to a bug, it was't reset in case of errors (i.e. file not found).

Fixed in v1.2.1

@Fuco1
Copy link
Author

Fuco1 commented Sep 5, 2020

I tried to upgrade with pip3 install --upgrade but it downloaded 1.2.0 version. How can I install this manually?

@Lykos153
Copy link
Owner

Lykos153 commented Sep 5, 2020

Sorry, forgot to update PyPI. Upgrading via pip should work now!

@Fuco1
Copy link
Author

Fuco1 commented Sep 5, 2020

Yes, can confirm it upgrades now. Thanks! The token problem also seems to be fixed for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants