-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git Graph broken as of VS Code 1.52? #436
Comments
Hi @robvitaro, I've had no other reports of this occurring for any other users after upgrading to Visual Studio Code 1.52.0. After every release I always also check the extension myself on multiple operating systems (I didn't notice anything either). This behaviour occurs when Visual Studio Code fails to load the CSS & JS resources packaged in the extension that the Git Graph View requires. If you run the "Developer: Open Webview Developer Tools" command from the Visual Studio Code Command Palette, and switch to the Console Tab, you'll be able to see the errors that Visual Studio Code is having. These error logs will tell you to path of the two required files There are two possible causes of the behaviour you've observed:
I'll close this issue as either:
|
@mhutchie, I appreciate you taking the time to give such a detailed response. Looks as if my problem is 2, as I use WSL 2. I used one of the commenters' suggestion of starting WSL before opening VS Code, that is an acceptable workaround. Thanks so much. |
Hi @robvitaro, Thanks for letting me know that this is WSL2 related! I'm glad you have an acceptable workaround until it is properly fixed. |
Describe the Bug
As of VSCode 1.52 I cannot display GitGraph
Steps to Reproduce
Steps to reproduce the behavior:
Expected Behavior
I expect to see the graph
Environment
VS Code details
Version: 1.52.0 (user setup)
Commit: 940b5f4bb5fa47866a54529ed759d95d09ee80be
Date: 2020-12-10T22:45:11.850Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041
Screenshots (optional)
The text was updated successfully, but these errors were encountered: