Ruslan Kuprieiev

@mdekstrand What do you think? 🙂

@mdekstrand `--always-changed` was released in 0.59.2, please give it a try and be sure to let us know how that works for you :slightly_smiling_face: Thanks for all the feedback!

Hi @Guichaguri ! I'm not familiar with DBFS, but I would double check if maybe it supports one of the already supported APIs (e.g. we have s3 support, ssh, hdfs...

Thanks everyone for a great and detailed discussion, it was a pleasure going through it. After reading all the points made here, discussing this with @dberenbaum and @shcheklein , and...

We should probably just stop doing relinking by default in add/commit and introduce an explicit flag `--relink` like in `checkout`. This force-relinking is a bit of a legacy thing from...

One challenge here is handling permissions for symlink/hardlink cases because it could lead to data corruption. So we need to catch mismatched permissions during `checkout` phase of `add/commit` and relink...

@jpaasen Do you know how the corruption happened? We verify local files before uploading them, so it is quite unusual for files to get corrupted on remote. Alternative/additional approach here...

@Robinlovelace Could you elaborate, please? I'm not sure I understand how it would work. Every new `dvc push` creating a new release?

@Robinlovelace So updating the same release artifacts? Just trying to understand if you have particular ideas or if this is just a general idea.

Thanks to @dberenbaum for pointing me to this. I have a similar need for cache in https://github.com/iterative/studio/pull/6541, so thinking that we could introduce ``` $ dvc cache/remote check-missing [--rev REV]...