-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[cmd/mdatagen] Work around a go-generate issue blocking make generate #10133
Conversation
Does it make sense to do this since we can maybe drop the "_v2" from the file name, now that we are close to make transition to all? |
This actually helps to rename of all the files by running |
I'm ok to keep it as is but that error was too annoying so I wanted to get rid of it |
@bogdandrutu what's your thought on this? Can we merge it? I think it's good to have it to avoid confusing failures that still possibly can arise. I don't see downsides except for the 3 more lines in the generated code. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
4378468
to
f80c75e
Compare
…s builder, running `go generate ./...` ends up with a failure `no such file or directory` even if the `mdatagen` command successfully completed. The root cause of that is in how go generate works. This change adds a workaround for the issue using go build tags.
f80c75e
to
f0f0cb1
Compare
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
If
mdatagen
is causing file renames, e.g. migration to the new metrics builder, runninggo generate ./...
ends up with a failureno such file or directory
even if themdatagen
command successfully completed. The root cause of that is in howgo generate
works, see golang/go#36068. This change adds a workaround for the issue using go build tags.