Closed carlocardella closed 2 years ago
I have found https://github.com/microsoft/codetour/issues/194, but I do not think this applies, something seems to have changed in the VSCode environment outside extensions.
As mentioned in my initial issue, I use the same exceptions in both Stable and Insider releases, I have even exported the list (code --list-extensions --show-versions
) and compared the two lists, they are identical, down to the version of each extension I have installed.
So, whatever change has been made to Insiders very likely will make its way to Stable in the near future and Repositories in GistPad may be unusable
In today's Insiders this no longer reproes, I'll keep an eye on in in case it comes back or should repro on Stable
Version: 1.65.0-insider (user setup)
Commit: 8440b8f47231147823ba9696913d642e5f2d9d58
Date: 2022-02-25T05:17:33.544Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22543
Sounds good! I'm guessing it was a temporary regression in insiders that probably affected other extensions? I'm going to close this for now, and we can reopen it if it surfaces again. Thanks!
Describe the bug In recent builds of VSCode Insiders, GistPad Repositories no longer show the repo content (see screenshot below), VSCode Stable still works fine in the current build but if this behavior is due to some new change in Insiders, it will reach Stable soon and that may break as well.
To Reproduce Steps to reproduce the behavior:
Expected behavior See and edit files in the repo
Screenshots Problem with VSCode insiders
VSCode Stable works fine (for now)
Desktop (please complete the following information):
Additional context In
Log (Window)
I found this:I use the same extensions on both VSCode versions