-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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/vgo: no such file or directory #25674
Comments
@adamjacobmuller the repro you provided doesn't seem like valid shell to me, so I've taken a guess at the following:
At this point we must create a
Notice it will take the import path from Now if we look at the available releases of But then another thing to notice is that the CockroachDB support that you want to rely on has not actually made it to a release yet. So taking these points together (project not converted to be a Go module, major version
At which point we can see how
which gives:
Notice the pseudo-versions being used, pseudo versions that correspond (at the time of writing) to the Finally do a build to check:
I'll close this issue for now therefore because I think your expectation that But if there are any other issues, please feel free to comment back here or open a new issue. |
@myitcv thanks, I was not aware of the Thank you, |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
completed go.mod file
What did you see instead?
found this as part of a much larger project which is not using null imports, but, this reproducer was simpler and demonstrates the issue
The text was updated successfully, but these errors were encountered: