I'm not able to explain this bug perfectly since I'm not an asset pipeline expert, so forgive any terminology mistakes.
I have a Rails app running the asset pipeline with sass-rails. I also am mounting a Sinatra application in that Rails app which has its own non-Rails-based Sprockets / compass middleware. sass-rails' configuration is global and breaks the Sinatra sass pipeline. I believe this bug is fixed in this branch:
The Sinatra application is here:
What do you think?
@mperham Is this still an issue?
No, because I pulled out all sprockets/sass-related stuff. Easier just to reduce dependencies.