Stack level too deep during asset precompilation

[hron84]

Hi!

I experienced with 'stack level too deep' problem with asset precompilation. I am not sure its active_admin bug or bug in sprockets... but this is broken during i didn;t touched my code.

Rake output: https://gist.github.com/cabd748595a75a2619d9

In development mode, application works correctly, so the problem is around precompilation, not the normal compilation.

About your application's environment
Ruby version              1.8.7 (x86_64-linux)
RubyGems version          1.8.21
Rack version              1.3
Rails version             3.1.3
JavaScript Runtime        therubyracer (V8)
Active Record version     3.1.3
Action Pack version       3.1.3
Active Resource version   3.1.3
Action Mailer version     3.1.3
Active Support version    3.1.3
Middleware                ActionDispatch::Static, Rack::Lock, #<ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x7fd34dacd1e0>, Rack::Runtime, Rack::MethodOverride, Rails::Rack::Logger, ActionDispatch::ShowExceptions, ActionDispatch::RemoteIp, Rack::Sendfile, ActionDispatch::Reloader, ActionDispatch::Callbacks, ActiveRecord::ConnectionAdapters::ConnectionManagement, ActiveRecord::QueryCache, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ParamsParser, ActionDispatch::Head, Rack::ConditionalGet, Rack::ETag, ActionDispatch::BestStandardsSupport, Warden::Manager
Application root          /home/hron/Projects/job/rwh/rhcp

[latortuga]

Run with --trace and post a stack trace please.

[hron84]

@latortuga please take look into the gist. Last file is the stack trace

[hron84]

Hmm... it seems sass-rails 3.1.6 sucked me, because sass 3.2 does not like one of activeadmin scss files. I still dunno what is the real problem, but downgrading sass-rails to 3.1.5 vanished this bug. However, I keep issue open, because it is should be related to sass 3.2.

[jpmckinney]

It's a Sass bug, so it has to be fixed there: rails/sass-rails#78

[hron84]

@jpmckinney thanks for pointing to that issue. I'll track it.