Compass `watch` broken on OS X 10.8 Mountain Lion Developer Preview (Ruby 1.8.7) #732

Closed
OliverJAsh opened this Issue Feb 24, 2012 · 19 comments

Comments

Projects
None yet
@OliverJAsh

When running $ compass watch on OS X 10.8 Mountain Lion (Developer Preview), this bug appears:

/Library/Ruby/Gems/1.8/gems/fssm-0.2.7/lib/fssm/backends/fsevents.rb:27: [BUG] Segmentation fault
ruby 1.8.7 (2011-12-28 patchlevel 357) [universal-darwin12.0]

Abort trap: 6 
@chriseppstein

This comment has been minimized.

Show comment Hide comment
@chriseppstein

chriseppstein Mar 12, 2012

Owner

We'll probably need to switch from fssm to listen in order to address this. Or maybe just upgrade fsevents. Since you're on the cutting edge, some more investigation would be greatly appreciated.

Owner

chriseppstein commented Mar 12, 2012

We'll probably need to switch from fssm to listen in order to address this. Or maybe just upgrade fsevents. Since you're on the cutting edge, some more investigation would be greatly appreciated.

@ryanjcollier

This comment has been minimized.

Show comment Hide comment
@ryanjcollier

ryanjcollier Mar 13, 2012

I updated both fsevents and the compass gem, but still get the same issue. It still works for the initial compile, but will crash on any subsequent changes to the sass. For now the only work around is to run "compass watch" each time you want to view the compiled changes. This would be a nice fix as defeats the productivity enhancements achieved by using watch ... and is quite annoying. =D

I updated both fsevents and the compass gem, but still get the same issue. It still works for the initial compile, but will crash on any subsequent changes to the sass. For now the only work around is to run "compass watch" each time you want to view the compiled changes. This would be a nice fix as defeats the productivity enhancements achieved by using watch ... and is quite annoying. =D

@scottdavis

This comment has been minimized.

Show comment Hide comment
@scottdavis

scottdavis Mar 15, 2012

Owner

can you try the latest guard from master and see if it works? if it doesn't put a ticket in for the listen gem https://github.com/guard/listen this is much higher level then compass its self.

Owner

scottdavis commented Mar 15, 2012

can you try the latest guard from master and see if it works? if it doesn't put a ticket in for the listen gem https://github.com/guard/listen this is much higher level then compass its self.

@scottdavis

This comment has been minimized.

Show comment Hide comment
@scottdavis

scottdavis Mar 15, 2012

Owner

i was going handel this from the listen side since im working on that project

Owner

scottdavis commented Mar 15, 2012

i was going handel this from the listen side since im working on that project

@scottdavis

This comment has been minimized.

Show comment Hide comment
@scottdavis

scottdavis Mar 15, 2012

Owner

freaking ninja reopening!

Owner

scottdavis commented Mar 15, 2012

freaking ninja reopening!

@scottdavis

This comment has been minimized.

Show comment Hide comment
@scottdavis

scottdavis Mar 15, 2012

Owner
@chriseppstein

This comment has been minimized.

Show comment Hide comment
@chriseppstein

chriseppstein Mar 15, 2012

Owner

Don't want to close the issue on our end until it's fixed in compass

Owner

chriseppstein commented Mar 15, 2012

Don't want to close the issue on our end until it's fixed in compass

@scottdavis

This comment has been minimized.

Show comment Hide comment
@scottdavis

scottdavis Mar 15, 2012

Owner

i added a new label to test after listen integration and tagged a few tickets

Owner

scottdavis commented Mar 15, 2012

i added a new label to test after listen integration and tagged a few tickets

@ttilley

This comment has been minimized.

Show comment Hide comment
@ttilley

ttilley Mar 16, 2012

Contributor

Nuke the ruby cocoa fsevent backend. It's been broken since lion, and just if'd out. I'll update FSSM to just destroy it, though listen is the way moving forward.

Contributor

ttilley commented Mar 16, 2012

Nuke the ruby cocoa fsevent backend. It's been broken since lion, and just if'd out. I'll update FSSM to just destroy it, though listen is the way moving forward.

@chriseppstein

This comment has been minimized.

Show comment Hide comment
@chriseppstein

chriseppstein Mar 16, 2012

Owner

Workaround on mountain lion: compass watch --poll

Owner

chriseppstein commented Mar 16, 2012

Workaround on mountain lion: compass watch --poll

@travyo

This comment has been minimized.

Show comment Hide comment
@travyo

travyo Mar 22, 2012

Was having same problem. Confirmed that above workaround works for a directory watch as well.

travyo commented Mar 22, 2012

Was having same problem. Confirmed that above workaround works for a directory watch as well.

@gpbmike

This comment has been minimized.

Show comment Hide comment
@gpbmike

gpbmike Jul 25, 2012

Contributor

Still an issue, workaround still works. :D

Contributor

gpbmike commented Jul 25, 2012

Still an issue, workaround still works. :D

@chriseppstein

This comment has been minimized.

Show comment Hide comment
@chriseppstein

chriseppstein Jul 25, 2012

Owner

Noted.

Owner

chriseppstein commented Jul 25, 2012

Noted.

@jnettik

This comment has been minimized.

Show comment Hide comment
@jnettik

jnettik Aug 1, 2012

I'm having this problem as well. Confirm workaround works.

jnettik commented Aug 1, 2012

I'm having this problem as well. Confirm workaround works.

@jnettik

This comment has been minimized.

Show comment Hide comment
@jnettik

jnettik Aug 2, 2012

So I updated the fssm gem to version 0.2.9 and compass watch seems to work again (although there is the fun message about fssm being dead that pops up now). I installed listen and nothing seems to have changed. Do I need to do something more in order to get Compass (v0.12.1/ sass v3.1.15) working with listen?

jnettik commented Aug 2, 2012

So I updated the fssm gem to version 0.2.9 and compass watch seems to work again (although there is the fun message about fssm being dead that pops up now). I installed listen and nothing seems to have changed. Do I need to do something more in order to get Compass (v0.12.1/ sass v3.1.15) working with listen?

@MoOx

This comment has been minimized.

Show comment Hide comment
@MoOx

MoOx Aug 4, 2012

Contributor

I've personally no problem with mountain lion now.

Contributor

MoOx commented Aug 4, 2012

I've personally no problem with mountain lion now.

@cri5ti

This comment has been minimized.

Show comment Hide comment
@cri5ti

cri5ti Aug 14, 2012

For me, updating the fssm (to 0.2.9) fixed the issue. I get that warning like @jnettik mentioned, but works for me. (I also reinstalled latest version of compass)

gem update fssm

cri5ti commented Aug 14, 2012

For me, updating the fssm (to 0.2.9) fixed the issue. I get that warning like @jnettik mentioned, but works for me. (I also reinstalled latest version of compass)

gem update fssm

@osserpse

This comment has been minimized.

Show comment Hide comment
@osserpse

osserpse Aug 17, 2012

Confirms that workaround on mountain lion works: compass watch --poll
But after gem update fssm there is no need for the workaround longer

Confirms that workaround on mountain lion works: compass watch --poll
But after gem update fssm there is no need for the workaround longer

@scottdavis

This comment has been minimized.

Show comment Hide comment
@scottdavis

scottdavis Oct 20, 2012

Owner

try listen branch

Owner

scottdavis commented Oct 20, 2012

try listen branch

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