sass 3.2.19 → 3.4.25

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ee87925e31efa7b2b9f04b31651d51cda825569e
-  data.tar.gz: dd0e7f384e2a5625754529631f5b510757d1e0d5
+  metadata.gz: a8b2d6c079c8e8aec59e0dd45294419919f88239
+  data.tar.gz: 5e31ebbe100aa0b066d414ee32e3f29d792907f6
 SHA512:
-  metadata.gz: a865f9ebe4cc0a8f54d7f73679ff92c19401425f1f390d5b62e574decc98768a5e5fd96d54fa10e1daf701758c8532e555664e50fcb8664d9f489de7d413ab96
-  data.tar.gz: 09311860e8236dd537d391efa8e31dd2aaa8744932e4d2ca6a6e3d56174282b173bf614faeee4c4940b2c3ff465131ce783c408f3653ce53f7fc22d118ae90d7
+  metadata.gz: 1782f895c1aaeef19491dfb41434ca10a60d28395f53a3ec19f8a65ec21c97625db3325732007fbc3155821c53adf9bcd00ced70e9fe3c1c935295b34f3dfdaf
+  data.tar.gz: 39578a844dd4d6e381cb10ced82d5c6782ddd042c79cc5c4c9cc6a69163badbf1ce368526987447b955d44a3d20470ea5e4eae481ea9359d63eea09cab94ca70

data/.yardopts

@@ -1,6 +1,6 @@
 --readme          README.md
 --markup          markdown
---markup-provider maruku
+--markup-provider redcarpet
 --default-return  ""
 --title           "Sass Documentation"
 --query           'object.type != :classvariable'
@@ -9,3 +9,5 @@
 --protected
 --no-private
 --no-highlight
+--tag             comment
+--hide-tag        comment

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,10 @@
+Sass is more than a technology; Sass is driven by the community of individuals
+that power its development and use every day. As a community, we want to embrace
+the very differences that have made our collaboration so powerful, and work
+together to provide the best environment for learning, growing, and sharing of
+ideas. It is imperative that we keep Sass a fun, welcoming, challenging, and
+fair place to play.
+
+[The full community guidelines can be found on the Sass website.][link]
+
+[link]: http://sass-lang.com/community-guidelines

data/CONTRIBUTING.md

@@ -0,0 +1,148 @@
+Contributions are welcomed. Please see the following site for guidelines:
+
+[http://sass-lang.com/community#Contribute](http://sass-lang.com/community#Contribute)
+
+* [Branches](#main-development-branches)
+  * [Feature Branches](#feature-branches)
+  * [Experimental Branches](#experimental-branches)
+  * [Old Stable Branches](#old-stable-branches)
+* [Versioning](#versioning)
+  * [Making Breaking Changes](#making-breaking-changes)
+  * [Exceptional Breakages](#exceptional-breakages)
+
+## Branches
+
+The Sass repository has three primary development branches, each of which tracks
+a different line of releases (see [versioning](#versioning) below). Each branch
+is regularly merged into the one below: `stable` into `next`, `next` into
+`master`.
+
+* The `stable` branch is the default—it's what GitHub shows if you go to
+  [sass/sass](https://github.com/sass/sass), and it's the default place for pull
+  requests to go. This branch is where we work on the next patch release. Bug
+  fixes and documentation improvements belong here, but not new features.
+
+* The `next` branch is where we work on the next minor release. It's where most
+  new features go, as long as they're not breaking changes. Very occasionally
+  breaking changes will go here as well—see
+  [exceptional breakages](#exceptional-breakages) below for details.
+
+* The `master` branch is where we work on the next major release. It's where
+  breaking changes go. We also occasionally decide that a non-breaking feature
+  is big enough to warrant saving until the next major release, in which case it
+  will also be developed here.
+
+Ideally, pull requests would be made against the appropriate
+branch, but don't worry about it too much; if you make a request against the
+wrong branch, the maintainer will take responsibility for rebasing it before
+merging.
+
+### Testing
+
+Tests for changes to the Sass language go in
+[sass-spec](https://github.com/sass/sass-spec) so that other
+implementations (E.g. libSass) can be tested against the same test
+suite. The sass-spec repo follows a "trunk development" model in that
+the tests there test against different version of the Sass language (as
+opposed to having branches that track different Sass versions). When
+contributing changes to Sass, update the Gemfile to use sass-spec from a
+branch or fork that has the new tests. When the feature lands in Sass,
+the committer will also merge the corresponding sass-spec changes.
+
+The [documentation of
+sass-spec](https://github.com/sass/sass-spec/blob/master/README.md)
+explains how to run sass-spec and contribute changes. In development,
+Change the Gemfile(s) to use the `:path` option against the sass-spec gem
+to link your local checkout of sass and sass-spec together in one or
+both directions.
+
+Changes to Sass internals or Ruby Sass specific features (E.g.
+the `sass-convert` tool) should always have tests in the Sass `test`
+directory following the conventions you see there.
+
+### Feature Branches
+
+Sometimes it won't be possible to merge a new feature into `next` or `master`
+immediately. It may require longer-term work before it's complete, or we may not
+want to release it as part of any alpha releases of the branch in question.
+Branches like this are labeled `feature.#{name}` and stay on GitHub until
+they're ready to be merged.
+
+### Experimental Branches
+
+Not all features pan out, and not all code is a good fit for merging into the
+main codebase. Usually when this happens the code is just discarded, but every
+so often it's interesting or promising enough that it's worth keeping around.
+This is what experimental branches (labeled `experimental.#{name}`) are for.
+While they're not currently in use, they contain code that might be useful in
+the future.
+
+### Old Stable Branches
+
+Usually Sass doesn't have the development time to do long-term maintenance of
+old release. But occasionally, very rarely, it becomes necessary. In cases like
+that, a branch named `stable_#{version}` will be created, starting from the last
+tag in that version series.
+
+## Versioning
+
+Starting with version 3.5.0, Sass uses [semantic versioning](http://semver.org/)
+to indicate the evolution of its language semantics as much as possible. This
+means that patch releases (such as 3.5.3) contain only bug fixes, minor releases
+(such as 3.6.0) contain backwards-compatible features, and only major releases
+(such as 4.0.0) are allowed to have backwards-incompatible behavior. There are
+[exceptions](#exceptional-breakages), but we try to follow this rule as closely
+as possible.
+
+Note, however, that the semantic versioning applies only to the language's
+semantics, not to the Ruby APIs. Although we try hard to keep widely-used APIs
+like [`Sass::Engine`][Sass::Engine] stable, we don't have a strong distinction
+between public and private APIs and we need to be able to freely refactor our
+code.
+
+[Sass::Engine]: http://sass-lang.com/documentation/Sass/Engine.html
+
+### Making Breaking Changes
+
+Sometimes the old way of doing something just isn't going to work anymore, and
+the new way just can't be made backwards-compatible. In that case, a breaking
+change is necessary. These changes are rarely pleasant, but they contribute to
+making the language better in the long term.
+
+Our breaking change process tries to make such changes as clear to users and as
+easy to adapt to as possible. We want to ensure that there's a clear path
+forward for users using functionality that will no longer exist, and that they
+are able to understand what's changing and what they need to do. We've developed
+the following process for this:
+
+1. Deprecate the old behavior [in `stable`](#branches). At minimum, deprecating
+   some behavior involves printing a warning when that behavior is used
+   explaining that it's going to go away in the future. Ideally, this message
+   will also include code that will do the same thing in a non-deprecated way.
+   If there's a thorough prose explanation of the change available online, the
+   message should link to that as well.
+
+2. If possible, make `sass-convert` (also in `stable`) convert the deprecated
+   behavior into a non-deprecated form. This allows users to run `sass-convert
+   -R -i` to automatically update their stylesheets.
+
+3. Implement the new behavior in `master`. The sooner this happens, the better:
+   it may be unclear exactly what needs to be deprecated until the new
+   implementation exists.
+
+4. Release an alpha version of `master` that includes the new behavior. This
+   allows users who are dissatisfied with the workaround to use the new
+   behavior early. Normally a maintainer will take care of this.
+
+### Exceptional Breakages
+
+Because Sass's syntax and semantics are closely tied to those of CSS, there are
+occasionally times when CSS syntax is introduced that overlaps with
+previously-valid Sass. In this case in particular, we may introduce a breaking
+change in a minor version to get back to CSS compatibility as soon as possible.
+
+Exceptional breakages still require the full deprecation process; the only
+change is that the new behavior is implemented in `next` rather than `master`.
+Because there are no minor releases between the deprecation and the removal of
+the old behavior, the deprecation warning should be introduced soon as it
+becomes clear that an exceptional breakage is necessary.

data/MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2006-2013 Hampton Catlin, Nathan Weizenbaum, and Chris Eppstein
+Copyright (c) 2006-2016 Hampton Catlin, Natalie Weizenbaum, and Chris Eppstein
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/README.md

@@ -1,14 +1,14 @@
-# Sass [![Gem Version](https://badge.fury.io/rb/sass.png)](http://badge.fury.io/rb/sass)
+# Sass [![Gem Version](https://badge.fury.io/rb/sass.svg)](http://badge.fury.io/rb/sass) [![Inline docs](http://inch-ci.org/github/sass/sass.svg)](http://inch-ci.org/github/sass/sass)
 
-**Sass makes CSS fun again**. Sass is an extension of CSS3,
+**Sass makes CSS fun again**. Sass is an extension of CSS,
 adding nested rules, variables, mixins, selector inheritance, and more.
 It's translated to well-formatted, standard CSS
 using the command line tool or a web-framework plugin.
 
 Sass has two syntaxes. The new main syntax (as of Sass 3)
 is known as "SCSS" (for "Sassy CSS"),
-and is a superset of CSS3's syntax.
-This means that every valid CSS3 stylesheet is valid SCSS as well.
+and is a superset of CSS's syntax.
+This means that every valid CSS stylesheet is valid SCSS as well.
 SCSS files use the extension `.scss`.
 
 The second, older syntax is known as the indented syntax (or just "Sass").
@@ -49,8 +49,10 @@ see [the Sass reference](http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.ht
 Sass can also be used with any Rack-enabled web framework.
 To do so, just add
 
-    require 'sass/plugin/rack'
-    use Sass::Plugin::Rack
+```ruby
+require 'sass/plugin/rack'
+use Sass::Plugin::Rack
+```
 
 to `config.ru`.
 Then any Sass files in `public/stylesheets/sass`
@@ -93,18 +95,20 @@ put them in a file called `test.scss` and run `sass test.scss`.
 Sass avoids repetition by nesting selectors within one another.
 The same thing works for properties.
 
-    table.hl {
-      margin: 2em 0;
-      td.ln { text-align: right; }
-    }
-
-    li {
-      font: {
-        family: serif;
-        weight: bold;
-        size: 1.2em;
-      }
-    }
+```scss
+table.hl {
+  margin: 2em 0;
+  td.ln { text-align: right; }
+}
+
+li {
+  font: {
+    family: serif;
+    weight: bold;
+    size: 1.2em;
+  }
+}
+```
 
 ### Variables
 
@@ -112,19 +116,21 @@ Use the same color all over the place?
 Need to do some math with height and width and text size?
 Sass supports variables, math operations, and many useful functions.
 
-    $blue: #3bbfce;
-    $margin: 16px;
+```scss
+$blue: #3bbfce;
+$margin: 16px;
 
-    .content_navigation {
-      border-color: $blue;
-      color: darken($blue, 10%);
-    }
+.content_navigation {
+  border-color: $blue;
+  color: darken($blue, 10%);
+}
 
-    .border {
-      padding: $margin / 2;
-      margin: $margin / 2;
-      border-color: $blue;
-    }
+.border {
+  padding: $margin / 2;
+  margin: $margin / 2;
+  border-color: $blue;
+}
+```
 
 ### Mixins
 
@@ -133,23 +139,25 @@ mixins allow you to re-use whole chunks of CSS,
 properties or selectors.
 You can even give them arguments. 
 
-    @mixin table-scaffolding {
-      th {
-        text-align: center;
-        font-weight: bold;
-      }
-      td, th { padding: 2px; }
-    }
-
-    @mixin left($dist) {
-      float: left;
-      margin-left: $dist;
-    }
-
-    #data {
-      @include left(10px);
-      @include table-scaffolding;
-    }
+```scss
+@mixin table-scaffolding {
+  th {
+    text-align: center;
+    font-weight: bold;
+  }
+  td, th { padding: 2px; }
+}
+
+@mixin left($dist) {
+  float: left;
+  margin-left: $dist;
+}
+
+#data {
+  @include left(10px);
+  @include table-scaffolding;
+}
+```
 
 A comprehensive list of features is available
 in the [Sass reference](http://sass-lang.com/documentation/file.SASS_REFERENCE.html).
@@ -171,6 +179,18 @@ When converting from CSS to Sass or SCSS,
 nesting is applied where appropriate.
 See `sass-convert --help` for further information and options.
 
+### Running locally
+
+To run the Sass executables from a source checkout instead of from rubygems:
+
+```
+$ cd sass
+$ bundle
+$ bundle exec sass ...
+$ bundle exec scss ...
+$ bundle exec sass-convert ...
+```
+
 ## Authors
 
 Sass was envisioned by [Hampton Catlin](http://www.hamptoncatlin.com)
@@ -179,23 +199,29 @@ and now occasionally consults on the language issues. Hampton lives in San
 Francisco, California and works as VP of Technology
 at [Moovweb](http://www.moovweb.com/).
 
-[Nathan Weizenbaum](http://nex-3.com) is the primary developer and architect of
-Sass. His hard work has kept the project alive by endlessly answering forum
-posts, fixing bugs, refactoring, finding speed improvements, writing
-documentation, implementing new features, and getting Hampton coffee (a fitting
-task for a boy-genius). Nathan lives in Seattle, Washington and works on
-[Dart](http://dartlang.org) application libraries at Google.
+[Natalie Weizenbaum](https://twitter.com/nex3) is the primary developer and
+architect of Sass. Her hard work has kept the project alive by endlessly
+answering forum posts, fixing bugs, refactoring, finding speed improvements,
+writing documentation, implementing new features, and designing the language.
+Natalie lives in Seattle, Washington and works on [Dart](http://dartlang.org)
+application libraries at Google.
 
-[Chris Eppstein](http://acts-as-architect.blogspot.com) is a core contributor to
-Sass and the creator of Compass, the first Sass-based framework. Chris focuses
+[Chris Eppstein](http://twitter.com/chriseppstein) is a core contributor to
+Sass and the creator of [Compass](http://compass-style.org/), the first Sass-based framework, and
+[Eyeglass](http://github.com/sass-eyeglass/eyeglass), a node-sass plugin ecosystem for NPM. Chris focuses
 on making Sass more powerful, easy to use, and on ways to speed its adoption
 through the web development community. Chris lives in San Jose, California with
-his wife and daughter. He is the Software Architect for
-[Caring.com](http://caring.com), a website devoted to the 34 Million caregivers
-whose parents are sick or elderly, that uses Haml and Sass.
+his wife and two children. He is an Engineer for
+[LinkedIn.com](http://linkedin.com), where his primary responsibility is to
+maintain Sass and many other Sass-related open source projects.
+
+If you use this software, we'd be truly honored if you'd make a
+tax-deductible donation to a non-profit organization and then
+[let us know on twitter](http://twitter.com/SassCSS), so that we can
+thank you. Here's a few that we endorse:
 
-If you use this software, you must pay Hampton a compliment. And
-buy Nathan some jelly beans. Maybe pet a kitten. Yeah. Pet that kitty.
+* [Trans Justice Funding Project](http://www.transjusticefundingproject.org/)
+* [United Mitochondrial Disease Foundation](http://umdf.org/compass)
+* [Girl Develop It](https://www.girldevelopit.com/donate)
 
-Beyond that, the implementation is licensed under the MIT License.
-Okay, fine, I guess that means compliments aren't __required__.
+Sass is licensed under the MIT License.

data/Rakefile

@@ -12,13 +12,116 @@ task :default => :test
 
 require 'rake/testtask'
 
-Rake::TestTask.new do |t|
-  t.libs << 'test'
-  test_files = FileList[scope('test/**/*_test.rb')]
-  test_files.exclude(scope('test/rails/*'))
-  test_files.exclude(scope('test/plugins/*'))
-  t.test_files = test_files
-  t.verbose = true
+LINE_SIZE = 80
+DECORATION_CHAR = '#'
+
+def print_header(string)
+  length = string.length
+  puts DECORATION_CHAR * LINE_SIZE
+  puts string.center(length + 2, ' ').center(LINE_SIZE, DECORATION_CHAR)
+  puts DECORATION_CHAR * LINE_SIZE
+end
+
+desc "Run all tests"
+task :test do
+  test_cases = [
+    {
+      'env'   => {'MATHN' => 'true'},
+      'tasks' => ['test:ruby', 'test:spec', :rubocop]
+    },
+    {
+      'env'   => {'MATHN' => 'false'},
+      'tasks' => ['test:ruby']
+    }
+  ]
+
+  test_cases.each do |test_case|
+    env = test_case['env']
+    tasks = test_case['tasks']
+
+    env.each do |key, value|
+      ENV[key] = value
+    end
+    tasks.each do |task|
+      print_header("Running task: #{task}, env: #{env}")
+      Rake::Task[task].execute
+    end
+  end
+end
+
+namespace :test do
+  desc "Run the ruby tests (without sass-spec)"
+  Rake::TestTask.new("ruby") do |t|
+    t.libs << 'test'
+    test_files = FileList[scope('test/**/*_test.rb')]
+    test_files.exclude(scope('test/rails/*'))
+    test_files.exclude(scope('test/plugins/*'))
+    t.test_files = test_files
+    t.warning = true
+    t.verbose = true
+  end
+
+  desc "Run sass-spec tests against the local code."
+  task :spec do
+    require "yaml"
+    sass_spec_options = YAML.load_file(scope("test/sass-spec.yml"))
+    enabled = sass_spec_options.delete(:enabled)
+    unless enabled
+      puts "SassSpec tests are disabled."
+      next
+    end
+    if ruby_version_at_least?("1.9.2")
+      old_load_path = $:.dup
+      begin
+        $:.unshift(File.join(File.dirname(__FILE__), "lib"))
+        begin
+          require 'sass_spec'
+        rescue LoadError
+          puts "You probably forgot to run: bundle exec rake"
+          raise
+        end
+        default_options = {
+          :spec_directory => SassSpec::SPEC_DIR,
+          :engine_adapter => SassEngineAdapter.new,
+          :generate => false,
+          :tap => false,
+          :skip => false,
+          :verbose => false,
+          :filter => "",
+          :limit => -1,
+          :unexpected_pass => false,
+          :nuke => false,
+        }
+        SassSpec::Runner.new(default_options.merge(sass_spec_options)).run || exit(1)
+      ensure
+        $:.replace(old_load_path)
+      end
+    else
+      "Skipping sass-spec on ruby versions less than 1.9.2"
+    end
+  end
+end
+
+# ----- Code Style Enforcement -----
+
+def ruby_version_at_least?(version_string)
+  ruby_version = Gem::Version.new(RUBY_VERSION.dup)
+  version = Gem::Version.new(version_string)
+  ruby_version >= version
+end
+
+begin
+  require 'rubocop/rake_task'
+  RuboCop = Rubocop unless defined?(RuboCop)
+  RuboCop::RakeTask.new do |t|
+    t.patterns = FileList["lib/**/*"]
+  end
+rescue LoadError
+  task :rubocop do
+    puts "Rubocop is disabled."
+    puts "Passing this check is required in order for your patch to be accepted."
+    puts "Install Rubocop and then run the style check with: rake rubocop."
+  end
 end
 
 # ----- Packaging -----
@@ -79,16 +182,13 @@ end
 
 desc "Install Sass as a gem. Use SUDO=1 to install with sudo."
 task :install => [:package] do
-  gem  = RUBY_PLATFORM =~ /java/  ? 'jgem' : 'gem' 
+  gem  = RUBY_PLATFORM =~ /java/  ? 'jgem' : 'gem'
   sh %{#{'sudo ' if ENV["SUDO"]}#{gem} install --no-ri pkg/sass-#{get_version}}
 end
 
-desc "Release a new Sass package to Rubyforge."
+desc "Release a new Sass package to RubyGems.org."
 task :release => [:check_release, :package] do
-  name = File.read(scope("VERSION_NAME")).strip
   version = File.read(scope("VERSION")).strip
-  # sh %{rubyforge add_release sass sass "#{name} (v#{version})" pkg/sass-#{version}.gem}
-  # sh %{rubyforge add_file    sass sass "#{name} (v#{version})" pkg/sass-#{version}.tar.gz}
   sh %{gem push pkg/sass-#{version}.gem}
 end
 
@@ -142,7 +242,11 @@ task :release_edge do
     sh %{git reset --hard origin/master}
     sh %{rake package}
     version = get_version
-    # sh %{rubyforge add_release sass sass "Bleeding Edge (v#{version})" pkg/sass-#{version}.gem}
+    if version.include?('.rc.')
+      puts "#{'=' * 20} Not releasing edge gem for RC version"
+      next
+    end
+
     sh %{gem push pkg/sass-#{version}.gem}
   end
 end
@@ -193,7 +297,7 @@ begin
     task :undocumented do
       opts = ENV["YARD_OPTS"] || ""
       ENV["YARD_OPTS"] = opts.dup + <<OPTS
- --list --query "
+ --list --tag comment --hide-tag comment --query "
   object.docstring.blank? &&
   !(object.type == :method && object.is_alias?)"
 OPTS
@@ -289,7 +393,7 @@ END
     file = File.read(scope("test/sass/templates/#{file || 'complex'}.sass"))
     result = RubyProf.profile { times.times { Sass::Engine.new(file).render } }
 
-    RubyProf.const_get("#{(ENV['OUTPUT'] || 'Flat').capitalize}Printer").new(result).print 
+    RubyProf.const_get("#{(ENV['OUTPUT'] || 'Flat').capitalize}Printer").new(result).print
   end
 rescue LoadError; end
 

data/VERSION

@@ -1 +1 @@
-3.2.19
+3.4.25

data/VERSION_DATE

@@ -1 +1 @@
-05 April 2014 19:55:56 UTC
+07 July 2017 22:00:34 UTC

data/VERSION_NAME

@@ -1 +1 @@
-Media Mark
+Selective Steve

data/bin/sass

@@ -9,5 +9,5 @@ rescue LoadError
 end
 require 'sass/exec'
 
-opts = Sass::Exec::Sass.new(ARGV)
+opts = Sass::Exec::SassScss.new(ARGV, :sass)
 opts.parse!

data/bin/scss

@@ -9,5 +9,5 @@ rescue LoadError
 end
 require 'sass/exec'
 
-opts = Sass::Exec::Scss.new(ARGV)
+opts = Sass::Exec::SassScss.new(ARGV, :scss)
 opts.parse!

data/extra/sass-spec-ref.sh

@@ -0,0 +1,32 @@
+#!/bin/bash -e
+# Copyright 2016 Google Inc. Use of this source code is governed by an MIT-style
+# license that can be found in the LICENSE file or at
+# https://opensource.org/licenses/MIT.
+
+# Echoes the sass-spec Git ref that should be checked out for the current Travis
+# run. If we're running specs for a pull request which refers to a sass-spec
+# pull request, we'll run against the latter rather than sass-spec master.
+
+default=master
+
+if [ "$TRAVIS_PULL_REQUEST" == "false" ]; then
+  >&2 echo "TRAVIS_PULL_REQUEST: $TRAVIS_PULL_REQUEST."
+  >&2 echo "Ref: $default."
+  echo "$default"
+  exit 0
+fi
+
+>&2 echo "Fetching pull request $TRAVIS_PULL_REQUEST..."
+
+JSON=$(curl -L -sS https://api.github.com/repos/sass/sass/pulls/$TRAVIS_PULL_REQUEST)
+
+RE_SPEC_PR="sass\/sass-spec(#|\/pull\/)([0-9]+)"
+
+if [[ $JSON =~ $RE_SPEC_PR ]]; then
+  ref="pull/${BASH_REMATCH[2]}/head"
+  >&2 echo "Ref: $ref."
+  echo "$ref"
+else
+  >&2 echo "Ref: $default."
+  echo "$default"
+fi

data/extra/update_watch.rb

@@ -7,7 +7,7 @@ enable :lock
 Dir.chdir(File.dirname(__FILE__) + "/..")
 
 post "/" do
-  puts "Recieved payload!"
+  puts "Received payload!"
   puts "Rev: #{`git name-rev HEAD`.strip}"
   system %{rake handle_update --trace REF=#{JSON.parse(params["payload"])["ref"].inspect}}
 end

data/lib/sass/cache_stores/base.rb

@@ -27,7 +27,7 @@ module Sass
 
       # Retrieved cached contents.
       # Must be implemented by all subclasses.
-      # 
+      #
       # Note: if the key exists but the sha or version have changed,
       # then the key may be deleted by the cache store, if it wants to do so.
       #
@@ -46,7 +46,7 @@ module Sass
       #
       # @param key [String] The key to store it under.
       # @param sha [String] The checksum for the contents that are being stored.
-      # @param obj [Object] The object to cache.
+      # @param root [Object] The root node to cache.
       def store(key, sha, root)
         _store(key, Sass::VERSION, sha, Marshal.dump(root))
       rescue TypeError, LoadError => e

data/lib/sass/cache_stores/chain.rb

@@ -22,7 +22,8 @@ module Sass
       # @see Base#retrieve
       def retrieve(key, sha)
         @caches.each_with_index do |c, i|
-          next unless obj = c.retrieve(key, sha)
+          obj = c.retrieve(key, sha)
+          next unless obj
           @caches[0...i].each {|prev| prev.store(key, sha, obj)}
           return obj
         end