action_subscriber 4.2.3.pre → 4.2.3.pre2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 45ae69689291e9fcda93dc4b92648b224add38d0
-  data.tar.gz: 01b00b6b55bd1a4c4995021c6e4843b0707ee756
+  metadata.gz: 18d1da57332fc7ae0f0c061d57e1d57648618fc6
+  data.tar.gz: 35665b898dea262b08f10851cbd369c934bdc2ab
 SHA512:
-  metadata.gz: 41e3a0fbac6c65b5c7b04abe3f44dcd18132ab2d8cbe24583958c22805a9b285efaf4cc3a60c90d1de2c86559e06a2e33340562a539165f065719a9251f2069f
-  data.tar.gz: 34bba997f2819957baa13da7ac0edf956dd66fc0477ad388fcb43fe99762eeb96d0dd41e8afd08a92058e56c45d3c11e4e9cc92a08841c1481b04218425e3aca
+  metadata.gz: 915323ad15ffaeeddb669866a9b39a74154520b18efe3ed43e66a85e4ac7c333a9435bfd646bfea0b5eabc80a47c129dbfb61ee73574cdf68340b5b29ef9196e
+  data.tar.gz: b23741a03018c01ad19c449321944a43f56a5ba6c66084f546d20cb8ab2848a5004e8cf3e729695d142df67a97f6d77ca1948243260c00033e37caf015fe3420

data/README.md

@@ -163,10 +163,10 @@ Rabbit is told to expect message acknowledgements, but sending the acknowledgeme
 We send the acknowledgement right after calling your subscriber.
 If an error is raised your message will be retried on a sent back to rabbitmq and retried on an exponential backoff schedule.
 
-### retry
+### redeliver
 
-A message can be sent to "retry" with `::ActionSubscriber::MessageRetry.redeliver_message_with_backoff` or the DSL method `retry` and optionally
-takes a "backoff schedule" which is a hash of backoff milliseconds for each retry, the default:
+A message can be sent to "redeliver" with `::ActionSubscriber::MessageRetry.redeliver_message_with_backoff` or the DSL method `redeliver` and optionally
+takes a "backoff schedule" which is a hash of backoff milliseconds for each redeliver, the default:
 
 ```ruby
   SCHEDULE = {
@@ -184,7 +184,7 @@ takes a "backoff schedule" which is a hash of backoff milliseconds for each retr
 
 when the schedule "returns" `nil` the message will not be retried
 
-> Warning: If you use `retry` you need to handle reject/acknowledge according how errors are handled; if an error is caught and the
+> Warning: If you use `redeliver` you need to handle reject/acknowledge according how errors are handled; if an error is caught and the
 > ack/reject is already done then you may duplicate the message in `at_least_once!` mode
 
 Testing

data/lib/action_subscriber/base.rb

@@ -60,7 +60,7 @@ module ActionSubscriber
       env.reject
     end
 
-    def retry(backoff_schedule = ::ActionSubscriber::MessageRetry::SCHEDULE)
+    def redeliver(backoff_schedule = ::ActionSubscriber::MessageRetry::SCHEDULE)
       ::ActionSubscriber::MessageRetry::redeliver_message_with_backoff(env, backoff_schedule)
     end
   end

data/lib/action_subscriber/version.rb

@@ -1,3 +1,3 @@
 module ActionSubscriber
-  VERSION = "4.2.3.pre"
+  VERSION = "4.2.3.pre2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: action_subscriber
 version: !ruby/object:Gem::Version
-  version: 4.2.3.pre
+  version: 4.2.3.pre2
 platform: ruby
 authors:
 - Brian Stien