-
Notifications
You must be signed in to change notification settings - Fork 1.6k
parsing go.mod: unexpected module path "golang.org/x/lint" #804
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
Comments
I just realized that pinning protobuf fixed the build step, but in the lint step the problem again appeared but this is probably related to golint itself, not protobuf, sorry. |
grpc upgrade to 1.19.0 and pinning protobuf stuff to 1.2.0 helped, so there is maybe an issue here with the latest release dependencies. |
As of #808, |
@dsnet Thank you for doing that! Are you planning on making a new semver tag, so that |
Same here. |
Done. |
The v1.3.0 has some dependency on a broken version of github.com/golang/lint, and I need this update so that my test_planner module can use v1.3.1 too. Bug referenced here: golang/protobuf#804 (comment) I ran the generate.sh script with this change, and it worked fine with no changes. Change-Id: Ib4b08d0d784228b2ad66901f6072ee8f92562554 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/1553108 Tested-by: Sean Abraham <[email protected]> Trybot-Ready: Sean Abraham <[email protected]> Reviewed-by: Andrew Lamb <[email protected]> Commit-Queue: Sean Abraham <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
What version of protobuf and what language are you using?
Version: (e.g.,
v1.1.0
,89a0c16f
, etc)go 1.12, protobuf 1.3.0
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good with
.proto
and.go
source code.What did you expect to see?
Fetching requirements properly.
What did you see instead?
Can't fetch requrements.
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment?
After I pinned protobuf to version 1.2.0, the pipeline worked again.
go get github.com/golang/protobuf/{[email protected],[email protected]}
The text was updated successfully, but these errors were encountered: