SAPikachu / icomoon-build

Build IcoMoon project in Node
MIT License
27 stars 9 forks source link

Error breaking my GULP #3

Closed yairEO closed 10 years ago

yairEO commented 10 years ago

I've been using your icomoon-build for many months now without a problem, and today, after updating the JSON from icomoon, i suddenly see this error that breaks everything:

C:\Users\vsync\AppData\Roaming\npm\node_modules\icomoon-build\lib\cli.js:10
            throw err;
                  ^
Error: stdout maxBuffer exceeded.
    at Socket.<anonymous> (child_process.js:689:13)
    at Socket.emit (events.js:95:17)
    at Socket.<anonymous> (_stream_readable.js:764:14)
    at Socket.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:426:10)
    at emitReadable (_stream_readable.js:422:5)
    at readableAddChunk (_stream_readable.js:165:9)
    at Socket.Readable.push (_stream_readable.js:127:10)
    at Pipe.onread (net.js:528:21)
[gulp] Errored 'icomoon' in 10 s Command failed:
C:\Users\vsync\AppData\Roaming\npm\node_modules\icomoon-build\lib\cli.js:10
            throw err;
                  ^
Error: stdout maxBuffer exceeded.
    at Socket.<anonymous> (child_process.js:689:13)
    at Socket.emit (events.js:95:17)
    at Socket.<anonymous> (_stream_readable.js:764:14)
    at Socket.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:426:10)
    at emitReadable (_stream_readable.js:422:5)
    at readableAddChunk (_stream_readable.js:165:9)
    at Socket.Readable.push (_stream_readable.js:127:10)
    at Pipe.onread (net.js:528:21)

C:\xampp\htdocs\gurushots\html\trunk\website\node_modules\gulp\node_modules\orchestrator\index.js:153
                        throw err;
                              ^
Error: Command failed:
C:\Users\vsync\AppData\Roaming\npm\node_modules\icomoon-build\lib\cli.js:10
            throw err;
                  ^
Error: stdout maxBuffer exceeded.
    at Socket.<anonymous> (child_process.js:689:13)
    at Socket.emit (events.js:95:17)
    at Socket.<anonymous> (_stream_readable.js:764:14)
    at Socket.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:426:10)
    at emitReadable (_stream_readable.js:422:5)
    at readableAddChunk (_stream_readable.js:165:9)
    at Socket.Readable.push (_stream_readable.js:127:10)
    at Pipe.onread (net.js:528:21)

    at ChildProcess.exithandler (child_process.js:648:15)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:756:16)
    at Socket.<anonymous> (child_process.js:969:11)
    at Socket.emit (events.js:117:20)
    at Pipe.close (net.js:465:12)
yairEO commented 10 years ago

I think the problem is the icomoon generated 2 icons with the same code:

"code": 58938

Very odd.

SAPikachu commented 10 years ago

Can you upload the JSON to pastebin (or somewhere else) and link it here? Need the file to see what exactly caused the error.

yairEO commented 10 years ago

no it's actually not what I've said. I now confirmed it that some SVG I added which broke things.

The name of the SVG in the JSON is oliveBranch_right

here's the JSON file - http://kl1p.com/Q6ab alternative link - http://sharetext.org/hsz5

SAPikachu commented 10 years ago

Sorry for the delay, was a bit busy in last 2 days.

This problem was not caused by any specific icon, just because the icon set was too big and exceeded limit of child_process. Relaxed the limit and it works again.