We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
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 of go get?
smartcontractkit/chainlink existing on go.dev.
smartcontractkit/chainlink is not found in go.dev.
The text was updated successfully, but these errors were encountered:
Are you sure? There it is: https://pkg.go.dev/github.com/smartcontractkit/chainlink?tab=subdirectories
Sorry, something went wrong.
OP probably meant the search results: https://pkg.go.dev/search?q=chainlink or https://pkg.go.dev/search?q=smartcontractkit
If this issue is about search results, it seems to be related to supporting fuzzy matching in search. See also #37783 and #36806.
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.
I believe this is because the module path they put in their go.mod file is chainlink, not github.com/smartcontractkit/chainlink.
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:
No branches or pull requests