osinfo | Platform Module for Collecting OS Information

After noting the various comments and other posts, I've not found a reason not to continue using the isWindows check I currently have in my code, which is simply the first test listed:

https://play.golang.org/p/jzU_lHj1wk7

Other than the usual suspects (process.exit(), or process termination/signal, or crash/hardware failure), are there any circumstances where code in a finally block will not be reached?

If the promise will resolve or reject in future then it should reach to the final block.

According to the MDN docs,

The finally-block contains statements to execute after the try-block and catch-block(s) execute, but before the statements following the try...catch...finally-block. Note that the finally-block executes regardless of whether an exception is thrown. Also, if an exception is thrown, the statements in the finally-block execute even if no catch-block handles the exception.

A promise is just a JavaScript object. An object can have many states. A promise object can be in pending state or settled state. The state settled can divide as fulfilled and rejected. For this example just imagine we have only two state as PENDING and SETTLED.

Now if the promise never resolve or reject then it will never go to the settled state which means your then..catch..finally will never call. If nothing is reference to the promise then it will just garbage collected.

In your original question you mentioned about a 3rd party async method. If you see that code, the first thing you can see is, there are set of if(..) blocks to determine the current OS. But it does not have any else block or a default case.

What if non of the if(..) blocks are trigger ? There is nothing to execute and you already returned a promise with return new Promise(). So basically if non of the if(..) blocks are triggered, the promise will never change its state from pending to settled.

And then as @Bergi also mentioned there are some codes like this. A classic Promise constructor antipattern as he mentioned. For example see the below code,

You are nearly there, you need to have both carriage return and linefeed.

So instead of +#13+ you need +#13+#10+ or you can use +#13#10+

I suspect that you will also then need to Percent Encode the string that's set to the Body value to pass it properly in the URL.

You can use TURLEncoding.Encode() for this.

res.end(Hello, world!

Hello, world!

The HTML you send back from here (and throughout your code) needs to be in a string so it can parse it and then send that HTML later on because you can't just put HTML anywhere in Javascript (and this isn't React for example).

use ls -ld /usr/share to see what the permissions on the directory are (without -d, you get the contents and their permissions).

Use code like:

As you just removed the files instead of using apt-get or dpkg to uninstall the package, the package management is not aware of your manual removal, and so apt-get and dpkg still think the newest version is already installed, and so do nothing.

apt-get --reinstall install vagrant

should solve this.

you can use pipe map from RxJs

The solution ended up being to do it in the constructor. Some alternatives were mentioned in the comments, and seem like they might suit other use cases better.