bunny 2.17.0 → 2.19.0

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bunny
 version: !ruby/object:Gem::Version
-  version: 2.17.0
+  version: 2.19.0
 platform: ruby
 authors:
 - Chris Duncan
@@ -9,10 +9,10 @@ authors:
 - Jakub Stastny aka botanicus
 - Michael S. Klishin
 - Stefan Kaes
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2020-09-11 00:00:00.000000000 Z
+date: 2021-06-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: amq-protocol
@@ -34,6 +34,26 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 2.3.1
+- !ruby/object:Gem::Dependency
+  name: sorted_set
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.0.2
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.0.2
 description: Easy to use, feature complete Ruby client for RabbitMQ 3.3 and later
   versions.
 email:
@@ -43,68 +63,7 @@ extensions: []
 extra_rdoc_files:
 - README.md
 files:
-- ".github/ISSUE_TEMPLATE.md"
-- ".gitignore"
-- ".rspec"
-- ".travis.yml"
-- ".yardopts"
-- CONTRIBUTING.md
-- ChangeLog.md
-- Gemfile
-- LICENSE
 - README.md
-- Rakefile
-- benchmarks/basic_publish/with_128K_messages.rb
-- benchmarks/basic_publish/with_1k_messages.rb
-- benchmarks/basic_publish/with_4K_messages.rb
-- benchmarks/basic_publish/with_64K_messages.rb
-- benchmarks/channel_open.rb
-- benchmarks/mutex_and_monitor.rb
-- benchmarks/queue_declare.rb
-- benchmarks/queue_declare_and_bind.rb
-- benchmarks/queue_declare_bind_and_delete.rb
-- benchmarks/synchronized_sorted_set.rb
-- benchmarks/write_vs_write_nonblock.rb
-- bunny.gemspec
-- docker-compose.yml
-- docker/Dockerfile
-- docker/apt/preferences.d/erlang
-- docker/apt/sources.list.d/bintray.rabbitmq.list
-- docker/docker-entrypoint.sh
-- docker/rabbitmq.conf
-- examples/connection/authentication_failure.rb
-- examples/connection/automatic_recovery_with_basic_get.rb
-- examples/connection/automatic_recovery_with_client_named_queues.rb
-- examples/connection/automatic_recovery_with_multiple_consumers.rb
-- examples/connection/automatic_recovery_with_republishing.rb
-- examples/connection/automatic_recovery_with_server_named_queues.rb
-- examples/connection/channel_level_exception.rb
-- examples/connection/disabled_automatic_recovery.rb
-- examples/connection/heartbeat.rb
-- examples/connection/manually_reconnecting_consumer.rb
-- examples/connection/manually_reconnecting_publisher.rb
-- examples/connection/unknown_host.rb
-- examples/consumers/high_and_low_priority.rb
-- examples/guides/exchanges/direct_exchange_routing.rb
-- examples/guides/exchanges/fanout_exchange_routing.rb
-- examples/guides/exchanges/headers_exchange_routing.rb
-- examples/guides/exchanges/mandatory_messages.rb
-- examples/guides/extensions/alternate_exchange.rb
-- examples/guides/extensions/basic_nack.rb
-- examples/guides/extensions/connection_blocked.rb
-- examples/guides/extensions/consumer_cancellation_notification.rb
-- examples/guides/extensions/dead_letter_exchange.rb
-- examples/guides/extensions/exchange_to_exchange_bindings.rb
-- examples/guides/extensions/per_message_ttl.rb
-- examples/guides/extensions/per_queue_message_ttl.rb
-- examples/guides/extensions/publisher_confirms.rb
-- examples/guides/extensions/queue_lease.rb
-- examples/guides/extensions/sender_selected_distribution.rb
-- examples/guides/getting_started/blabbr.rb
-- examples/guides/getting_started/hello_world.rb
-- examples/guides/getting_started/weathr.rb
-- examples/guides/queues/one_off_consumer.rb
-- examples/guides/queues/redeliveries.rb
 - lib/amq/protocol/extensions.rb
 - lib/bunny.rb
 - lib/bunny/authentication/credentials_encoder.rb
@@ -142,8 +101,6 @@ files:
 - lib/bunny/transport.rb
 - lib/bunny/version.rb
 - lib/bunny/versioned_delivery_tag.rb
-- profiling/basic_publish/with_4K_messages.rb
-- repl
 - spec/config/enabled_plugins
 - spec/config/rabbitmq.conf
 - spec/higher_level_api/integration/basic_ack_spec.rb
@@ -191,6 +148,7 @@ files:
 - spec/issues/issue224_spec.rb
 - spec/issues/issue465_spec.rb
 - spec/issues/issue549_spec.rb
+- spec/issues/issue609_spec.rb
 - spec/issues/issue78_spec.rb
 - spec/issues/issue83_spec.rb
 - spec/issues/issue97_attachment.json
@@ -205,15 +163,6 @@ files:
 - spec/stress/concurrent_publishers_stress_spec.rb
 - spec/stress/connection_open_close_spec.rb
 - spec/stress/merry_go_round_spec.rb
-- spec/tls/ca_certificate.pem
-- spec/tls/ca_key.pem
-- spec/tls/client_certificate.pem
-- spec/tls/client_key.pem
-- spec/tls/generate-server-cert.sh
-- spec/tls/server-openssl.cnf
-- spec/tls/server.csr
-- spec/tls/server_certificate.pem
-- spec/tls/server_key.pem
 - spec/toxiproxy_helper.rb
 - spec/unit/bunny_spec.rb
 - spec/unit/concurrent/atomic_fixnum_spec.rb
@@ -226,7 +175,7 @@ homepage: http://rubybunny.info
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -241,8 +190,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.2
-signing_key: 
+rubygems_version: 3.1.4
+signing_key:
 specification_version: 4
 summary: Popular easy to use Ruby client for RabbitMQ
 test_files:
@@ -293,6 +242,7 @@ test_files:
 - spec/issues/issue224_spec.rb
 - spec/issues/issue465_spec.rb
 - spec/issues/issue549_spec.rb
+- spec/issues/issue609_spec.rb
 - spec/issues/issue78_spec.rb
 - spec/issues/issue83_spec.rb
 - spec/issues/issue97_attachment.json
@@ -307,15 +257,6 @@ test_files:
 - spec/stress/concurrent_publishers_stress_spec.rb
 - spec/stress/connection_open_close_spec.rb
 - spec/stress/merry_go_round_spec.rb
-- spec/tls/ca_certificate.pem
-- spec/tls/ca_key.pem
-- spec/tls/client_certificate.pem
-- spec/tls/client_key.pem
-- spec/tls/generate-server-cert.sh
-- spec/tls/server-openssl.cnf
-- spec/tls/server.csr
-- spec/tls/server_certificate.pem
-- spec/tls/server_key.pem
 - spec/toxiproxy_helper.rb
 - spec/unit/bunny_spec.rb
 - spec/unit/concurrent/atomic_fixnum_spec.rb

data/.github/ISSUE_TEMPLATE.md

@@ -1,18 +0,0 @@
-## Does This Really Belong to GitHub issues?
-
-If you find a bug you understand well, poor default, incorrect or unclear piece of documentation,
-or missing feature, please [file an
-issue](http://github.com/ruby-amqp/bunny/issues) on GitHub.
-
-Please use [Bunny's mailing list](http://groups.google.com/group/ruby-amqp) for questions,
-investigations, and discussions. GitHub issues should be used for specific, well understood, actionable
-maintainers and contributors can work on.
-
-When filing an issue, please specify
-
- * Which Bunny and RabbitMQ versions are used
- * Recent RabbitMQ log file contents
- * Full exception stack traces
- * Steps to reproduce or a failing test case
-
-This would greatly help the maintainers help you.

data/.gitignore

@@ -1,28 +0,0 @@
-.DS_Store
-.*.swp
-*.class
-*.rbc
-*.gem
-/doc/
-.yardoc
-.rvmrc
-Gemfile.lock
-.rbx/*
-.tags
-.tags_sorted_by_file
-.Apple*
-/bin/*
-.bundle/*
-vendor/*
-playground/*
-*.org
-repl-*
-debug/*
-*.dump
-deploy.docs.sh
-.ruby-version
-.idea
-*.srl
-spec/tls/*.pem
-spec/tls/*.pem~
-spec/tls/*.p12

data/.rspec

@@ -1 +0,0 @@
--c -fp

data/.travis.yml

@@ -1,33 +0,0 @@
-dist: bionic
-language: ruby
-bundler_args: --without development
-cache: bundler
-before_install:
-  - gem install bundler
-before_script:
-  - "./bin/ci/install_on_debian.sh"
-  - until sudo lsof -i:5672; do echo "Waiting for RabbitMQ to start..."; sleep 1; done
-  - "./bin/ci/before_build.sh"
-script: "bundle exec rake integration_without_recovery"
-rvm:
-  - ruby-head
-  - "2.7.1"
-  - "2.6.6"
-  - "2.5.8"
-  - "2.4.10"
-  - "2.3.8"
-notifications:
-  email: michael@rabbitmq.com
-services:
-  - rabbitmq
-branches:
-  only:
-    - master
-    - 2.14.x-stable
-    - 2.13.x-stable
-env:
-  - CI=true
-matrix:
-  allow_failures:
-    rvm:
-      - ruby-head

data/.yardopts

@@ -1,8 +0,0 @@
---no-private
---protected
---markup="markdown" lib/**/*.rb
---main README.md
---hide-tag todo
--
-LICENSE
-ChangeLog.md

data/CONTRIBUTING.md

@@ -1,132 +0,0 @@
-## Overview
-
-This project **does not** use GitHub issues for questions, investigations, discussions, and so on.
-Issues are appropriate for something specific enough for a maintainer or contributor to work on:
-
- * There should be enough information to reproduce the behavior observed in a reasonable amount of time
- * It should be reasonably clear why the behavior should be changed and why this cannot or should not be addressed
-   in application code, a separate library and so on
-
- All issues that do not satisfy the above properties belong to the [Ruby RabbitMQ clients mailing list](http://groups.google.com/forum/#!forum/ruby-amqp). Pull request that do not satisfy them have a high chance
- of being closed.
-
-## Submitting a Pull Request
-
-Please read the sections below to get an idea about how to run Bunny test suites first. Successfully
-running all tests, at least with `CI` environment variable exported to `true`, is an important
-first step for any contributor.
-
-Once you have a passing test suite, create a branch and make your changes on it.
-When you are done with your changes and all
-tests pass, write a [good, detailed commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) submit a pull request on GitHub.
-
-## Pre-requisites
-
-The project uses Bundler for dependency management and requires RabbitMQ `3.5+` to be running
-locally with the `rabbitmq-management` and `rabbitmq_consistent_hash_exchange` plugins enabled.
-
-### Running the Specs
-
-The specs require RabbitMQ to be running locally with a specific set of virtual hosts
-and users. RabbitMQ can be provisioned and started any way that's convenient to you
-as long as it has a suitable TLS keys configuration and management plugin enabled.
-Make sure you have a recent version of RabbitMQ (> `3.7.10`).
-
-The test suite can either use a locally available RabbitMQ node ([generic binary builds](http://www.rabbitmq.com/install-generic-unix.html)
-are an option that works well) or by running a RabbitMQ server in a Docker container.
-
-### Using a locally installed RabbitMQ node
-
-It is possible to start a local RabbitMQ node from the repository root. It is not necessarily
-optimal but can be a good starting point but is a useful example:
-
-```
-RABBITMQ_NODENAME=bunny RABBITMQ_CONFIG_FILE=./spec/config/rabbitmq.conf RABBITMQ_ENABLED_PLUGINS_FILE=./spec/config/enabled_plugins rabbitmq-server
-```
-
-The specs need the RabbitMQ management plugin to be enabled and include TLS connectivity tests,
-so the node must be configured to use a [certificate and key pair](http://www.rabbitmq.com/ssl.html#certificates-and-keys).
-The config and enabled plugin files in the spec/config directory take care of that
-but certificates must be provisioned locally. By default there's a set of CA, server, and client certificates pre-generated at `spec/tls`.
-
-The `BUNNY_CERTIFICATE_DIR` environment variable can be used to a directory containing a CA certificate
-and a certificate/key pair to be used by the server. The directory can be generated using
-[tls-gen](https://github.com/michaelklishin/tls-gen)'s basic profile. This option is recommended.
-
-`BUNNY_RABBITMQ_HOSTNAME` can be used to override the expected server hostname for [peer verification](http://www.rabbitmq.com/ssl.html#peer-verification) in the TLS test suite:
-
-```
-BUNNY_CERTIFICATE_DIR="/path/to/tls-gen/basic/result" BUNNY_RABBITMQ_HOSTNAME="mayflower" bundle exec rspec
-
-```
-
-Certificates can be generated with [tls-gen](https://github.com/michaelklishin/tls-gen)'s basic profile.
-In that case they include a Subject Alternative Name of `localhost` for improved portability.
-
-
-### Node Setup
-
-There is also a script that preconfigured the node for Bunny tests. It is sufficient to run
-it once but if RabbitMQ is reset it has to be executed again:
-
-```
-RABBITMQ_NODENAME=bunny ./bin/ci/before_build
-```
-
-The script uses `rabbitmqctl` and `rabbitmq-plugins`
-to set up RabbitMQ in a way that Bunny test suites expect. Two environment variables,
-`RABBITMQCTL` and `RABBITMQ_PLUGINS`, are available to control what `rabbitmqctl` and
-`rabbitmq-plugins` commands will be used. By default they are taken from `PATH`
-and prefixed with `sudo`.
-
-And then run the core integration suite:
-
-```
-RABBITMQ_NODENAME=bunny CI=true rspec
-```
-
-#### Running a RabbitMQ server in a Docker container
-
-First off you have to [install Docker Compose](https://docker.github.io/compose/install/) (and by proxy Docker).
-Version >= 1.6.0+ is required for compose version 2 syntax.
-
-After those have been installed (and the `docker-compose` command is available on your command line path), run
-
-```
-docker-compose build && docker-compose run --service-ports rabbitmq
-```
-
-The first time you do this, it will take some time, since it has to download everything it needs
-to build the Docker image.
-
-The RabbitMQ server will run in the foreground in the terminal where you started it. You can stop
-it by pressing CTRL+C. If you want to run it in the background, pass `-d` to `docker-compose`.
-
-### Toxiproxy
-
-If Toxiproxy is running locally on standard ports or started via Docker:
-
-```
-docker-compose run --service-ports toxiproxy
-```
-
-then Bunny will run additional resiliency tests.
-
-### Running Test Suites
-
-Prior to running the tests, configure the RabbitMQ permissions by running `./bin/ci/before_build`
-if you have RabbitMQ locally installed, if you are running RabbitMQ via Docker as above this step
-is not required as the setup is baked in.
-
-Make sure you have those two installed and then run integration tests:
-
-    bundle install
-    rake integration
-
-It is possible to run all tests:
-
-    bundle exec rspec
-
-It is possible to run only integration and regression tests but exclude unit and stress tests:
-
-    CI=true bundle exec rspec spec/higher_level_api/ spec/lower_level_api spec/issues spec/higher_level_api/integration/connection_recovery_spec.rb