-
Notifications
You must be signed in to change notification settings - Fork 895
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
problem encoutered when test neurd_example.py #18
Comments
Which version of Tensorflow are you using? |
I was following the installation instruction on ubuntu 18.04 and all test has been passed. (venv) hadoop2@hadoop2-OptiPlex-3060:~/open_spiel$ pip list
Package Version
---------------------- ---------
absl-py 0.7.1
astor 0.8.0
cloudpickle 1.2.1
contextlib2 0.5.5
cvxopt 1.2.3
cycler 0.10.0
decorator 4.4.0
dm-sonnet 1.32
gast 0.2.2
google-pasta 0.1.7
grpcio 1.23.0
h5py 2.9.0
ipython 5.8.0
ipython-genutils 0.2.0
Keras-Applications 1.0.8
Keras-Preprocessing 1.1.0
kiwisolver 1.1.0
Markdown 3.1.1
matplotlib 3.1.1
mock 3.0.5
networkx 2.2
numpy 1.17.1
pexpect 4.7.0
pickleshare 0.7.5
pip 19.2.3
pkg-resources 0.0.0
prompt-toolkit 1.0.16
protobuf 3.9.1
ptyprocess 0.6.0
Pygments 2.4.2
pyparsing 2.4.2
python-dateutil 2.8.0
scipy 1.1.0
semantic-version 2.8.1
setuptools 41.2.0
simplegeneric 0.8.1
six 1.12.0
tensorboard 1.14.0
tensorflow 1.14.0
tensorflow-estimator 1.14.0rc1
tensorflow-probability 0.7.0
termcolor 1.1.0
traitlets 4.3.2
wcwidth 0.1.7
Werkzeug 0.15.5
wheel 0.33.6
wrapt 1.11.1 |
No, this is a TensorFlow error that I haven't seen before. |
Alright, I have reproduced the problem on Ubuntu 19.10. This seems to be tensorflow-internal. I will do a few google searches, but I wonder if a newer version of TF would fix it. @dmorrill10 or anyone, do you remember why we needed TF < 1.15.0 in our requirements.txt ? |
@lanctot just to ensure more consistent behavior. In this case, it doesn't matter because 14.0 is the most recent 1.x version. Yeah, I didn't find anything when I quickly searched it, but maybe you'll find something. |
Ok thanks. My current guess is it's related to the Python3 type annotations mixed with tf.function problem mentioned here: tensorflow/tensorflow#28849 (Fixed on Jul 15th, so I assume this will be fixed in TF 2) But it's just a wild guess based on ~10 min of searching. |
This has been recently fixed by #117 |
The text was updated successfully, but these errors were encountered: