You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dvc exp push is doing a lot, potentially pushing multiple experiments to Git, a DVC remote, and Studio. The output doesn't always make clear what happened, what was successful, and what failed.
Example 1: When the dvc push fails, the command errors out with no additional info even though the git push succeeded:
$ dvc exp push origin crank-prat
ERROR: unexpected error - [Errno 22] Bad Request: An error occurred (400) when calling the HeadObject operation: Bad Request
We should still show what was pushed to git even if we throw this error.
Example 2: When some experiments have already been pushed and some haven't, the message could better clarify that some of the experiments were already pushed:
$ dvc exp push --no-cache origin handy-puns lardy-vara
Pushed experiment 'lardy-vara' to Git remote 'origin'.
To push cached outputs for this experiment to DVC remote storage,re-run this command without '--no-cache'.
We should include that experiment 'handy-puns' was already pushed to that git remote.
Example 3: When the experiment was previously pushed with --no-cache, pushing again with the cache will take time to upload to the dvc remote but then report nothing was pushed:
$ dvc exp push origin lardy-vara
No experiments to push.
We should include the push output, like "9 files pushed to DVC remote 'storage'."
Example 4: Even when the experiment is successfully pushed, it would help to clarify that it was pushed not only to the Git remote but also to the DVC remote:
dvc exp push
is doing a lot, potentially pushing multiple experiments to Git, a DVC remote, and Studio. The output doesn't always make clear what happened, what was successful, and what failed.Example 1: When the dvc push fails, the command errors out with no additional info even though the git push succeeded:
We should still show what was pushed to git even if we throw this error.
Example 2: When some experiments have already been pushed and some haven't, the message could better clarify that some of the experiments were already pushed:
We should include that experiment 'handy-puns' was already pushed to that git remote.
Example 3: When the experiment was previously pushed with
--no-cache
, pushing again with the cache will take time to upload to the dvc remote but then report nothing was pushed:We should include the push output, like "9 files pushed to DVC remote 'storage'."
Example 4: Even when the experiment is successfully pushed, it would help to clarify that it was pushed not only to the Git remote but also to the DVC remote:
This could use the same kind of output suggested for example 3.
The text was updated successfully, but these errors were encountered: