sidekiq-unique-jobs 6.0.0 → 6.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 33a903bdf609e340a2a99f7e18d6b1e4d39e8ede054299a951c8edba2c3a547a
-  data.tar.gz: 44d5c6a919d5dc5769c68ea485091a761c8643e7c69a23e35daf6d8ebb9b7ec1
+  metadata.gz: 43b75e11e1343bf44faec8dec56f4c0356d6bec4549034b2197dd0624eef3fe5
+  data.tar.gz: 7e6cb6380f3c6544170d699fdd6296726e236761e916921b8a541e025b527e50
 SHA512:
-  metadata.gz: d0038e130e631ace167a39436386e0dccc05991f51c7c7779193e90bb7f6fac3d91ffe15586559fd6543fda5ca9062df82943ecf315d81f8f099975df7b50fc6
-  data.tar.gz: 3c3c91017041567342ba3cd1d89fd0d09d2a6b7b985f16357f73d39d7b00a133057b59d74994c9429e9539105b39934aaf966e4401ee5d74da12748122ba3021
+  metadata.gz: 02fa7a131157f9aefc859a841571a942c0af8de90accc6fcfc38e9da39e2fa4f88a9cdf1fc0505d9f5869989c29dd5da8299282491c01b1a17302f59212e44ad
+  data.tar.gz: acca8c9d924c8158f8dba0748808b690106c5f212f2a899e7d4a2286bbf006d9f52880c33d6a89f9463287d172d0e61ccddb057bcfe3e3d18b3e4054554754fd

data/README.md

@@ -29,6 +29,7 @@
   * [Finer Control over Uniqueness](#finer-control-over-uniqueness)
   * [After Unlock Callback](#after-unlock-callback)
   * [Logging](#logging)
+  * [Cleanup Dead Locks](#cleanup-dead-locks)
 * [Debugging](#debugging)
   * [Sidekiq Web](#sidekiq-web)
     * [Show Unique Digests](#show-unique-digests)
@@ -353,6 +354,29 @@ class UniqueJobWithFilterMethod
 end
 ```
 
+### Cleanup Dead Locks
+
+For sidekiq versions before 5.1 a `sidekiq_retries_exhausted` block is required per worker class.
+
+```ruby
+class MyWorker
+  sidekiq_retries_exhausted do |msg, _ex|
+    SidekiqUniqueJobs::Digests.delete_by(digest: msg['unique_digest']) if msg['unique_digest']
+  end
+end
+```
+
+Starting in v5.1, Sidekiq can also fire a global callback when a job dies:
+
+```ruby
+# this goes in your initializer
+Sidekiq.configure_server do |config|
+  config.death_handlers << ->(job, _ex) do
+    SidekiqUniqueJobs::Digests.delete_by(digest: job['unique_digest']) if job['unique_digest']
+  end
+end
+```
+
 ## Debugging
 
 There are two ways to display and remove keys regarding uniqueness. The console way and the command line way.
@@ -363,7 +387,7 @@ To use the web extension you need to require it in your routes.
 
 ```ruby
 # app/config/routes.rb
-require 'sidekiq-unique-jobs/web'
+require 'sidekiq_unique_jobs/web'
 mount Sidekiq::Web, at: '/sidekiq'
 ```
 

data/lib/sidekiq_unique_jobs/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module SidekiqUniqueJobs
-  VERSION = '6.0.0'
+  VERSION = '6.0.1'
 end

data/lib/sidekiq_unique_jobs/web/helpers.rb

@@ -5,10 +5,6 @@ module SidekiqUniqueJobs
     module Helpers
       VIEW_PATH = File.expand_path('../web/views', __dir__)
 
-      def filtering(pattern, count)
-        SidekiqUniqueJobs::Util.keys(pattern, count)
-      end
-
       def unique_template(name)
         File.open(File.join(VIEW_PATH, "#{name}.erb")).read
       end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: sidekiq-unique-jobs
 version: !ruby/object:Gem::Version
-  version: 6.0.0
+  version: 6.0.1
 platform: ruby
 authors:
 - Mikael Henriksson
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-07-27 00:00:00.000000000 Z
+date: 2018-07-31 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: concurrent-ruby