Closed lucataglia closed 6 years ago
@lucaRadicalbit Does that refer to a graph saved with a previous version of the API or one both saved and restored with the current master?
@eaplatanios No, I saved the graph with the Python API and then restored the graph the 0.2.0-SNAPSHOT
version. Il the first time I have this problem, with the other version was everything ok.
@lucaRadicalbit Ok. Let me look into this. It's just a matter of changing the default name of the read op.
@lucaRadicalbit Could you please confirm that this has now been fixed? Thanks!
@eaplatanios At the moment I don't know why but in my project I still have your code without the bug fix done in the commit a084e85. I also try to clean the cache and reload everything.
In the commit 8051664 I see that in the
fromProto
method thegraphElement
is taken adding thehandle.op.name
to the/Read/ReadVariable:0
String. But restoring the graph the name in the protobuf is:So I wondering if the
/Read/ReadVariable:0
String shuldn't be/Read/ReadVariableOp:0
String