que-locks 0.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: bd840db1d95e1dc04b8efae206dfd9600423999972af509b37266187d53dd535
+  data.tar.gz: 3505096ad35333c9b2fb00397e8c3ba5266097f8d180e9a0fb76d5ba9b12e16a
+SHA512:
+  metadata.gz: 9aaee5425dc4819614715e3364f608d03bb2985b1a05420acb0fcc7ef500a63398ddfa19137dc6762a9747346cd72bb27747b27cfaa729fc2f56b93e4d833e3f
+  data.tar.gz: adb3ad01415719ad0845ff3141f3e102a2edde81b2ff9fa68cfe3fac68d41c6c6fdebf76e447e3112a9639c57244baa5f48938903dc1b7c3b8b0405862458935

data/.gitignore

@@ -0,0 +1,10 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+.byebug_history
+.vscode

data/.rubocop.yml

@@ -0,0 +1,33 @@
+AllCops:
+  Exclude:
+    - "vendor/**/*"
+    - "node_modules/**/*"
+    - "test/scratch/**/*"
+  TargetRubyVersion: 2.6
+
+require:
+  - rubocop-performance
+
+Security:
+  Enabled: true
+
+Performance:
+  Enabled: true
+
+Layout:
+  Enabled: false
+
+Metrics:
+  Enabled: false
+
+Style:
+  Enabled: false
+
+Naming/MemoizedInstanceVariableName:
+  Enabled: false
+
+Lint/AmbiguousBlockAssociation:
+  Enabled: false
+
+Bundler/OrderedGems:
+  Enabled: false

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at harry.brundage@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,22 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+gem 'que', '1.0.0.beta3', github: 'chanks/que'
+
+# Specify your gem's dependencies in que-locks.gemspec
+gemspec
+
+group :development do
+  gem 'activerecord'
+  gem 'pg'
+  gem 'database_cleaner'
+
+  gem 'minitest'
+
+  gem 'byebug'
+  gem 'rufo'
+  gem 'rubocop'
+  gem 'rubocop-performance'
+end
+

data/Gemfile.lock

@@ -0,0 +1,80 @@
+GIT
+  remote: https://github.com/chanks/que
+  revision: 53106609b24d7e8bc231ae3883f69dca8c989d9d
+  specs:
+    que (1.0.0.beta3)
+
+PATH
+  remote: .
+  specs:
+    que-locks (0.2.0)
+      neatjson
+      que (~> 1.0.0.beta3)
+      xxhash
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activemodel (6.0.1)
+      activesupport (= 6.0.1)
+    activerecord (6.0.1)
+      activemodel (= 6.0.1)
+      activesupport (= 6.0.1)
+    activesupport (6.0.1)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 0.7, < 2)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+      zeitwerk (~> 2.2)
+    ast (2.4.0)
+    byebug (11.0.1)
+    concurrent-ruby (1.1.5)
+    database_cleaner (1.7.0)
+    i18n (1.7.0)
+      concurrent-ruby (~> 1.0)
+    jaro_winkler (1.5.4)
+    minitest (5.13.0)
+    neatjson (0.9)
+    parallel (1.19.1)
+    parser (2.6.5.0)
+      ast (~> 2.4.0)
+    pg (1.1.4)
+    rainbow (3.0.0)
+    rake (10.5.0)
+    rubocop (0.76.0)
+      jaro_winkler (~> 1.5.1)
+      parallel (~> 1.10)
+      parser (>= 2.6)
+      rainbow (>= 2.2.2, < 4.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 1.7)
+    rubocop-performance (1.5.1)
+      rubocop (>= 0.71.0)
+    ruby-progressbar (1.10.1)
+    rufo (0.7.0)
+    thread_safe (0.3.6)
+    tzinfo (1.2.5)
+      thread_safe (~> 0.1)
+    unicode-display_width (1.6.0)
+    xxhash (0.4.0)
+    zeitwerk (2.2.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activerecord
+  bundler (~> 1.17)
+  byebug
+  database_cleaner
+  minitest
+  pg
+  que (= 1.0.0.beta3)!
+  que-locks!
+  rake (~> 10.0)
+  rubocop
+  rubocop-performance
+  rufo
+
+BUNDLED WITH
+   1.17.2

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2019 Harry Brundage
+
+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/README.md

@@ -0,0 +1,99 @@
+# Que::Locks
+
+`que-locks` adds an opt-in feature to `Que::Jobs` allowing jobs to specify that exactly one instance of a job should be executing at once. This is useful for jobs that are doing something important that should only ever happen one at a time, like processing a payment for a given user, or super expensive jobs that could cause thundering herd problems if enqueued all at the same time.
+
+`que-locks` uses Postgres' advisory locks in a similar manner as que `0.x` did to provide scalable and automatically cleaned up locking around job execution. `que-locks` provides slightly better atomicity guarantees compared to the locking functionality of Redis based job queues for the same reasons `que` can as well. Because locks are taken and released using the same database connection that the `que` worker uses to pull jobs, the transactional semantics apply just the same where locks are automatically released if the connection fails, unlike the multistep Redis logic that requires complicated crash cleanup.
+
+This is also sometimes called "unique jobs", "job concurrency limiting", and "exclusive jobs".
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'que-locks'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install que-locks
+
+## Usage
+
+After requiring the gem, set the `exclusive_execution_lock` property on your job class:
+
+```ruby
+class SomeJob < Que::Job
+  self.exclusive_execution_lock = true
+
+  def run(user_id:, bar:)
+    # useful stuff
+  end
+end
+```
+
+That's it!
+
+#### Checking lock status
+
+Occasionally, code enqueuing a job might want to check if the job is already running and do something different if it is, like display a message to the user or log the skipped execution. `que-locks` supports some basic job lock introspection like so:
+
+```ruby
+SomeJobClass.exclusive_execution_lock  #=> returns true if the job is indeed using que-locks
+
+SomeJobClass.lock_available?(user_id: 1)  #=> returns true if no job is currently enqueued with these arguments or running right now holding the lock
+```
+
+Note that checking the lock's availability reports on the current state of the locks, but that state might change in between when the check is made and if/when the job is enqueued with the same arguments. Put differently, the `#lock_available?` method is advisory to user code, and doesn't actaully reserve the lock or execute a compare-and-swap operation. It's safe for multiple processes to race to enqueue a job after checking to see that the lock is available, as only one will still be executed, but they may both report that the lock was available before enqueuing.
+
+## Semantics
+
+`que-locks` guarantees that the maximum number of instances given job class executing with a given set of arguments will be one. This means that:
+
+- two of the same job class each pushed with different arguments can both execute simultaneously
+- if the job takes no arguments, there can only ever be one executing globally
+- two of the same job class each pushed with the same arguments may result in one or two executions, but they won't ever be simultaneous
+
+In some instances, multiple jobs with the same arguments can be enqueued and sit in the queue simultaneously. Despite this the semantics above will remain in tact: only one job will execute at once. The first one worked will get the lock and the second one worked will skip execution if the first job is still executing. `que-locks` tries to avoid extraneous job pushes by checking to see if the lock for a job is available at enqueue time, and skipping enqueue if so. This preemptive lock check helps keeps queues small in the event that a huge number of identical jobs are pushed at once.
+
+`que-locks` uses a sorted JSON serialized version of the arguments to compute lock keys, so it's important that arguments that should be considered identical JSON serialize using `Que.serialize_json` to the exact same string.
+
+`que-locks` adds no overhead to jobs that don't use locking, adds one more SQL query to check an advisory lock (which is only memory access) to enqueuing jobs, and adds two more SQL queries to lock and unlock to job execution.
+
+## Missing features
+
+- Configurable preemptive lock checking at enqueue time
+- Selective argument comparison for lock key computation
+- maybe a `que-web` integration to expose lock info
+
+If you wish for any of this stuff, feel free to open a PR, contributions are always welcome!!
+
+## Non features
+
+- Locking to a limited concurrency greater than 1. If you want a lock that several different jobs can take out, a good option is to use Que's multiple queue support and run a limited number of workers working a certain queue so the concurrency is limited by the available worker slots.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/hornairs/que-locks. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Que::Locks project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/hornairs/que-locks/blob/master/CODE_OF_CONDUCT.md).
+
+```
+
+```

data/Rakefile

@@ -0,0 +1,10 @@
+require "bundler/gem_tasks"
+require "rake/testtask"
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList["test/**/test_*.rb"]
+end
+
+task :default => :test

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "que/locks"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/lint

@@ -0,0 +1,4 @@
+#!/usr/bin/env bash
+set -ex
+bundle exec rufo --check lib test
+bundle exec rubocop

data/bin/lintfix

@@ -0,0 +1,4 @@
+#!/usr/bin/env bash
+set -x
+bundle exec rufo lib test
+bundle exec rubocop -a

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/que/locks.rb

@@ -0,0 +1,11 @@
+require "que/locks/version"
+require "que/locks/execution_lock"
+require "que/locks/json_extensions"
+require "que/locks/job_extensions"
+require "que/locks/lock_middleware"
+
+module Que
+  module Locks
+    class Error < StandardError; end
+  end
+end

data/lib/que/locks/execution_lock.rb

@@ -0,0 +1,54 @@
+require "xxhash"
+
+module Que
+  SQL[:args_already_enqueued] = %{
+    SELECT COUNT(*) FROM public.que_jobs WHERE job_class = $1 AND args = $2 AND finished_at IS NULL AND expired_at IS NULL;
+  }
+
+  SQL[:try_aquire_execution_lock] = %{
+    SELECT pg_try_advisory_lock(42, $1) AS locked
+  }
+
+  SQL[:release_execution_lock] = %{
+    SELECT pg_advisory_unlock(42, $1)
+  }
+
+  module Locks::ExecutionLock
+    class << self
+      def already_enqueued_job_wanting_lock?(klass, args)
+        args_string = Que.serialize_json(args)
+        values = Que.execute(:args_already_enqueued, [klass.name, args_string]).first
+        values[:count] != 0
+      end
+
+      def can_aquire?(klass, args)
+        can_aquire_key?(lock_key(klass, args))
+      end
+
+      def can_aquire_key?(key)
+        result = false
+        begin
+          result = aquire!(key)
+        ensure
+          if result
+            release!(key)
+          end
+        end
+        result
+      end
+
+      def lock_key(klass, args)
+        XXhash.xxh32(klass.name + ":" + Que.serialize_json(args), 42) / 2
+      end
+
+      def aquire!(key)
+        result = Que.execute(:try_aquire_execution_lock, [key]).first
+        result[:locked]
+      end
+
+      def release!(key)
+        Que.execute(:release_execution_lock, [key])
+      end
+    end
+  end
+end

data/lib/que/locks/job_extensions.rb

@@ -0,0 +1,29 @@
+module Que::Locks
+  module JobExtensions
+    attr_accessor :exclusive_execution_lock
+
+    def lock_available?(*args, queue: nil, priority: nil, run_at: nil, job_class: nil, tags: nil, **arg_opts) # rubocop:disable Lint/UnusedMethodArgument
+      args << arg_opts if arg_opts.any?
+      return true unless self.exclusive_execution_lock
+      return false if Que::Locks::ExecutionLock.already_enqueued_job_wanting_lock?(self, args)
+      return Que::Locks::ExecutionLock.can_aquire?(self, args)
+    end
+
+    def enqueue(*args, queue: nil, priority: nil, run_at: nil, job_class: nil, tags: nil, **arg_opts)
+      if self.exclusive_execution_lock
+        args_list = args.clone
+        args_list << arg_opts if arg_opts.any?
+
+        if Que::Locks::ExecutionLock.already_enqueued_job_wanting_lock?(self, args_list)
+          Que.log(level: :info, event: :skipped_enqueue_due_to_preemptive_lock_check, args: args_list)
+        else
+          super
+        end
+      else
+        super
+      end
+    end
+  end
+end
+
+Que::Job.singleton_class.send(:prepend, Que::Locks::JobExtensions)

data/lib/que/locks/json_extensions.rb

@@ -0,0 +1,11 @@
+require "neatjson"
+
+# For comparing job args, the JSON serialization of them is used
+# This patches Que to use a stable json serialization that is independent of the insertion order of keys into hash arguments
+module Que::Locks::JSONExtensions
+  def serialize_json(object)
+    JSON.neat_generate(object, sort: true)
+  end
+end
+
+Que.singleton_class.send(:prepend, Que::Locks::JSONExtensions)

data/lib/que/locks/lock_middleware.rb

@@ -0,0 +1,23 @@
+module Que::Locks
+  LockMiddleware = ->(job, &block) {
+    if job.class.exclusive_execution_lock
+      args = job.que_attrs[:args]
+      lock_key = ExecutionLock.lock_key(job.class, args)
+      if ExecutionLock.aquire!(lock_key)
+        begin
+          block.call
+        ensure
+          ExecutionLock.release!(lock_key)
+        end
+      else
+        Que.log(level: :info, event: :skipped_execution_due_to_lock, args: args, job_class: job.class.name)
+      end
+    else
+      block.call
+    end
+
+    nil
+  }
+end
+
+Que.job_middleware.push(Que::Locks::LockMiddleware)

data/lib/que/locks/version.rb

@@ -0,0 +1,5 @@
+module Que
+  module Locks
+    VERSION = "0.2.0"
+  end
+end

data/que-locks.gemspec

@@ -0,0 +1,31 @@
+
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "que/locks/version"
+
+Gem::Specification.new do |spec|
+  spec.name = "que-locks"
+  spec.version = Que::Locks::VERSION
+  spec.authors = ["Harry Brundage"]
+  spec.email = ["harry.brundage@gmail.com"]
+
+  spec.summary = %q{Job locking for que jobs such that only one can be in the queue or executing at once.}
+  spec.homepage = "https://github.com/superpro-inc/que-locks"
+  spec.license = "MIT"
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files = Dir.chdir(File.expand_path("..", __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features|.github)/}) }
+  end
+  spec.bindir = "exe"
+  spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.17"
+  spec.add_development_dependency "rake", "~> 10.0"
+
+  spec.add_dependency "neatjson"
+  spec.add_dependency "que", "~> 1.0.0.beta3"
+  spec.add_dependency "xxhash"
+end

metadata

@@ -0,0 +1,133 @@
+--- !ruby/object:Gem::Specification
+name: que-locks
+version: !ruby/object:Gem::Version
+  version: 0.2.0
+platform: ruby
+authors:
+- Harry Brundage
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2019-11-28 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.17'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.17'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+- !ruby/object:Gem::Dependency
+  name: neatjson
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: que
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.0.0.beta3
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.0.0.beta3
+- !ruby/object:Gem::Dependency
+  name: xxhash
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description: 
+email:
+- harry.brundage@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".rubocop.yml"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/lint
+- bin/lintfix
+- bin/setup
+- lib/que/locks.rb
+- lib/que/locks/execution_lock.rb
+- lib/que/locks/job_extensions.rb
+- lib/que/locks/json_extensions.rb
+- lib/que/locks/lock_middleware.rb
+- lib/que/locks/version.rb
+- que-locks.gemspec
+homepage: https://github.com/superpro-inc/que-locks
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.0.3
+signing_key: 
+specification_version: 4
+summary: Job locking for que jobs such that only one can be in the queue or executing
+  at once.
+test_files: []