Peter Rowlands (변기호)

> Hello. I am getting the same error when using `dvc exp`: @ayeright could you run the following command and then post the output here: ``` git reflog show refs/exps/stash...

@ayeright thanks, could you also please upload/attach the file `.git/logs/refs/exps/stash` to this issue? After you've done that, you should be able to fix your repo state by doing ``` git...

I think this is probably p2, given that there's a workaround and that we haven't seen any other reports on this

DVC push/pull performance for many small files is a known limitation. But a part of the issue is probably also specific to the HTTP remote type, it's possible you would...

This is also an issue that can be addressed by future cache structure changes (https://github.com/iterative/dvc/issues/829). Ideally with those kinds of cache changes we will be pushing and pulling a small...

> use more thread by default - why don't we do this? When we used the old "# of cores x2" method (without a hard cap on the default) for...

S3 does not directly support HTTP/2 unless you are serving it behind CloudFront (or your own proxy server). --- Also, just to be clear, HTTP/1.1 pipelining is not the same...

Can't this already be done with `dvc pull -d/--with-deps B`? The behavior for `repro --pull` is definitely confusing and needs to be updated at some point, but I'm not sure...

Ah I see, so what we want would be something along the lines of `pull --deps-only`. Although I'm not sure I understand why pulling the output here is a problem....

I'm still not following > 1. I don't want to pull unnecessary data. > a. Pulling dependencies from unmodified or upstream stages doesn't help. Dependencies only need to be pulled...