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

"depth" does not seem to work on any packages other than "depth" #18

Open
iphydf opened this issue Aug 30, 2019 · 8 comments
Open

"depth" does not seem to work on any packages other than "depth" #18

iphydf opened this issue Aug 30, 2019 · 8 comments

Comments

@iphydf
Copy link

iphydf commented Aug 30, 2019

[~] % depth github.com/KyleBanks/conways-gol
'github.com/KyleBanks/conways-gol': FATAL: unable to resolve root package
[~]!% depth github.com/KyleBanks/goggles
'github.com/KyleBanks/goggles': FATAL: unable to resolve root package

It doesn't work on any KyleBanks packages other than "depth" itself, as far as I have tried.

@lgarciaaco
Copy link

I have the same issue

@JFixby
Copy link

JFixby commented Sep 13, 2019

try calling depth . from your project/package root

@ghohmann-asapp
Copy link

I had the same problem, but it worked when it called it from the cmd folder (where main.go is)

@virak-panha
Copy link

#18

@zhangxinyang97
Copy link

zhangxinyang97 commented Aug 26, 2021

have the same issue, and still doesn't work even if I called it from cmd folder

@vikramTungsten
Copy link

vikramTungsten commented Nov 28, 2022

it is only showing the dependencies of main.go,
When I tired with -internal too, and when I am specifying the package name like
depth -internal -max 2 github.com/Dreamacro/clash/config
it is giving me the FATAL: unable to resolve root package issue.

@gaborposz
Copy link

I've downloaded the windows binaries, and I also get this message:

depth_1.2.1_windows_386.exe github.com/KyleBanks/conways-gol
'github.com/KyleBanks/conways-gol': FATAL: unable to resolve root package

I suspected that it has something to do with my proxy settings, but it's the same with disabled proxy as well. :(

@lordofscripts
Copy link

Tried it on my unpublished package root and got the same. I ended up writing my own version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants