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

Assertion error when starting wallaby #1124

Closed
kristojorg opened this issue Apr 18, 2017 · 4 comments
Closed

Assertion error when starting wallaby #1124

kristojorg opened this issue Apr 18, 2017 · 4 comments

Comments

@kristojorg
Copy link

Issue description or question

When I start wallaby I am sometimes given an error:

​​[Error] Runtime error: Assertion failed: (handle->type == UV_TCP || handle->type == UV_TTY || handle->type == UV_NAMED_PIPE), function uv___stream_fd, file ../deps/uv/src/unix/stream.c, line 1591.​​

This appears to happen when there is also some syntax or other error in my code.

Wallaby.js configuration file

module.exports = function(wallaby) {
  return {
    files: [
      'src/**/*.js',
      '!src/**/*.test.js',
      { pattern: '.env', instrument: false },
    ],

    tests: ['__tests__/**/*.test.js', 'src/**/*.test.js'],

    env: {
      type: 'node',
    },
    testFramework: 'jest',
    compilers: {
      '**/*.js': wallaby.compilers.babel(),
    },

    workers: {
      recycle: true,
    },
  };
};

Code editor or IDE name and version

Visual Studio Code v1.11.2

OS name and version

OSX 10.12.3

@ArtemGovorov
Copy link
Member

The issue doesn't seem to be wallaby specific. It actually may not even be specific to your tests, but may also come up in your app at some point.

According to this, it happens when there's memory corruption in node because of some native modules that you may be using (wallaby itself doesn't use any native modules).

I'd suggest trying to exclude some native modules in question, and see it it helps. If it does, then I'd perhaps report the issue to that module repo.

@kristojorg
Copy link
Author

Thank you, sorry for the misplaced issue

@ArtemGovorov
Copy link
Member

No worries at all, please let me know if you find the module that is causing the issue, I'm interested to know what it was.

@kristojorg
Copy link
Author

kristojorg commented Apr 18, 2017

It ended up being related to a deasync library being called in massive js module for postgres database querying. 😢 I just want an easy node database

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

No branches or pull requests

2 participants