expeditor 0.7.0 → 0.7.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: '0295f51ed41290a443f84e29704254cb92773e54'
-  data.tar.gz: d4525b17a023e7aed723ed8b5d40cc7842d14d6a
+SHA256:
+  metadata.gz: a260bbe17a9db35fafb969bd979d87cfc74c7f9b23932567b7f6dd3f378c2a98
+  data.tar.gz: 044615f3a206c7948f60e6fbaeb9f9c055ac1320e016c165123ddf58ec4ff5fc
 SHA512:
-  metadata.gz: 5c07b956a48818d56ae0edfc9f282c21ffa7e90ba3432b91d3abba8a095456281cdc6ce22a8a887e72c096b94525a12fa9ddf72929761644df05492f70d02ea7
-  data.tar.gz: 047f91f6875c87e815796801f5a67e49b4d1bcb1821a7c36c8e4835ae6c1cd0a0cfc7992d69a079b1afeb6ec9ad8e6ddf4dcbbfb1b06bbfe97476bc42dcafcf3
+  metadata.gz: 76dbc470fe709056315dda8d7cdbf63bd8b0ada4a62f735cbb9a7ff87c70b80aff42cd6775036a0b82a23652730d06bb878335444ce69db31f6544dd5516f109
+  data.tar.gz: 39e8389e033b6a2e7d2c4af73105380e878d6426002d8644253e63a3c2315de1d9730b69f9d17c306aa2d31b883e585b0968ba151b52e46ec3c12421ddffbc29

data/.travis.yml

@@ -1,11 +1,12 @@
 language: ruby
-sudo: false
 cache: bundler
 rvm:
   - 2.1.10
-  - 2.2.6
-  - 2.3.3
-  - 2.4.0
+  - 2.2.10
+  - 2.3.8
+  - 2.4.6
+  - 2.5.5
+  - 2.6.2
   - ruby-head
 matrix:
   allow_failures:

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 0.7.1
+- Fix Ruby 2 style keyword arguments to support Ruby 3 [#45](https://github.com/cookpad/expeditor/pull/27)
+
 ## 0.7.0
 - Add `gem 'concurrent-ruby-ext'` to your Gemfile if you want to use that gem.
     - We should not depend on this in a gemspec [#27](https://github.com/cookpad/expeditor/pull/27)

data/README.md

@@ -137,18 +137,14 @@ The circuit breaker needs a service metrics (success, failure, timeout, ...) to
 Expeditor's circuit breaker has a few configuration for how it collects service metrics and how it opens the circuit.
 
 For service metrics, Expeditor collects them with the given time window.
-The metrics is guradually collected by breaking given time window into some peice of short time windows and resetting previous metrics when passing each short time window.
-
-`non_break_count` is used to ignore requests to the service which is not frequentlly requested. Configure this value considering your estimated "requests per period to the service".
-For example, when `period = 10` and `non_break_count = 20` and the requests do not occur more than 20 per 10 seconds, the circuit never opens because Expeditor ignores that "small number of requests".
-If you don't ignore the failures in that case, set `non_break_count` to smaller value than `20`.
+The metrics is gradually collected by breaking given time window into some peice of short time windows and resetting previous metrics when passing each short time window.
 
 ```ruby
 service = Expeditor::Service.new(
-  threshold: 0.5,     # If the failure rate is more than or equal to threshold, the circuit will be opened.
-  sleep: 1,           # If once the circuit is opened, the circuit is still open until sleep time seconds is passed even though failure rate is less than threshold.
-  non_break_count: 20 # If the total count of metrics is not more than non_break_count, the circuit is not opened even though failure rate is more than threshold.
-  period: 10,         # Time window of collecting metrics (in seconds).
+  threshold: 0.5,      # If the failure rate is more than or equal to threshold, the circuit will be opened.
+  sleep: 1,            # If once the circuit is opened, the circuit is still open until sleep time seconds is passed even though failure rate is less than threshold.
+  non_break_count: 20, # If the total count of metrics is not more than non_break_count, the circuit is not opened even though failure rate is more than threshold.
+  period: 10,          # Time window of collecting metrics (in seconds).
 )
 
 command = Expeditor::Command.new(service: service) do
@@ -156,6 +152,17 @@ command = Expeditor::Command.new(service: service) do
 end
 ```
 
+`non_break_count` is used to ignore requests to the service which is not frequentlly requested. Configure this value considering your estimated "requests per period to the service".
+For example, when `period = 10` and `non_break_count = 20` and the requests do not occur more than 20 per 10 seconds, the circuit never opens because Expeditor ignores that "small number of requests".
+If you don't ignore the failures in that case, set `non_break_count` to smaller value than `20`.
+
+The default values are:
+
+- threshold: 0.5
+- sleep: 1
+- non_break_count: 20
+- period: 10
+
 ### synchronous execution
 
 Use `current_thread` option of `#start`, command executes synchronous on current thread.

data/lib/expeditor/service.rb

@@ -108,7 +108,7 @@ module Expeditor
 
     def reset_status!
       @mutex.synchronize do
-        @rolling_number = Expeditor::RollingNumber.new(@rolling_number_opts)
+        @rolling_number = Expeditor::RollingNumber.new(**@rolling_number_opts)
         @breaking = false
         @break_start = nil
       end

data/lib/expeditor/version.rb

@@ -1,3 +1,3 @@
 module Expeditor
-  VERSION = "0.7.0"
+  VERSION = "0.7.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: expeditor
 version: !ruby/object:Gem::Version
-  version: 0.7.0
+  version: 0.7.1
 platform: ruby
 authors:
 - shohei-yasutake
-autorequire: 
+autorequire:
 bindir: exe
 cert_chain: []
-date: 2017-05-08 00:00:00.000000000 Z
+date: 2022-04-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: concurrent-ruby
@@ -144,7 +144,7 @@ homepage: https://github.com/cookpad/expeditor
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -159,9 +159,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.6.11
-signing_key: 
+rubygems_version: 3.3.8
+signing_key:
 specification_version: 4
 summary: Expeditor provides asynchronous execution and fault tolerance for microservices
 test_files: []