BUG: Weasel DVC command error "run"
Nobody has claimed this yet.
- #90 by @svlandeg — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start with the weasel/cli/dvc.py entry point and reproduce the failure with the reported weasel dvc command and environment. Review linked pull request #90 for prior work, then verify that the command completes and creates the expected dvc.yml for the listed templates.
Written by the indexing model from the issue text.
Description
Hi, I'm quite new to weasel and ran into this basic problem and haven't been able to figure out a way to solve it.
Expected Behaviour
With running weasel dvc I can automatically create and maintain a dvc.yml from my project.yml.
Current Behaviour
When running weasel dvc I get an error message that "run" is an invalid command choice and no dvc.yml is created.
$ weasel dvc
⚠ No workflow specified for DVC pipeline. Using the first workflow
defined in project.yml: 'all'
ERROR: argument command: invalid choice: 'run' (choose from 'add', 'artifacts', 'cache', 'check-ignore', 'checkout', 'commit', 'completion', 'config', 'daemon', 'dag', 'data',
Steps to reproduce
I ran into this issue with both the templates tagger_parser_ud and textcat_demo as well as the tutorial ner_fashion_brands.
Set-up new project
mkdir new_folder && cd new_folderpython -m venv .venvsource .venv/bin/activatepip install weasel && pip install dvcgit init && dvc init
Download and set-up template
6. weasel clone pipelines/tagger_parser_ud
7. cd tagger_parser_ud
8. weasel assets
Set-up weasel from project.yml
9. weasel dvc
Environment
- WSL 2 Ubuntu
- Python 3.10.12
- weasel 0.3.4
- dvc 3.48.1
- git version 2.34.1
Detailed Description
It seems to me like under the hood a dvc run command is triggered, which causes an issue. It already tried to check the code weasel/cli/dvc.py, but couldn't find a run command there or in utils.
- Dominant language
- Python
- Stars
- 93
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from explosion/weasel
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Fix command parsing Openbug
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in explosion/weasel
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100