vscode-dvc: Experiments webview stuck on loading experiments

I confirm - it works for me now.

Looks like it’s fixed now! Thanks @rogermparent @mattseddon .

Now I’m confused, at some moment I was able to open experiments view for example-get-started, but can’t reproduce this again. Surprisingly, log messages were present:

Also I’m not sure why “seed” columns was repeated twice. It looks like a bug.

I’ve hit the same issue. I tried two repos - a project of mine with dvc and example-get-started. Interesting, that the issue only appears with example-get-started. I cloned the repo to have no changes there, the open VSCode with the extension, and then see (among other errors):

ERROR: failed to show experiments - Unable to acquire lock. Most likely another DVC process is running or was terminated abruptly. Check the page <https://dvc.org/doc/user-guide/troubleshooting#lock-issue> for other possible reasons and to learn how to resolve this. (at Function.i.write (/Users/aguschin/.vscode-insiders/extensions/iterative.dvc-0.1.0-223adcd1714536ad86741d24c815ce12f214861e/dist/extension.js:21:61846))

I’ve tried resolutions suggested in the link above (first: remove .dvc/tmp/lock, second: run dvc config core.hardlink_lock true), but none work. What I found out, that the .dvc/tmp/lock file is refreshing every time I click on VScode (even with experiments webview closed). This also happens on the first repo I mentioned, where experiments are shown correctly. Not sure, what is the difference. The logs in Developer Tools are different, so I just provide both of them in case there is something interesting.

What I’m getting at is that the dev tools toggled by “Toggle Developer Tools” where you see DevTools failed to load SourceMap: […] is that console, but the problem in this PR may be within the VSCode extension, and that part of the VSCode extension is likely silently failing in this case because you don’t see any relevant console output.

Yep, I think we are on the page. My question is about application level logging and being able to set some flag - DEBUG=true, run it an see the logs. Something like “Running dvc exp show” … “Exp show returned …”

This issue that we have also means that we need to rethink a bit how do we change the page behavior. Probably we want to explain to users what is happening under the hood. I think we can create a Story out of this.

What’s going on with my repo - I don’t know yet … will keep looking into this

@rogermparent is there a way to enable logs for the VSIX build so that we can debug/see what is happening? Are there some best practices in terms of logging for extensions?

and saw a few “repo locked” errors.

for me dvc exp show alone works fine

@rogermparent haha, no worries 😃 but this is the first thing I would try - “reset your machine” Windows © 😃