Skip to content
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

docs: locking-related updates #868

Merged
merged 1 commit into from
Jan 6, 2020
Merged

docs: locking-related updates #868

merged 1 commit into from
Jan 6, 2020

Conversation

efiop
Copy link
Contributor

@efiop efiop commented Dec 16, 2019

Related to #860

Disregard the recommendations below if you use Edit on GitHub button to improve the docs in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.

🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This enables GitHub to link the PR to the corresponding bug and close it automatically when PR is merged.

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

@efiop efiop changed the title document locking in dvc run/repro [WIP] document locking in dvc run/repro Dec 16, 2019
@efiop efiop changed the title [WIP] document locking in dvc run/repro document locking in dvc run/repro Dec 16, 2019
@efiop efiop changed the title document locking in dvc run/repro [WIP] document locking in dvc run/repro Dec 16, 2019
@shcheklein
Copy link
Member

@efiop still WIP?

@efiop
Copy link
Contributor Author

efiop commented Dec 16, 2019

@efiop still WIP?

Yes, I am a bit ashamed of this PR, so made it WIP to take another look 🙂Will give it another look till tomorrow and will address your concerns.

Copy link
Contributor

@jorgeorpinel jorgeorpinel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to previous comments, it would be great if we can link existing instanced of "always locked" phrase in the few docs where these exist. Thanks

jorgeorpinel added a commit to maykulkarni/dvc.org that referenced this pull request Dec 18, 2019
…oject (instead of downloading)

per iterative#859 (review),
+ remove "s around 'locked` in some docs (related to iterative#860 and iterative#868).
@efiop

This comment has been minimized.

@jorgeorpinel

This comment has been minimized.

@efiop efiop force-pushed the 860 branch 2 times, most recently from 28dc9a3 to 5d007cc Compare December 22, 2019 20:16
@efiop efiop changed the title [WIP] document locking in dvc run/repro document locking in dvc run/repro Dec 22, 2019
@efiop
Copy link
Contributor Author

efiop commented Dec 22, 2019

In addition to previous comments, it would be great if we can link existing instanced of "always locked" phrase in the few docs where these exist. Thanks

@jorgeorpinel Not sure what you mean. Could you clarify?

@efiop
Copy link
Contributor Author

efiop commented Dec 22, 2019

Updated this PR a bit. Don't want to make it turn into a long one, so I suppose it is better to stay with the current amount of info to start with. Open to suggestions to improve it and make it mergeable.

@jorgeorpinel
Copy link
Contributor

Open to suggestions to improve it and make it mergeable.

My main general concern here at this point is that basic locking is not explained anywhere, I think. So talking about how locking still allows parallel execution seems like skipping a step 🙂

Please see #868 (review)

@shcheklein
Copy link
Member

shcheklein commented Dec 30, 2019

@jorgeorpinel I think it's a good first step for the "document multiple parallel repros/runs" - that's what this PR is essentially about, not "document locking in dvc run/repro" in general the @efiop named it initially. I think we do describe project lock only in the DVC files and directories? It's not enough, true. But it should be probably a separate PR to write a proper DVC internals section aboutt .dvc/lock and related stuff.

  • @efiop Btw, let's may be change Parallel execution to even more explicit - "Running multiple runs/repros in parallel"? Parallel execution might be an overloaded term and can lead to some confusion. If we keep it it's better to explicitly specify that we don't support in-repro parallelism, for example.

Copy link
Member

@shcheklein shcheklein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Think about making the section name more explicit.
Some clarification in the dvc repro doc can be beneficial.

@efiop
Copy link
Contributor Author

efiop commented Dec 30, 2019

Sorry guys, will get back to this later(hopefully tomorrow). It is in my saved tickets.

Copy link
Contributor

@jorgeorpinel jorgeorpinel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with Ivan's review so approving on my end.

I think we should prioritize #876 as well though – cc @shcheklein

@efiop efiop force-pushed the 860 branch 2 times, most recently from 3861fbb to 1b1c1b2 Compare January 4, 2020 20:19
@efiop efiop changed the title [WIP] document locking in dvc run/repro document locking in dvc run/repro Jan 5, 2020
@efiop
Copy link
Contributor Author

efiop commented Jan 5, 2020

Sorry for the delay. I've updated the docs to separate "running other commands parallel" from "parallel stage execution". Should be more clear now.

@@ -52,6 +52,14 @@ captures data and <abbr>caches</abbr> relevant <abbr>data artifacts</abbr> along
the way. See [this example](/doc/get-started/example-pipeline) to learn more and
try creating a pipeline.

### Running other dvc commands in parallel
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about this ... why do we mention this here and in repro and not in dvc add?

We also def missing any reasonable context about the project lock.

It feels that it can be a general user guide section that describes locking and when and how do we release it. How to find those files, etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shcheklein because dvc add doesn't release repo lock, but repro/run do release it. So for add the section would be running dvc run/repro in parallel which is odd to say the least. Eventually we will release repo lock on checksum computations/copies too, so we will alter the docs accordingly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I guess this behaviour is simply an expected one, hence why so many people were running into it. So it is not worth documenting it here. Will move to user-guide.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, removed that note entirely. Will wait until we do similar things on hash computation/copying/downloading and will then create a locking article, that would be too incomplete to bother with right now.

See
[Running other dvc commands in parallel](/doc/command-reference/run#running-other-dvc-commands-in-parallel).

### Parallel stage execution
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a good one! I'll @jorgeorpinel review specific language nuances, but I hope it will be useful for people. (When we at last have a How to section it can be probably moved there with a link to it from this document - just to keep a sane size)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How to section?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"How to" (name can change) - we have a bunch of tickets already that start like "write a How to **** "

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. OK, I created #899 to determine this.

Copy link
Member

@shcheklein shcheklein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

parallel stage execution is great!

locking looks strange, w/o context - I doubt users would get it - check my comment with some suggestions on how to move forward with it.

@efiop efiop changed the title document locking in dvc run/repro docs: locking-related updates Jan 6, 2020
@efiop
Copy link
Contributor Author

efiop commented Jan 6, 2020

Removed locking explanation entirely for now, will wait until we implement the same thing for hash/copying/downloading and will then create an article about it in the user-guide. If I try to do it now it will be too incomplete.

Now this PR introduces a note about parallel execution to repro cmd reference as well as updates user-guide internal files list doc.

Copy link
Contributor

@jorgeorpinel jorgeorpinel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rephrasing of text in Parallel stage execution:

public/static/docs/command-reference/repro.md Outdated Show resolved Hide resolved
public/static/docs/command-reference/repro.md Outdated Show resolved Hide resolved
@jorgeorpinel
Copy link
Contributor

locking looks strange, w/o context - I doubt users would get it

I had this same impression before (see #868 (review)). Do you want to assign a priority to #876 so we address it sooner than later @shcheklein?

will wait until we implement the same thing for hash/copying/downloading and will then create an article about it in the user-guide

@efiop you can probably just reuse #876 for this. Feel free to update that issue's description or add a comment.

@jorgeorpinel
Copy link
Contributor

Just one last comment from me, I think ^
Thanks Ruslan!

@shcheklein
Copy link
Member

@jorgeorpinel please, feel free to merge whenever you feel it's ready.

@efiop thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants