Note: This is still up for debate, but we think this is a pretty strong contender to ship. We may still change our minds on details. So, if you give it a shot, expect some of us to come in and maybe make changes at the end of the PR's lifecycle.

Suggestion

As of 4.4, a run of tsc looks like:

$ /Users/ortatherox/dev/typescript/repros/compilerSamples/node_modules/.bin/tsc
inde

Hello,

I recently upgraded to Node v4.17.5 and it seems a newly added exception there is breaking my Less build.

I'm using less v4.1.1 and less-plugin-autoprefix v2.0.0. To recreate the issue I've -

1. Installed the above packages globally
2. Created a less file (test.less) with the following content -

p {
    color: blue;
}

3. On the command line, run -
   `lessc test.less tes

This came up in ethereum/solidity#11861 (comment).

Abstract

If you search the repo for Disabled because of Spacer nondeterminism, you'll see that we have quite a few SMTChecker tests where assertions had to be disabled due to results not being deterministic between platforms. The workaround is to comment-out these assertions, which disables them on all

### Example
let unreachableProxy = "http://127.0.0.1:8888"
try:
  let client = newHttpClient(proxy=newProxy(unreachableProxy), timeout=1)
  var res = client.getContent("https://github.com")
  echo res
except:
  echo "Timed out"

Current Output

timeout variable is ignored, program stuck until default socket timeout will happen

Expected Output

Timed out a

It would be useful to have a java.util.BitSet implementation. It looks like most Java collections are available but this one fell through the cracks (perhaps because it's not part of the Collection hierarchy).