Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node --use_strict fails silently #302

Closed
mLuby opened this issue Oct 25, 2015 · 2 comments
Closed

node --use_strict fails silently #302

mLuby opened this issue Oct 25, 2015 · 2 comments
Labels

Comments

@mLuby
Copy link

mLuby commented Oct 25, 2015

repro: use the wallaby-node-iojs-sample with the following changes:

  1. remove 'use strict'; from calculator.js and calculatorSpec.js.
  2. replace --harmony --harmony_arrow_functions with --use_strict in wallaby.js

After restarting wallaby, it reports 0 out of 0 tests (should be 1 passed); debugger shows this error:

Sun, 25 Oct 2015 18:45:43 GMT wallaby:project File cache requires some updates, waiting required files from IDE
Sun, 25 Oct 2015 18:45:43 GMT wallaby:extended-core New document or complex document change
Sun, 25 Oct 2015 18:45:43 GMT wallaby:project File lib/calculator.js changes are patches only: false
Sun, 25 Oct 2015 18:45:43 GMT wallaby:project File test/calculatorSpec.js changes are patches only: false
Sun, 25 Oct 2015 18:45:43 GMT wallaby:project Preparing to process lib/calculator.js
Sun, 25 Oct 2015 18:45:43 GMT wallaby:project Starting processor pool (if not yet started)
Sun, 25 Oct 2015 18:45:43 GMT wallaby:project Preparing to process test/calculatorSpec.js
Sun, 25 Oct 2015 18:45:43 GMT wallaby:project Starting processor pool (if not yet started)
Sun, 25 Oct 2015 18:45:43 GMT wallaby:nodeRunner Error in worker: TypeError: Cannot read property 'addEventListener' of undefined
    at /Users/me/.atom/packages/atom-wallaby/wallaby/server.js:18:23847
    at Object.32 (/Users/me/.atom/packages/atom-wallaby/wallaby/server.js:19:3781)
    at e (/Users/me/.atom/packages/atom-wallaby/wallaby/server.js:14:254)
    at /Users/me/.atom/packages/atom-wallaby/wallaby/server.js:14:305
    at Object.n (/Users/me/.atom/packages/atom-wallaby/wallaby/server.js:16:21012)
    at b.exports (/Users/me/.atom/packages/atom-wallaby/wallaby/server.js:16:22734)
    at Object.39../lib/app (/Users/me/.atom/packages/atom-wallaby/wallaby/server.js:19:19316)
    at e (/Users/me/.atom/packages/atom-wallaby/wallaby/server.js:14:254)
    at a (/Users/me/.atom/packages/atom-wallaby/wallaby/server.js:14:421)
    at Object.<anonymous> (/Users/me/.atom/packages/atom-wallaby/wallaby/server.js:14:438)
@ArtemGovorov
Copy link
Member

Thanks for the repro steps, the issue is fixed in core v1.0.134.

@mLuby
Copy link
Author

mLuby commented Oct 26, 2015

@ArtemGovorov did you mean Wallaby v1.0.134? I found the above in atom-wallaby v1.0.6 (and node v4.0.0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants