Coder Social home page Coder Social logo

rack-freeze's Introduction

Rack::Freeze

Provides a policy for Rack middleware which should be frozen by default to prevent mutability bugs in a multi-threaded environment.

In Rack 2.1+, you can use Builder#freeze_app instead of this gem.

Build Status Code Climate Coverage Status

Motivation

I found issues due to unexpected state mutation when developing Utopia. It only became apparent when running in production using multi-threaded passenger. Freezing the middleware (and related state) allowed me to identify these issues, find other issues, and helps prevent these issues in the future.

Ideally, this concept would be part of rack. However, regardless of whether Rack adopts a policy on immutable middleware, this gem provides the tools necessary to implement such a policy transparently on top of existing rack middleware where possible.

Installation

Add this line to your application's Gemfile:

gem 'rack-freeze'

Usage

Add this to your config.ru:

require 'rack/freeze'

Now all your middleware will be frozen by default.

What bugs does this fix?

It guarantees as much as is possible, that middleware won't mutate during a request.

# This modifies `Rack::Builder#use` and `Rack::Builder#to_app` to generate a frozen stack of middleware.
require 'rack/freeze'

class NonThreadSafeMiddleware
	def initialize(app)
		@app = app
		@state = 0
	end
	
	def call(env)
		@state += 1
		
		return @app.call(env)
	end
end

use NonThreadSafeMiddleware

As NonThreadSafeMiddleware mutates it's state @state += 1, it will raise a RuntimeError. In a multi-threaded web-server, unprotected mutation of internal state will lead to undefined behavior. 5 out of 4 dentists agree that multi-threaded programming is hard to get right.

How to write thread-safe middleware?

There are two options: Don't mutate state, or if you need to for the purposes of performance, implement #freeze and use data-structures from concurrent-ruby.

require 'concurrent/map'

# Cache every request based on the path. Don't do this in production :)
class CacheEverythingForever
	def initialize(app)
		@app = app
		@cache_all_the_things = Concurrent::Map.new
	end
	
	def freeze
		return self if frozen?
		
		# Don't freeze @cache_all_the_things
		@app.freeze
		
		super
	end
	
	def call(env)
		# Use the thread-safe `Concurrent::Map` to fetch the value or store it if it doesn't exist already.
		@cache_all_the_things.fetch_or_store(env[Rack::PATH_INFO]) do
			@app.call(env)
		end
	end
end

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

Released under the MIT license.

Copyright, 2017, by Samuel G. D. Williams.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

rack-freeze's People

Contributors

ioquatix avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

rack-freeze's Issues

Freezes Only First Middleware Instance (or Application if No Middleware)

rack-freeze appears to freeze the rack application (set using Builder#run) if no middleware are used, or only the first middleware instance, as Builder#to_app returns the application itself or first middleware instance:

x = proc{}
Rack::Builder.new{run x}.to_app == x
# => true
Rack::Builder.new{use Rack::CommonLogger; run x}.to_app == x
# => false
Rack::Builder.new{use Rack::CommonLogger; run x}.to_app
# => #<Rack::CommonLogger:0x0008132b414510 @app=#<Proc:0x0008132b415a28@(irb):3>, @logger=nil>
Rack::Builder.new{use Rack::CommonLogger; use Rack::Lint; run x}.to_app
# => #<Rack::CommonLogger:0x00081317000460 @app=#<Rack::Lint:0x00081317000488 @app=#<Proc:0x000812e51f7a20@(irb):4>, @content_length=nil>, @logger=nil>

I'm guessing the intent is that rack-freeze should freeze all middleware instances used, not just the first one, and should either always freeze the rack application or never freeze the rack application for consistency. My vote would be always freeze the rack application, but that's more likely to break things.

I apologize if I'm off base here, I didn't actually try rack-freeze, just inspected the code and specs. If I'm wrong, it would probably be worth at least adding specs for the no middleware and multiple middleware cases.

How to use this on rails application without error?

I tried to use this gem but I got error due to rails code lazying loading stuff:

The error

App 10285 stderr: [ 2017-04-03 14:04:33.2507 10319/0x007fec20701b60(Worker 1) utils.rb:87 ]: *** Exception RuntimeError in Rack application object (can't modify frozen #<Class:#<Spacious::Application:0x007fec26b13680>>) (process 10319, thread 0x007fec20701b60(Worker 1)):
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/railties-5.0.2/lib/rails/engine.rb:527:in `env_config'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/railties-5.0.2/lib/rails/application.rb:248:in `env_config'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/railties-5.0.2/lib/rails/engine.rb:693:in `build_request'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/railties-5.0.2/lib/rails/application.rb:521:in `build_request'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/railties-5.0.2/lib/rails/engine.rb:521:in `call'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/newrelic_rpm-4.0.0.332/lib/new_relic/agent/instrumentation/middleware_tracing.rb:92:in `call'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:97:in `process_request'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:160:in `accept_and_process_next_request'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:113:in `main_loop'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/request_handler.rb:416:in `block (3 levels) in start_threads'
App 10285 stderr: 	from /users/pikachuexe/.rvm/gems/ruby-2.3.4/gems/passenger-5.1.2/src/ruby_supportlib/phusion_passenger/utils.rb:113:in `block in create_thread_and_abort_on_exception'

The rails source code

https://github.com/rails/rails/blob/5-0-stable/railties/lib/rails/engine.rb#L527

What should be done to get rid of the error?

Tabs versus spaces

First, i love this library. You are amazing and this is great. I just had a conversation with someone the other day about writing something like this, and here it is already written!

Minor question/nit. I was looking through the internals, they're very clean. I was however wondering if we could switch from tabs to 2 spaces instead? It's not a requirement by any stretch, but 2 spaces seems to be the community norm and as you start getting contributions you'll likely end up with a miss-mash of tabs and spaces.

Would you accept a pull request that converted all the tabs to 2 spaces?

Is it possible to use this gem with Newrelic?

When I try to set this up on an app that also uses Newrelic it produces stack overflow error:

Unable to load application: SystemStackError: stack level too deep
/app/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.2.0.334/lib/new_relic/agent/instrumentation/rack.rb:20:in `>=': stack level too deep (SystemStackError)
from /app/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.2.0.334/lib/new_relic/agent/instrumentation/rack.rb:20:in `rack_version_supported?'
from /app/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.2.0.334/lib/new_relic/agent/instrumentation/rack.rb:12:in `version_supported?'
from /app/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.2.0.334/lib/new_relic/agent/instrumentation/rack.rb:32:in `middleware_instrumentation_enabled?'
from /app/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.2.0.334/lib/new_relic/agent/instrumentation/rack.rb:94:in `use_with_newrelic'
from /app/vendor/bundle/ruby/2.4.0/gems/rack-freeze-1.2.0/lib/rack/freeze/builder.rb:28:in `use'
from /app/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.2.0.334/lib/new_relic/agent/instrumentation/rack.rb:96:in `use_with_newrelic'
from /app/vendor/bundle/ruby/2.4.0/gems/rack-freeze-1.2.0/lib/rack/freeze/builder.rb:28:in `use'
from /app/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.2.0.334/lib/new_relic/agent/instrumentation/rack.rb:96:in `use_with_newrelic'
 ... 9702 levels...
from /app/vendor/bundle/ruby/2.4.0/gems/puma-3.9.0/lib/puma/cli.rb:77:in `run'
from /app/vendor/bundle/ruby/2.4.0/gems/puma-3.9.0/bin/puma:10:in `<top (required)>'
from /app/vendor/bundle/ruby/2.4.0/bin/puma:22:in `load'
from /app/vendor/bundle/ruby/2.4.0/bin/puma:22:in `<main>'

From what I understand newrelic also wraps all middleware classes in its own class, which conflicts with rack-freeze:
https://github.com/newrelic/rpm/blob/master/lib/new_relic/agent/instrumentation/rack.rb#L142

Any advice on how to use this with Rails?

rack/rack#1149 (comment) hinted at the fact that Rails doesn't use Rack::Builder.

I've tried the steps in the readme, and am still able to run middleware that mutates state on each request.

Just wondering if you have any advice on how to run this (or something similar) on a Rails 4 (or 5 if that's easier, we are about to upgrade) app?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.