You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem seems to be an import of a package that doesn't exist, but go get handles it fine, so they probably never had any reason to change it.
The files in question also seem to belong to a sub package that it never imported, so that might be the problem.
vendoring package github.com/onsi/ginkgo
ERROR: multiple package error: found packages tmp (extra_functions_test.go) and subpackage (nested_subpackage_test.go) in /home/ZiRo/Documents/go/src/github.com/onsi/ginkgo/integration/_fixtures/convert_goldmasters
- processing dep github.com/onsi/ginkgo for github.com/onsi/ginkgo [1 / 3]
- processing dep github.com/onsi/B for github.com/onsi/ginkgo [2 / 3]
ERROR: go get github.com/onsi/B failed: go get failed: # cd .; git clone https://github.com/onsi/B /home/ZiRo/Documents/go/src/github.com/onsi/B
Cloning into '/home/ZiRo/Documents/go/src/github.com/onsi/B'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
package github.com/onsi/B: exit status 128
- exit status 1
ERROR: go get failed: # cd .; git clone https://github.com/onsi/B /home/ZiRo/Documents/go/src/github.com/onsi/B
Cloning into '/home/ZiRo/Documents/go/src/github.com/onsi/B'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
package github.com/onsi/B: exit status 128
- exit status 1
The text was updated successfully, but these errors were encountered:
hrm... gx-go import is pretty agressive on making sure it gets every import grabbed. It could use some tweaking to ignore broken packages (or at least print a big error about it and keep going).
The problem seems to be an import of a package that doesn't exist, but go get handles it fine, so they probably never had any reason to change it.
The files in question also seem to belong to a sub package that it never imported, so that might be the problem.
The text was updated successfully, but these errors were encountered: