repro: Move pull logic to inside Stage. #9434

daavoo · 2023-05-10T12:45:02Z

codecov · 2023-05-10T13:29:41Z

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (e69deaa) 91.60% compared to head (8ecd5ab) 91.60%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9434   +/-   ##
=======================================
  Coverage   91.60%   91.60%           
=======================================
  Files         489      489           
  Lines       38166    38167    +1     
  Branches     5469     5469           
=======================================
+ Hits        34962    34963    +1     
  Misses       2639     2639           
  Partials      565      565

Impacted Files	Coverage Δ
dvc/repo/reproduce.py	`97.63% <ø> (-0.06%)`	⬇️
dvc/stage/__init__.py	`93.89% <100.00%> (+0.05%)`	⬆️
tests/func/test_run_cache.py	`100.00% <100.00%> (ø)`

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

dberenbaum · 2023-05-11T18:15:33Z

Sorry, this is more about QA for #9395. I tried:

$ git clone [email protected]:iterative/example-get-started-experiments.git
$ cd example-get-started-experiments
$ dvc exp run --pull
Pulling run cache.
ERROR: run-cache is not supported for http filesystem: https://remote.dvc.org/get-started-pools

I think it shouldn't make the whole command fail if run cache isn't supported or fails to be pulled.

daavoo · 2023-05-12T08:06:36Z

Sorry, this is more about QA for #9395. I tried:
$ git clone [email protected]:iterative/example-get-started-experiments.git
$ cd example-get-started-experiments
$ dvc exp run --pull
Pulling run cache.
ERROR: run-cache is not supported for http filesystem: https://remote.dvc.org/get-started-pools
I think it shouldn't make the whole command fail if run cache isn't supported or fails to be pulled.

I guess so.

I think it is a problem of --pull now doing 2 things (pull run cache and missing data). If it fails to pull data, you would expect and error, right?

daavoo · 2023-05-12T08:07:36Z

ping @skshetry does this makes sense for your comment in #9395 (comment) ?

dberenbaum · 2023-05-12T15:25:36Z

I think it is a problem of --pull now doing 2 things (pull run cache and missing data). If it fails to pull data, you would expect and error, right?

IMHO since --pull is doing additional stuff to try to make repro work, I would say we should warn on failures for both and try to repro anyway. In many cases, if it fails to pull data, this will ultimately fail, but I don't see why I wouldn't want to run as much as possible until then.

skshetry · 2023-05-16T03:04:36Z

dvc/stage/__init__.py

+            for objs in self.get_used_objs().values():
+                self.repo.cloud.pull(objs)


You probably need to pass odb here.

Suggested change

for objs in self.get_used_objs().values():

self.repo.cloud.pull(objs)

for odb, objs in self.get_used_objs().items():

self.repo.cloud.pull(objs, odb=odb)

Talk to Ruslan and Peter please about this on how to pull from cloud versioned remotes. Most likely this involves index, but make sure to discuss. With this change, cloud versioning won't work.

I got the reasoning for putting it inside here because of the rwlocks, but still missing the point of not using the high level pull API, as it would solve that

@iterative/dvc could you reason what would be the downside of using self.repo.pull inside a stage vs trying to use some low-level API?

In addition to making this work for cloud versioning here, I also didn´t find a good way of pulling dependencies as in #9437 (comment) without using stage.repo.pull

It's a large dependency that we are adding that is not meant for internal consumption. Repo.pull() is equivalent to dvc pull, so it's heavy and complex. And this one does that in a loop, for multiple stages.
Repo.pull(stage.addressing) reloads dvc.yaml/dvc.lock file, finds proper objects/index, and downloads them.

Also, improving UI for dvc repro/dvc exp run may be difficult as it's now tied with dvc pull. What we really need here is a way to pull for one stage.
I don't have much issue with this as temporary solution, but I could see it getting permanent.

Makes sense

What we really need here is a way to pull for one stage.
I don't have much issue with this as temporary solution, but I could see it getting permanent.

Ok. I will open an issue to revisit this. Probably worth waiting for the new fetch

skshetry · 2023-05-16T03:07:00Z

dvc/stage/__init__.py

            self._sync_import(dry, force, kwargs.get("jobs", None), no_download)
        elif not self.frozen and self.cmd:
            self._run_stage(dry, force, **kwargs)
-        else:
+        elif kwargs.get("pull"):


Should not this come before you run the stage?

This is for pulling outputs of unchanged stages.

The follow-up P.R. adds a new flag that enables pulling dependencies see #9437 (comment)

dberenbaum · 2023-05-17T15:44:47Z

IMHO since --pull is doing additional stuff to try to make repro work, I would say we should warn on failures for both and try to repro anyway. In many cases, if it fails to pull data, this will ultimately fail, but I don't see why I wouldn't want to run as much as possible until then.

@daavoo Is it supposed to be fixed? Do you want me to create a follow-up issue? I still see the same error when trying to pull the run cache for an http remote.

daavoo · 2023-05-17T16:32:08Z

IMHO since --pull is doing additional stuff to try to make repro work, I would say we should warn on failures for both and try to repro anyway. In many cases, if it fails to pull data, this will ultimately fail, but I don't see why I wouldn't want to run as much as possible until then.

@daavoo Is it supposed to be fixed? Do you want me to create a follow-up issue? I still see the same error when trying to pull the run cache for an http remote.

Sorry, no, It is not fixed. Please open issue

daavoo added the refactoring Factoring and re-factoring label May 10, 2023

daavoo requested a review from skshetry May 10, 2023 12:45

daavoo self-assigned this May 10, 2023

daavoo force-pushed the repro-pull-followup branch 2 times, most recently from 365648d to 9c960d0 Compare May 10, 2023 13:19

daavoo mentioned this pull request May 10, 2023

repro: Add --allow-missing #9437

Merged

skshetry reviewed May 16, 2023

View reviewed changes

daavoo force-pushed the repro-pull-followup branch from 9c960d0 to 3577947 Compare May 16, 2023 13:28

daavoo enabled auto-merge (rebase) May 16, 2023 13:29

repro: Move pull logic to inside Stage.

8ecd5ab

daavoo force-pushed the repro-pull-followup branch from 3577947 to 8ecd5ab Compare May 16, 2023 13:29

daavoo merged commit 1e538ed into main May 16, 2023

daavoo deleted the repro-pull-followup branch May 16, 2023 14:11

daavoo mentioned this pull request May 17, 2023

Add mechanism to pull a single stage #9467

Closed

dberenbaum mentioned this pull request May 17, 2023

exp run --pull: keep going even if pull fails #9470

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

repro: Move pull logic to inside Stage. #9434

repro: Move pull logic to inside Stage. #9434

daavoo commented May 10, 2023 •

edited

Loading

codecov bot commented May 10, 2023 •

edited

Loading

dberenbaum commented May 11, 2023

daavoo commented May 12, 2023

daavoo commented May 12, 2023

dberenbaum commented May 12, 2023

skshetry May 16, 2023

skshetry May 16, 2023

daavoo May 16, 2023

daavoo May 16, 2023

skshetry May 16, 2023

daavoo May 16, 2023

skshetry May 16, 2023

daavoo May 16, 2023

dberenbaum commented May 17, 2023

daavoo commented May 17, 2023

		for objs in self.get_used_objs().values():
		self.repo.cloud.pull(objs)

repro: Move pull logic to inside Stage. #9434

repro: Move pull logic to inside Stage. #9434

Conversation

daavoo commented May 10, 2023 • edited Loading

codecov bot commented May 10, 2023 • edited Loading

Codecov Report

dberenbaum commented May 11, 2023

daavoo commented May 12, 2023

daavoo commented May 12, 2023

dberenbaum commented May 12, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dberenbaum commented May 17, 2023

daavoo commented May 17, 2023

daavoo commented May 10, 2023 •

edited

Loading

codecov bot commented May 10, 2023 •

edited

Loading