Matt Seddon

FWIW you cannot plot queued experiments in the extension before they start:

I thought the issue here was related to an experiment that ended in an error preventing `plots diff` from returning anything. The correct behaviour could be to allow selecting the...

> yep, but when they start you can immediately plot them, right? Yes, you can follow if you like. We don't track by default. > btw, why don't we allow...

@mnrozhkov how do other experiment-tracking tools handle this functionality? The simplest thing to do would be to remove the auto-selection logic. No experiments would be selected/de-selected unless the user performed...

I think the functionality should be added to DVC through the config. That way users could add a section to their local config and we don't have to add another...

We already have the ability to add untracked files via the SCM panel: https://github.com/iterative/vscode-dvc/assets/37993418/e155b812-a04e-4d4a-864b-ab61aa0dc4aa and we do have "Add Data" via the tracked tree: https://github.com/iterative/vscode-dvc/assets/37993418/4042158e-fe7d-4d60-affe-fe3bfa92f5b3 It does seem like a...

Which view are you talking about? The sidebar view or the main editor one? Did you know that you can name your experiments using the --name flag, which will appear...

@alanwilter what do you expect to see? Would you expect the test files to be 100% covered? They are obviously executed by the test runner but I would assume they...

In the context of pytest-cov (which uses coverage.py), "covered" refers to the executable statements or branches within your Python code that have been executed during a test run. By definition,...

@alanwilter no worries. Happy to review a PR if you raise one to fix the issue 👍🏻.