I'm having problems pushing files with DVC to DAGsHub.
Workflow:
It sits and waits, barring me from even canceling the operation with Ctrl+C. I'm forced to manually close the terminal, open a new one, ending the "Python" process in task manager and delete the lock file in .dvc/tmp/lock.
Short answer
Do not use ask_password
.
Instead, save your token in the local config by running once:
dvc remote modify origin --local --unset ask_password
dvc remote modify origin --local password <--access token-->
dvc push -r origin
should work then.
Long answer
Git Bash is not running the regular Windows command prompt but an emulated Unix-style bash prompt. From the information in your question, I cannot know for sure, but this is probably causing the msvcrt
package used by DVC to prompt the password on windows machines to fail/hang.
There are potentially 3 ways to deal with the issue:
dvc pull
from the regular Windows cmd prompt.winpty
- I am not 100% positive about how to do this, but not using winpty
seems to be the reason msvcrt
fails at prompting for your password.ask_password
.
Instead, save your token in the local config by running once:
dvc remote modify origin --local --unset ask_password
dvc remote modify origin --local password <--access token-->
You can get your access token by clicking on the question mark beside the DVC
remote of your DAGsHub repository, then click on "Reveal my token".