Skip to content
This repository has been archived by the owner on Mar 1, 2022. It is now read-only.

--local runs are broken #649

Closed
alexander-fenster opened this issue Jun 20, 2019 · 3 comments · Fixed by #650
Closed

--local runs are broken #649

alexander-fenster opened this issue Jun 20, 2019 · 3 comments · Fixed by #650
Assignees
Labels

Comments

@alexander-fenster
Copy link
Contributor

After #637, the --local runs don't work since the logic of install_protoc.sh does not work outside of the carefully crafted Docker image. We need to use install_protoc.sh in Docker only, and if it does not exist, not fail but revert to using the protoc installed in the system.

@alexander-fenster
Copy link
Contributor Author

@hzyi-google so since @andreamlin is out, do you think you'll have bandwidth to fix it, or should I just go ahead and do it? We do have folks using --local so they will complain soon I guess.

Also, I don't like the idea that the .sh script is being parsed in Python to extract the version numbers; I'd better refactor the version numbers away from the shell script but it's out of scope of this issue.

@yihanzhen
Copy link
Contributor

yihanzhen commented Jun 20, 2019 via email

@vam-google
Copy link
Contributor

@alexander-fenster I'm wondering why that change was introduced. It looks like older version used by java was the case. Why didn't we just bumped the java protoc and grpc version, instead of doing that change. I would strongly consider reverting the change, as it complicates the system even more

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

Successfully merging a pull request may close this issue.

3 participants