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

Leak Checking Output #315

Closed
timcosta opened this issue Mar 2, 2015 · 6 comments
Closed

Leak Checking Output #315

timcosta opened this issue Mar 2, 2015 · 6 comments
Assignees
Labels
support Questions, discussions, and general support

Comments

@timcosta
Copy link
Contributor

timcosta commented Mar 2, 2015

I'm confused by the output of the leak checking being run, which is The following leaks were detected:$M, $P, $V, $L.

Do any of you know what those symbols mean? I couldnt find them mentioned anywhere in this repo.

@cjihrig
Copy link
Contributor

cjihrig commented Mar 2, 2015

Those symbols are from the code that is being tested.

@geek geek added the question label Mar 2, 2015
@geek geek closed this as completed Mar 2, 2015
@krazik
Copy link

krazik commented May 30, 2016

I'm encountering this same error, I've tracked it to a 3rd party package I'm using but can't find the source. is there a workaround when you can't control the other code?

The following leaks were detected:$V, $M, $L, $P

@krazik
Copy link

krazik commented May 30, 2016

found the source: NaturalNode/node-sylvester#6

@cjihrig
Copy link
Contributor

cjihrig commented May 30, 2016

If the leak is out of your control, you can whitelist the global using -I. An example is here https://github.com/continuationlabs/big-time/blob/master/package.json#L7

@alexandrebodin
Copy link

@krazik Too ignore those leaks:

package.json

{
    "scripts": {
        "test": "lab -S -T test/babelTransform.js -I '$L,$V,$P,$M'"
    }
}

@Marsup Marsup added support Questions, discussions, and general support and removed question labels Sep 21, 2019
@lock
Copy link

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
support Questions, discussions, and general support
Projects
None yet
Development

No branches or pull requests

6 participants