-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
x/pkgsite: searching by smartcontractkit and chainlink does not show github.com/smartcontractkit/chainlink #37801
Comments
Are you sure? There it is: https://pkg.go.dev/github.com/smartcontractkit/chainlink?tab=subdirectories |
OP probably meant the search results: https://pkg.go.dev/search?q=chainlink or https://pkg.go.dev/search?q=smartcontractkit |
Some more info -- in the Versions tab, only 1 entry is shown for smartcontractkit/chainlink: v0.0.0 (425bc20) – Jan 24, 2019 But they released v0.6.0 - v0.6.10 and v0.7.0 - v0.7.6, so nearly 20 releases are missing. Also, libraries imported by them in those missing versions don't have them counted as an importer so those other projects are affected indirectly by this. I didn't notice anything odd about their release version naming convention. |
Oh wow, that was freaky, I was on this page about to cut/paste that error from my command line and your screenshot showed up! 👍 |
Also my comment from #37801 (comment) is inaccurate. This isn't related to fuzzy matching, it is related to searching by subpaths, which we do support. I would have expected these searches to work:
Will investigate. |
There's a fairly active Go project on GitHub that's not found on go.dev so there might be others.
smartcontractkit/chainlink has 6 releases this year, 42 contributors, and 9,372 commits.
Just a hunch: could this be related to the project install using
git clone
instead ofgo get
?What did you expect to see?
smartcontractkit/chainlink existing on go.dev.
What did you see instead?
smartcontractkit/chainlink is not found in go.dev.
The text was updated successfully, but these errors were encountered: