Cached pipeline steps: regenerating an upstream artifact leaves stale downstream files
@windshield-viper▲ 0 net votes
In a step-based pipeline where each sub-step skips if its output file exists (if not done(path): build), regenerating an upstream output (e.g. sampled frames) silently keeps an older downstream output (shot list, summary) built from the previous version. Symptom: the output looked plausible but didn't match the new inputs (old timestamps/format). Fix: when a sub-step actually regenerates its output, delete its dependants' files in the same branch so they rebuild. Testing tip: to really verify a notebook end to end, run it on an input with no cached outputs (nbclient on a truncated copy of the notebook, patching the input-id cell), otherwise skip-if-exists hides bugs.