https://github.com/microsoft/vscode/issues/145297 Skip to content Sign up * Product + Features + Mobile + Actions + Codespaces + Packages + Security + Code review + Issues + Integrations + GitHub Sponsors + Customer stories * Team * Enterprise * Explore + Explore GitHub + Learn and contribute + Topics + Collections + Trending + Learning Lab + Open source guides + Connect with others + The ReadME Project + Events + Community forum + GitHub Education + GitHub Stars program * Marketplace * Pricing + Plans + Compare plans + Contact Sales + Education [ ] * # In this repository All GitHub | Jump to | * No suggested jump to results * # In this repository All GitHub | Jump to | * # In this organization All GitHub | Jump to | * # In this repository All GitHub | Jump to | Sign in Sign up {{ message }} microsoft / vscode Public * Notifications * Fork 21.9k * Star 129k * Code * Issues 5k+ * Pull requests 258 * Actions * Projects 2 * Wiki * Security * Insights More * Code * Issues * Pull requests * Actions * Projects * Wiki * Security * Insights 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. Pick a username [ ] Email Address [ ] Password [ ] [ ] Sign up for GitHub 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 Jump to bottom When I use vscode to open a folder, many empty file with invalid code automatically are generated. #145297 Closed na-an opened this issue Mar 17, 2022 * 52 comments Closed When I use vscode to open a folder, many empty file with invalid code automatically are generated. #145297 na-an opened this issue Mar 17, 2022 * 52 comments Assignees @bpasero Labels *caused-by-extension needs more info Comments @na-an Copy link @na-an na-an commented Mar 17, 2022 Does this issue occur when all extensions are disabled?: Yes/No * VS Code Version: * OS Version: Sorry for I had deleted the VS Code, because I worry if the computer is attacked by virus. But VS Code is recent version. I update VS Code yesterday. Steps to Reproduce: When I use vscode to open a folder, many empty file with invalid code automatically are generated. And I use OpenFOAM(a software) to wmake(make) some function, the contents in some ".H" and ".C" which are related with this function is disappeared, these files become empty, though these files ".H" and ".C" are still exist. The text was updated successfully, but these errors were encountered: 7 @howardlau1999 Copy link @howardlau1999 howardlau1999 commented Mar 17, 2022 * edited Same issue here. Some empty files with random filenames are created when I open the folder using Remote SSH. [6874747073] [6874747073] Some susceptible filenames seem like SQL. Version: 1.65.2 (user setup) Commit: c722ca6 Date: 2022-03-10T14:33:55.248Z 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.19044 Remote OS is CentOS 7 6 Sorry, something went wrong. @vscode-triage-bot vscode-triage-bot added the triage-needed label Mar 17, 2022 @vscode-triage-bot vscode-triage-bot assigned alexr00 Mar 17, 2022 @daantimmer Copy link @daantimmer daantimmer commented Mar 17, 2022 * edited Same issue here. Tried with all extensions disabled, same issue. To make matters worse, some files are even modified to the point where the contents are erased. This happens in all sort of random files. Seems to occur more often when building or configuring using, for example, cmake. But the severity of modified//added files is completely random. I once had a filename that was about 100 characters long and looked like a string dump from a running process as it had a table 'look a like' string of characters. Version: 1.65.2 (user setup) Commit: c722ca6 Date: 2022-03-10T14:33:55.248Z 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.19042 I have this happening on two unrelated machines. Sorry, something went wrong. @zhanghb55 Copy link @zhanghb55 zhanghb55 commented Mar 17, 2022 * edited I meet the same situation Version: 1.65.2 (Universal) Commit: c722ca6 Date: 2022-03-10T14:33:49.188Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Darwin x64 20.6.0 InvalidCode Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 17, 2022 I have just downgraded (by installing without uninstalling) 1.64.2, the issue persists Sorry, something went wrong. @RenoirTan Copy link @RenoirTan RenoirTan commented Mar 17, 2022 Same issue here. I haven't been able to find out what exactly is the trigger but I know it's definitely caused by vs code because when I tried to write stuff using neovim or kate, these files don't appear. From what I can tell, these files only appear in the root of the folder (and not in any subdirectories in the project). The names of these files are not valid unicode (e.g. \312\316\361 which is in octal is 11001010 11001110 11110001 in binary). Screenshot_20220317_161207 Screenshot_20220317_161226 System Info CPUs 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 1091) 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: GPU disabled_off opengl: enabled_on rasterization: Status disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled Load 2, 2, 1 (avg) Memory 15.41GB (2.78GB free) (System) Process --no-sandbox --unity-launch --crash-reporter-id Argv 7f52dc70-39d5-4913-96f6-32ae4ae5e9d4 Screen no Reader VM 0% OS Linux x64 Kernel version 5.16.14 Extensions Extension Author (truncated) Version better-comments aar 2.1.0 codesnap adp 1.3.4 vscode-django bat 1.10.0 toml be5 0.6.0 doxdocgen csc 1.4.0 python-environment-manager don 1.0.3 python-extension-pack don 1.7.0 gitlens eam 12.0.4 go gol 0.32.0 helium-icon-theme hel 1.0.0 better-cpp-syntax jef 1.15.13 vsc-python-indent Kev 1.14.2 rust-analyzer mat 0.2.975 git-graph mhu 1.30.0 fluent-icons mig 0.0.17 vscode-docker ms- 1.20.0 python ms- 2022.2.1924087327 vscode-pylance ms- 2022.3.2 jupyter ms- 2022.2.1030672458 jupyter-keymap ms- 1.0.0 jupyter-renderers ms- 1.0.6 remote-containers ms- 0.224.2 remote-ssh ms- 0.76.1 remote-ssh-edit ms- 0.76.1 remote-wsl ms- 0.64.2 vscode-remote-extensionpack ms- 0.21.0 cmake-tools ms- 1.9.2 cpptools ms- 1.9.4 cpptools-extension-pack ms- 1.1.0 autodocstring njp 0.6.1 glassit s-n 0.2.4 cmake twx 0.0.17 vscodeintellicode Vis 1.2.17 jinja who 0.0.8 Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 17, 2022 * edited From what I can tell, these files only appear in the root of the folder (and not in any subdirectories in the project). This statement is incorrect. I get original files being emptied in my build tree and get files named cpp.hint in my build tree edit: I've just got a file name cpp.stop image Sorry, something went wrong. @howardlau1999 Copy link @howardlau1999 howardlau1999 commented Mar 17, 2022 * edited Seems like if you are using Remote SSH, you can temporarily resolve the issue by deleting ~/.vscode-server and reopening VSC. I don't know if the same issue would happen again. Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 17, 2022 For me personally I am not using Remote SSH. Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 17, 2022 * edited Additional information. The deletion of contents of files was not restricted to my working folder! It has even managed to delete contents outside this folder, for example my 'windows kits' has been destroyed and I don't know to what extend, but the following file, for example, is completely empty now: image I do not know if the issue is only affecting parsing of 'include' files or that it could possibly have touched completely unrelated files as well. A few more files were affected: image Searched on size 0, modified today 3 6 Sorry, something went wrong. @daantimmer daantimmer mentioned this issue Mar 17, 2022 Version 1.9.4 (pre-release) C++ extension automatically creates garbled files in the workspace microsoft/vscode-cpptools#9041 Closed @alexr00 alexr00 assigned bpasero and unassigned alexr00 Mar 17, 2022 @alexr00 alexr00 removed the triage-needed label Mar 17, 2022 @WoodsCumming Copy link @WoodsCumming WoodsCumming commented Mar 17, 2022 * edited image image This preview introduces this bug. Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 17, 2022 This preview introduces this bug. How would this explain that the issues persisted with all extensions disabled? Sorry, something went wrong. @WoodsCumming Copy link @WoodsCumming WoodsCumming commented Mar 17, 2022 * edited This preview introduces this bug. How would this explain that the issues persisted with all extensions disabled? image Switching to the official release solves this problem temporarily. 6 Sorry, something went wrong. @kblackcn Copy link @kblackcn kblackcn commented Mar 17, 2022 * edited In my case, I disable all extensions and restart vscode. Files are generated just after reenabling cpptools. Maybe there are still running process in the background or so. After I rollback to release branch, the problem just goes away. I'm also suspecting the file-deletion issue ruined my dev docker twice. I found many header files become zero-sized and even pthread won't work. Sorry, something went wrong. @bpasero Copy link Member @bpasero bpasero commented Mar 17, 2022 I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself. Sorry, something went wrong. @bpasero bpasero added the needs more info label Mar 17, 2022 @sbovbjerg Copy link @sbovbjerg sbovbjerg commented Mar 17, 2022 I traced this to 1.9.4 pre-release of the C/C++ extension. I can trigger the problem when there are updates to the files in the project folder. With all extension disabled the problem goes away. The problem also goes away if I switch to the release version (1.8.4) Sorry, something went wrong. @bpasero bpasero added the *caused-by-extension label Mar 17, 2022 @vscode-triage-bot Copy link Collaborator @vscode-triage-bot vscode-triage-bot commented Mar 17, 2022 This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. Happy Coding! 5 Sorry, something went wrong. @vscode-triage-bot vscode-triage-bot closed this Mar 17, 2022 @ericLemanissier ericLemanissier mentioned this issue Mar 17, 2022 [package] qt/6.2.1: ConanException: qt/6.2.1 package_info(): Package require 'glib' not used in components requires conan-io/ conan-center-index#9794 Closed @gjsjohnmurray gjsjohnmurray mentioned this issue Mar 17, 2022 Random files being created #145329 Closed @gev Copy link @gev gev commented Mar 17, 2022 node-ipc? 4 Sorry, something went wrong. @gjsjohnmurray gjsjohnmurray mentioned this issue Mar 17, 2022 Generate invalid encoding file when saving (Ctrl +S) #145331 Closed @spartanatreyu Copy link @spartanatreyu spartanatreyu commented Mar 17, 2022 Man, I can't wait to read the blog post explaining what happened here 4 [?] 3 Sorry, something went wrong. 4 hidden items Load more... @mhavill Copy link @mhavill mhavill commented Mar 18, 2022 Is that a bug? @hello-smile6 I would guess so! they installed the language extension while it was still in pre-release. Thank you @spartanatreyu. Unfortunately, I don't believe that to be the case in my situation. * I only loaded the extension less than 8 months ago and I think this extension well proceeded that * I am old enough to know not to risk pre-release software * It doesn't explain how duff code got into a release (albeit 'pre-release') * it doesn't explain how it deployed to my environment this morning without my activation. Reading the VSC documentation I cannot find anything that would enable auto updates of extensions, and in fact the sync function implies that there is not an auto update function (IMO). Perhaps @sean-mcmanus can help us understand how this has happened? (I recall seeing that there had been about 29k downloads of the update this morning - that is a big widespread impact!) ATM, I am not convinced that there has not been a wider impact on my environment. Sorry, something went wrong. @hello-smile6 Copy link @hello-smile6 hello-smile6 commented Mar 18, 2022 Is that a bug? @hello-smile6 I would guess so! they installed the language extension while it was still in pre-release. Thank you @spartanatreyu. Unfortunately, I don't believe that to be the case in my situation. + I only loaded the extension less than 8 months ago and I think this extension well proceeded that + I am old enough to know not to risk pre-release software + It doesn't explain how duff code got into a release (albeit 'pre-release') + it doesn't explain how it deployed to my environment this morning without my activation. Reading the VSC documentation I cannot find anything that would enable auto updates of extensions, and in fact the sync function implies that there is not an auto update function (IMO). Perhaps @sean-mcmanus can help us understand how this has happened? (I recall seeing that there had been about 29k downloads of the update this morning - that is a big widespread impact!) ATM, I am not convinced that there has not been a wider impact on my environment. As far as I understand, vscode automatically updates extensions. Sorry, something went wrong. @sean-mcmanus Copy link Contributor @sean-mcmanus sean-mcmanus commented Mar 18, 2022 * None of us on our team have been able to repro the issue so far on multiple machines and projects. We have not identified what factor causes the repro. * We've published a 1.9.5 update that reverts the changes that caused the bug. * We've released a 1.9.6-prerelease1 update on GitHub (not via the Marketplace) that has a fix for a read of deleted memory along with the other reverted changes, but since we don't know how that read of deleted memory could cause the bug and we can't repro the bug, we're not sure yet if it's been fixed or not. Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 18, 2022 Thank you @sean-mcmanus My experience was more that * Files were getting created every minute or so with very random names and all zero-length in the currently active folder of the workspace - this was an annoyance more than a big problem * '.exe' files in toolchains and in frameworks were re-written with zero-length - this was a bigger issue as I had to delete all of these and allow VSC to reload them plus all of the delays on rebuilding the projects * At this stage I am not convinced that the changes were limited just to the above folders - feeling a bit edgy and vulnerable! I'll see if I can scan for 0 length files modified/created today. + None of us on our team have been able to repro the issue so far on multiple machines and projects. We have not identified what factor causes the repro. I could see if I can re-produce it! Sorry, something went wrong. @hello-smile6 Copy link @hello-smile6 hello-smile6 commented Mar 18, 2022 I'm glad I have absolutely no knowledge of C++ and and barely any of C, and don't have that extension installed. I routinely open application install directories using vscode. Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 18, 2022 * edited As far as I understand, vscode automatically updates extensions. That would be very worrying if so, particularly if it switches you from a release version to a pre-release version! https://code.visualstudio.com/docs/editor/settings-sync To me this implies that updates are not automatic (or they would override your Sync preferences) Does anyone have contrary documentation? Sorry, something went wrong. @sean-mcmanus Copy link Contributor @sean-mcmanus sean-mcmanus commented Mar 18, 2022 @mhavill You have to opt-in to pre-release version and there's and extenions.autoUpdate setting for disabling extension updates. Sorry, something went wrong. @hello-smile6 Copy link @hello-smile6 hello-smile6 commented Mar 18, 2022 For reference: microsoft/vscode-cpptools#9041 (comment) 2 Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 18, 2022 I have searched in the .platformio\packages folder and there were 118 files modified in a couple of minutes around 6:20 am. I have replaced about 90%. They were all in toolchains or frameworks but there were a variety of file types - .exe, .h, .cpp, .hint , .stop Looks like it only smashed the projects I had open at the time, but it not only dropped new files, it also hit some .h, .hint , .stop and .txt files I'm still searching across the whole of the drive - this caught my eye as it seems to be the time when the update happened image I cannot see anything significant in Event Viewer although it is not one of my strong areas. Sorry, something went wrong. @sean-mcmanus Copy link Contributor @sean-mcmanus sean-mcmanus commented Mar 18, 2022 @mhavill We've finally found the repro and a fix for the root issue for our pending 1.9.6 release. We're very sorry for any problems this may have caused and our looking into various things that could potentially prevent this from happening again. 1 Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 18, 2022 Thank you @sean-mcmanus - believe me - I am absolutely delighted that you have found this - The alternative would point (in my mind) to some security attack/breach. I don't know if anything provided helped, but I would be more than happy to be involved in forensics on these matters. I have a long history in safety critical systems and high value financial services, so I do get twitchy when the unexplained happens and I strive to get to the root cause. Have a great day (if there is any left!) Sorry, something went wrong. @sean-mcmanus Copy link Contributor @sean-mcmanus sean-mcmanus commented Mar 18, 2022 Yeah, there was no security attack or breach -- just an accidental usage of uninitialized memory from a modification to an external third party subsystem that doesn't follow modern C++ coding guideline that could have prevented or detected usage of uninitialized pointers (like our main code base does). Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 18, 2022 Yeah, there was no security attack or breach -- just an accidental usage of uninitialized memory from a modification to an external third party subsystem that doesn't follow modern C++ coding guideline that could have prevented or detected usage of uninitialized pointers (like our main code base does). Oof, that sounds like a deep deep deeeeeep rabbit hole to find. Good on finding though! Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 18, 2022 Can anyone tell me how I picked up this pre-release this morning without knowing? I recall seeing someone on reddit say they thought it was because they installed the language extension while it was still in pre-release. After some time had passed, the extension officially released, however vscode still had them marked down as pre-release, so it kept installing the new pre-release versions, which eventually led to some of their files becoming corrupted today. That was me. I've had my installation for the past 4 years :-). Even the 'insiders' configuration in my settings file was still there from a long long time ago. For me the insiders setting carried over, I guess, to the pre-release version of the 'new new way' that extensions were updated. But then again, this issue could easily, as it sounds, have slipped in a proper released version. So, sometimes shit just hits the fan. Sorry, something went wrong. @sean-mcmanus Copy link Contributor @sean-mcmanus sean-mcmanus commented Mar 18, 2022 @daantimmer I don't believe this bug would've made it into the non-pre-release builds, because we have a policy of shipping changes to the pre-release version first and then releasing into the non-pre-release after things seem okay after a few days...with "last minute" changes generally only occurring if we believe it's a low risk fix. Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 18, 2022 @daantimmer I don't believe this bug would've made it into the non-pre-release builds, because we have a policy of shipping changes to the pre-release version first and then releasing into the non-pre-release after things seem okay after a few days...with "last minute" changes generally only occurring if we believe it's a low risk fix. I was not trying to imply that this specific bug could have slipped through. Was trying to imply that nobody is ever perfect and mistakes can happen. Even on a thoroughly tested release. "Looking at you, any random game development studio" :-) 1 Sorry, something went wrong. @TavakoliAli Copy link @TavakoliAli TavakoliAli commented Mar 18, 2022 * edited Hello Due this bug the content of one of my source file which had 3000 line, was deleted . I don't use version control system. How can i restore it? 2 Sorry, something went wrong. @sean-mcmanus Copy link Contributor @sean-mcmanus sean-mcmanus commented Mar 18, 2022 @TavakoliAli Unfortunately, there is no way to restore the file (as far as I know). You should consider using a source control system such as git, cloud storage backup, etc.. Using the non-pre-release version of the C/C++ extension (1.8.4) would also be recommended. File deletion/corruption bugs are pretty rare. That last one we had was a couple years ago during code formatting in a multi-root workspace (microsoft/vscode-cpptools#1073). In fact, we still have a bug where formatting on a symlinked workspace folder can corrupt files (microsoft/vscode-cpptools#5061), which has a root cause of microsoft/vscode-cpptools#4573. Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 18, 2022 @sean-mcmanus , @hello-smile6 - thank you Indeed the default setting in VSC is enabled! image Wow! That seems pretty dangerous! I don't know what controls are put over the Extension Marketplace but we have just seen a small example of a change that happened invisibly and caused widespread confusion. My config is now changed from default to 'None' I can't prove it but I don't believe I opted into the pre-release version. Is there any log of Extension updates in VSC? Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 18, 2022 Due this bug the content of one of my source file which had 3000 line, was deleted . This is the first post that mentions deletion of source files? Are there other examples? So far I have detected in my system: * Creation of zero length files in the active folder in my workspace * No deletion of my code * But rewriting to zero length files in the packages folder of the extension I was using (PlatformIO in my case) - these packages could 'simply' be deleted and reloaded Sorry, something went wrong. @daantimmer Copy link @daantimmer daantimmer commented Mar 18, 2022 * edited Due this bug the content of one of my source file which had 3000 line, was deleted . This is the first post that mentions deletion of source files? Are there other examples? So far I have detected in my system. I've had source and header file contents deleted. Both in source control, but also in my windows SDK installation. I've mentioned this here and there as well :-) Sorry, something went wrong. @hello-smile6 Copy link @hello-smile6 hello-smile6 commented Mar 19, 2022 @sean-mcmanus , @hello-smile6 - thank you Indeed the default setting in VSC is enabled! image Wow! That seems pretty dangerous! I don't know what controls are put over the Extension Marketplace but we have just seen a small example of a change that happened invisibly and caused widespread confusion. My config is now changed from default to 'None' I can't prove it but I don't believe I opted into the pre-release version. Is there any log of Extension updates in VSC? Should be in /var/log or something. Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 19, 2022 Should be in /var/log or something. Sounds like Linux? not Windows 10? Sorry, something went wrong. @hello-smile6 Copy link @hello-smile6 hello-smile6 commented Mar 19, 2022 Should be in /var/log or something. Sounds like Linux? not Windows 10? Then try C:\Windows\system32\drivers\var\log or wherever logs would be stored. Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 19, 2022 Ah - if only Windows and Windows developers were so consistent! No such logs and I cannot find anything in Google searches. Perhaps @sean-mcmanus can let us know if there is such for logging installations/updates in VSC? Sorry, something went wrong. @hello-smile6 Copy link @hello-smile6 hello-smile6 commented Mar 19, 2022 Ah - if only Windows and Windows developers were so consistent! No such logs and I cannot find anything in Google searches. Perhaps @sean-mcmanus can let us know if there is such for logging installations/updates in VSC? Maybe use a VM and wine? Sorry, something went wrong. @sean-mcmanus Copy link Contributor @sean-mcmanus sean-mcmanus commented Mar 19, 2022 @mhavill I'm not familiar with any logging in regards to installation of extensions (someone on the VS Code team might know). I know that prior to VS Code's pre-release feature we had our own custom C_Cpp.updateChannel "Insiders" setting, so if you had that setting set somehow, then you got auto-migrated to the VS Code's new pre-release mechanism and we had a dialog box that appeared that prompted users to switch to the Insiders build, so you may have clicked that. Sorry, something went wrong. @mhavill Copy link @mhavill mhavill commented Mar 19, 2022 Thanks @sean-mcmanus. Maybe someone will pick it up in the future!? I won't disturb you more. My system is all back to normal with no major impact. "Insiders" setting, so if you had that setting set I am most definitely an outsider not an insider :) It'll be a mystery. Sorry, something went wrong. @TavakoliAli Copy link @TavakoliAli TavakoliAli commented Mar 19, 2022 Due this bug the content of one of my source file which had 3000 line, was deleted . This is the first post that mentions deletion of source files? Are there other examples? So far I have detected in my system: So i have all problems you mentioned. I rewrote header and deleted null files but i don't have enough time to rewrite source file. Sorry, something went wrong. @hello-smile6 Copy link @hello-smile6 hello-smile6 commented Mar 19, 2022 Could it be a disk issue? Maybe check the lost+found directory. Sorry, something went wrong. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Assignees @bpasero bpasero Labels *caused-by-extension needs more info Projects None yet Milestone No milestone Linked pull requests Successfully merging a pull request may close this issue. None yet 18 participants @bpasero @gev @spartanatreyu @kblackcn @howardlau1999 @daantimmer @sean-mcmanus @sbovbjerg @wangym307 @alexr00 @WoodsCumming @mhavill @na-an @zhanghb55 @vscode-triage-bot @hello-smile6 @RenoirTan @TavakoliAli * (c) 2022 GitHub, Inc. * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.