Skip to content

[0.6.0] Throws exception when using node cli via child_process #176

@brentlintner

Description

@brentlintner

Steps to Reproduce:

git clone [email protected]:blackberry-webworks/Ripple-UI.git 
git checkout 3561ad5a755232c3e0a8ee01a11736a9dedfce69
./configure
npm install -g [email protected]
jake lint

Expected: CSSLint to run properly

Actual: Crashes with this trace:

node.js:134
    throw e; // process.nextTick error, or 'error' event on first tick
    ^
Error: ENOTSUP, Operation not supported
    at Object.fsyncSync (fs.js:352:18)
    at Object.print (/Users/brent/local/node/lib/node_modules/csslint/cli.js:208:12)
    at processFile (/Users/brent/local/node/lib/node_modules/csslint/cli.js:73:17)
    at /Users/brent/local/node/lib/node_modules/csslint/cli.js:129:36
    at Array.forEach (native)
    at processFiles (/Users/brent/local/node/lib/node_modules/csslint/cli.js:127:23)
    at cli (/Users/brent/local/node/lib/node_modules/csslint/cli.js:193:14)
    at Object.<anonymous> (/Users/brent/local/node/lib/node_modules/csslint/cli.js:203:1)
    at Module._compile (module.js:402:26)
    at Object..js (module.js:408:10)

Note: The CLI is being executed via the child_process module and that is where it seems to fail. Running it straight in the terminal works as expected, so I have not ruled out the possibility it is still our code causing the issue. I plan to look into it more when I can, but it seems like a CSSLint specific bug (as everything works in 0.5.0).

System

  • OSX 10.6.8
  • Node v0.4.11, NPM v1.0.22

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions