jets 1.9.7 → 1.9.8

data/vendor/jets-gems/lib/jets/gems/report.rb

@@ -1,69 +0,0 @@
-require "net/http"
-
-module Jets::Gems
-  class Report
-    # For local testing, example:
-    #   LAMBDAGEM_API_URL=localhost:8888/api/v1 jets gems:check
-    LAMBDAGEM_API_URL = ENV["LAMBDAGEM_API_URL"] || "https://api.lambdagems.com/api/v1"
-
-    def self.missing(gems)
-      new(gems).report
-    end
-
-    def initialize(gems)
-      @gems = gems
-    end
-
-    def report
-      version_pattern = /(.*)-(\d+\.\d+\.\d+.*)/
-      threads = []
-      @gems.each do |gem_name|
-        if md = gem_name.match(version_pattern)
-          name, version = md[1], md[2]
-          threads << Thread.new do
-            call_api("report/missing?name=#{name}&version=#{version}", async: true)
-          end
-        else
-          puts "WARN: Unable to extract the version from the gem name."
-        end
-      end
-      # Wait for request to finish because the command might finish before
-      # the Threads even send the request. So we join them just case
-      threads.each(&:join)
-    end
-
-    def api_url(path)
-      url = "#{LAMBDAGEM_API_URL}/#{path}"
-      url.include?("http") ? url : "http://#{url}" # ensure http or https has been provided
-    end
-
-    def call_api(path, async: false)
-      uri = URI(api_url(path))
-      http = Net::HTTP.new(uri.host, uri.port)
-      http.use_ssl = uri.scheme == "https"
-      # Abusing read_timeout to mimic async fire and forget behavior.
-      # This makes the code continue and return very quickly and we ignore the response
-      # Thanks: https://www.mikeperham.com/2015/05/08/timeout-rubys-most-dangerous-api/
-      # https://github.com/ankane/the-ultimate-guide-to-ruby-timeouts/issues/8
-      http.max_retries = 0 # Fix http retries, read_timeout will cause retries immediately, we want to disable this behavior
-      http.read_timeout = 0.01 if async
-      request = Net::HTTP::Get.new(uri)
-      begin
-        response = http.request(request)
-      rescue Net::ReadTimeout
-        # Abusing read_timeout to mimic async fire and forget behavior
-      end
-      return nil if async # always return nil if async behavior requested.
-        # In theory we can sometimes get back a response if it returns before
-        # the read timeout but that's a confusing interface.
-
-      resp = {
-        status: response.code.to_i,
-        headers: response.each_header.to_h,
-        body: response.body,
-      }
-      # pp resp # Uncomment to debug
-      resp
-    end
-  end
-end

data/vendor/jets-gems/lib/jets/gems/version.rb

@@ -1,5 +0,0 @@
-module Jets
-  module Gems
-    VERSION = "0.1.0"
-  end
-end

data/vendor/jets-gems/spec/jets/gems_spec.rb

@@ -1,5 +0,0 @@
-RSpec.describe Jets::Gems do
-  it "has a version number" do
-    expect(Jets::Gems::VERSION).not_to be nil
-  end
-end

data/vendor/jets-gems/spec/spec_helper.rb

@@ -1,14 +0,0 @@
-require "bundler/setup"
-require "jets/gems"
-
-RSpec.configure do |config|
-  # Enable flags like --only-failures and --next-failure
-  config.example_status_persistence_file_path = ".rspec_status"
-
-  # Disable RSpec exposing methods globally on `Module` and `main`
-  config.disable_monkey_patching!
-
-  config.expect_with :rspec do |c|
-    c.syntax = :expect
-  end
-end

data/vendor/rails/Brewfile

@@ -1,13 +0,0 @@
-tap "homebrew/core"
-tap "homebrew/bundle"
-tap "homebrew/services"
-tap "caskroom/cask"
-brew "ffmpeg"
-brew "memcached"
-brew "mysql"
-brew "postgresql"
-brew "redis"
-brew "yarn"
-cask "xquartz"
-brew "mupdf"
-brew "poppler"

data/vendor/rails/CODE_OF_CONDUCT.md

@@ -1,12 +0,0 @@
-# Contributor Code of Conduct
-
-The Rails team is committed to fostering a welcoming community.
-
-**Our Code of Conduct can be found here**:
-
-http://rubyonrails.org/conduct/
-
-For a history of updates, see the page history here:
-
-https://github.com/rails/rails.github.com/commits/master/conduct/index.html
-

data/vendor/rails/CONTRIBUTING.md

@@ -1,49 +0,0 @@
-## How to contribute to Ruby on Rails
-
-#### **Did you find a bug?**
-
-* **Do not open up a GitHub issue if the bug is a security vulnerability
-  in Rails**, and instead to refer to our [security policy](http://rubyonrails.org/security/).
-
-* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/rails/rails/issues).
-
-* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/rails/rails/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
-
-* If possible, use the relevant bug report templates to create the issue. Simply copy the content of the appropriate template into a .rb file, make the necessary changes to demonstrate the issue, and **paste the content into the issue description**:
-  * [**Active Record** (models, database) issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/active_record_master.rb)
-  * [**Action Pack** (controllers, routing) issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/action_controller_master.rb)
-  * [**Generic template** for other issues](https://github.com/rails/rails/blob/master/guides/bug_report_templates/generic_master.rb)
-
-* For more detailed information on submitting a bug report and creating an issue, visit our [reporting guidelines](http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#reporting-an-issue).
-
-#### **Did you write a patch that fixes a bug?**
-
-* Open a new GitHub pull request with the patch.
-
-* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
-* Before submitting, please read the [Contributing to Ruby on Rails](http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html) guide to know more about coding conventions and benchmarks.
-
-#### **Did you fix whitespace, format code, or make a purely cosmetic patch?**
-
-Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of Rails will generally not be accepted (read more about [our rationales behind this decision](https://github.com/rails/rails/pull/13771#issuecomment-32746700)).
-
-#### **Do you intend to add a new feature or change an existing one?**
-
-* Suggest your change in the [rubyonrails-core mailing list](https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-core) and start writing code.
-
-* Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes.
-
-#### **Do you have questions about the source code?**
-
-* Ask any question about how to use Ruby on Rails in the [rubyonrails-talk mailing list](https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-talk).
-
-#### **Do you want to contribute to the Rails documentation?**
-
-* Please read [Contributing to the Rails Documentation](http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#contributing-to-the-rails-documentation).
-
-Ruby on Rails is a volunteer effort. We encourage you to pitch in and [join the team](http://contributors.rubyonrails.org)!
-
-Thanks! :heart: :heart: :heart:
-
-Rails Team

data/vendor/rails/Gemfile

@@ -1,174 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-git_source(:github) { |repo| "https://github.com/#{repo}.git" }
-
-gemspec
-
-# We need a newish Rake since Active Job sets its test tasks' descriptions.
-gem "rake", ">= 11.1"
-
-# This needs to be with require false to ensure correct loading order, as it has to
-# be loaded after loading the test library.
-gem "mocha", require: false
-
-if RUBY_VERSION < "2.3"
-  gem "capybara", ">= 2.15", "< 3.2"
-else
-  gem "capybara", ">= 2.15"
-end
-
-gem "rack-cache", "~> 1.2"
-gem "coffee-rails"
-gem "sass-rails"
-gem "turbolinks", "~> 5"
-
-# require: false so bcrypt is loaded only when has_secure_password is used.
-# This is to avoid Active Model (and by extension the entire framework)
-# being dependent on a binary library.
-gem "bcrypt", "~> 3.1.11", require: false
-
-# This needs to be with require false to avoid it being automatically loaded by
-# sprockets.
-gem "uglifier", ">= 1.3.0", require: false
-
-# Explicitly avoid 1.x that doesn't support Ruby 2.4+
-gem "json", ">= 2.0.0"
-
-gem "rubocop", ">= 0.47", require: false
-
-# https://github.com/guard/rb-inotify/pull/79
-gem "rb-inotify", github: "matthewd/rb-inotify", branch: "close-handling", require: false
-
-# https://github.com/puma/puma/pull/1345
-gem "stopgap_13632", github: "pixeltrix/stopgap_13632", platforms: :mri if RUBY_VERSION < "2.3"
-
-group :doc do
-  gem "sdoc", "~> 1.0"
-  gem "redcarpet", "~> 3.2.3", platforms: :ruby
-  gem "w3c_validators"
-  gem "kindlerb", "~> 1.2.0"
-end
-
-# Active Support.
-gem "dalli", ">= 2.2.1"
-gem "listen", ">= 3.0.5", "< 3.2", require: false
-gem "libxml-ruby", platforms: :ruby
-gem "connection_pool", require: false
-
-# for railties app_generator_test
-gem "bootsnap", ">= 1.1.0", require: false
-
-# Active Job.
-group :job do
-  gem "resque", require: false
-  gem "resque-scheduler", require: false
-  gem "sidekiq", require: false
-  gem "sucker_punch", require: false
-  gem "delayed_job", require: false
-  gem "queue_classic", github: "rafaelfranca/queue_classic", branch: "update-pg", require: false, platforms: :ruby
-  gem "sneakers", require: false
-  gem "que", require: false
-  gem "backburner", require: false
-  # TODO: add qu after it support Rails 5.1
-  # gem 'qu-rails', github: "bkeepers/qu", branch: "master", require: false
-  # gem "qu-redis", require: false
-  gem "delayed_job_active_record", require: false
-  gem "sequel", require: false
-end
-
-# Action Cable
-group :cable do
-  gem "puma", require: false
-
-  gem "hiredis", require: false
-  gem "redis", "~> 4.0", require: false
-
-  gem "redis-namespace"
-
-  gem "websocket-client-simple", github: "matthewd/websocket-client-simple", branch: "close-race", require: false
-
-  gem "blade", require: false, platforms: [:ruby]
-  gem "blade-sauce_labs_plugin", require: false, platforms: [:ruby]
-  gem "sprockets-export", require: false
-end
-
-# Active Storage
-group :storage do
-  gem "aws-sdk-s3", require: false
-  gem "google-cloud-storage", "~> 1.8", require: false
-  gem "azure-storage", require: false
-
-  gem "mini_magick"
-end
-
-group :ujs do
-  gem "qunit-selenium"
-  gem "chromedriver-helper"
-end
-
-# Add your own local bundler stuff.
-local_gemfile = File.expand_path(".Gemfile", __dir__)
-instance_eval File.read local_gemfile if File.exist? local_gemfile
-
-group :test do
-  gem "minitest-bisect"
-
-  platforms :mri do
-    gem "stackprof"
-    gem "byebug"
-  end
-
-  gem "benchmark-ips"
-end
-
-platforms :ruby, :mswin, :mswin64, :mingw, :x64_mingw do
-  gem "nokogiri", ">= 1.8.1"
-
-  # Needed for compiling the ActionDispatch::Journey parser.
-  gem "racc", ">=1.4.6", require: false
-
-  # Active Record.
-  gem "sqlite3", "~> 1.3.6"
-
-  group :db do
-    gem "pg", ">= 0.18.0"
-    gem "mysql2", ">= 0.4.4"
-  end
-end
-
-platforms :jruby do
-  if ENV["AR_JDBC"]
-    gem "activerecord-jdbcsqlite3-adapter", github: "jruby/activerecord-jdbc-adapter", branch: "master"
-    group :db do
-      gem "activerecord-jdbcmysql-adapter", github: "jruby/activerecord-jdbc-adapter", branch: "master"
-      gem "activerecord-jdbcpostgresql-adapter", github: "jruby/activerecord-jdbc-adapter", branch: "master"
-    end
-  else
-    gem "activerecord-jdbcsqlite3-adapter", ">= 1.3.0"
-    group :db do
-      gem "activerecord-jdbcmysql-adapter", ">= 1.3.0"
-      gem "activerecord-jdbcpostgresql-adapter", ">= 1.3.0"
-    end
-  end
-end
-
-platforms :rbx do
-  # The rubysl-yaml gem doesn't ship with Psych by default as it needs
-  # libyaml that isn't always available.
-  gem "psych", "~> 2.0"
-end
-
-# Gems that are necessary for Active Record tests with Oracle.
-if ENV["ORACLE_ENHANCED"]
-  platforms :ruby do
-    gem "ruby-oci8", "~> 2.2"
-  end
-  gem "activerecord-oracle_enhanced-adapter", github: "rsim/oracle-enhanced", branch: "release52"
-end
-
-# A gem necessary for Active Record tests with IBM DB.
-gem "ibm_db" if ENV["IBM_DB"]
-gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw, :jruby]
-gem "wdm", ">= 0.1.0", platforms: [:mingw, :mswin, :x64_mingw, :mswin64]

data/vendor/rails/MIT-LICENSE

@@ -1,20 +0,0 @@
-Copyright (c) 2005-2018 David Heinemeier Hansson
-
-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.

data/vendor/rails/RAILS_VERSION

@@ -1 +0,0 @@
-5.2.2

data/vendor/rails/README.md

@@ -1,97 +0,0 @@
-# Welcome to Rails
-
-Rails is a web-application framework that includes everything needed to
-create database-backed web applications according to the
-[Model-View-Controller (MVC)](http://en.wikipedia.org/wiki/Model-view-controller)
-pattern.
-
-Understanding the MVC pattern is key to understanding Rails. MVC divides your
-application into three layers, each with a specific responsibility.
-
-The _Model layer_ represents your domain model (such as Account, Product,
-Person, Post, etc.) and encapsulates the business logic that is specific to
-your application. In Rails, database-backed model classes are derived from
-`ActiveRecord::Base`. Active Record allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in its [README](activerecord/README.rdoc).
-Although most Rails models are backed by a database, models can also be ordinary
-Ruby classes, or Ruby classes that implement a set of interfaces as provided by
-the Active Model module. You can read more about Active Model in its [README](activemodel/README.rdoc).
-
-The _Controller layer_ is responsible for handling incoming HTTP requests and
-providing a suitable response. Usually this means returning HTML, but Rails controllers
-can also generate XML, JSON, PDFs, mobile-specific views, and more. Controllers load and
-manipulate models, and render view templates in order to generate the appropriate HTTP response.
-In Rails, incoming requests are routed by Action Dispatch to an appropriate controller, and
-controller classes are derived from `ActionController::Base`. Action Dispatch and Action Controller
-are bundled together in Action Pack. You can read more about Action Pack in its
-[README](actionpack/README.rdoc).
-
-The _View layer_ is composed of "templates" that are responsible for providing
-appropriate representations of your application's resources. Templates can
-come in a variety of formats, but most view templates are HTML with embedded
-Ruby code (ERB files). Views are typically rendered to generate a controller response,
-or to generate the body of an email. In Rails, View generation is handled by Action View.
-You can read more about Action View in its [README](actionview/README.rdoc).
-
-Active Record, Active Model, Action Pack, and Action View can each be used independently outside Rails.
-In addition to that, Rails also comes with Action Mailer ([README](actionmailer/README.rdoc)), a library
-to generate and send emails; Active Job ([README](activejob/README.md)), a
-framework for declaring jobs and making them run on a variety of queueing
-backends; Action Cable ([README](actioncable/README.md)), a framework to
-integrate WebSockets with a Rails application;
-Active Storage ([README](activestorage/README.md)), a library to attach cloud
-and local files to Rails applications;
-and Active Support ([README](activesupport/README.rdoc)), a collection
-of utility classes and standard library extensions that are useful for Rails,
-and may also be used independently outside Rails.
-
-## Getting Started
-
-1. Install Rails at the command prompt if you haven't yet:
-
-        $ gem install rails
-
-2. At the command prompt, create a new Rails application:
-
-        $ rails new myapp
-
-   where "myapp" is the application name.
-
-3. Change directory to `myapp` and start the web server:
-
-        $ cd myapp
-        $ rails server
-
-   Run with `--help` or `-h` for options.
-
-4. Using a browser, go to `http://localhost:3000` and you'll see:
-"Yay! You’re on Rails!"
-
-5. Follow the guidelines to start developing your application. You may find
-   the following resources handy:
-    * [Getting Started with Rails](http://guides.rubyonrails.org/getting_started.html)
-    * [Ruby on Rails Guides](http://guides.rubyonrails.org)
-    * [The API Documentation](http://api.rubyonrails.org)
-    * [Ruby on Rails Tutorial](https://www.railstutorial.org/book)
-
-## Contributing
-
-[![Code Triage Badge](https://www.codetriage.com/rails/rails/badges/users.svg)](https://www.codetriage.com/rails/rails)
-
-We encourage you to contribute to Ruby on Rails! Please check out the
-[Contributing to Ruby on Rails guide](http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html) for guidelines about how to proceed. [Join us!](http://contributors.rubyonrails.org)
-
-Trying to report a possible security vulnerability in Rails? Please
-check out our [security policy](http://rubyonrails.org/security/) for
-guidelines about how to proceed.
-
-Everyone interacting in Rails and its sub-projects' codebases, issue trackers, chat rooms, and mailing lists is expected to follow the Rails [code of conduct](http://rubyonrails.org/conduct/).
-
-## Code Status
-
-[![Build Status](https://travis-ci.org/rails/rails.svg?branch=5-2-stable)](https://travis-ci.org/rails/rails)
-
-## License
-
-Ruby on Rails is released under the [MIT License](https://opensource.org/licenses/MIT).