Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Some commands fails on VSCode Insiders
See original GitHub issueSome commands like jumping to a commit, staging a file, switching branches etc. fails on the latest build of VSCode Insiders with the Cannot read properties of undefined (reading 'exec') error.
I’ve tried to debug the issue and I think the problem is: we are using a private variable from VSCode Git API in gitRun and with https://github.com/microsoft/vscode/issues/167269 it started to get mangled.
You can see private variable repository mangled to J for example:
Issue Analytics
- State:
- Created 10 months ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah, realised when unexge posted that 👍🏻 Working on a fix that does not rely on private fields
Thanks for the heads up! Edamagit will break badly when this is released. Will work on fixing this properly