Notebooks with cached stages via magic can cause conflicting outputs
Open
bug
- Dominant language
- Python
- Stars
- 60
- Forks
- 18
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 38
Description
If we declare an output path from a notebook and also in one of its cells via the stage magic we have a DVC conflict. We should only have the the output paths in one place.
Contributor guide
Research direction
Start by tracing how notebook-declared outputs and outputs declared through the stage magic are collected, then reproduce the conflict described in the issue with a notebook. Done means an output path declared in both places is handled consistently so the project has only one output-path declaration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100