Ruslan Kuprieiev

@pmrowla Could you please take a look as well? Since you are working on #8164 which is related.

For the record: discussed with @dberenbaum and @pmrowla that the `commit` part should be fixed in this PR, but the `pull`-related logic is more about `import-url` in general and we...

@dberenbaum Good point, for some reason I thought this wasn't broken before. Yeah, let's merge and move on then. Thanks for a great discussion folks, the initial implementation seemed deceptively...

CC @dtrifiro

@jorgeorpinel Just for the record: Both links are not related to this issue. > Also @dberenbaum @efiop @shcheklein WDYT about establishing some non-functional requirements such as basic operation speeds and...

Hey @brbarkley , thanks for the interest! We are currently actively working on improving the internals in order for them to accommodate the optimizations that will be the result of...

Hi @jmblackmer . Thank you for your interest! As you've noticed, thanks to @agurtovoy we have #6111 :pray: that solves those particular issues. I can't give an ETA on it...

Hi @ZhengRui That sounds correct, yes. Using nfs only for cache (or as a local remote) is the workaround. Seeming data loss is just dvc not transferring everything completely, but...

@brbarkley Correct. This particular issue is about other things too, like optimizing, which is on our todo list.

@brbarkley It is, but it is not great in terms of ui/performace. You need to use these config options `core.hardlink_lock`, `state.dir`(should be pointing to a normal filesystem, e.g. `/tmp/something`) and...