Dave Berenbaum

> If we want to take the same approach for experiments being run in the foreground then we would need some mechanism to save the logs for each run. Potentially...

> On the vscode side this could be reflected in the UI by adding a completely empty row with nothing but the ID/name field into the table (but we do...

Suggestion from @mattseddon is to use the `State` column with something like 'Starting'. @pmrowla Thoughts?

By the way, the row is already in the table, correct? The problem is that it continues to show up in the `Queued` state in `dvc exp show` after it...

I don't think we should be constrained by existing CLI flags here like `--all-branches` etc. VS Code might be able to provide way more flexibility to pick and choose specific...

@shcheklein I think it's related to https://github.com/iterative/dvclive/issues/326. If we enforce a DVC approach of keeping one image per step, it should simplify it. I think it's enough for now to...

It would have to depend on checkpoints. That might be okay if we work on improving/making easier the checkpoints workflow and funnel users to it. Edit: The alternative seems to...

:+1: to pretty much everything here. --- > We have an in-product prompt to install that extension. It was added in #903. Under this ticket we'll look at expanding support...

@mattseddon I'm able to confirm on the latest dev branch (and looks like it started in https://github.com/iterative/dvc/pull/7724). 2.10.2 still works fast for me. Can you confirm the same?

That's interesting. Here's what I get using the vscode demo with 150 checkpoints: ```console $ time dvc exp show --no-fetch --show-json ... dvc exp show --no-fetch --show-json 2.43s user 0.26s...