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

Indexing Kythe go targets can't resolve imports. #3096

Closed
robinp opened this issue Oct 2, 2018 · 2 comments
Closed

Indexing Kythe go targets can't resolve imports. #3096

robinp opened this issue Oct 2, 2018 · 2 comments
Labels
bug go Issues affecting the Go language indexing Issues pertaining to indexing

Comments

@robinp
Copy link
Contributor

robinp commented Oct 2, 2018

$ ./kythe/extractors/bazel/extract.sh --go "$PWD" .comps
$ bazel-bin/kythe/go/indexer/cmd/go_indexer/go_indexer $(find bazel-out/k8-fastbuild/extra_actions/kythe/go/extractors/cmd/bazel/extra_action/kythe/go/ -name '**.kzip') | bazel-bin/kythe/go/storage/tools/write_entries/write_entries -graphstore /tmp/ky.gs                                                            
2018/10/02 22:59:48 Unable to resolve import path "kythe.io/kythe/go/services/xrefs"                                                                                                             
2018/10/02 22:59:48 Unable to resolve import path "kythe.io/kythe/go/storage/table"                                                                                                             
2018/10/02 22:59:48 Unable to resolve import path "bitbucket.org/creachadair/stringset"
...

Does the extractor work as expected? Or do I miss some mapping? Thank you!

@salguarnieri salguarnieri added bug go Issues affecting the Go language indexing Issues pertaining to indexing labels Oct 5, 2018
@salguarnieri
Copy link
Contributor

That seems like a bug. I was able to reproduce it locally after making some updates to the extract script in #3115.

@robinp
Copy link
Contributor Author

robinp commented Jan 22, 2019

Still reproduces on current head. Do you have a hint what could cause this?

Not sure if related, but it looks like the package names emit defines/binding to an empty package path. Just saying.

Edit: hm, this could actually be a cause, no wonder that the package path was not found then. The question might be why.

Edit: I have a lead on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug go Issues affecting the Go language indexing Issues pertaining to indexing
Projects
None yet
Development

No branches or pull requests

2 participants