Bug Report

🔎 Search Terms

comments, preserve, emit, array

🕗 Version & Regression Information

I noticed it in 4.4.2, but it seems to have happened in some form since 3.3.2 (oldest available on the playground).
The behavior appeared to change slightly after 4.2.3. (See playground link for details).

• This is the behavior in every version I tried, and I reviewed the FAQ for

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

Currently validation errors are reported as if they were internal compiler errors which makes it look like as if a bug in the compiler was triggered. A nicely formatted message should be printed instead.

For example the error caused by using --testpath with an empty value looks like this:

soltest -- --testpath

Test setup error: Throw location unknown (consider using BOOST

### 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).