Content-Length header during build, no problems running locally

I get an error during Middleman build that I don’t understand and can’t solve:
Does anyone know why this might happen? Thanks!

== Prerendering CSS
== Request: /stylesheets/application-bde924fc.css
== Finishing Request: stylesheets/application-bde924fc.css (0.12s)
error build/stylesheets/application-bde924fc.css
Content-Length header was 156436, but should be 156463
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rack-2.2.2/lib/rack/lint.rb:21:in assert' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rack-2.2.2/lib/rack/lint.rb:738:in verify_content_length’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rack-2.2.2/lib/rack/lint.rb:762:in each' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rack-2.2.2/lib/rack/response.rb:277:in buffered_body!’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rack-2.2.2/lib/rack/mock.rb:191:in initialize' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rack-2.2.2/lib/rack/mock.rb:85:in new’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rack-2.2.2/lib/rack/mock.rb:85:in request' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rack-2.2.2/lib/rack/mock.rb:57:in get’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/middleman-core-4.3.5/lib/middleman-core/builder.rb:232:in block in output_resource' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activesupport-5.0.7.2/lib/active_support/notifications.rb:166:in instrument’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/middleman-core-4.3.5/lib/middleman-core/util.rb:21:in instrument' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/middleman-core-4.3.5/lib/middleman-core/builder.rb:225:in output_resource’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/contracts-0.13.0/lib/contracts/method_reference.rb:43:in send_to' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/contracts-0.13.0/lib/contracts/call_with.rb:76:in call_with’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/contracts-0.13.0/lib/contracts/method_handler.rb:138:in block in redefine_method' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:507:in call_with_index’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:471:in process_incoming_jobs' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:453:in block in worker’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:444:in fork' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:444:in worker’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:435:in block in create_workers' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:434:in each’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:434:in each_with_index' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:434:in create_workers’
/usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:373:in work_in_processes' /usr/local/Cellar/rbenv/1.1.0/versions/2.6.2/lib/ruby/gems/2.6.0/gems/parallel-1.19.1/lib/parallel.rb:277:in map’

gemfile:
source ‘https://rubygems.org

gem ‘middleman’, ‘~> 4.3’
gem ‘middleman-deploy’, git: ‘https://github.com/lewagon/middleman-deploy.git
gem ‘pry-byebug’, require: true
gem ‘middleman-autoprefixer’, ‘~> 2.7.1’

gem “bootstrap”

gem ‘middleman-google-analytics’, ‘~> 3.0’

Never mind, sorry for the duplicate post.
Just saw I had to downgrade rack to 2.0.8

1 Like

Forgot to mention it here but this issue is fixed in v4.3.6. You can safely update your bundle again.