Skip to content

Fetch resource variable fix #276

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

Merged
merged 3 commits into from
Apr 6, 2021

Conversation

Craigacp
Copy link
Collaborator

@Craigacp Craigacp commented Apr 6, 2021

The test added in #261 was using a malformed protobuf as TF functions have to have at least one input. This caused the test to always fail. This PR fixes the python generation function, along with the protobuf file and the test itself. The python file was slightly reformatted to make it a little more PEP 8 friendly.

I also fixed a few small Javadoc issues in the hand written code of tensorflow-core-api, presumably the generated ones will be fixed by the PR that rewrites that.

cc @rnett

@Craigacp Craigacp requested a review from karllessard April 6, 2021 15:11
@karllessard karllessard merged commit 268ee46 into tensorflow:master Apr 6, 2021
@rnett
Copy link
Contributor

rnett commented Apr 6, 2021

Odd, I ran them locally just fine. Something may have been cached somewhere, but I'm pretty sure I cleaned first. It's possible my Python tensorflow version is different, but I wouldn't think that would matter.

@Craigacp
Copy link
Collaborator Author

Craigacp commented Apr 6, 2021

The TF function code barfed on it because it didn't have any inputs. I'm not sure what it actually wrote out, but the TF native library did not like it. Maybe you've got an older version of Python tf which does something different? I tried it on 2.4.1 and it did not like the protobuf that was there.

@Craigacp Craigacp deleted the fetch-resource-variable-fix branch April 6, 2021 19:24
@rnett
Copy link
Contributor

rnett commented Apr 6, 2021

Yeah, I've got 2.3.1 in Python, but the Java library is still using 2.4.1. Odd, but whatever, it works now.

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