Linus Unnebäck
Linus Unnebäck
Yeah, this bites me with `mocha` and `standard` for every package I publish 😄 Would love to accept a pull request, any takers? 💌
@Ionaru ```js { // ... "scripts": { "test": "standard && mocha" } } ``` Thanks for getting on top of this ❤️
Hmm, have you also added `standard` and `mocha` to your dependencies? ```sh npm install --save-dev standard mocha ```
@alanshaw any thoughts on merging this? ☺️
I'm calling `readImage` and `detectObject` with a buffer that I provide. e.g. ``` js function hasFaces (buffer, cb) { opencv.readImage(buffer, function (err, image) { if (err) { return cb(err); }...
I just tried again and I'm very sure that the buffers are alright. I've tried rerunning the script numerous times, only changing the number of jobs that runs in parallel....
I also tried to remove the `image.detectObject` and only load the buffers into opencv. It worked and didn't crash a single time.
Don't know if this is relevant but I _might_ have found a bug in the c++ code. Detecting faces is done with the help of `uv_queue_work` which basically means that...
I'm not too familiar with opencv but from my understanding the code currently just loads the cascade file once inside the `CascadeClassifierWrap` constructor. If you look at the function `matrix.detectObject`...
Okay, so I added in a test case (I didn't really get along with vows, can't I use assert in an async function? wtf?) and I actually got a segmentation...