Matt Seddon

> Could you please try it again I will test today.

@karajan1001 I'm still seeing the same behaviour. Even with a fresh clone of https://github.com/iterative/vscode-dvc: ``` dvc exp show --show-json -v 2022-09-20 15:36:25,649 ERROR: unexpected error - Invalid revision: b'1dbb61e08d6d96c6db910a6d392cb1a1bdb9d04d' ------------------------------------------------------------...

> Sorry I can not reproduce this error. Can you try with `watch -n0 dvc exp show --show-json`? I can reproduce with just two terminals: https://user-images.githubusercontent.com/37993418/191486910-60410f59-31ff-453f-9a94-53c107e26821.mov https://user-images.githubusercontent.com/37993418/191488158-0312862c-4fac-46aa-a422-bede75f9e7e6.mov

> @mattseddon Are these issues blockers for you? If you are getting intermittent errors, is it possible to ignore those? This is a blocker. We cannot reliably ignore these errors...

> 1. Should it block the current PR? I see the VS Code table disappearing for a bit both before and after this PR. After this PR, I at least...

> For JSON, do we need to have a general guideline for all commands that errors should be output in JSON? It would be good to head in that direction.

> @mattseddon Given [iterative/vscode-dvc#2301](https://github.com/iterative/vscode-dvc/pull/2301), is this still an issue? Do you still need JSON errors? What info do you need and how important is it? For this particular issue, it...

The missing part is having the path to the broken file(s) as a string (or list of strings) instead of having to parse the text to work it out. In...

> for failed exp > > ```json > "data": { > "timestamp": ANY, > "params": {"params.yaml": {"data": {"foo": 2}}}, > "deps": {"copy.py": {"hash": None, "size": None, "nfiles": None}}, > "outs":...

@maxagin all of the experiments table screenshots are out of date already.