bootsnap 1.1.8 → 1.7.2

data/.travis.yml

@@ -1,4 +0,0 @@
-language: ruby
-rvm: ruby-2.4.1
-before_script: rake
-script: bin/testunit

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at burke@libbey.me. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/CONTRIBUTING.md

@@ -1,21 +0,0 @@
-# Contributing to Bootsnap
-
-We love receiving pull requests!
-
-## Standards
-
-* PR should explain what the feature does, and why the change exists.
-* PR should include any carrier specific documentation explaining how it works.
-* Code _must_ be tested, including both unit and remote tests where applicable.
-* Be consistent. Write clean code that follows [Ruby community standards](https://github.com/bbatsov/ruby-style-guide).
-* Code should be generic and reusable.
-
-If you're stuck, ask questions!
-
-## How to contribute
-
-1. Fork it ( https://github.com/Shopify/bootsnap/fork )
-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 a new Pull Request

data/Gemfile

@@ -1,8 +0,0 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in bootsnap.gemspec
-gemspec
-
-group :development do
-  gem 'rubocop'
-end

data/Rakefile

@@ -1,11 +0,0 @@
-require 'rake/extensiontask'
-
-gemspec = Gem::Specification.load('bootsnap.gemspec')
-Rake::ExtensionTask.new do |ext|
-  ext.name = 'bootsnap'
-  ext.ext_dir = 'ext/bootsnap'
-  ext.lib_dir = 'lib/bootsnap'
-  ext.gem_spec = gemspec
-end
-
-task(default: :compile)

data/bin/console

@@ -1,14 +0,0 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "bootsnap"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start(__FILE__)

data/bin/setup

@@ -1,8 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-
-# Do any other automated setup that you need to do here

data/bin/testunit

@@ -1,8 +0,0 @@
-#!/bin/bash
-
-if [[ $# -eq 0 ]]; then
-  exec ruby -I"test" -w -e 'Dir.glob("./test/**/*_test.rb").each { |f| require f }' -- "$@"
-else
-  path=$1
-  exec ruby -I"test" -w -e "require '${path#test/}'" -- "$@"
-fi

data/bootsnap.gemspec

@@ -1,39 +0,0 @@
-# coding: utf-8
-lib = File.expand_path('../lib', __FILE__)
-$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require 'bootsnap/version'
-
-Gem::Specification.new do |spec|
-  spec.name          = "bootsnap"
-  spec.version       = Bootsnap::VERSION
-  spec.authors       = ["Burke Libbey"]
-  spec.email         = ["burke.libbey@shopify.com"]
-
-  spec.license       = "MIT"
-
-  spec.summary       = "Boot large ruby/rails apps faster"
-  spec.description   = spec.summary
-  spec.homepage      = "https://github.com/Shopify/bootsnap"
-
-  spec.files = `git ls-files -z`.split("\x0").reject do |f|
-    f.match(%r{^(test|spec|features)/})
-  end
-  spec.require_paths = ["lib"]
-
-  spec.required_ruby_version = '>= 2.0.0'
-
-  if RUBY_PLATFORM =~ /java/
-    spec.platform = 'java'
-  else
-    spec.platform    = Gem::Platform::RUBY
-    spec.extensions  = ['ext/bootsnap/extconf.rb']
-  end
-
-  spec.add_development_dependency "bundler", '~> 1'
-  spec.add_development_dependency 'rake', '~> 10.0'
-  spec.add_development_dependency 'rake-compiler', '~> 0'
-  spec.add_development_dependency "minitest", "~> 5.0"
-  spec.add_development_dependency "mocha", "~> 1.2"
-
-  spec.add_runtime_dependency "msgpack", "~> 1.0"
-end

data/dev.yml

@@ -1,10 +0,0 @@
-env:
-  BOOTSNAP_PEDANTIC: '1'
-
-up:
-  - ruby: 2.3.3
-  - bundler
-commands:
-  build: rake compile
-  test: 'rake compile && exec bin/testunit'
-  style: 'exec rubocop -D'

data/lib/bootsnap/load_path_cache/core_ext/active_support.rb

@@ -1,75 +0,0 @@
-module Bootsnap
-  module LoadPathCache
-    module CoreExt
-      module ActiveSupport
-        def self.without_bootsnap_cache
-          prev = Thread.current[:without_bootsnap_cache] || false
-          Thread.current[:without_bootsnap_cache] = true
-          yield
-        ensure
-          Thread.current[:without_bootsnap_cache] = prev
-        end
-
-        module ClassMethods
-          def autoload_paths=(o)
-            super
-            Bootsnap::LoadPathCache.autoload_paths_cache.reinitialize(o)
-          end
-
-          def search_for_file(path)
-            return super if Thread.current[:without_bootsnap_cache]
-            begin
-              Bootsnap::LoadPathCache.autoload_paths_cache.find(path)
-            rescue Bootsnap::LoadPathCache::ReturnFalse
-              nil # doesn't really apply here
-            end
-          end
-
-          def autoloadable_module?(path_suffix)
-            Bootsnap::LoadPathCache.autoload_paths_cache.has_dir?(path_suffix)
-          end
-
-          def remove_constant(const)
-            CoreExt::ActiveSupport.without_bootsnap_cache { super }
-          end
-
-          # If we can't find a constant using the patched implementation of
-          # search_for_file, try again with the default implementation.
-          #
-          # These methods call search_for_file, and we want to modify its
-          # behaviour.  The gymnastics here are a bit awkward, but it prevents
-          # 200+ lines of monkeypatches.
-          def load_missing_constant(from_mod, const_name)
-            super
-          rescue NameError => e
-            # NoMethodError is a NameError, but we only want to handle actual
-            # NameError instances.
-            raise unless e.class == NameError
-            # We can only confidently handle cases when *this* constant fails
-            # to load, not other constants referred to by it.
-            raise unless e.name == const_name
-            # If the constant was actually loaded, something else went wrong?
-            raise if from_mod.const_defined?(const_name)
-            CoreExt::ActiveSupport.without_bootsnap_cache { super }
-          end
-
-          # Signature has changed a few times over the years; easiest to not
-          # reiterate it with version polymorphism here...
-          def depend_on(*)
-            super
-          rescue LoadError
-            CoreExt::ActiveSupport.without_bootsnap_cache { super }
-          end
-        end
-      end
-    end
-  end
-end
-
-module ActiveSupport
-  module Dependencies
-    class << self
-      prepend Bootsnap::LoadPathCache::CoreExt::ActiveSupport::ClassMethods
-    end
-  end
-end