phil294
commented
11 months ago "unknown visuals at row 0" means the output returned from git's log command has an unknown format. I guess this can happen if you have changed the log command (very top in the main view)? Perhaps you have adjusted something there which used to work, but then I broke it unintentionally in a subsequent update. Could you share what this field holds for you currently, if it is shown as modified? Before clicking on "Reset", as then the error will not be reproducible anymore.
Otherwise, you could try setting the config flag verbose-logging to true. Afterwards, you can open the "Output" view and select git log --graph. This view should also contain the error, and more information around it - such as said git output. If you paste the relevant information here, I'm sure we'll find something.
Anyway, the error handling should be improved here: If any of the git inputs (including the main log one) return an error and the user has altered the input command, there should be a message suggesting them to click "reset" to potentially fix the error. These kinds of errors are rather unique to this extension, I don't think there is an easy way to prevent them, really. I guess that's the downside of exposing such powerful functionality to the extension user :|
hansu
After using my VM after some time again, I get this error when trying to run this extension:
When I run Code it with a clean
--user-data-dirthen it works. But I don't want to delete my user data dir. Any hints what this could cause?