![]() I suspect this is hard to repro because it probably has more to do with the large number of cascading errors that stems from removing one fragment closure line than removal of the line itself. The only way I've found to recover from this state is to sigterm the electron thread at 100% load or to restart vscode (at which point, with the replaced fragment close, will continue to format correctly) This problem happens both with the prettier plugin or the eslint vscode plugin (because we use the prettier plugin for eslint.) I'm not sure where the failure is really happening, probably on the first save after line delete and then isn't recovering on the second. Save again, you should find that the preceding errors were not cleared and the format will no longer run, instead it "hangs" and uses 100% cpu (well on one thread anyway).Saving, you should see eslint give you 70 odd errors. ![]() ![]() Delete this fragment close line, you may need to add some tabs/line blanks to trigger it.Add a couple of newlines and save to confirm format on save is working as expected.Open the repo with vscode and prettier (or eslint plugin as we use the prettier eslint plugin).Everyone was I'm able to mostly consistently repro this, That's the best solution I could find even after consulting associates and friends for help. Go for a fresh install and try to make sure that you don't have too many things which could effect formatting. Save yourself the headache and just make note of the important settings. It's the worst kind of bug because you don't get any logs to reference regarding what's happening behind the scenes, other people can't reproduce it because I think it has something to do with your settings (ESLint, Prettier, Vetur, etc.) Now I don't have the issue anymore but I was never able to get to the bottom of it and I tried hard. I ended up having to play with a lot of settings and extensions to get everything to feel normal for me again since I work largely with VueJS. Once I started reinstalling extensions, it became apparent that I have really customized my editor to my liking over the past several months and I thought that I would be able to remember all of the settings that I was using but I couldn't even come close. When I tried to back everything up before taking the nuclear option, the problem just persisted so I realize I had to wipe everything out if I was going to truly fix this. I deleted all the temporary files, cleared the caches, started with a fresh install and reinstalled all of my extensions once again. I eventually realized that I was wasting an absurd amount of time on this one problem and I uninstalled every version of VS Code that I had on my computer. I was never able to solve this issue and I spent countless hours debugging it over the course of two very frustrating months that it was happening.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |