-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd ref: document releasing of locks in dvc run
#860
Comments
…oject (instead of downloading) per iterative#859 (review), + remove "s around 'locked` in some docs (related to iterative#860 and iterative#868).
Related to iterative#860
Related to iterative#860
Related to iterative#860
Related to iterative#860
dvc run
dvc run
This comment has been minimized.
This comment has been minimized.
Hi there! @efiop can you confirm the given context is still up to date and/or copy the parts that now affect |
Hello again. Is this the what we're talking about? From iterative/dvc#2584 (comment):
I don't think any user has ever needed to know about this so it sounds like an implementation detail we don't need to document. Please reopen if I'm incorrect. |
I think it's about the user visible behavior - now you could run other DVC commands when |
Hmmm well in general the repo is supposed to be locked during any DVC operation or at least that's implied by https://dvc.org/doc/user-guide/troubleshooting#lock-issue . Is that outdated? We could separately expand on the description of what I started #3251 for this. |
Hi @dberenbaum (me again 🙂 ) do you know if this info. is outdated? Would be great to get clarification from the core team on what needs to be updated here, if anything (otherwise please close this issue). Thanks |
There is a big improvement here for users, because when the user However, I don't see any changes needed here because the docs don't address when the repo will or won't be locked, so I think let's close the issue. If we ever put in an in-depth locking guide, we can revisit. |
Good to know, and sounds good. Thanks |
Context: iterative/dvc#2584
The text was updated successfully, but these errors were encountered: