Peter Rowlands (변기호)
Peter Rowlands (변기호)
The issue is that `exp show` output is always `utf-8`, but git filenames are encoding agnostic (and use the system encoding). We should be handling git filenames with `os.fsdecode()` in...
@jorgeorpinel the idea has come up before as something that we could consider doing in the future, but not seriously considered yet
This is definitely a bug for the `--temp/--queue` use case, we don't handle submodules at all there. We probably need to be doing submodule pull/update in the temp workspaces that...
@woodshop unfortunately we have not been able to get to this issue yet, and it's not currently planned. There's a few submodule related `dvc exp` issues that are open, but...
You can already use git to version text-based metrics files by using `cache: false` to tell DVC not to handle it as a DVC-tracked file, and then tracking the file...
It looks like the issue happens when `asyncssh` tries to parse your OpenSSH configuration file (`~/.ssh/config`). `asyncssh` tries to load and parse the file using your terminal's system encoding (`cp950`),...
I don't think that workaround is viable here given that the request here is specifically regarding: > Some config files containing sensible data (API keys, password) And if an experiment...
There's not really anything we can do to prevent people from doing this, users can add whatever they want into git. I think anyone using `git add --force` on a...
> Not without `git commit`. In this scenario people would stage the secrets specifically because we copy staged (not committed) files into tmp exp dirs. And anything that is staged...
> Any script used in `cmd` run should be listed under `deps` right? In this case pretty tricky as .venv/ is probably Git or DVC ignored, so would DVC even...