dvc queue logs -f could take more then one job_id
Open
Nobody has claimed this yet.
feature request
p2-medium
- Dominant language
- Python
- Stars
- 15.9k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Similar to "dvc exp run --run-all", which follows the log of all running jobs.
so maybe as simple as:
dvc queue logs -f 107f918,a6ca492
or maybe as options to follow "all running"
dvc queue logs -f all
Contributor guide
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.
Research direction
Start by reading the existing dvc queue logs -f command and compare its behavior with dvc exp run --run-all, as described in the issue. Clarify whether completion means accepting multiple comma-separated job IDs, following all running jobs, or both; add coverage for the chosen behavior and verify that logs for the requested jobs are followed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100