Skip to content
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

Numerous TF warnings when running SAC from source #574

Closed
Antymon opened this issue Nov 21, 2019 · 2 comments
Closed

Numerous TF warnings when running SAC from source #574

Antymon opened this issue Nov 21, 2019 · 2 comments
Labels
duplicate This issue or pull request already exists question Further information is requested

Comments

@Antymon
Copy link

Antymon commented Nov 21, 2019

Describe the bug
When running SAC I get flooded with following warnings (possibly for each layer created):

WARNING:tensorflow:Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7fc4e447c518>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, export AUTOGRAPH_VERBOSITY=10) and attach the full output. Cause: converting <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7fc4e447c518>>: AssertionError: Bad argument number for Name: 3, expecting 4

Are those safe to ignore, or? Why are those appearing on presumably legit code?

System Info
Describe the characteristic of your environment:

  • Describe how the library was installed: source
  • GPU models and configuration: no GPU
  • Python version: 3.6.8
  • Tensorflow version 1.14
  • Versions of any other relevant libraries: Ubuntu 18.04 LTS
@araffin araffin added the question Further information is requested label Nov 21, 2019
@araffin
Copy link
Collaborator

araffin commented Nov 21, 2019

Duplicate of #298

Are those safe to ignore, or? Why are those appearing on presumably legit code?

I remember having those (but I can't remember which setting exactly) but you can normally ignore those.

Again, should be closed by #366 when v3.x is out.

@araffin araffin added the duplicate This issue or pull request already exists label Nov 21, 2019
@araffin
Copy link
Collaborator

araffin commented Nov 28, 2019

Closing this in favor of #298

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants