Closed thisiswhereitype closed 11 months ago
Whilst looking into https://github.com/iterative/dvclive/issues/657
The experiments
panel and table rely on the results of a dvc exp show
call. If the exp show
call fails with an error it will show that error in the experiments
panel.
Looks like the extension tried to run dvc exp show --rev 8f12f0abe78e691bcb32ecd9c81ef7df20677fe3 --rev 89568df4560dc051c8c34572c1f59ea4e90115ab --rev f85d20ff8b8037c480c2c2e7504eca1ee9de7677 --json
but it failed with an error.
Can you try running ...bin/python -m dvc exp show --rev 8f12f0abe78e691bcb32ecd9c81ef7df20677fe3 --rev 89568df4560dc051c8c34572c1f59ea4e90115ab --rev f85d20ff8b8037c480c2c2e7504eca1ee9de7677 --json
, replacing ...bin/python
with the full path of your chosen python environment?
Sorry just looked over this, the command I have censored is the conda DVC reported by dvc doctor
running between the HEAD
and HEAD~1
I have no experiments showing without revisions (I think unless the DVCLive scripts are doing something)
I noticed when running dvc queue logs
has an encoding arg, is it possible this is related to something amiss on my WSL distro?
Sorry just looked over this, the command I have censored is the conda DVC reported by dvc doctor running between the HEAD and HEAD~1
I have no experiments showing without revisions (I think unless the DVCLive scripts are doing something)
@thisiswhereitype does this mean that you can run dvc exp show --rev 8f12f0abe78e691bcb32ecd9c81ef7df20677fe3 --rev 89568df4560dc051c8c34572c1f59ea4e90115ab --rev f85d20ff8b8037c480c2c2e7504eca1ee9de7677 --json
in a terminal with the correct virtual environment activated?
No the result is the same except, I can get the stack using -vv
, all python interpreters are from the conda environment set in the vscode workspace and terminals
Thanks @thisiswhereitype.
@dberenbaum are we able to move this upstream into DVC? Not much we can do on the extension side. Reminds me a bit of https://github.com/iterative/dvc/issues/9565
@thisiswhereitype hey, could you please give us a way to reproduce this? share the repo? Or at least describe the steps it took you to get the params
files that you have. Could you share it with us btw?
My development of the params files is in here: https://github.com/iterative/dvclive/issues/657
Once I got params and experiments to run I promoted one to a branch (as I couldn't see the output due to this issue) (although maybe the successfull experiments supressed/fixed this but I didn't check) and found that this appeared to resolve the problems.
I am not sure I can send or share the repo due to NDA, I am really at a loss to help but I appreciate your collective effort and love using DVC. I had concluded eventually the source of the error was on an older experiment committed but mislabelled in the yaml as a metric maybe? - DVC and vsocde-dvc both got minor patches in this time.
I am happy to try the help but I am not sure I can repro the issue anymore.
Thanks @thisiswhereitype. Closing now. Please reopen if the issue occurs again.
Extension version:
v1.0.57