Make triggers less susceptible to false positives #480
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
cc @AlexAxthelm. In #478, we decided to detect dependencies from triggers: for example,
g()
may not be part of the command, but we should at least check and process it before we attemptx
. The problem with this approach is that it is oversensitive to changes tog()
. Clearly, if we changeg()
tofunction(){FALSE}
,x
should not build. But under #478, it does build because thedepend
trigger is still activated. And we don't want to usetrigger(depend = FALSE)
because we still want to react to changes tof()
.The solution in this PR is to ignore changes to dependencies that only show up in the triggers. Implementation details:
"ignore_changes"
igraph
attribute inbuild_drake_graph()
to keep track of these trigger-only dependencies.dependency_hash()
andfile_dependency_hash()
, exclude everything listed in"ignore_changes"
.The implementation admittedly added a little complexity to the code base, and it was not my most elegant work. However, it is consistent with the existing internals and design patterns.
Related GitHub issues and pull requests
Checklist
drake
's code of conduct, and I agree to follow its rules.testthat
unit tests totests/testthat
to confirm that any new features or functionality work correctly.devtools::check()