Pow doesn't play well with sass 3.2.0 .sass files #316

Closed
paradox460 opened this Issue Aug 11, 2012 · 20 comments

Comments

Projects
None yet
@paradox460

I recently updated to Sass 3.2, and all my rails projects using Pow! broke. Where pages used to load fine, I get EOFErrors in the SASS file.

Steps to reproduce

  1. Start a rails project
  2. Link it to pow
  3. See that everything works right
  4. Create a .sass file
  5. Watch it fail
@Hates

This comment has been minimized.

Show comment Hide comment
@Hates

Hates Aug 11, 2012

Having the same problem. Strange that if I startup the rails server and refresh the page in that, it fixes it for pow.

Hates commented Aug 11, 2012

Having the same problem. Strange that if I startup the rails server and refresh the page in that, it fixes it for pow.

@be9

This comment has been minimized.

Show comment Hide comment
@be9

be9 Aug 12, 2012

Same here. Seems rails server regenerates some sass cache files and pow-backed app runs again.

be9 commented Aug 12, 2012

Same here. Seems rails server regenerates some sass cache files and pow-backed app runs again.

@sandelius

This comment has been minimized.

Show comment Hide comment
@sandelius

sandelius Aug 12, 2012

Same here

Same here

@walter

This comment has been minimized.

Show comment Hide comment
@walter

walter Aug 14, 2012

Ditto.

walter commented Aug 14, 2012

Ditto.

@juni0r

This comment has been minimized.

Show comment Hide comment
@juni0r

juni0r Aug 14, 2012

Sa-hame!

juni0r commented Aug 14, 2012

Sa-hame!

@be9

This comment has been minimized.

Show comment Hide comment
@be9

be9 Aug 14, 2012

Downgraded to latest 3.1.x sass, works for me.

be9 commented Aug 14, 2012

Downgraded to latest 3.1.x sass, works for me.

@juni0r

This comment has been minimized.

Show comment Hide comment
@juni0r

juni0r Aug 14, 2012

@be9: I was trying to confirm this by reproducing the error first and then downgrade sass to see if it's fixed.

However, by deleting ./tmp/cache I couldn't reproduce the error. I have no idea what running 'rails server' did to make it work with Pow, but I can't go back to the broken state.

Any version of sass now works for me in my current setup (3.1.21 and 3.2.0). What happens if you go back to 3.2.0? Does it break?

juni0r commented Aug 14, 2012

@be9: I was trying to confirm this by reproducing the error first and then downgrade sass to see if it's fixed.

However, by deleting ./tmp/cache I couldn't reproduce the error. I have no idea what running 'rails server' did to make it work with Pow, but I can't go back to the broken state.

Any version of sass now works for me in my current setup (3.1.21 and 3.2.0). What happens if you go back to 3.2.0? Does it break?

@be9

This comment has been minimized.

Show comment Hide comment
@be9

be9 Aug 14, 2012

Try to change your SASS file and it breaks again.

be9 commented Aug 14, 2012

Try to change your SASS file and it breaks again.

@juni0r

This comment has been minimized.

Show comment Hide comment
@juni0r

juni0r Aug 14, 2012

Breaks indeed. I could have figured that out by myself :)

Confirmed that sass ~> 3.1.0 works.

juni0r commented Aug 14, 2012

Breaks indeed. I could have figured that out by myself :)

Confirmed that sass ~> 3.1.0 works.

@onlymejosh

This comment has been minimized.

Show comment Hide comment
@onlymejosh

onlymejosh Aug 14, 2012

Doesn't work with 3.2.3. When I start rails server pow works again

Doesn't work with 3.2.3. When I start rails server pow works again

@patricklewis

This comment has been minimized.

Show comment Hide comment
@patricklewis

patricklewis Aug 14, 2012

@Hates Same experience for me; pow throws EOFErrors until I rails server and pow restart, at which point it works without error.

@Hates Same experience for me; pow throws EOFErrors until I rails server and pow restart, at which point it works without error.

@linjunpop

This comment has been minimized.

Show comment Hide comment
@linjunpop

linjunpop Aug 15, 2012

Here's the same issue: nex3/sass#482

Here's the same issue: nex3/sass#482

@mweppler

This comment has been minimized.

Show comment Hide comment
@mweppler

mweppler Aug 15, 2012

Took the advice from this issue:

nex3/sass#482

The assets block of my Gemfile now looks like:

group :assets do
  gem 'coffee-rails', '~> 3.2'
  gem 'sass', '3.2.0.alpha.278'
  gem 'sass-rails',   '~> 3.2'
  gem 'bootstrap-sass', '~> 2.0.4.0'
  gem 'therubyracer', :platforms => :ruby
  gem 'uglifier', '>= 1.0.3'
end

Ran:

$ bundle update

Followed by:

$ touch tmp/restart.txt

I am able to work with sass now.

Took the advice from this issue:

nex3/sass#482

The assets block of my Gemfile now looks like:

group :assets do
  gem 'coffee-rails', '~> 3.2'
  gem 'sass', '3.2.0.alpha.278'
  gem 'sass-rails',   '~> 3.2'
  gem 'bootstrap-sass', '~> 2.0.4.0'
  gem 'therubyracer', :platforms => :ruby
  gem 'uglifier', '>= 1.0.3'
end

Ran:

$ bundle update

Followed by:

$ touch tmp/restart.txt

I am able to work with sass now.

@ream88

This comment has been minimized.

Show comment Hide comment
@ream88

ream88 Aug 15, 2012

Same here :(

ream88 commented Aug 15, 2012

Same here :(

@linjunpop

This comment has been minimized.

Show comment Hide comment
@linjunpop

linjunpop Aug 16, 2012

sass/sass@c0fba44 should fix this

sass/sass@c0fba44 should fix this

@sandelius

This comment has been minimized.

Show comment Hide comment
@sandelius

sandelius Aug 16, 2012

@linjunpop Goodie! Works like a charm!

@linjunpop Goodie! Works like a charm!

@thomasklemm

This comment has been minimized.

Show comment Hide comment
@thomasklemm

thomasklemm Aug 16, 2012

Works fine. You can upgrade to gem 'sass', '3.3.0.alpha.2', it's in there. Thanks!

Works fine. You can upgrade to gem 'sass', '3.3.0.alpha.2', it's in there. Thanks!

@paradox460

This comment has been minimized.

Show comment Hide comment
@paradox460

paradox460 Aug 20, 2012

Fixed in Sass 3.2.1

Fixed in Sass 3.2.1

@paradox460 paradox460 closed this Aug 20, 2012

@ashleyconnor

This comment has been minimized.

Show comment Hide comment
@ashleyconnor

ashleyconnor Sep 22, 2012

This also happens when using compass-rails plugin, if you use @import without starting rails s first, POW blows up.

This also happens when using compass-rails plugin, if you use @import without starting rails s first, POW blows up.

@IanMitchell

This comment has been minimized.

Show comment Hide comment
@IanMitchell

IanMitchell Nov 19, 2012

I'm having problems with Compass + Susy on a Sinatra based site as well.

I'm having problems with Compass + Susy on a Sinatra based site as well.

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