Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

exp run: Remove unsupported `dvc repro` options from the help text

See original GitHub issue

Bug Report

UPDATE: Jump to https://github.com/iterative/dvc/issues/6791#issuecomment-1043363367

Description

dvc exp run --help lists the following options:

  -s, --single-item     Reproduce only single data item without recursive dependencies check.
  -m, --metrics         Show metrics after reproduction.
  --dry                 Only print the commands that would be executed without actually executing.
  -i, --interactive     Ask for confirmation before reproducing each stage.
  -p, --pipeline        Reproduce the whole pipeline that the specified targets belong to.
  -P, --all-pipelines   Reproduce all pipelines in the repo.
  -R, --recursive       Reproduce all stages in the specified directory.
  --no-run-cache        Execute stage commands even if they have already been run with the same command/dependencies/outputs/etc
                        before.
  --force-downstream    Reproduce all descendants of a changed stage even if their direct dependencies didn't change.
  --no-commit           Don't put files/directories into cache.
  --downstream          Start from the specified stages when reproducing pipelines.
  --pull                Try automatically pulling missing cache for outputs restored from the run-cache.
  --glob                Allows targets containing shell-style wildcards.

Some of them are not supported. I tested a few of them and testing the rest. Could you remove those from the help text? We’re going to update the command reference according to this.

--force: Seems to run
--single-item: I didn’t get what does this do in dvc exp run context
--metrics : ✅
--interactive: ✅
--pipeline: ✅
--all-pipelines: seems to run ✅
--recursive: ✅
--no-run-cache: seems to have no effect ❌
--force-downstream:
--no-commit: seems to have no effect ❌
--downstream:
--pull:
--glob: ❌

Issue Analytics

State:
Created 2 years ago
Reactions:4
Comments:13 (7 by maintainers)

Top GitHub Comments

3reactions

dberenbaumcommented, Feb 17, 2022

All of these commands have been tested here or in https://github.com/iterative/dvc.org/issues/2861. We need to remove --no-run-cache, --no-commit, and --glob (unless someone prefers to address #6457).

cc @pmrowla @karajan1001

1reaction

jorgeorpinelcommented, Dec 9, 2021

–no-commit: seems to have no effect ❌

I unchecked this since the option is still shown and accepted (2.8.1).

Didn’t double check any other ones.

Top Results From Across the Web

exp run | Data Version Control - DVC

Open-source version control system for Data Science and Machine Learning projects. Git-like experience to organize your data, models, and experiments.

DZt - River Thames Conditions - Environment Agency - GOV.UK

When you need help, Az cardinals vs cowboys images, Laser cut screens sydney, Unteres odertal unterkunft, Gel nail designs cute, #Jamoz, Les marais...

command error status unsupported - You.com | The AI Search ...

clang: error: unsupported option '-fopenmp' error: command 'gcc' failed with ... Note that while running these commands, another DVC process was running.

The DataLad Handbook

B.21 Help - Why does Github display my dataset with git-annex as the ... When you run the installer, make sure to select...

HL7 Version 2.5.1 Implementation Guide: Immunization ... - CDC

Immunization Information Systems Support ... be unsupported in this Guide. ... for race (alternate identifier, alternate text, and name of alternate coding ...