EPERM: operation not permitted, write about vscode-eslint HOT 10 CLOSED

@ALF-er sorry for that. On which OS are you?

from vscode-eslint.

@dbaeumer Windows 10 (10586.17) x64

from vscode-eslint.

@ALF-er strange me too. Does it easy reproduce for you with the test case you once provided to me?

from vscode-eslint.

@dbaeumer sorry, looks like i'ts project-dependent. I'll try to pick out new minimal project for it tomorrow (I'm from eastern Europe)

from vscode-eslint.

@ALF-er thanks for trying to come up with a minimal project revealing the problem.

from vscode-eslint.

@dbaeumer sorry for delay here it's https://github.com/ALF-er/vscode-eslint-test Just npm install and try to lint (via VSCode) index.js

from vscode-eslint.

@ALF-er The problem is caused by the react plugin writing to console.log which when executed in a electron node environment causes an exception:

"Error: EPERM: operation not permitted, write
    at Error (native)\n    at Object.fs.writeSync (fs.js:663:20)
    at SyncWriteStream.write (fs.js:1981:6)
    at Console.log (console.js:36:16)
    at EventEmitter.module.exports.character.Program (p:\mseng\VSCode\Playgrounds\bugs\vscode-eslint-test\node_modules\eslint-plugin-react\lib\rules\jsx-quotes.js:52:15)
    at emitOne (events.js:82:20)
    at EventEmitter.emit (events.js:169:7)
    at NodeEventGenerator.enterNode (p:\mseng\VSCode\Playgrounds\bugs\vscode-eslint-test\node_modules\eslint\lib\util\node-event-generator.js:42:22)
    at CommentEventGenerator.enterNode (p:\mseng\VSCode\Playgrounds\bugs\vscode-eslint-test\node_modules\eslint\lib\util\comment-event-generator.js:98:23)
    at Controller.module.exports.api.verify.controller.traverse.enter (p:\mseng\VSCode\Playgrounds\bugs\vscode-eslint-test\node_modules\eslint\lib\eslint.js:767:36)"

This seems to be related to electron/electron#1471 and electron/electron#3482

from vscode-eslint.

and electron/electron#2033

from vscode-eslint.

I fixed this by using a separate pipe for stdio even if we use IPC communication. Nice side effect is that console.log statements of the linter now show up in a corresponding output channel.

from vscode-eslint.

Sweet! Thank you!

from vscode-eslint.