uahaser.blogg.se - Extension install utility

#Extension install utility code#

We see that in each step, bisect reduces the search space by half. This means we have found the "bad" extension and that we are done.

The 8th extension is the only disabled extension, and the issue is gone.

The 8th extension is now disabled, things are good again and bisect proceeds on the second half, dividing it into 1 enabled and 1 disabled extension.

It divides them into 1 enabled and 2 disabled extensions. This means bisect proceeds on the first half.

Now, the 8th extension is re-enabled, and the issue has reappeared.

That means bisect can proceed on the second half (extensions 6-11), and divides them into 3 enabled and 3 disabled extensions. All other extensions are also re-enabled. Because there is still an issue, extension bisect repeats the process, dividing the first 12 extensions into two parts: 6 are enabled and 6 are disabled. Things are still not working as we'd expect.

In this sample, the 8th extension is the "bad" one, so it is the first half and not disabled.

Bisect divides 24 extensions into two halves of 12 extensions each, and it disables all 12 extensions of the second half.

Here's step by step how the "bad" extension was found: Once identified, you have the option to report an issue for that extension. The video below shows starting extension bisect via the Help: Start Extension Bisect command and then selecting either Good now or This is bad until the "bad" extension is identified. We know that the iterative approach requires 8 steps. Let's use a sample: I have 24 extensions installed and the 8th extension is "bad". For those familiar with Git, this command is helpful for finding out which commit in the repository introduced an issue.

#Extension install utility code#

The Extension bisect utility in VS Code was inspired by the git bisect command. It is much better in the worst and average cases because it disables extensions by halves.

This is where the extension bisect utility comes in handy. Because this algorithm is operated by a human (you), even small values of N are laborious. Using computer science language, this means with N extensions, you have a worst-case of repeating the process O(N) (order N), and an average-case of O(N/2). If you are lucky, the first extension is the "bad" one if you are unlucky, it's the last extension. Otherwise, re-enable the extension and repeat the process with the next extension.

If the problem is gone, that extension is "bad" and you are done. Open the Extensions view ( ⇧⌘X (Windows, Linux Ctrl+Shift+X)), disable an extension, reload the window ( Developer: Reload Window), and check to see if the problem still exists. Today, finding a "bad" extension can be easy or hard. You can use this extension to follow along in this blog post. When installed, it will annoyingly reset your cursor whenever you reach the word "bisect". This isolation guarantees that VS Code keeps running, the cursor always blinks, and that you can always save your work.įor fun, and to make it easier to demonstrate extension bisect, we have created and published the Extension Bisect Demo extension.

Fortunately, we designed VS Code with "bad" extensions in mind and therefore run them in a separate process. So, for reading ease and artificial drama, let's use the term "bad extensions", which is an extension that might crash or simply show unwanted behavior. However, like all software, extensions have bugs and feature gaps. We love extensions and don't really think there are any "bad" extensions. Instead of denial, we want to make troubleshooting easy. With so many extensions out there, bugs are inevitable. The VS Code Marketplace hosts more than 28,000 extensions and it is not uncommon that users have 50 or more extensions installed. There are extensions that play music, some that show stock tickers, and there are extensions that enable collaborative work across locations and time zones. The true power of Visual Studio Code is its extensions: theme extensions add colors and icons, language extensions enable smart code completion (IntelliSense) and navigation, debugger extensions enable you to run your code and easily find bugs. Node.js Development with Visual Studio Code and Azureįebruby Johannes Rieken, like git-bisect, but for VS Code extensions.".