From 2fac77cc488011925d8d972595c997bd0cef869f Mon Sep 17 00:00:00 2001
From: Joffrey JAFFEUX <j.jaffeux@gmail.com>
Date: Fri, 21 Aug 2020 13:46:46 +0200
Subject: [PATCH] DEV: upgrades sassc to 2.4.0 (#10447)

We were stuck on 2.0.1 but multiple reports on the original issue shows that the issue has been fixed since 2.3 and 2.4:

https://github.com/sass/sassc-ruby/issues/146#issuecomment-654522157
https://github.com/sass/sassc-ruby/issues/146#issuecomment-654522157

There's one report show it was not fixed in 2.3.0, but that's the only one, it's probably worth trying: https://github.com/sass/sassc-ruby/issues/146#issuecomment-639073736
---
 Gemfile      | 4 +---
 Gemfile.lock | 5 ++---
 2 files changed, 3 insertions(+), 6 deletions(-)

diff --git a/Gemfile b/Gemfile
index 19bd41d097..050a8145ef 100644
--- a/Gemfile
+++ b/Gemfile
@@ -218,9 +218,7 @@ gem 'logstash-event', require: false
 gem 'logstash-logger', require: false
 gem 'logster'
 
-# NOTE: later versions of sassc are causing a segfault, possibly dependent on processer architecture
-# and until resolved should be locked at 2.0.1
-gem 'sassc', '2.0.1', require: false
+gem 'sassc', '2.4.0', require: false
 gem "sassc-rails"
 
 gem 'rotp', require: false
diff --git a/Gemfile.lock b/Gemfile.lock
index 9f053cac2c..3edcc0a4e6 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -376,9 +376,8 @@ GEM
       crass (~> 1.0.2)
       nokogiri (>= 1.8.0)
       nokogumbo (~> 2.0)
-    sassc (2.0.1)
+    sassc (2.4.0)
       ffi (~> 1.9)
-      rake
     sassc-rails (2.1.2)
       railties (>= 4.0.0)
       sassc (>= 2.0)
@@ -544,7 +543,7 @@ DEPENDENCIES
   ruby-prof
   ruby-readability
   rubyzip
-  sassc (= 2.0.1)
+  sassc (= 2.4.0)
   sassc-rails
   seed-fu
   shoulda-matchers