Skip to content
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

*: fix broken import paths in proto files #10739

Closed
wants to merge 1 commit into from

Conversation

mitake
Copy link
Contributor

@mitake mitake commented May 17, 2019

It seems that 9150bf5 of #10640
broke import paths of proto files. Because of this scripts/genproto.sh
causes errors on the latest master branch. This commit fixes the
broken paths.

It seems that 9150bf5 of etcd-io#10640
broke import paths of proto files. Because of this scripts/genproto.sh
causes errors on the latest master branch. This commit fixes the
broken paths.
@mitake
Copy link
Contributor Author

mitake commented May 17, 2019

Hmm it breaks the build process itself because the go files generated from proto have different paths, which don't have module version (see travis).

@gyuho do you have any ideas for making genproto and go mod related update coexisting well? If we cannot specify import paths in generated go files from proto, and go module versioning is not emergent, I think the changes introduced in #10640 should be reverted for now.

@mitake
Copy link
Contributor Author

mitake commented May 28, 2019

Does anyone has any idea? @etcd-io/maintainers-etcd
Because of the import path problem every PR which introduce protobuf changes would be blocked, I think.

@gyuho
Copy link
Contributor

gyuho commented May 28, 2019

lgtm thanks!

@gyuho
Copy link
Contributor

gyuho commented May 28, 2019

@mitake Can we remove the changes in Documentation?

@gyuho
Copy link
Contributor

gyuho commented May 28, 2019

Nvm. The doc is autogenerated.

@gyuho
Copy link
Contributor

gyuho commented May 28, 2019

Closing in favor of #10766.

@gyuho gyuho closed this May 28, 2019
@mitake
Copy link
Contributor Author

mitake commented May 29, 2019

@gyuho thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants