Maximum call stack size exceeded on gulp test:server

[ingoncalves]

After generate my app and run it normally, I simulated an error on server/api/user/user.integration.js adding code:
res.body.foo.should.equal('bar');
on line 54.

The test froze and I got the following error:

GET /api/users/me 200 12.153 ms - 102
/home/user/myapp/node_modules/gulp-mocha/index.js:47
                    stack: err.stack,
                              ^
RangeError: Maximum call stack size exceeded
  at Array.join (native)
  at Function.Error.prepareStackTrace (/home/user/myapp/node_modules/coffee-script/lib/coffee-script/coffee-script.js:373:46)
  at Domain.handleException (/home/user/myapp/node_modules/gulp-mocha/index.js:47:16)
  at emitOne (events.js:90:13)
  at Domain.emit (events.js:182:7)
  at emitError (domain.js:66:24)
  at Domain.errorHandler [as _errorHandler] (domain.js:110:18)
  at process._fatalException (node.js:234:33)
  at Domain.errorHandler [as _errorHandler] (domain.js:137:26)
  at process._fatalException (node.js:234:33)
  at Domain.errorHandler [as _errorHandler] (domain.js:137:26)
  at process._fatalException (node.js:234:33)
...

Item	Version
OS	Ubuntu 16.04
generator-angular-fullstack	3.6.1
node	5.11.0
npm	3.8.8
yo	1.7.0
mocha	2.4.5

Item	Answer
Transpiler	Babel
Markup	Jade
CSS	SCSS
Router	ui-router
Build Tool	Gulp
Client Tests	Mocha
DB	MongoDB
Auth	Y

[Awk34]

The call to coffee-script seems suspicious

[ingoncalves]

You need any more information?

[Awk34]

Any extra info couldn't hurt

[ingoncalves]

I reproduce this issue in another computer and got the following error:

/home/user/myapp/node_modules/gulp-util/lib/PluginError.js:45
        self[prop] = options.error[prop];
                                  ^

RangeError: Maximum call stack size exceeded
  at /home/user/myapp/node_modules/gulp-util/lib/PluginError.js:45:35
  at Array.forEach (native)
  at new PluginError (/home/user/myapp/node_modules/gulp-util/lib/PluginError.js:44:8)
  at Domain.handleException (/home/user/myapp/node_modules/gulp-mocha/index.js:46:24)
  at emitOne (events.js:90:13)
  at Domain.emit (events.js:182:7)
  at emitError (domain.js:66:24)
  at Domain.errorHandler [as _errorHandler] (domain.js:110:18)
  at process._fatalException (node.js:234:33)
  at Domain.errorHandler [as _errorHandler] (domain.js:137:26)
  at process._fatalException (node.js:234:33)
  at Domain.errorHandler [as _errorHandler] (domain.js:137:26)
  at process._fatalException (node.js:234:33)
  at Domain.errorHandler [as _errorHandler] (domain.js:137:26)
  at process._fatalException (node.js:234:33)
  ... many lines later
  at Domain.errorHandler [as _errorHandler] (domain.js:110:18)
  at process._fatalException (node.js:234:33)

Item	Version
OS	Ubuntu 14.04
node	5.11.0
npm	3.8.8
yo	1.7.0
mocha	2.4.5

PS: the code tested is the same, just clone my git repo and run test in another computer.

[ingoncalves]

@Awk34 can you reproduce?

I was analyzing that error and I arrived on gulp-mocha plugin.
This erro has been fixed on sindresorhus/gulp-mocha#114, but the latest version was not yet released to npm.

So i installed this module by:

npm  install --save-dev https://github.com/sindresorhus/gulp-mocha.git

[Awk34]

Does installing from master fix it?

[ingoncalves]

Installing gulp-mocha from master fix it

[Awk34]

@ingoncalves okay well I guess we'll just have to wait for the next patch version to be released

[huyouare]

Still experiencing this issue, but @ingoncalves solution fixed it.

[Awk34]

3.0.1 is the latest version, we'll have to make sure we use that one