RubyGems - rails-rfc6570 - Versions diffs - 3.2.0 → 3.3.0 - Mend

rails-rfc6570 3.2.0 → 3.3.0

Files changed (259) hide show

data/vendor/bundle/ruby/3.3.0/gems/appraisal-2.5.0/README.md DELETED Viewed

@@ -1,243 +0,0 @@
-Appraisal
-=========
-Find out what your Ruby gems are worth.
-Synopsis
---------
-Appraisal integrates with bundler and rake to test your library against
-different versions of dependencies in repeatable scenarios called "appraisals."
-Appraisal is designed to make it easy to check for regressions in your library
-without interfering with day-to-day development using Bundler.
-Installation
-------------
-In your package's `.gemspec`:
-    s.add_development_dependency "appraisal"
-Note that gems must be bundled in the global namespace. Bundling gems to a
-local location or vendoring plugins is not supported. If you do not want to
-pollute the global namespace, one alternative is
-[RVM's Gemsets](http://rvm.io/gemsets).
-Setup
------
-Setting up appraisal requires an `Appraisals` file (similar to a `Gemfile`) in
-your project root, named "Appraisals" (note the case), and some slight changes
-to your project's `Rakefile`.
-An `Appraisals` file consists of several appraisal definitions. An appraisal
-definition is simply a list of gem dependencies. For example, to test with a
-few versions of Rails:
-    appraise "rails-3" do
-      gem "rails", "3.2.14"
-    end
-    appraise "rails-4" do
-      gem "rails", "4.0.0"
-    end
-The dependencies in your `Appraisals` file are combined with dependencies in
-your `Gemfile`, so you don't need to repeat anything that's the same for each
-appraisal. If something is specified in both the Gemfile and an appraisal, the
-version from the appraisal takes precedence.
-Usage
------
-Once you've configured the appraisals you want to use, you need to install the
-dependencies for each appraisal:
-    $ bundle exec appraisal install
-This will resolve, install, and lock the dependencies for that appraisal using
-bundler. Once you have your dependencies set up, you can run any command in a
-single appraisal:
-    $ bundle exec appraisal rails-3 rake test
-This will run `rake test` using the dependencies configured for Rails 3. You can
-also run each appraisal in turn:
-    $ bundle exec appraisal rake test
-If you want to use only the dependencies from your Gemfile, just run `rake
-test` as normal. This allows you to keep running with the latest versions of
-your dependencies in quick test runs, but keep running the tests in older
-versions to check for regressions.
-In the case that you want to run all the appraisals by default when you run
-`rake`, you can override your default Rake task by put this into your Rakefile:
-    if !ENV["APPRAISAL_INITIALIZED"] && !ENV["TRAVIS"]
-      task :default => :appraisal
-    end
-(Appraisal sets `APPRAISAL_INITIALIZED` environment variable when it runs your
-process. We put a check here to ensure that `appraisal rake` command should run
-your real default task, which usually is your `test` task.)
-Note that this may conflict with your CI setup if you decide to split the test
-into multiple processes by Appraisal and you are using `rake` to run tests by
-default.
-### Commands
-```bash
-appraisal clean                  # Remove all generated gemfiles and lockfiles from gemfiles folder
-appraisal generate               # Generate a gemfile for each appraisal
-appraisal help [COMMAND]         # Describe available commands or one specific command
-appraisal install                # Resolve and install dependencies for each appraisal
-appraisal list                   # List the names of the defined appraisals
-appraisal update [LIST_OF_GEMS]  # Remove all generated gemfiles and lockfiles, resolve, and install dependencies again
-appraisal version                # Display the version and exit
-```
-Under the hood
---------------
-Running `appraisal install` generates a Gemfile for each appraisal by combining
-your root Gemfile with the specific requirements for each appraisal. These are
-stored in the `gemfiles` directory, and should be added to version control to
-ensure that the same versions are always used.
-When you prefix a command with `appraisal`, the command is run with the
-appropriate Gemfile for that appraisal, ensuring the correct dependencies
-are used.
-Removing Gems using Appraisal
--------
-It is common while managing multiple Gemfiles for dependencies to become deprecated and no
-longer necessary, meaning they need to be removed from the Gemfile for a specific `appraisal`.
-To do this, use the `remove_gem` declaration within the necessary `appraise` block in your
-`Appraisals` file.
-### Example Usage
-**Gemfile**
-```ruby
-gem 'rails', '~> 4.2'
-group :test do
-  gem 'rspec', '~> 4.0'
-  gem 'test_after_commit'
-end
-```
-**Appraisals**
-```ruby
-appraise 'rails-5' do
-  gem 'rails', '~> 5.2'
-  group :test do
-    remove_gem :test_after_commit
-  end
-end
-```
-Using the `Appraisals` file defined above, this is what the resulting `Gemfile` will look like:
-```ruby
-gem 'rails', '~> 5.2'
-group :test do
-  gem 'rspec', '~> 4.0'
-end
-```
-Customization
--------------
-It is possible to customize the generated Gemfiles by adding a `customize_gemfiles` block to
-your `Appraisals` file. The block must contain a hash of key/value pairs. Currently supported
-customizations include:
-- heading: a string that by default adds "# This file was generated by Appraisal" to the top of each Gemfile, (the string will be commented for you)
-- single_quotes: a boolean that controls if strings are single quoted in each Gemfile, defaults to false
-### Example Usage
-**Appraisals**
-```ruby
-customize_gemfiles do
-  {
-    single_quotes: true,
-    heading: <<~HEADING
-      frozen_string_literal: true
-      File has been generated by Appraisal, do NOT modify it directly!
-      See the conventions at https://example.com/
-    HEADING
-  }
-end
-appraise "rails-3" do
-  gem "rails", "3.2.14"
-end
-```
-Using the `Appraisals` file defined above, this is what the resulting `Gemfile` will look like:
-```ruby
-# frozen_string_literal: true
-# File has been generated by Appraisal, do NOT modify it directly!
-# See the conventions at https://example.com/
-gem 'rails', '3.2.14'
-```
-Version Control
----------------
-When using Appraisal, we recommend you check in the Gemfiles that Appraisal
-generates within the gemfiles directory, but exclude the lockfiles there
-(`*.gemfile.lock`.) The Gemfiles are useful when running your tests against a
-continuous integration server.
-Circle CI Integration
----------------------
-In Circle CI you can override the default testing behaviour to customize your
-testing. Using this feature you can configure appraisal to execute your tests.
-In order to this you can put the following configuration in your circle.yml file:
-```yml
-dependencies:
-  post:
-    - bundle exec appraisal install
-test:
-  pre:
-    - bundle exec appraisal rake db:create
-    - bundle exec appraisal rake db:migrate
-  override:
-    - bundle exec appraisal rspec
-```
-Notice that we are running an rspec suite. You can customize your testing
-command in the `override` section and use your favourite one.
-Credits
--------
-![thoughtbot](https://thoughtbot.com/thoughtbot-logo-for-readmes.svg)
-Appraisal is maintained and funded by [thoughtbot, inc][thoughtbot]
-Thank you to all [the contributors][contributors]
-The names and logos for thoughtbot are trademarks of thoughtbot, inc.
-[thoughtbot]: http://thoughtbot.com/community
-[contributors]: https://github.com/thoughtbot/appraisal/contributors
-License
--------
-Appraisal is Copyright © 2010-2013 Joe Ferris and thoughtbot, inc. It is free
-software, and may be redistributed under the terms specified in the MIT-LICENSE
-file.

data/vendor/bundle/ruby/3.3.0/gems/appraisal-2.5.0/appraisal.gemspec DELETED Viewed

@@ -1,29 +0,0 @@
-# -*- encoding: utf-8 -*-
-$:.push File.expand_path("../lib", __FILE__)
-require "appraisal/version"
-Gem::Specification.new do |s|
-  s.name        = 'appraisal'
-  s.version     = Appraisal::VERSION.dup
-  s.platform    = Gem::Platform::RUBY
-  s.authors     = ['Joe Ferris', 'Prem Sichanugrist']
-  s.email       = ['jferris@thoughtbot.com', 'prem@thoughtbot.com']
-  s.homepage    = 'http://github.com/thoughtbot/appraisal'
-  s.summary     = 'Find out what your Ruby gems are worth'
-  s.description = 'Appraisal integrates with bundler and rake to test your library against different versions of dependencies in repeatable scenarios called "appraisals."'
-  s.license     = 'MIT'
-  s.files         = `git ls-files`.split("\n")
-  s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
-  s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
-  s.require_paths = ["lib"]
-  s.required_ruby_version = ">= 2.3.0"
-  s.add_runtime_dependency('rake')
-  s.add_runtime_dependency('bundler')
-  s.add_runtime_dependency('thor', '>= 0.14.0')
-  s.add_development_dependency("activesupport", ">= 3.2.21")
-  s.add_development_dependency('rspec', '~> 3.0')
-end

data/vendor/bundle/ruby/3.3.0/gems/ast-2.4.2/LICENSE.MIT DELETED Viewed

@@ -1,20 +0,0 @@
-Copyright (c) 2011-2013  Peter Zotov <whitequark@whitequark.org>
-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/bundle/ruby/3.3.0/gems/ast-2.4.2/README.YARD.md DELETED Viewed

@@ -1,12 +0,0 @@
-{AST} is a library for manipulating abstract syntax trees.
-It embraces immutability; each AST node is inherently frozen at
-creation, and updating a child node requires recreating that node
-and its every parent, recursively.
-This is a design choice. It does create some pressure on
-garbage collector, but completely eliminates all concurrency
-and aliasing problems.
-See also {AST::Node}, {AST::Processor::Mixin} and {AST::Sexp} for
-additional recommendations and design patterns.

data/vendor/bundle/ruby/3.3.0/gems/benchmark-ips-2.13.0/LICENSE DELETED Viewed

@@ -1,20 +0,0 @@
-Copyright (c) 2015 Evan Phoenix
-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/bundle/ruby/3.3.0/gems/benchmark-ips-2.13.0/README.md DELETED Viewed

@@ -1,279 +0,0 @@
-# benchmark-ips
-* rdoc :: http://rubydoc.info/gems/benchmark-ips
-* home :: https://github.com/evanphx/benchmark-ips
-[![Gem Version](https://badge.fury.io/rb/benchmark-ips.svg)](http://badge.fury.io/rb/benchmark-ips)
-[![Build Status](https://secure.travis-ci.org/evanphx/benchmark-ips.svg)](http://travis-ci.org/evanphx/benchmark-ips)
-[![Inline docs](http://inch-ci.org/github/evanphx/benchmark-ips.svg)](http://inch-ci.org/github/evanphx/benchmark-ips)
-* https://github.com/evanphx/benchmark-ips
-## DESCRIPTION:
-An iterations per second enhancement to Benchmark.
-## FEATURES/PROBLEMS:
- * benchmark/ips - benchmarks a blocks iterations/second. For short snippits
-   of code, ips automatically figures out how many times to run the code
-   to get interesting data. No more guessing at random iteration counts!
-## SYNOPSIS:
-```ruby
-require 'benchmark/ips'
-Benchmark.ips do |x|
-  # Configure the number of seconds used during
-  # the warmup phase (default 2) and calculation phase (default 5)
-  x.config(:time => 5, :warmup => 2)
-  # These parameters can also be configured this way
-  x.time = 5
-  x.warmup = 2
-  # Typical mode, runs the block as many times as it can
-  x.report("addition") { 1 + 2 }
-  # To reduce overhead, the number of iterations is passed in
-  # and the block must run the code the specific number of times.
-  # Used for when the workload is very small and any overhead
-  # introduces incorrectable errors.
-  x.report("addition2") do |times|
-    i = 0
-    while i < times
-      1 + 2
-      i += 1
-    end
-  end
-  # To reduce overhead even more, grafts the code given into
-  # the loop that performs the iterations internally to reduce
-  # overhead. Typically not needed, use the |times| form instead.
-  x.report("addition3", "1 + 2")
-  # Really long labels should be formatted correctly
-  x.report("addition-test-long-label") { 1 + 2 }
-  # Compare the iterations per second of the various reports!
-  x.compare!
-end
-```
-This will generate the following report:
-```
-Calculating -------------------------------------
-            addition    71.254k i/100ms
-           addition2    68.658k i/100ms
-           addition3    83.079k i/100ms
-addition-test-long-label
-                        70.129k i/100ms
--------------------------------------------------
-            addition     4.955M (± 8.7%) i/s -     24.155M
-           addition2    24.011M (± 9.5%) i/s -    114.246M
-           addition3    23.958M (±10.1%) i/s -    115.064M
-addition-test-long-label
-                         5.014M (± 9.1%) i/s -     24.545M
-Comparison:
-           addition2: 24011974.8 i/s
-           addition3: 23958619.8 i/s - 1.00x slower
-addition-test-long-label:  5014756.0 i/s - 4.79x slower
-            addition:  4955278.9 i/s - 4.85x slower
-```
-Benchmark/ips will report the number of iterations per second for a given block
-of code. When analyzing the results, notice the percent of [standard
-deviation](http://en.wikipedia.org/wiki/Standard\_deviation) which tells us how
-spread out our measurements are from the average. A high standard deviation
-could indicate the results having too much variability.
-One benefit to using this method is benchmark-ips automatically determines the
-data points for testing our code, so we can focus on the results instead of
-guessing iteration counts as we do with the traditional Benchmark library.
-### Custom Suite
-Pass a custom suite to disable garbage collection during benchmark:
-```ruby
-require 'benchmark/ips'
-# Enable and start GC before each job run. Disable GC afterwards.
-#
-# Inspired by https://www.omniref.com/ruby/2.2.1/symbols/Benchmark/bm?#annotation=4095926&line=182
-class GCSuite
-  def warming(*)
-    run_gc
-  end
-  def running(*)
-    run_gc
-  end
-  def warmup_stats(*)
-  end
-  def add_report(*)
-  end
-  private
-  def run_gc
-    GC.enable
-    GC.start
-    GC.disable
-  end
-end
-suite = GCSuite.new
-Benchmark.ips do |x|
-  x.config(:suite => suite)
-  x.report("job1") { ... }
-  x.report("job2") { ... }
-end
-```
-### Independent benchmarking
-If you are comparing multiple implementations of a piece of code you may want
-to benchmark them in separate invocations of Ruby so that the measurements
-are independent of each other. You can do this with the `hold!` command.
-```ruby
-Benchmark.ips do |x|
-  # Hold results between multiple invocations of Ruby
-  x.hold! 'filename'
-end
-```
-This will run only one benchmarks each time you run the command, storing
-results in the specified file. The file is deleted when all results have been
-gathered and the report is shown.
-Alternatively, if you prefer a different approach, the `save!` command is
-available. Examples for [hold!](examples/hold.rb) and [save!](examples/save.rb) are available in
-the `examples/` directory.
-### Multiple iterations
-In some cases you may want to run multiple iterations of the warmup and
-calculation stages and take only the last result for comparison. This is useful
-if you are benchmarking with an implementation of Ruby that optimizes using
-tracing or on-stack-replacement, because to those implementations the
-calculation phase may appear as new, unoptimized code.
-You can do this with the `iterations` option, which by default is `1`. The
-total time spent will then be `iterations * warmup + iterations * time` seconds.
-```ruby
-Benchmark.ips do |x|
-  x.config(:iterations => 3)
-    # or
-  x.iterations = 3
-end
-```
-### Online sharing
-If you want to quickly share your benchmark result with others, run you benchmark
-with `SHARE=1` argument. For example: `SHARE=1 ruby my_benchmark.rb`.
-Result will be sent to [benchmark.fyi](https://ips.fastruby.io/) and benchmark-ips
-will display the link to share the benchmark's result.
-If you want to run your own instance of [benchmark.fyi](https://github.com/evanphx/benchmark.fyi)
-and share it to that instance, you can do this: `SHARE_URL=https://ips.example.com ruby my_benchmark.rb`
-### Advanced Statistics
-By default, the margin of error shown is plus-minus one standard deviation. If
-a more advanced statistical test is wanted, a bootstrap confidence interval
-can be calculated instead. A bootstrap confidence interval has the advantages of
-arguably being more mathematically sound for this application than a standard
-deviation, it additionally produces an error for relative slowdowns, which the
-standard deviation does not, and it is arguably more intuitive and actionable.
-When a bootstrap confidence interval is used, a median of the interval is used
-rather than the mean of the samples, which is what you get with the default
-standard deviation.
-The bootstrap confidence interval used is the one described by Tomas Kalibera.
-Note that for this technique to be valid your benchmark should have reached a
-non-periodic steady state with statistically independent samples (it should
-have warmed up) by the time measurements start.
-Using a bootstrap confidence internal requires that the 'kalibera' gem is
-installed separately. This gem is not a formal dependency, as by default it is
-not needed.
-```
-gem install kalibera
-```
-```ruby
-Benchmark.ips do |x|
-  # The default is :stats => :sd, which doesn't have a configurable confidence
-  x.config(:stats => :bootstrap, :confidence => 95)
-    # or
-  x.stats = :bootstrap
-  x.confidence = 95
-  # confidence is 95% by default, so it can be omitted
-end
-```
-### Output as JSON
-You can generate output in JSON. If you want to write JSON to a file, pass filename to `json!` method:
-```ruby
-Benchmark.ips do |x|
-  x.report("some report") {  }
-  x.json! 'filename.json'
-end
-```
-If you want to write JSON to STDOUT, pass `STDOUT` to `json!` method and set `quiet = true` before `json!`:
-```ruby
-Benchmark.ips do |x|
-  x.report("some report") {  }
-  x.quiet = true
-  x.json! STDOUT
-end
-```
-This is useful when the output from `benchmark-ips` becomes an input of other tools via stdin.
-## REQUIREMENTS:
-* None!
-## INSTALL:
-    $ gem install benchmark-ips
-## DEVELOPERS:
-After checking out the source, run:
-    $ rake newb
-This task will install any missing dependencies, run the tests/specs,
-and generate the RDoc.

data/vendor/bundle/ruby/3.3.0/gems/bigdecimal-3.1.8/LICENSE DELETED Viewed

@@ -1,56 +0,0 @@
-Ruby is copyrighted free software by Yukihiro Matsumoto <matz@netlab.jp>.
-You can redistribute it and/or modify it under either the terms of the
-2-clause BSDL (see the file BSDL), or the conditions below:
-  1. You may make and give away verbatim copies of the source form of the
-     software without restriction, provided that you duplicate all of the
-     original copyright notices and associated disclaimers.
-  2. You may modify your copy of the software in any way, provided that
-     you do at least ONE of the following:
-       a) place your modifications in the Public Domain or otherwise
-          make them Freely Available, such as by posting said
-	  modifications to Usenet or an equivalent medium, or by allowing
-	  the author to include your modifications in the software.
-       b) use the modified software only within your corporation or
-          organization.
-       c) give non-standard binaries non-standard names, with
-          instructions on where to get the original software distribution.
-       d) make other distribution arrangements with the author.
-  3. You may distribute the software in object code or binary form,
-     provided that you do at least ONE of the following:
-       a) distribute the binaries and library files of the software,
-	  together with instructions (in the manual page or equivalent)
-	  on where to get the original distribution.
-       b) accompany the distribution with the machine-readable source of
-	  the software.
-       c) give non-standard binaries non-standard names, with
-          instructions on where to get the original software distribution.
-       d) make other distribution arrangements with the author.
-  4. You may modify and include the part of the software into any other
-     software (possibly commercial).  But some files in the distribution
-     are not written by the author, so that they are not under these terms.
-     For the list of those files and their copying conditions, see the
-     file LEGAL.
-  5. The scripts and library files supplied as input to or produced as
-     output from the software do not automatically fall under the
-     copyright of the software, but belong to whomever generated them,
-     and may be sold commercially, and may be aggregated with this
-     software.
-  6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
-     IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
-     WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-     PURPOSE.