-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Something's not right with cargo login/token migration to ~/.cargo/credentials
(regression in nightly)
#4199
Comments
carols10cents
changed the title
Something's not right with cargo login/token migration to
Something's not right with cargo login/token migration to Jun 21, 2017
~/.cargo/credentials
~/.cargo/credentials
(regression in nightly)
cc @dethoter, mind taking a look? |
Sure, already looking into it. |
It's my fault. The problem is in fn load_credentials(&self, cfg: &mut ConfigValue) -> CargoResult<()> {
...
registry.merge(value).chain_err(|| {
|
bors
added a commit
that referenced
this issue
Jun 21, 2017
Fix an incorrect merge of credentials. Add a new test for that. Fix for #4199.
Just tested with cargo master (hasn't made it into the cargo shipped with nightly yet) and can confirm this is fixed! Thank you! ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think this is related to the changes in #3978.
I'm currently using cargo 0.21.0-nightly (50b1c24 2017-06-17).
What happened:
I got an "unauthorized API access" error.
I noticed I now have
~/.cargo/config
and~/.cargo/credentials
.~/.cargo/config
:~/.cargo/credentials
:So it looks like
cargo login
is now only updating~/.cargo/credentials
butcargo publish
is reading from~/.cargo/config
?This has not made it to beta yet.
The text was updated successfully, but these errors were encountered: