Ivan Shcheklein

Queued experiments fail, can't see logs to understand what's up

9

https://github.com/iterative/vscode-dvc/assets/3659196/d2e544bb-0de3-440b-9769-2609b996093c Single experiment runs fine even within a queue. Might be related to some resource allocation when it tries to do 2 of them, but I can't say what's going...

Plots should be more resilient to errors in specific revisions

18

https://github.com/iterative/vscode-dvc/assets/3659196/9b346856-bf72-4cc0-a467-eea94c6ccaeb

Use hash, not experiment names in all DVC commands and as IDs in the table

9

E.g. `/usr/local/bin/python -m dvc plots diff workspace testy-leno`. We should not be using `testy-leno` - it's ambiguous. Only if we don't know the hash yet it's fine to use name...

From using it: https://github.com/iterative/vscode-dvc/assets/3659196/f7b41659-7014-4a56-bcf4-926a63280041 - In the preview screen. As we change the step number we need to also update the preview. - Multiple previews (?) - need some research...

Remote storage onboarding section improvements

2

- [ ] If storage of a specific type is detected we should activate the relevant tab automatically (e.g. Azure one) - [ ] Should we collapse the whole section...

`log_artifact`: external and non-DVC tracked files support

8

More of a question for now: - Should DVC tracking be optional / disabled by default? E.g. if model weights are in Git-lfs? I can still see the model in...

add prints to see values

4

Just to debug test failures on main for now.

Adds GitLab CI pipeline to publish reports. Example: https://gitlab.com/iterative.ai/cse_public/example-text-classifier https://gitlab.com/iterative.ai/cse_public/example-text-classifier/-/merge_requests/2

Move projects to their proper place, add READMEs

4

- ~DVC repos into `docs/dvc` ... cc @jorgeorpinel (low priority)~ removed bc of https://github.com/iterative/dataset-registry/issues/34#issuecomment-1331136693 - [ ] [github-issues](https://github.com/iterative/dataset-registry/tree/master/github-issues) cc @ykasimov @mnrozhkov do we still need it? Do you plan to...

Add CI/CD to check that data exists when PR is published

1

There should be a CI check that would run `dvc status -c` to ensure that data is uploaded. Question: should we run it per-commit or per PR - not clear...