exp push/pull: make all the flags in exp show and exp list support pull/push (#7154)

[karajan1001]

wait for #7245

exp push/pull: make all the flags in exp show and exp list support pull/push (#7154)

fix: #7154

1. add all flags (A/--all-commits , -a/--all-branches, --all-tags) in exp show to the exp pull/push
2. add unit and func tests for exp push/pull

• ❗ I have followed the Contributing to DVC checklist.

• 📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

[karajan1001]

Demos for the push

for the pull

[dberenbaum]

Nice work @karajan1001! I have a few questions:

1. Should there be an error if dvc exp push/pull are run without any arguments?

2. When there are no experiments to push, the output doesn't look right:

$ dvc exp push --no-cache myremote
Pushed experiment '[]'to Git remote 'myremote'.

To push cached outputs for this experiment to DVC remote storage,re-run this command without '--no-cache'.

We should recognize that no experiments have actually been pushed and make the output something like No experiments pushed.

3. num only seems to work when combined with --rev. Should it also be able to work from the current commit (like dvc exp show -n 2)?

[karajan1001]

1. Should there be an error if dvc exp push/pull are run without any arguments?

In my opinion, For exp push/pull/remove/gc they are not a frequent cmd and will cause exp status changes, users must explicitly give the exps to be operated on, and should raise error if none arguments are given.

2. When there are no experiments to push, the output doesn't look right:

$ dvc exp push --no-cache myremote
Pushed experiment '[]'to Git remote 'myremote'.

To push cached outputs for this experiment to DVC remote storage,re-run this command without '--no-cache'.

We should recognize that no experiments have actually been pushed and make the output something like No experiments pushed.

Yeah.

3. num only seems to work when combined with --rev. Should it also be able to work from the current commit (like dvc exp show -n 2)?

Yes, it works, dvc exp show -n 2 will show the exps derive from HEAD and HEAD~

[dberenbaum]

In my opinion, For exp push/pull/remove/gc they are not a frequent cmd and will cause exp status changes, users must explicitly give the exps to be operated on, and should raise error if none arguments are given.

👍

We should recognize that no experiments have actually been pushed and make the output something like No experiments pushed.

Yeah.

👍

3. num only seems to work when combined with --rev. Should it also be able to work from the current commit (like dvc exp show -n 2)?

Yes, it works, dvc exp show -n 2 will show the exps derive from HEAD and HEAD~

It works for me in dvc exp show but not in these other commands. For example:

$ dvc exp pull -n 2 myremote
Pulled experiment '[]' from Git remote 'myremote'.
$ dvc exp pull --rev HEAD -n 2 myremote
Pulled experiment '['exp-45e9f']' from Git remote 'myremote'.

[karajan1001]

In my opinion, For exp push/pull/remove/gc they are not a frequent cmd and will cause exp status changes, users must explicitly give the exps to be operated on, and should raise error if none arguments are given.

👍

We should recognize that no experiments have actually been pushed and make the output something like No experiments pushed.

Yeah.

👍

3. num only seems to work when combined with --rev. Should it also be able to work from the current commit (like dvc exp show -n 2)?

Yes, it works, dvc exp show -n 2 will show the exps derive from HEAD and HEAD~

It works for me in dvc exp show but not in these other commands. For example:

$ dvc exp pull -n 2 myremote
Pulled experiment '[]' from Git remote 'myremote'.
$ dvc exp pull --rev HEAD -n 2 myremote
Pulled experiment '['exp-45e9f']' from Git remote 'myremote'.

Excuse me, Are you in the latest version? I had already removed the default HEAD support. And this is the latest result from my computer.

> dvc exp pull -n 2 myremote
ERROR: Either of `experiment`, `--all-commits` or `--rev` needs to be set.
> dvc exp pull --rev HEAD -n 2 origin
Pulled experiment '['exp0.15', 'exp0.25', 'exp0.3', 'exp0.1']' from Git remote 'origin'.
>  dvc exp pull --rev HEAD~~ origin
No experiments to pull.

[dberenbaum]

Sorry, must have been behind. Looks good now! One last thing:

$ dvc exp pull
ERROR: the following arguments are required: <git_remote>, <experiment>

Should <experiment> be included as a required argument?

[karajan1001]

Sorry, must have been behind. Looks good now! One last thing:

$ dvc exp pull
ERROR: the following arguments are required: <git_remote>, <experiment>

Should <experiment> be included as a required argument?

This error comes from argparse I had set made experiment to be * which means it can be 0 to any integer, but looks like argparse can not automatically know it is not required. I tried on my computer, add a default value for the arguments can solve this problem.

[dberenbaum]

add a default value for the arguments can solve this problem

Can the default be None?

[karajan1001]

add a default value for the arguments can solve this problem

Can the default be None?

I had tried several cases on my computer. It works fine for me.

[jorgeorpinel]

UI strings LGTM 👍🏼

[karajan1001]

@pmrowla This one needs to be merged first before #7275.