Paweł Redzyński

@dberenbaum yep, hence the WIP, but I am not sure yet if we want to merge it, as I see that vscode team can handle that support even with existing...

Ok, as I see in https://github.com/iterative/vscode-dvc/issues/1757#issuecomment-1250230807 we do rely on it. I will update this PR

Seems that even "normal" run suffers from this problem: ```bash #!/bin/bash rm -rf wspace mkdir wspace pushd wspace set -ex main=$(pwd) mkdir repo pushd repo git init --quiet dvc init...

Seems like a bug of `--dry` reproduction script: ``` #!/bin/bash set -exu pushd $TMPDIR wsp=test_wspace rep=test_repo rm -rf $wsp && mkdir $wsp && pushd $wsp main=$(pwd) mkdir $rep && pushd...

@skshetry maybe bug is too much but I guess feature request? From user point of view it doesn't matter if we `run` or `run --dry`

> Instantiating ODB does not involve anything other than simple __init__, and the underlying filesystems are already cached. I did not expect that to be slow. Is there a use...

We should probably get to implementing the configuration of timeout. Original report from @michuhu: https://discord.com/channels/485586884165107732/563406153334128681/1035466365659779093

I didn't left any comment during research, so: We were able to implement top level plots basing on old data format. In order to support errors we will need to...

Idea: maybe we should implement local s3 storage using MinIO, to cut the time of data transfer.

@isidentical that might be a good idea. I still wonder whether we shouldn't try to implement MinIO remote. But I guess retry won't contradict with MinIO if we decide to...