-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
cmd/go: private git repo shows "fatal: could not read Username: terminal prompts disabled" #26145
Comments
What What happens if you attempt to Are you using the credential helper? |
Is that true for both HTTPS and SSH, or just one of the two? |
I happened to encounter a similar error message. It turned out that it's a typo in my import path.
|
Seems I had to run it with HTTPS. After I authed with HTTPS using Imo the bug here is that vgo does not forward the prompt. Edit: by the way even the workaround is not especially intuitive. One might argue "just auth using git and try again", but simply authenticating using git alone will not work around this issue. You first have to configure git to cache your credentials, only then can you first manually auth using git to work around the issue with vgo. Point being that if you know what to do it is relatively easily worked around, but it does not seem like a workflow you'd want to depend on with vgo. |
This is not an issue in vgo but in cmd/go itself (if you run "go get" instead of "vgo get" you should see the same behavior). It's not a new bug either - we've turned off the terminal prompts for quite a few releases. It would be great to have better output here but I don't think it's critical for Go 1.11. To reproduce:
|
That's #25982. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.10.3 linux/amd64 vgo:2018-02-20.1
This is meaningless though as this number is exactly the same when doing a fresh vgo build from master, a bug in itself if you ask me.
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?Arch Linux
What did you do?
Ran
go run foo.go
on a file that relies on a package that is hosted by a private repository. I have full access to the private repository (git clone runs without prompts).What did you expect to see?
Expected foo.go to run without issue
What did you see instead?
Repo names anonymised
Additional Information
I found this relevant issue:
#25590
Tried building vgo with the fix included but no dice, error remains the same.
The text was updated successfully, but these errors were encountered: