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

add node to container instead of changing output node of container #478

Merged
merged 2 commits into from
Jul 14, 2021

Conversation

janjagusch
Copy link
Contributor

Hi!

In #463 I added a bug (sorry about that!) by changing that output node of the container. This is a really bad idea and can lead to strange side effects where this node will remain a container output, even after adding more nodes that use it as input.

Generally I believe it's much safer to use the container.add_node function instead, which is what I'm doing in this PR.

Signed-off-by: Jan-Benedikt Jagusch <jan.jagusch@gmail.com>
@janjagusch janjagusch force-pushed the fix-custom-post-transform-nodes-3 branch from c1fbebc to aab08a2 Compare July 2, 2021 14:32
Signed-off-by: Jan-Benedikt Jagusch <jan.jagusch@gmail.com>
@janjagusch janjagusch force-pushed the fix-custom-post-transform-nodes-3 branch from 8195092 to 178370c Compare July 2, 2021 14:46
@janjagusch
Copy link
Contributor Author

@xadupre thanks for approving! could you also merge it, please? 🙂

@xadupre xadupre merged commit f295db6 into onnx:master Jul 14, 2021
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.

2 participants