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
Stack too deep when subnetworks are involved #993
Comments
albertz
added a commit
that referenced
this issue
Mar 16, 2022
albertz
added a commit
that referenced
this issue
Mar 16, 2022
albertz
added a commit
that referenced
this issue
Mar 16, 2022
albertz
added a commit
that referenced
this issue
Mar 17, 2022
albertz
added a commit
that referenced
this issue
Mar 17, 2022
This was referenced Mar 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With subnetworks, the stack can become quite deep and convoluted (independent of not using flat net construction, #992), like:
See here for a better stack trace: https://gist.github.com/albertz/a1a20710e4d08292e35ba6910ca132e8 (via #1001)
Esp the logic using
wrapped_get_layer
contributes to this.This should be cleaned up.
The text was updated successfully, but these errors were encountered: