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
I often run into situations in which rule params or code have been updated, but these updates slip through unnoticed, causing errors downstream. I am aware that I can rerun rules with updated code or parameters, but as that has to be done manually, it does not necessarily help in these situations.
A command line option that always reruns rules with updated code or parameters would solve this problem. For my own work, I don't see a reason why I would ever not use this command line option.
This is different from forcing rerun using the existing --list-params-changes/--list-code-changes. Essentially, it would put code and parameter value changes on the same level as other existing rerun triggers, like outdated output files.
The text was updated successfully, but these errors were encountered:
I often run into situations in which rule params or code have been updated, but these updates slip through unnoticed, causing errors downstream. I am aware that I can rerun rules with updated code or parameters, but as that has to be done manually, it does not necessarily help in these situations.
A command line option that always reruns rules with updated code or parameters would solve this problem. For my own work, I don't see a reason why I would ever not use this command line option.
This is different from forcing rerun using the existing
--list-params-changes
/--list-code-changes
. Essentially, it would put code and parameter value changes on the same level as other existing rerun triggers, like outdated output files.The text was updated successfully, but these errors were encountered: