What vgo commit did you build from?

What happens if you attempt to go get the same repository with the ordinary go tool?

Are you using the credential helper?

git clone runs without prompts

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.

vgo: resolving import "github.com/PuerkitioBio/goquery"                                               
vgo: import "github.com/PuerkitioBio/goquery": git ls-remote -q https://github.com/PuerkitioBio/goquery in /Users/mura/go/src/mod/cache/vcs/07f08583e403b0b6a20a20e9ad3cfc653e2cdb3124291642a1351c3b33c3a64
8: exit status 128:                                                                                   
        fatal: could not read Username for 'https://github.com': terminal prompts disabled 
           
 ~/w/mops  ⑂ master + ⇡11    git ls-remote -q https://github.com/PuerkitioBio/goquery in /Users/mura/go/src/mod/cache/vcs/07f08583e403b0b6a20a20e9ad3cfc653e2cdb3124291642a1351c3b33c3a648                
Username for 'https://github.com': typeless                                                           
Password for 'https://typeless@github.com':                                                           
remote: Repository not found.                             

Is that true for both HTTPS and SSH, or just one of the two?

Seems I had to run it with HTTPS. After I authed with HTTPS using git then I could run vgo without issue.

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:

$ HOME=/tmp go get github.com/rsc/nonexist
# cd .; git clone https://github.com/rsc/nonexist /Users/rsc/src/github.com/rsc/nonexist
Cloning into '/Users/rsc/src/github.com/rsc/nonexist'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
package github.com/rsc/nonexist: exit status 128
$

It would be great to have better output here

That's #25982.