Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

CSS

Scott Reuber
PLUS
Scott Reuber
Courses Plus Student 12,756 Points
Posted by Scott Reuber
Scott Reuber
Courses Plus Student 12,756 Points

Trying to use Sass after Installing Ruby Development Environment is a disaster

I'm on OS X Mavericks, followed the instructions for setting up a Ruby development environment for Mac, from Jason's lesson. Everything installed OK with no errors, including SASS and Compass, which were a part of that lesson.

Now I just tried to use Sass on two test files, I get this:

$ sass --watch test.scss:test.css
>>> Sass is watching for changes. Press Ctrl-C to stop.
      write test.css
NoMethodError:

Yeah, WTF. Tried stopping, got this:

^Cundefined method `thread' for #<Listen::Listener:0x007fc2222295e8>
  Use --trace for backtrace.

Did not stop Sass yet, so did Ctrl + C again:

^C/Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid/thread_handle.rb:36:in `join': Interrupt
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid/actor.rb:129:in `join'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:162:in `block (2 levels) in shutdown'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:160:in `each'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:160:in `block in shutdown'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:144:in `shutdown'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:131:in `block in register_shutdown'

So yeah, I have zero idea what is going on here. One of those moments where anyone who tells me, or any other designer, that the Command Line "isn't hard", I give them the stink eye.

Full console:

$ sass --watch test.scss:test.css
>>> Sass is watching for changes. Press Ctrl-C to stop.
      write test.css
NoMethodError: ^Cundefined method `thread' for #<Listen::Listener:0x007fc2222295e8>
  Use --trace for backtrace.
^C/Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid/thread_handle.rb:36:in `join': Interrupt
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid/actor.rb:129:in `join'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:162:in `block (2 levels) in shutdown'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:160:in `each'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:160:in `block in shutdown'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:144:in `shutdown'
    from /Users/scott/.rbenv/versions/2.0.0-p451/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib/celluloid.rb:131:in `block in register_shutdown'

2 Answers

James Barnett
James Barnett
39,199 Points
James Barnett
James Barnett
39,199 Points

According to the Sass change log there's a bug in Sass version 3.3.0, it's supposed to be fixed in Sass version 3.3.2.

Scott Reuber
Scott Reuber
Courses Plus Student 12,756 Points
Scott Reuber
Scott Reuber
Courses Plus Student 12,756 Points

So, being the terminal-phobe I am, is sudo gem update sass all I need?

Scott Reuber
Scott Reuber
Courses Plus Student 12,756 Points
Scott Reuber
Scott Reuber
Courses Plus Student 12,756 Points

Did the trick. Thanks much. One of these days terminal and I will get along a little better.

Adam Sackfield
PLUS
Adam Sackfield
Courses Plus Student 19,663 Points
Adam Sackfield
Adam Sackfield
Courses Plus Student 19,663 Points

I had this issue the other day on Windows. Even though had Sass and Ruby installed for ages. Anyway this fix worked for me.

gem uninstall listen

// then

gem install listen --version '2.4.1'

If not then this post may guide you to the correct place github