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

ssh failure when attempting to install cargo-watch #63

Closed
joprice opened this issue Aug 26, 2021 · 6 comments
Closed

ssh failure when attempting to install cargo-watch #63

joprice opened this issue Aug 26, 2021 · 6 comments
Labels
Blocked: upstream Fix or feature is needed to be implemented upstream (in a dependency) Report: bug Something isn't working

Comments

@joprice
Copy link

joprice commented Aug 26, 2021

I get the error below when trying to install cargo-watch:

cargo binstall cargo-watch
11:17:18 [INFO] Installing package: 'cargo-watch'
Error: authentication required but no callback set; class=Ssh (23)

I found this related issue rust-lang/git2-rs#329.

@ryankurte
Copy link
Collaborator

hmm, it shouldn't be using git to install cargo-watch, and seems to work okay from here :-/
could you try with --log-level debug and attach the log as a file here?

@joprice
Copy link
Author

joprice commented Aug 27, 2021

Maybe it has something to do with my local setup.

13:50:38 [INFO] Installing package: 'cargo-watch'
13:50:38 [DEBUG] (1) cargo_binstall::drivers: Updating crates.io index
Error: authentication required but no callback set; class=Ssh (23)

Caused by:
    authentication required but no callback set; class=Ssh (23)

@ryankurte
Copy link
Collaborator

oh interesting, we do use git to fetch the crates.io registry via the crates_index package. i suspect maybe you have some local configuration that is forcing this to attempt to fetch via ssh instead of http?

it would be interesting to know how cargo behaves in comparison, --log-level trace may also be helpful but, tends to be unreasonably verbose.

@ngocketit
Copy link

oh interesting, we do use git to fetch the crates.io registry via the crates_index package. i suspect maybe you have some local configuration that is forcing this to attempt to fetch via ssh instead of http?

This is indeed the cause of the issue for me but shouldn't cargo handle that (e.g, with ssh) as well?

@passcod
Copy link
Member

passcod commented Dec 7, 2021

Upstream issues: frewsxcv/rust-crates-index#37 and rust-lang/git2-rs#600.

There's some suggestion that gitoxide might not have this issue, if that's indeed the case there may be a way forward without waiting on git2-rs (which has some other issues, e.g. failing when the dynlib version bumps, as recently happened)

@passcod passcod added Report: bug Something isn't working Blocked: upstream Fix or feature is needed to be implemented upstream (in a dependency) labels Dec 7, 2021
@somehowchris
Copy link
Contributor

This would be gone crates_index would be removed, right?

@passcod passcod closed this as completed May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked: upstream Fix or feature is needed to be implemented upstream (in a dependency) Report: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants