Jeff Levesque

Got the same thing, with my [`package.json`](https://github.com/jeff1evesque/machine-learning/blob/ec62640e0839ac9feb58b19d8c08a648baa70c44/src/package.json): ```bash root@trusty64:/home/vagrant# /usr/bin/npm install react-rangeslider@^2.2.0 --no-bin-links /home/vagrant ├── UNMET PEER DEPENDENCY react@^0.14.0 || ^15.0.0 └─┬ [email protected] ├── [email protected] └── [email protected] npm WARN enoent...

@jseminck, @tizmagik: sorry to bother in this thread. I'm using jest + enzyme, and hoping to pipe the coverage results to coveralls. So, I implemented `test:coveralls`, a `script` from my...

@jseminck, @tizmagik: nevermind, I think I've fixed it. The corresponding travis [build](https://travis-ci.org/jeff1evesque/machine-learning/jobs/386322980#L593-L594), seems to have run the following without erroring: ```bash cat lcov.info | ./node_modules/coveralls/bin/coveralls.js ``` I guess I'll merge...

Ah, didn't have to wait for PR to be merged. Seems like the configurations [worked](https://coveralls.io/builds/17257835). Thank you everyone, pretty much recycled different aspects from various comments in this issue.

The following is a lazy googling result suggesting against using PCA for SVM's: - https://www.quora.com/Is-it-worth-trying-PCA-on-your-data-before-feeding-to-SVM

We are removing this issue from [milestone 0.4](https://github.com/jeff1evesque/machine-learning/milestone/9) for [similar reasons](https://github.com/jeff1evesque/machine-learning/issues/2297#issuecomment-247207592) as #2297.

Since this issue would greatly improve the user experience, it will be better placed with [milestone 0.7](https://github.com/jeff1evesque/machine-learning/milestones/0.7).

This issue is related to #2300. Therefore, we'll relocate this to milestone 0.8.

The above `500` error is achieved when the correct port rules are configured to be open. Otherwise, variations of different http errors are returned. However, the former http error indicates...

Part of our earlier confusion was due to the fact that the reverse proxy for the backend api, was configured on port `9595`. However, we were making a request the...