You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user uses the exclude_dependencies attribute of the exclude block, all ancestor dependencies should be excluded from the run queue in addition to direct dependencies.
The workaround right now is to set the same exclude block on all dependencies in the chain, but it is a more convenient feature to do this automatically. It is also likely what users expect to happen.
Expected behavior
The exclude_dependencies attribute recursively removes ancestral dependencies from the run queue.
Additional context
Avoid working on this until after #3629 . We will likely take advantage of those data structures to implement this behavior.
The text was updated successfully, but these errors were encountered:
Describe the bug
When a user uses the
exclude_dependencies
attribute of theexclude
block, all ancestor dependencies should be excluded from the run queue in addition to direct dependencies.The workaround right now is to set the same
exclude
block on all dependencies in the chain, but it is a more convenient feature to do this automatically. It is also likely what users expect to happen.Expected behavior
The
exclude_dependencies
attribute recursively removes ancestral dependencies from the run queue.Additional context
Avoid working on this until after #3629 . We will likely take advantage of those data structures to implement this behavior.
The text was updated successfully, but these errors were encountered: