brunch build error #2

Closed
tdurand opened this Issue May 14, 2012 · 36 comments

Comments

Projects
None yet
5 participants

tdurand commented May 14, 2012

Hi,

I'm facing an issue when i try to use your skeleton:

brunch build
node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: write EPIPE
    at errnoException (net.js:670:11)
    at Object.afterWrite [as oncomplete] (net.js:503:19)

My configuration:

$ node -v v0.6.14 $ brunch -v 1.2.1

Thanks

Owner

nezoomie commented May 14, 2012

this works for me:

$ brunch new testeggsbacon -s git://github.com/nezoomie/brunch-eggs-and-bacon.git

$ cd testeggsbacon

$ brunch build

14 May 19:11:40 - info: compiled.

can you give me more details?

tdurand commented May 14, 2012

Do you have the same version of brunch ? (1.2.1)

$ brunch -v 1.2.1

Owner

nezoomie commented May 14, 2012

yep

perhaps it is a package version issue, because I have not updated them yet for version 1.2.1.

Please try the instructions in http://brunch.readthedocs.org/en/latest/upgrading.html#upgrading-to-1-2 and let me know if it works for you.

tdurand commented May 14, 2012

I've run a npm install at the root of the brunch project but it changes
nothing. All packages seem to be installed.

2012/5/14 nezoomie <
reply@reply.github.com

yep

perhaps it is a package version issue, because I have not updated them yet
for version 1.2.1.

Please try the instructions in
http://brunch.readthedocs.org/en/latest/upgrading.html#upgrading-to-1-2and let me know if it works for you.


Reply to this email directly or view it on GitHub:

#2 (comment)

Owner

nezoomie commented May 14, 2012

just committed the new package.json file with the new packages version updated, still work for me.

are you running brunch build from the root of your project?

tdurand commented May 14, 2012

Yep of course.

Weird, still the same issue, i tried the other skeletons of the home page
of brunch.io and it worked.

2012/5/14 nezoomie <
reply@reply.github.com

just committed the new package.json file with the new packages version
updated, still work for me.

are you running brunch build from the root of your project?


Reply to this email directly or view it on GitHub:

#2 (comment)

Owner

nezoomie commented May 14, 2012

This is weird indeed.
Could be node version? I'm running 0.6.15.

Can you try also sending me your test project?

tdurand commented May 14, 2012

I was running on 0.6.14 , i've upgraded to v0.6.17 but i'm facing the same
issue.

I don't have any project, i'm just trying to clone and build your skeleton

2012/5/14 nezoomie <
reply@reply.github.com

This is weird indeed.
Could be node version? I'm running 0.6.15.

Can you try also sending me your test project?


Reply to this email directly or view it on GitHub:

#2 (comment)

Owner

nezoomie commented May 14, 2012

perfect, create a new project that way, pack it in a .zip and send it to me

Owner

nezoomie commented May 14, 2012

ok also I stumbled upon this:

http://stackoverflow.com/questions/8673775/process-nexttick-error-in-node-js

in particular the last comment:

"For anyone else who might stumble here looking for why node pukes this error when they try to issue brunch watch --server, check and make sure you don't have any other servers running using the same port (i.e. in another shell)."

Owner

nezoomie commented May 14, 2012

I can build your test-project with no issues. Please check comment above.

tdurand commented May 14, 2012

I've already see this comment, but i'm not even trying to watch --server, i'm just trying to build.. And i don't have another brunch watch server shell open...

Maybe it's a brunch 1.2.1 issue.

Owner

nezoomie commented May 14, 2012

Are you running Ubuntu?

brunch/brunch#26

tdurand commented May 14, 2012

No, i'm running on Mac OSX Snow Leopard.

@tdurand tdurand closed this May 14, 2012

@tdurand tdurand reopened this May 14, 2012

Owner

nezoomie commented May 14, 2012

ok, let's see when it crashes.

Try to run: BRUNCH_DEBUG=1 brunch build -o build

then paste here the result

tdurand commented May 14, 2012

14 May 15:33:17 - debug: Initializing fs_utils.SourceFile: { path: '/Users/tdurand/Documents/ProjetGitHub/eggs/node_modules/handlebars-brunch/vendor/handlebars.runtime-1.0.0.beta.6.js',
  isHelper: true,
  isVendor: false }
14 May 15:33:18 - debug: Compiled file 'vendor/scripts/brunch_JavaScriptCompiler_handlebars.runtime-1.0.0.beta.6.js'
14 May 15:33:18 - debug: File '/Users/tdurand/Documents/ProjetGitHub/eggs/config.coffee' received event 'add'
14 May 15:33:18 - debug: File 'package.json' received event 'add'
14 May 15:33:18 - debug: File 'app/application.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/application.js', isHelper: false, isVendor: false }
14 May 15:33:18 - debug: File 'app/initialize.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/initialize.js', isHelper: false, isVendor: false }
14 May 15:33:18 - debug: File 'app/assets/index.html' received event 'add'
14 May 15:33:18 - debug: Compiled file 'app/application.js'
14 May 15:33:18 - debug: Compiled file 'app/initialize.js'
14 May 15:33:18 - debug: File 'vendor/scripts/backbone-0.9.2.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'vendor/scripts/backbone-0.9.2.js',
  isHelper: false,
  isVendor: true }
14 May 15:33:18 - debug: File 'vendor/scripts/backbone-mediator.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'vendor/scripts/backbone-mediator.js',
  isHelper: false,
  isVendor: true }
14 May 15:33:18 - debug: File 'vendor/scripts/console-helper.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'vendor/scripts/console-helper.js',
  isHelper: false,
  isVendor: true }
14 May 15:33:18 - debug: File 'vendor/scripts/jquery-1.7.2.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'vendor/scripts/jquery-1.7.2.js',
  isHelper: false,
  isVendor: true }
14 May 15:33:18 - debug: File 'vendor/scripts/underscore-1.3.1.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'vendor/scripts/underscore-1.3.1.js',
  isHelper: false,
  isVendor: true }
14 May 15:33:18 - debug: File 'app/assets/index.html' received event 'add'
14 May 15:33:18 - debug: File 'app/lib/router.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/lib/router.js', isHelper: false, isVendor: false }
14 May 15:33:18 - debug: File 'app/lib/view_helper.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/lib/view_helper.js',
  isHelper: false,
  isVendor: false }
14 May 15:33:18 - debug: File 'app/models/model.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/models/model.js', isHelper: false, isVendor: false }
14 May 15:33:18 - debug: File 'app/models/collection.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/models/collection.js',
  isHelper: false,
  isVendor: false }
14 May 15:33:18 - debug: File 'app/styles/main.scss' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/styles/main.scss',
  isHelper: false,
  isVendor: false }
14 May 15:33:18 - debug: File 'app/views/home_view.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/views/home_view.js',
  isHelper: false,
  isVendor: false }
14 May 15:33:18 - debug: File 'app/views/view.js' received event 'add'
14 May 15:33:18 - debug: Initializing fs_utils.SourceFile: { path: 'app/views/view.js', isHelper: false, isVendor: false }
14 May 15:33:18 - debug: Compiled file 'vendor/scripts/backbone-mediator.js'
14 May 15:33:18 - debug: Compiled file 'vendor/scripts/console-helper.js'
14 May 15:33:18 - debug: Compiled file 'vendor/scripts/underscore-1.3.1.js'
14 May 15:33:18 - debug: Compiled file 'app/lib/router.js'
14 May 15:33:18 - debug: Compiled file 'vendor/scripts/backbone-0.9.2.js'
14 May 15:33:18 - debug: Compiled file 'app/lib/view_helper.js'
14 May 15:33:18 - debug: Compiled file 'app/models/model.js'
14 May 15:33:18 - debug: File 'app/assets/images/glyphicons-halflings-white.png' received event 'add'
14 May 15:33:18 - debug: File 'app/assets/images/glyphicons-halflings.png' received event 'add'
14 May 15:33:18 - debug: Compiled file 'app/models/collection.js'
14 May 15:33:18 - debug: Compiled file 'app/views/home_view.js'
14 May 15:33:18 - debug: Compiled file 'app/views/view.js'

node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: write EPIPE
    at errnoException (net.js:670:11)
    at Object.afterWrite [as oncomplete] (net.js:503:19)```
Owner

nezoomie commented May 14, 2012

it seems it's crashing before compiling backbone.mediator.js. In config.coffee try to comment it like this:

      order:
        before: [
          'vendor/scripts/console-helper.js',
          'vendor/scripts/jquery-1.7.2.js',
          'vendor/scripts/underscore-1.3.1.js',
          'vendor/scripts/backbone-0.9.2.js'

          #'vendor/scripts/backbone-mediator.js',

and try again

Contributor

paulmillr commented May 14, 2012

I don't think commenting-out scripts will happen. The problem is much deeper.

tdurand commented May 14, 2012

Same log.

Contributor

paulmillr commented May 14, 2012

Just curious — is building a default project (brunch new app) gives you EPIPE too?

tdurand commented May 14, 2012

No, it's an issue relative to this skeleton.

It works with the default template and this one as well : https://github.com/paulmillr/brunch-with-chaplin

Contributor

paulmillr commented May 14, 2012

ಠ_ಠ

Owner

nezoomie commented May 14, 2012

yeah, same face as well.

Clueless at the moment. Not a node expert, I don't know exactly when an EPIPE error can be thrown. I'll have a better look later.

Contributor

paulmillr commented May 14, 2012

It can be an issue with simultaneous write + read. @tdurand does removing app/assets helps?

tdurand commented May 14, 2012

Okay, no problem, i was just benchmarking some tools, like brunch, maybe the next release will solve the problem. And is i really want to use it, i can make my own skeleton ;-)

Anyway, thanks for your help.

tdurand commented May 14, 2012

@paulmillr It doesn't help

Contributor

paulmillr commented May 14, 2012

The only plugin that brunch with eggs and bacon has unlike other skeletons is a Sass plugin. It could be a problem too in my opinion.

a) sass installed on the system sucks or
b) sass plugin somehow sucks

this can be checked by removing its line from package.json and removing node_modules/sass-brunch

tdurand commented May 14, 2012

Well done, brunch succeed to compile.

Contributor

paulmillr commented May 14, 2012

I've opened brunch/sass-brunch#5 for this, but because it's very hard to reproduce, not sure how to solve it.

tdurand commented May 14, 2012

Ok, i've renamed the scss file in css but i get this page when watching --server:

Cannot GET /
Owner

nezoomie commented May 14, 2012

wow you succeed isolating the problem! Do you think the os (snow leopard/lion) can make any difference?

@tdurand did you put the assets folder that Paul told you to delete back where it was?

@nezoomie nezoomie closed this May 14, 2012

Contributor

paulmillr commented May 14, 2012

Do you think the os (snow leopard/lion) can make any difference?

@tdurand 's environment certainly somehow related to this, but I don't think snow leopard is a main problem. I think brunch got more than one Sass + osx 10.6 users.

tdurand commented May 14, 2012

@nezoomie I've forgotten to replace asset, thanks !

@nezoomie @paulmillr The good thing is that i don't need saas ;-). But yep, it's a tricky issue, great job.

grumpit commented May 24, 2012

I can also confirm it's a sass issue - I had this same problem (despite not having another server instance running), OS X Lion 10.7.4, and when I removed the sass-brunch line from package.json, the issue was resolved.

Edit:

FWIW, it may be a coffeescript/sass-brunch version issue:

$ npm ls
package-name@0.0.1 /Users/grumpit/rest/of/path
]snip[
├─┬ sass-brunch@1.1.3
│ └── coffee-script@1.2.0
]snip[

$ npm ls -g
/usr/local/lib
├─┬ brunch@1.1.2
]snip[
├── coffee-script@1.3.3
└─┬ npm@1.1.21

$ coffee -v
CoffeeScript version 1.3.3

eriwen commented Jun 29, 2012

I was able to resolve this problem by using MRI 1.9 instead of JRuby and making sure sass was installed. See discussion on brunch/sass-brunch#5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment