primary_connect_proto 0.12.1 → 0.14.0

data/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.10.1/LICENSE.md

@@ -1,26 +0,0 @@
-The MIT License (MIT)
-=====================
-
-* Copyright © 2012 Chad Humphries, David Chelimsky, Myron Marston
-* Copyright © 2009 Chad Humphries, David Chelimsky
-* Copyright © 2006 David Chelimsky, The RSpec Development Team
-* Copyright © 2005 Steven Baker
-
-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/2.7.0/gems/rspec-core-3.10.1/README.md

@@ -1,384 +0,0 @@
-# rspec-core [![Build Status](https://secure.travis-ci.org/rspec/rspec-core.svg?branch=main)](http://travis-ci.org/rspec/rspec-core) [![Code Climate](https://codeclimate.com/github/rspec/rspec-core.svg)](https://codeclimate.com/github/rspec/rspec-core)
-
-rspec-core provides the structure for writing executable examples of how your
-code should behave, and an `rspec` command with tools to constrain which
-examples get run and tailor the output.
-
-## Install
-
-    gem install rspec      # for rspec-core, rspec-expectations, rspec-mocks
-    gem install rspec-core # for rspec-core only
-    rspec --help
-
-Want to run against the `main` branch? You'll need to include the dependent
-RSpec repos as well. Add the following to your `Gemfile`:
-
-```ruby
-%w[rspec rspec-core rspec-expectations rspec-mocks rspec-support].each do |lib|
-  gem lib, :git => "https://github.com/rspec/#{lib}.git", :branch => 'main'
-end
-```
-
-## Basic Structure
-
-RSpec uses the words "describe" and "it" so we can express concepts like a conversation:
-
-    "Describe an order."
-    "It sums the prices of its line items."
-
-```ruby
-RSpec.describe Order do
-  it "sums the prices of its line items" do
-    order = Order.new
-
-    order.add_entry(LineItem.new(:item => Item.new(
-      :price => Money.new(1.11, :USD)
-    )))
-    order.add_entry(LineItem.new(:item => Item.new(
-      :price => Money.new(2.22, :USD),
-      :quantity => 2
-    )))
-
-    expect(order.total).to eq(Money.new(5.55, :USD))
-  end
-end
-```
-
-The `describe` method creates an [ExampleGroup](http://rubydoc.info/gems/rspec-core/RSpec/Core/ExampleGroup).  Within the
-block passed to `describe` you can declare examples using the `it` method.
-
-Under the hood, an example group is a class in which the block passed to
-`describe` is evaluated. The blocks passed to `it` are evaluated in the
-context of an _instance_ of that class.
-
-## Nested Groups
-
-You can also declare nested groups using the `describe` or `context`
-methods:
-
-```ruby
-RSpec.describe Order do
-  context "with no items" do
-    it "behaves one way" do
-      # ...
-    end
-  end
-
-  context "with one item" do
-    it "behaves another way" do
-      # ...
-    end
-  end
-end
-```
-
-Nested groups are subclasses of the outer example group class, providing
-the inheritance semantics you'd want for free.
-
-## Aliases
-
-You can declare example groups using either `describe` or `context`.
-For a top level example group, `describe` and `context` are available
-off of `RSpec`. For backwards compatibility, they are also available
-off of the `main` object and `Module` unless you disable monkey
-patching.
-
-You can declare examples within a group using any of `it`, `specify`, or
-`example`.
-
-## Shared Examples and Contexts
-
-Declare a shared example group using `shared_examples`, and then include it
-in any group using `include_examples`.
-
-```ruby
-RSpec.shared_examples "collections" do |collection_class|
-  it "is empty when first created" do
-    expect(collection_class.new).to be_empty
-  end
-end
-
-RSpec.describe Array do
-  include_examples "collections", Array
-end
-
-RSpec.describe Hash do
-  include_examples "collections", Hash
-end
-```
-
-Nearly anything that can be declared within an example group can be declared
-within a shared example group. This includes `before`, `after`, and `around`
-hooks, `let` declarations, and nested groups/contexts.
-
-You can also use the names `shared_context` and `include_context`. These are
-pretty much the same as `shared_examples` and `include_examples`, providing
-more accurate naming when you share hooks, `let` declarations, helper methods,
-etc, but no examples.
-
-## Metadata
-
-rspec-core stores a metadata hash with every example and group, which
-contains their descriptions, the locations at which they were
-declared, etc, etc. This hash powers many of rspec-core's features,
-including output formatters (which access descriptions and locations),
-and filtering before and after hooks.
-
-Although you probably won't ever need this unless you are writing an
-extension, you can access it from an example like this:
-
-```ruby
-it "does something" do |example|
-  expect(example.metadata[:description]).to eq("does something")
-end
-```
-
-### `described_class`
-
-When a class is passed to `describe`, you can access it from an example
-using the `described_class` method, which is a wrapper for
-`example.metadata[:described_class]`.
-
-```ruby
-RSpec.describe Widget do
-  example do
-    expect(described_class).to equal(Widget)
-  end
-end
-```
-
-This is useful in extensions or shared example groups in which the specific
-class is unknown. Taking the collections shared example group from above, we can
-clean it up a bit using `described_class`:
-
-```ruby
-RSpec.shared_examples "collections" do
-  it "is empty when first created" do
-    expect(described_class.new).to be_empty
-  end
-end
-
-RSpec.describe Array do
-  include_examples "collections"
-end
-
-RSpec.describe Hash do
-  include_examples "collections"
-end
-```
-
-## A Word on Scope
-
-RSpec has two scopes:
-
-* **Example Group**: Example groups are defined by a `describe` or
-  `context` block, which is eagerly evaluated when the spec file is
-  loaded. The block is evaluated in the context of a subclass of
-  `RSpec::Core::ExampleGroup`, or a subclass of the parent example group
-  when you're nesting them.
-* **Example**: Examples -- typically defined by an `it` block -- and any other
-  blocks with per-example semantics -- such as a `before(:example)` hook -- are
-  evaluated in the context of
-  an _instance_ of the example group class to which the example belongs.
-  Examples are _not_ executed when the spec file is loaded; instead,
-  RSpec waits to run any examples until all spec files have been loaded,
-  at which point it can apply filtering, randomization, etc.
-
-To make this more concrete, consider this code snippet:
-
-``` ruby
-RSpec.describe "Using an array as a stack" do
-  def build_stack
-    []
-  end
-
-  before(:example) do
-    @stack = build_stack
-  end
-
-  it 'is initially empty' do
-    expect(@stack).to be_empty
-  end
-
-  context "after an item has been pushed" do
-    before(:example) do
-      @stack.push :item
-    end
-
-    it 'allows the pushed item to be popped' do
-      expect(@stack.pop).to eq(:item)
-    end
-  end
-end
-```
-
-Under the covers, this is (roughly) equivalent to:
-
-``` ruby
-class UsingAnArrayAsAStack < RSpec::Core::ExampleGroup
-  def build_stack
-    []
-  end
-
-  def before_example_1
-    @stack = build_stack
-  end
-
-  def it_is_initially_empty
-    expect(@stack).to be_empty
-  end
-
-  class AfterAnItemHasBeenPushed < self
-    def before_example_2
-      @stack.push :item
-    end
-
-    def it_allows_the_pushed_item_to_be_popped
-      expect(@stack.pop).to eq(:item)
-    end
-  end
-end
-```
-
-To run these examples, RSpec would (roughly) do the following:
-
-``` ruby
-example_1 = UsingAnArrayAsAStack.new
-example_1.before_example_1
-example_1.it_is_initially_empty
-
-example_2 = UsingAnArrayAsAStack::AfterAnItemHasBeenPushed.new
-example_2.before_example_1
-example_2.before_example_2
-example_2.it_allows_the_pushed_item_to_be_popped
-```
-
-## The `rspec` Command
-
-When you install the rspec-core gem, it installs the `rspec` executable,
-which you'll use to run rspec. The `rspec` command comes with many useful
-options.
-Run `rspec --help` to see the complete list.
-
-## Store Command Line Options `.rspec`
-
-You can store command line options in a `.rspec` file in the project's root
-directory, and the `rspec` command will read them as though you typed them on
-the command line.
-
-## Get Started
-
-Start with a simple example of behavior you expect from your system. Do
-this before you write any implementation code:
-
-```ruby
-# in spec/calculator_spec.rb
-RSpec.describe Calculator do
-  describe '#add' do
-    it 'returns the sum of its arguments' do
-      expect(Calculator.new.add(1, 2)).to eq(3)
-    end
-  end
-end
-```
-
-Run this with the rspec command, and watch it fail:
-
-```
-$ rspec spec/calculator_spec.rb
-./spec/calculator_spec.rb:1: uninitialized constant Calculator
-```
-
-Address the failure by defining a skeleton of the `Calculator` class:
-
-```ruby
-# in lib/calculator.rb
-class Calculator
-  def add(a, b)
-  end
-end
-```
-
-Be sure to require the implementation file in the spec:
-
-```ruby
-# in spec/calculator_spec.rb
-# - RSpec adds ./lib to the $LOAD_PATH
-require "calculator"
-```
-
-Now run the spec again, and watch the expectation fail:
-
-```
-$ rspec spec/calculator_spec.rb
-F
-
-Failures:
-
-  1) Calculator#add returns the sum of its arguments
-     Failure/Error: expect(Calculator.new.add(1, 2)).to eq(3)
-
-       expected: 3
-            got: nil
-
-       (compared using ==)
-     # ./spec/calcalator_spec.rb:6:in `block (3 levels) in <top (required)>'
-
-Finished in 0.00131 seconds (files took 0.10968 seconds to load)
-1 example, 1 failure
-
-Failed examples:
-
-rspec ./spec/calcalator_spec.rb:5 # Calculator#add returns the sum of its arguments
-```
-
-Implement the simplest solution, by changing the definition of `Calculator#add` to:
-
-```ruby
-def add(a, b)
-  a + b
-end
-```
-
-Now run the spec again, and watch it pass:
-
-```
-$ rspec spec/calculator_spec.rb
-.
-
-Finished in 0.000315 seconds
-1 example, 0 failures
-```
-
-Use the `documentation` formatter to see the resulting spec:
-
-```
-$ rspec spec/calculator_spec.rb --format doc
-Calculator
-  #add
-    returns the sum of its arguments
-
-Finished in 0.000379 seconds
-1 example, 0 failures
-```
-
-## Contributing
-
-Once you've set up the environment, you'll need to cd into the working
-directory of whichever repo you want to work in. From there you can run the
-specs and cucumber features, and make patches.
-
-NOTE: You do not need to use rspec-dev to work on a specific RSpec repo. You
-can treat each RSpec repo as an independent project.
-
-* [Build details](BUILD_DETAIL.md)
-* [Code of Conduct](CODE_OF_CONDUCT.md)
-* [Detailed contributing guide](CONTRIBUTING.md)
-* [Development setup guide](DEVELOPMENT.md)
-
-## Also see
-
-* [https://github.com/rspec/rspec](https://github.com/rspec/rspec)
-* [https://github.com/rspec/rspec-expectations](https://github.com/rspec/rspec-expectations)
-* [https://github.com/rspec/rspec-mocks](https://github.com/rspec/rspec-mocks)
-* [https://github.com/rspec/rspec-rails](https://github.com/rspec/rspec-rails)

data/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.10.1/exe/rspec

@@ -1,4 +0,0 @@
-#!/usr/bin/env ruby
-
-require 'rspec/core'
-RSpec::Core::Runner.invoke

data/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.10.1/lib/rspec/autorun.rb

@@ -1,3 +0,0 @@
-require 'rspec/core'
-# Ensure the default config is loaded
-RSpec::Core::Runner.autorun

data/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.10.1/lib/rspec/core/backtrace_formatter.rb

@@ -1,65 +0,0 @@
-module RSpec
-  module Core
-    # @private
-    class BacktraceFormatter
-      # @private
-      attr_accessor :exclusion_patterns, :inclusion_patterns
-
-      def initialize
-        @full_backtrace = false
-
-        patterns = %w[ /lib\d*/ruby/ bin/ exe/rspec /lib/bundler/ /exe/bundle: ]
-        patterns << "org/jruby/" if RUBY_PLATFORM == 'java'
-        patterns.map! { |s| Regexp.new(s.gsub("/", File::SEPARATOR)) }
-
-        @exclusion_patterns = [Regexp.union(RSpec::CallerFilter::IGNORE_REGEX, *patterns)]
-        @inclusion_patterns = []
-
-        return unless matches?(@exclusion_patterns, File.join(Dir.getwd, "lib", "foo.rb:13"))
-        inclusion_patterns << Regexp.new(Dir.getwd)
-      end
-
-      attr_writer :full_backtrace
-
-      def full_backtrace?
-        @full_backtrace || exclusion_patterns.empty?
-      end
-
-      def filter_gem(gem_name)
-        sep = File::SEPARATOR
-        exclusion_patterns << /#{sep}#{gem_name}(-[^#{sep}]+)?#{sep}/
-      end
-
-      def format_backtrace(backtrace, options={})
-        return [] unless backtrace
-        return backtrace if options[:full_backtrace] || backtrace.empty?
-
-        backtrace.map { |l| backtrace_line(l) }.compact.
-          tap do |filtered|
-            if filtered.empty?
-              filtered.concat backtrace
-              filtered << ""
-              filtered << "  Showing full backtrace because every line was filtered out."
-              filtered << "  See docs for RSpec::Configuration#backtrace_exclusion_patterns and"
-              filtered << "  RSpec::Configuration#backtrace_inclusion_patterns for more information."
-            end
-          end
-      end
-
-      def backtrace_line(line)
-        Metadata.relative_path(line) unless exclude?(line)
-      end
-
-      def exclude?(line)
-        return false if @full_backtrace
-        matches?(exclusion_patterns, line) && !matches?(inclusion_patterns, line)
-      end
-
-    private
-
-      def matches?(patterns, line)
-        patterns.any? { |p| line =~ p }
-      end
-    end
-  end
-end

data/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.10.1/lib/rspec/core/bisect/coordinator.rb

@@ -1,62 +0,0 @@
-RSpec::Support.require_rspec_core "bisect/shell_command"
-RSpec::Support.require_rspec_core "bisect/example_minimizer"
-RSpec::Support.require_rspec_core "bisect/utilities"
-RSpec::Support.require_rspec_core "formatters/bisect_progress_formatter"
-
-module RSpec
-  module Core
-    module Bisect
-      # The main entry point into the bisect logic. Coordinates among:
-      #   - Bisect::ShellCommand: Generates shell commands to run spec subsets
-      #   - Bisect::ExampleMinimizer: Contains the core bisect logic.
-      #   - A bisect runner: runs a set of examples and returns the results.
-      #   - A bisect formatter: provides progress updates to the user.
-      # @private
-      class Coordinator
-        def self.bisect_with(spec_runner, original_cli_args, formatter)
-          new(spec_runner, original_cli_args, formatter).bisect
-        end
-
-        def initialize(spec_runner, original_cli_args, formatter)
-          @spec_runner   = spec_runner
-          @shell_command = ShellCommand.new(original_cli_args)
-          @notifier      = Bisect::Notifier.new(formatter)
-        end
-
-        def bisect
-          repro = start_bisect_runner do |runner|
-            minimizer = ExampleMinimizer.new(@shell_command, runner, @notifier)
-
-            gracefully_abort_on_sigint(minimizer)
-            minimizer.find_minimal_repro
-            minimizer.repro_command_for_currently_needed_ids
-          end
-
-          @notifier.publish(:bisect_repro_command, :repro => repro)
-
-          true
-        rescue BisectFailedError => e
-          @notifier.publish(:bisect_failed, :failure_explanation => e.message)
-          false
-        ensure
-          @notifier.publish(:close)
-        end
-
-      private
-
-        def start_bisect_runner(&block)
-          klass = @spec_runner.configuration.bisect_runner_class
-          klass.start(@shell_command, @spec_runner, &block)
-        end
-
-        def gracefully_abort_on_sigint(minimizer)
-          trap('INT') do
-            repro = minimizer.repro_command_for_currently_needed_ids
-            @notifier.publish(:bisect_aborted, :repro => repro)
-            exit(1)
-          end
-        end
-      end
-    end
-  end
-end