Skip to content

proto: Regenerate protobuf files.#2584

Merged
michael-berlin merged 1 commit intovitessio:masterfrom
michael-berlin:fix_up_proto
Feb 23, 2017
Merged

proto: Regenerate protobuf files.#2584
michael-berlin merged 1 commit intovitessio:masterfrom
michael-berlin:fix_up_proto

Conversation

@michael-berlin
Copy link
Copy Markdown
Contributor

This is a follow-up fix for #2495.

We were not able to fix Yipei's workstation such that it would use the
same protobuf generator as Travis and our setups does. Therefore, I'm
re-generating the files separately on my machine.

This is a follow-up fix for vitessio#2495.

We were not able to fix Yipei's workstation such that it would use the
same protobuf generator as Travis and our setups does. Therefore, I'm
re-generating the files separately on my machine.
@alainjobart
Copy link
Copy Markdown
Contributor

Sugu had them in his PR too. Not sure why.

@alainjobart
Copy link
Copy Markdown
Contributor

alainjobart commented Feb 23, 2017

LGTM

Approved with PullApprove

@michael-berlin
Copy link
Copy Markdown
Contributor Author

Yipei and I spent quiet some time on this and could not reproduce it :(

The protoc binary (version 3.0.0, installed with our pinned gRPC installation) is supposed to call the protoc-gen-go binary (pinned by govendor).

The easiest solution for now is to update protoc-gen-go. But it's still worrisome that the pinning doesn't work.

@michael-berlin michael-berlin merged commit 5e6eb88 into vitessio:master Feb 23, 2017
@michael-berlin michael-berlin deleted the fix_up_proto branch February 23, 2017 04:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants