Repository navigation
Conversation
philpearl
approved these changes
Jun 24, 2020
philpearl
left a comment
Contributor
There was a problem hiding this comment.
Review from random stranger here, which unfortunately won't help this get merged. But yes! yes! yes! Thank-you!
jhseu
approved these changes
Jun 24, 2020
Contributor
|
Needed to change this a bit to match the BUILD rule, which is required for bazel compatibility: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes
#39744
Summary
After running the following in accordance with the installation instructions for go:
The first command generates error message unrelated to this PR, a fix for which is ready to pull. That error message is relatively low impact and should not impact the functionality of the library after the
go generatecommand is run. However, the third command generates the following error:This is caused by a bad import that seemed to be from an accident during a refactor. The problematic import that occurs in several files is:
This line is supposed to point to the generated files, however the generated files are actually placed in
github.com/tensorflow/tensorflow/tensorflow/go/core/core_protos_go_protodue to the following line in several proto files intensorflow/core/protobufread by protoc during generation:The fix is simply to correct the import lines to point to the actual location of the files.