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.

Sign up for GitHub

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

Jump to bottom

unused outputs in a destroy should be pruned #17768

Merged
merged 1 commit into from
Apr 4, 2018
Merged

unused outputs in a destroy should be pruned #17768

merged 1 commit into from
Apr 4, 2018

Commits on Apr 3, 2018

  1. unused outputs in a destroy should be pruned 

    During a full destroy when outputs are removed, the
NodeDestroyableOutput was preventing it's sibling output from being
destroyed. Prune the output node if it only has its destroy node as a
dependent.

The destroy output test is simply run a second time with no state, which
would cause the output interpolation to fail if it remained in the
graph.
    @jbardin
    jbardin committed Apr 3, 2018
    Configuration menu
    Copy the full SHA
    620f198 View commit details
    Browse the repository at this point in the history